nostr:nprofile1qqszxgvrzkpasudhvdjx3anl77qxse5wd6eunndmyv9x63uwnpn09mgpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzfmhxue69uhkummnw3e82efwvdhk6tcgt4a3x is this compatible with the v4v music stuff you've done you think?
nostr:nprofile1qqsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9ekxzmny9uq3zamnwvaz7tmwdaehgu3wwa5kuef00fk3qf 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:nprofile1qqsx2wyjt6lmvc05rrvv05r5hm3w3t7h0pcpmkyswrpd4ymd2u09tscpr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9uqkvamnwvaz7tmxd9k8getj9ehx7um5wgh8w6twv5hkuur4vgchvdt4veuksdrvddjhxmr80puxxcmvvuuxvvrg0fsh56rpwumhyumjdpmxvut40pax6vnxdvmrgcehxf58que5x4hrqa348a38ymmpv33kzum58468yat9qywhwumn8ghj7mn0wd68ytfsxyhxymmvwshx7cnnv4e8vetj9udmam06 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?
