retention = min_age + (-max_age + min_age) * pow((file_size / max_size - 1), 3)
365 | \
197.5 | ----------..-------------------------------------------
30 | ....................
0 256 512
No. That way fill up his hard drive, break the server and ruin it for everybody. Don't be that guy.
I don't see what the correlation is between a user's file size and how long the user will need it to remain.
Generally people use these services to host a file for around the time it takes someone to check their e-mail/ticket/etc. to download the item -- hopefully within a day, usually a couple days, worst-case scenario a week.
The time-cutoff is based on human behavior.
Plus, it's too much mental overhead for a user to have to worry that each file uploaded lasts for a different amount of time.
The current policy of 25GB for seven days is very generous, but I fear it will prove unsustainable.
Files are sent peer to peer and are encrypted. The main downside is that the sender has to keep the browser tab open until the recipient receives the file.
Edit: nvm I found it
"Bashupload has no control over, and assumes no responsibility for, the content, privacy policies, or practices of any third party web sites or services. You further acknowledge and agree that Bashupload shall not be responsible or liable, directly or indirectly, for any damage or loss caused or alleged to be caused by or in connection with use of or reliance on any such content, goods or services available on or through any such web sites or services."
And how does one compare Nginx and curl, one is a webserver, the other a Swiss knife for mainly doing client side requests to various protocols, http/https being one of them.