S3

If a user makes a bucket public, all objects they upload under said bucket will be public. (only said user can upload to it still, just to keep things simple)

This means we can then serve files like so

https://s3.hippius.com/my-photos/image.jpg
without the need to decrypt, and their respective CID will also contain the unencrypted image.jpg.

For GET operations like the above we need to skip all auth and credit checks, etc (just leave IP rate limiting in), and serve directly.

I made it so you can create public buckets, and any objects put inside them will be unencrypted. (this means public in ipfs land)
Then you can simply reference the objects via their CIDs to download them.

You wont be able to reference them via https://s3.hippius.com/my-photos/image.jpg though. We can add that feature later.