Hacker News Reader

Immense friction.

Also you probably don't want every image you want to share on the internet coming from the same S3 bucket. And you don't want to pay S3/Cloudfront pricing so you'll probably want to put Cloudflare in front of it. Etc, etc.

View on HN

Why? Just use GUIDs.

I'm guessing you're thinking about discoverablity? I think the comment to which you were replying was pointing out that you might want to serve different images out of different buckets (e.g. because they have different audiences) or use a different bucket for images versus other content.

But if you're happy with just using whatever S3 bucket you have, then there's no reason to switch.

What does the audience have to do with anything? Why are you mixing application layer concerns with data storage concerns? It’s like saying you want images for one audience served from Azure but another audience served from AWS. It makes no difference, it’s all just data and bits stored somewhere and served out. Might as well just put it all in the same place. Could easily be the same bucket.

Reply on news.ycombinator.com