Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: File0 – An easier way to manage files in serverless apps

file0.dev

Post reply on HN
Print view View original

1–10 of 158 posts

Show HN: File0 – An easier way to manage files in serverless apps

#1

Post by davidkarolyi »

Cmon... I just want to upload a file and make it public on the internet. Now you tell me I need to master bucket policies, ACL, CORS, multipart uploads, content headers, CDN, presigned URLs, and a bunch of other crap?

I can't be asked, so I built FILE0. It's for storing files but you don't need to complete an online course.

Show HN: File0 – An easier way to manage files in serverless apps
file0.dev

Re: Show HN: File0 – An easier way to manage files in serverless apps

#2

Post by immibis »

It suffers the usual effect as seen in eg. Wayland. You think the problem is simple and make a new protocol that's simple. Then you find complexity in the problem and solve it with complexity in the solution. Then your protocol becomes as complex as the one you're replacing. There are reasons S3 does all these things.

ACLs, for example? How do you control who can access a file you uploaded?

Also, it costs about 20 times as much as Backblaze B2.

Re: Show HN: File0 – An easier way to manage files in serverless apps

#3

Post by piterrro »

immibis wrote: post #2

It suffers the usual effect as seen in eg. Wayland. You think the problem is simple and make a new protocol that's simple. Then you find complexity in the problem and solve it with complexity in the solution. Then your protocol becomes as complex as the one you're replacing. There are reasons S3 does all these things. ACLs, for example? How do you control who can access a file you uploaded? Also, it costs about 20 ti…

I guess that's when you switch to a more robust solution. If all you want is to host a couple of gigs at most because you're just starting then you're optimizing for speed and simplicity.

Re: Show HN: File0 – An easier way to manage files in serverless apps

#4

Post by davidkarolyi »

immibis wrote: post #2

It suffers the usual effect as seen in eg. Wayland. You think the problem is simple and make a new protocol that's simple. Then you find complexity in the problem and solve it with complexity in the solution. Then your protocol becomes as complex as the one you're replacing. There are reasons S3 does all these things. ACLs, for example? How do you control who can access a file you uploaded? Also, it costs about 20 ti…

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.

Re: Show HN: File0 – An easier way to manage files in serverless apps

#9

Post by NeoTar »

jjgreen wrote: post #7
davidkarolyi wrote: post #6

Earlier quoted context omitted.

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

Reminiscent of Diane Morgan's Mandy -- "I'm at my lowest egg"

Interesting, since such plausible mishearing are often called ‘Eggcorns’ (https://en.m.wikipedia.org/wiki/Eggcorn)

Re: Show HN: File0 – An easier way to manage files in serverless apps

#10

Post by donatj »

I am old enough that I still remember people including myself being perplexed why s3 didn't ship with an FTP adapter. They FINALLY added the option in 2020, 14 years late.

I do think the storage "space" could use some disruption. I use s3 every day at work, and my general feeling is that the entire permission system is more complicated than 99% of apps actually need, to the point of being dangerous; I think the complexity has absolutely contributed to so many people getting it wrong and leaking data.

An alternative where the only options were public and private, exclusively set at the bucket level would be good enough for 95% of users and simple enough to rarely get wrong.

Post reply on HN