Files are hosted on blossom servers. Track and playlists are nostr events that contain all the info including url to track.
In RSS your files live on one server here the model is reversed, you host your own content if you like or use blossom servers and people discover it from you.
The big difference is that this is all easily discoverable in nostr and can live along other event types.
nostr:npub1yvscx9vrmpcmwcmydrm8lauqdpngum4ne8xmkgc2d4rcaxrx7tkswdwzdu is this compatible with the v4v music stuff you've done you think?
nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac could this be extended for podcasting2.0
It’s super easy for any service to broadcast a Nostr event at the time of adding a track or album or playlist. It’s just a matter of them deciding to do this or not.
nostr:npub1v5ufyh4lkeslgxxcclg8f0hzazhaw7rsrhvfquxzm2fk64c72hps45n0v5 and @podverse should adopt then?
They could if they want to
Im wondering, how does this system handle updates to a track? Changes can range from updating titles and metadata to changing the mp3 track itself. What is preventing duplicates or multiple versions appearing simultaneously?
