Thread
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
Replies (3)
One major hurdle that is a non-starter is ability to edit and ensure all end users are being delivered the most up to date version every time. The uploader must have control over a universal truth "current" copy. I believe this is difficult over nostr because of the relay model. Maybe not impossible but whatever is being explored needs to be absolutely certain it first answers the problem of editing files and all end users being delivered the correct latest version.
So the thing is RSS already solves this. I simply change the address on my feed, hit save, and it updates across any and all feeds that also reference my feed.
I dont understand why we have to shoehorn nostr into all of it. It has a really amazing use-case. It just needs to plug in to the existing tech.
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.
