StevenB's avatar
StevenB 11 months ago
Since I already have MSP for building music RSS feeds, and LNBeats for consuming music RSS feeds, I figured I can start learning how to maybe put music into notes so the musicians could have their music available in nostr for v4v as well. Having a project is a good way for me to learn something new. Then I remembered @Wavlake did something a few years back called Wavman, and it's very similar to the idea I had. I think the Wavlake guys are super innovative, and I've reached out to them from time to time with issues and bug reports, because although I have my criticisms, they're making things easier for musicians, and by and large, I think they want to help out musicians. I don't even care that they're making a business out of it and charging for their services, handling hosting is a big deal that they make easier. There's a problem, and they're charging for a solution, that's how the free market works. I just want them to open their player to all the musicians, even those that choose not to host on Wavlake. nostr and RSS are meant to be a protocol that allows a musician to choose where they host their content, and any and all clients can find that content and play it. They are truly open protocols. It doesn't look like much came of Wavman, maybe too soon for it's time. But I think it's an idea still worth exploring, so I'm going to continue playing around with the idea, and see about hosting artwork and mp3s on satellite.earth, or maybe a Blossom server (I'm not sure how to use one of those yet), and then having the necessary metadata in a note to allow all nostr clients to be potential music players. If we can figure out and widely implement splittable zaps, or maybe wide adoption of Bolt 12, I think zappable media in every nostr client is highly feasible. The musicians will have the potential to get financial support for their art and the listeners can use any client they choose to support any v4v enabled musician they choose.

Replies (2)

I appreciate you pointing this out. It does seem to solve the polling problem. But it seems to me that NOSTR also solves this problem, but does so in a much more elegant way, with a turnaround time of updates to distribution potentially being measured in milliseconds. Not only that, but the content IS the message. Plus, I like the idea that the NOSTR protocol carries all the things that I want timely updates on. I would like to have a feed that can handle articles, podcast episodes, comments on all of the above, and all the menagerie of note kinds that I have yet to explore, using a single protocol, so I don't need to mix and match betweeen them. Obviously, if there is a superior protocol for a particular kind of content, I wouldn't hobble utility to have uniformity, but it would be nice to minimize the number of integrations, accounts, and book keeping required to both publish and consume such content. Have you personally used the Podping stack to publish stuff? I'm curious to hear your experience with it.
I use podping everytime I publish a new episode of Lightning Thrashes and when I do live shows every Sat to signal it's statuses (pending, live, ended) to podcast apps like Fountain, Curiocaster, PodcastGuru, etc. I also use it whenever I publish or update an RSS feed. (I've got about 30ish so far) I don't have much of a dog in the hunt re: nostr vs RSS. I tend to prefer the way the current RSS ecosystem works, but I have no problem with other solutions being developed and tried. My biggest concern is openness, scalability and interoperability. So far RSS has been rock solid for over 20 years. I invite you to learn more about podcasting 2.0 and the amazing innovations that have been made over the past several years. podcastindex.org