appreciate it. ill reach out if i have issues.
I'm happy to help. There's a bunch of us here that understand the RSS spec. nostr:npub177fz5zkm87jdmf0we2nz7mm7uc2e7l64uzqrv6rvdrsg8qkrg7yqx0aaq7
nostr:npub1yvgrrzf4dnmu30qfhw95x87ruu0g2kpv3a64h8hpvqsre8qeuspsgd6pv9 nostr:npub19ha7tju4teqp3dmwv4p28wrcy9zd6h6hxkg5mwvjrlfycweazpkse2q0fa nostr:npub1yvscx9vrmpcmwcmydrm8lauqdpngum4ne8xmkgc2d4rcaxrx7tkswdwzdu to name a few.
Discussion
If you're focus is nostr, and I know that's where your heart is, the Wavlake api may be a better choice for you because of the way they handle the value block. Because nostr doesn't do splits very well, non-Wavlake feeds may be problematic for you.
However, if you're interested in other non-Wavlake music, the Podcast Index also has an API that lets you fetch all of the music feeds, but the value blocks are considerably more difficult to do using nostr based wallets.
Hopefully, nostr figures out an elegant way to handle splits, because it is really cool being able to have multiple people paid from the listener.
nostr supports splits on events, but profiles only use the lightning address on the profile.
so i have podcastindex.org's API now working on my local dev environment of zaptrax. it works and i can play music just fine. the issue is now supporting keysend. that is not widely supported. i guess the issue is also wavlake music just does a keysend to their node instead of doing the split with the artist sand them?
i need to figure out how to handle all of this elegantly in a user interface so it doesn't look jumbled or confusing.
Yeah, Wavlake handled splits on their server instead of your wallet sending multiple payments. It works, and given some of the limitations, it makes sense.
but it works :) 