Replying to Avatar StevenB

I am also working on ways to perhaps bridge nostr and RSS. One thing you may be interested in, because you're right, polling is very wasteful, is something The Podcast Index came up with called Podping. The basic idea is when a new podcast is published, the publisher adds a new event to the Hive block chain. The Index and others are watching the block chain through a websocket, and anytime they see that the feed has been updated, then, and only then, does the Index reparse the feed to get the updated data. It's reduced their bandwidth tremendously and has solved the problem of constant polling. I've been considering building a podping to nostr bridge, since podping is also being used to let podcast apps know when a particular podcast is going live. This way the nostr relays can also know when a podcast is going live.

Now, I happen to be a Podcasting 2.0 fan boy, so my heart is with RSS, but I think there are definitely some things that can be improved, and that the nostr and RSS community can learn some things from each other to improve both experiences. Perhaps you're right, and nostr will ultimately be the protocol to rule them all, but until then, I'd like any of the artists, musicians, and writers to be able to have options for getting their art into the world and supported by their fans, so I'll be working to figure out ways for the two protocols to work together or at least be able to be translated from one to the other so the legacy apps will continue to work if and until we transition.

I would have a much more detailed response, but your note only shows up on my phone, via amethyst. on my desktop, primal doesn't see this. hmm

my one quick point here is that value for value is amazing, but I think the much more direct use of zaps via nostr could be a better alternative. or at least equivalent. I want to build things that people with bitcoin find valuable, and nostr is a good starting point for that audience.

Reply to this note

Please Login to reply.

Discussion

I only have one issue with zaps. I wish they were splittable. I wish it was widely adopted that an event could have a split tag, and in that tag were several different addresses with the percent of the zap that went to each address. You now have an auditable contract.

If we make a video together and put it in a note, I would like that note to have 50% of the zap amount go to you and 50% to me, and either off us could look at the raw event to verify the splits were what we agreed to.

I agree, this would be a very impactful feature.

Zap splits do exist but itโ€™s not available on every client yet, so the experience is inconsistent.