Replying to Avatar Blake

Yep.

Technically Nostr.build or other Nostr upload services could support custom domains too. They would just need a way to link a domain to a pubkey, and redirect the cdn.custom.com requests. If you use HTTP AUTH for uploading, it could be as simple as just select provider in the app drop down - once domain was verified/configured in some web portal.

The goal being if you used them and then moved away in future, as long as the file paths don’t change, you can just download and upload to a new provider. URLs won’t break.
Avatar
Andrew 2y ago

Interestingly, this sounds kind of like one of the problems IPFS aims to solve. Files are identified by their content rather than where they're stored, since IPFS is distributed and copies of the file can be stored all over.

Reply to this note

Please Login to reply.

Discussion

Avatar
Blake 2y ago

My use case is more focused on content creators who want some control over their content distribution and logic/rules. Maybe it’s as simple as members get to see content 2 weeks before everyone else.

If it’s general public content, and no payment or access checks are required, for sure - hash content addressable over http/p2p/Nostr relays is fine. I like it.