Nostr Web Client

Seems to me a Nostr event can be the canonical publishing if and only if we get the content delivery to be resilient (something like IPFS or torrents)

Then interoperability with RSS and then you’re bulletproof for self-publishing audio and video

Anyone can develop the clients and publishers can hit all of them at once

Maybe a simpler answer is pointing to a cdn in the kind zero like we do with lightning addresses. Then having a schema where notes reference hashes instead of full URLs, so you can swap a new CDN and all the old notes still register

BITwise 🐳 >>= RIGHTish 0mo ago

You could do all the fancy hashing and cdn lookups but i think thats still overcomplicated. There's no need to push the metadata or file hosting onto relays. All the relays need is the guid of the feed (its in plaintext, can't miss it) and the apps just need a library or template or git so it knows how to decode the tags. But I digress... it's self hosted and thats the key.

If you want it distributed, put it on a blossom server and literally ctrl+v that in your RSS (a text file). Done.

Reply to this note

Please Login to reply.

Discussion

mrclownworld 0mo ago

The hashing is the only way to make sure the right file is served from whatever server and that links don’t permabreak