I have some thoughts for you as someone who's done this before. I used to run a file hosting site called MediaCrush with a buddy of mine. It was moderately successful, but we ended up shutting it down. I later switched to a file host called pomf.se, which eventually was shut down as well. I wrote a blog post that sums up my thoughts on public file hosting:
The problem is growth. It will quickly get too expensive and you will not have nearly enough revenue to support it. I guarantee you it will happen.
Currently I run a file hosting service with controlled growth. Accounts are not available to the public - you have to apply for one, and I approve them conservatively (130 approved, 137 rejected users as of writing). All users are also expected to donate. I think all new file hosting sites should take link rot seriously and if they don't it's a net negative on the internet. I hate that if I look at a forum post written >5 years ago, odds are all of the images will be broken.
If anyone wants an account on my website, I might be inclined to approve a few today: https://sr.ht
I feel like WeTransfer has got this right. They have wonderful full page ads and are monetizing by selling premium accounts to corporates, which have the ability to change the ads to fit their branding. https://wetransfer.com
WeTransfers user experience is great. I'm not sure the economics are ultimately going to work for them; the funding [1] gives them some runway, but they are already transitioning to more of a cloud storage provider. Simple utilities usually add bloat to drive value for premium plans. [2] In my experience, as they approach Google Drive and Dropbox in features, the product will bloat and become less functional and useful.
I also ran some file/image hosting sites in early 2000s and another reason not to do them is that people post the most vile content and moderating can cause ptsd.
This is the second, possibly third, time I've seen you link to your post about public file hosting - and this is the second, possibly third, time I'll agree entirely.
There are tons of pomf.se clones - many that have been going on for years as well. The important part for many of these hosts is that (a) enough people donate to keep it online and/or (b) the community remains small enough to remain affordable for the dev. Personally I use a combination of safe.moe and mixtape.moe.
Often times I've noticed these are "labor of love" projects where a dev can work on learning how to (a) keep a server running and (b) upgrade services without any/significant downtime, etc. Standard DevOps things. The monthly cost to these sort of people is seen as a "learning cost" in a real environment where they have hundreds of, if not thousands or more, users depending on them to not mess things up.
>I hate that if I look at a forum post written >5 years ago, odds are all of the images will be broken.
Inactivity pruning is largely to blame for this, not just new websites going under. IIRC, even Imgur does pruning after 6 months of inactivity (no views) which is totally possible on niche technical forum posts.
I think that in the end, the way to really address these issues is with WebTorrent or a similar service. When you're online, you should be:
1. contributing your own bandwidth to the images you upload
2. contribute your own bandwidth to the images you look at.
If you look at an image, maybe you should be required to seed it twice over. If you upload your image, maybe you have to seed it at least 10 times for it to stay up past a certain deadline.
As a user of image websites and, well, websites in general, I'd gladly contribute my bandwidth to help the services run. Or even act as a mirror rather than a shared peer.
What do you think about that? It could lessen the load on the image host and help scale things. I just can't seen this happening if you embed an image directly unless you embed iframes or require users to go to the site itself.
Although the idea is great but I'm not comfortable with the legal implications of "seeding" the stuff I view. It might work in some legislations but I'd be putting myself in too much risk under my local law.
What if everyone "seeded" random content that others are browsing? Sort of like a Tor Relay for P2P traffic. Everyone assumes some small responsibility and yet could argue plausible deniability.
I'd question the assumption that all having web pages be immortal is a good thing. There is great value in letting natural processes erode items or things that don't get maintained.
Throughout history, we've learned to write down and preserve important stuff. Sometimes we've gotten it wrong or we create huge single points of failure (see, e.g., Library of Alexandria), but we should be careful in assuming that preserving everything is inherently better than the historical approach.
This was an interesting read and we will do our best to avoid this fate.
Right now we're focusing on patching bugs and providing a stable service, but in the future a premium service will be created which targets heavy users.
PS
You can change the status of the last active host in your list (Minus.com) to shut down as well.
I've been running a public file hosting site for 11 years, I've always treated it as a side project to use for playing with technology.
The primary reason it's still alive today is out of obligation to the URLs (2 million or so) that call it home. If you don't already find this fun and don't feel the same obligation, then you'll join the thousands of others littering the web with 404s.
Also, be aware that people will upload bad shit, and you can look forward to phone calls from the FBI and others.
The problem is one of capabilities; unrestricted image hosts delegate too much power to uploaders. An uploader should not be able to create a valid URL with any data under the hoster's domain.
In addition to what's been mentioned, another possibility is to force users to bring their own domains to the table when doing hosting; the user is free to host things from the service at their own domain, and the hoster's domains remain distinct and untainted.
"Currently I run a file hosting service with controlled growth."
Why do you do this ... that is, run a file hosting service for 130 people ? Is it a friends and family IT enabler sort of thing that you do to be nice ?
Or is there some kind of business here that I can't envision ?
Yep, it's a friends and family thing. Often friends of friends. Anyone who gets to know me a little bit can get an account. Since growth is controlled, costs are low. Since users are expected to donate, that completely stops being a concern.
The world is a smaller place than it seems. I've noticed this site having a measurable impact on the web around me, and lots of files that might have disappeared are sticking around now (23,946 of them, in fact).
On the profitability of image hosting websites - https://drewdevault.com/2014/10/10/The-profitability-of-onli...
I suggest you read it. In a nutshell: don't.
The problem is growth. It will quickly get too expensive and you will not have nearly enough revenue to support it. I guarantee you it will happen.
Currently I run a file hosting service with controlled growth. Accounts are not available to the public - you have to apply for one, and I approve them conservatively (130 approved, 137 rejected users as of writing). All users are also expected to donate. I think all new file hosting sites should take link rot seriously and if they don't it's a net negative on the internet. I hate that if I look at a forum post written >5 years ago, odds are all of the images will be broken.
If anyone wants an account on my website, I might be inclined to approve a few today: https://sr.ht