Nostr Web Client

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.

mrclownworld 0mo ago

I think the difference I’m suggesting is being able to publish without permanently maintaining anything. With RSS, someone can actively archive your files and update and publish a new RSS, yes

With what I’m saying, the notes remain the source of truth, so an archivist would just need to host the files on a discoverable CDN, not republish a feed.

The original author could add more CDNs to their kind zero, and the original notes still work. No replacing the notes, no replacing the files, just propagating verifiable copies of them

Reply to this note

Please Login to reply.

Discussion

BITwise 🐳 >>= RIGHTish 0mo ago

I see (sorta). But if IP protection is the goal, im not sure how this fully solves it either? Yes they cannot pull directly from the feed but as soon as they stream they can record. What would prevent someone from duplicating a feed that way?

On the flip side, a large part of the ecosystem involves dj's playing their tracks. If it can only be streamed, that limits things that can be done creatively on the broadcast side.

The CDN idea is good for setting a static address without doxxing the source location (pls correct me if im wrong). While that can be useful, I dont think its solving the right problems. IMO we dont need to lock down the audio files. Music is collaborative by nature. We just need to ensure artists can be tipped anytime their music is heard.