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.

Reply to this note

Please Login to reply.

Discussion

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

https://github.com/Podcastindex-org/podcast-namespace