What is Nostr?
merryoscar / Oscar Merry
npub1unm…d0j2
2024-10-24 08:18:37
in reply to nevent1q…gdnt

merryoscar on Nostr: nostr:note14j9hpvcfg7akplswgezgn76wt4amdpscsxvyup5w383ggce7f80qyzxfvr

ChadF (npub177f…aaq7) so many complaint boosts I wasn't sure which one to reply to so I picked this one...

First - the biggest complaint we've received over the years about Fountain is that the boosts and replies only work in Fountain and not the other Podcasting 2.0 apps. You in particular were one of those beating the drum on this. Nostr has solved this problem and now any other app can easily query the boosts, replies, and profiles from our relay or any other relay.

Second - I would say the biggest reason people use Fountain over other Podcasting 2.0 apps is because we surface the boosts as comments on both the episode pages and activity feed. As a listener it's interesting to see the boosts that people you follow are sending and provides great discovery for podcasters. We've heard this again and again. Nostr allows this feature to work between different podcast apps and it doesn't require the other apps to build their social features from scratch.

Third - you know as well as I do that the conversation within the Podcasting 2.0 community around cross-app comments has been happening for YEARS - basically since the project began. Everybody wants it but up until now there have been no credible solutions that work. There is no ActivityPub based solution that works with the boost payments integrated - it doesn't exist. For some reason adamcurry (npub13ql…qcg7) doesn't like nostr and this has put people off. But what I don't understand is why would you not be excited about a solution that literally solves the problem we've all spent countless hours discussing over the past few years.

Nostr for cross-app podcast comments and boosts works. It's working in Fountain and the other nostr clients and all we need is for the other Podcasting 2.0 apps to adopt it. It's not hard it's just a simple websocket query to load the comments for a particular episode based on the guid.

If you think there is a better solution for the goal we have all been working towards over the past few years - please let me know as I'd love to see it.

If you don't have an alternative solution - then why not help us try and get the other apps, podcasters, and listeners to adopt this rather than complaining about something that you've been asking to see for years?
Author Public Key
npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2