davidkarolyi

Interesting you mention this. That was the first approach. The problem comes when you want to introduce missing features to S3. Like tokens, or file filtering.

No docs. In your dashboard there is a "Snippets" collection, which contains all information you need to use FILE0. It's kind of a code tutorial. If you find something fuzzy, let me know and I help you out.

Yes, it is using R2 and CF workers.

I disagree. Only an import statement is missing from both examples. Which parts is missing in your opinion?

Yes. No egress fees. It's built on top of R2. they don't charge for network transer, so FILE0 neither.

No! I believe if you look for S3 compatible storages you find much better options out there then FILE0. R2, Backbaze and others.

FILE0's mission is to keep things simple for the small guys.

100% legit concern. Obviously I can't sit here and say that my new crappy product is as stable as S3. But I can say that most parts are just a thin layer on top of R2. Obviously at the begining I expect bugs and disruption, but the product is simple enough to get it right quickly.

Good to hear! Initially I built it for myself without the intention to publish, but good to hear I'm not the only one has big-cloud provider fatigue.

This was my catch phrase for years, and today I learned I used it wrong all the time.

If you need granular control, you can use S3. If you need the cheapest option out there you can use Backblaze. If your application is bandwidth heavy, you can use R2.

If you're a busy indie hacker who just want to be up an running with file storage under 5 mins and forget the whole thing even exists, you can use FILE0.

S3 is stuffed with features for a reason. It's the backbone of the internet so it needs to cover 100% of the use cases and more.