@merryoscar
Building Fountain - a nostr powered podcast app
Relays (3)
- wss://relay.fountain.fm – read & write
- wss://relay.primal.net – read & write
- wss://relay.damus.io – read & write
Recent Notes
1❤️1💜1
nostr:nprofile1qqswfa547pdmqkerzf2uen3agudc67wxffjmenqpge3dylc006fppysprpmhxue69uhhyetvv9ujuen0w4h8gctfdchxvmf0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj754rj0e I sig...
Should be fixed now - let me know if any other issues and thanks for supporting us with premium 🙏
2🎉1
Looks like my boost failed! And I’m just realizing my boost from notes #1 or #2 failed as well 😕
The sats for the billandkeonne split never left my wallet even though they show up in Fountain li...
Unfortunately we do not account for payment split failures in our zap receipts - we generate a single zap receipt for all splits.
This is a tradeoff because the zap receipt cannot be updated as it's not a replaceable event. The fact that we have multiple splits makes it complicated and even if we did wait for the result of each split - that would not render easily on other nostr clients.
My view is that a more flexible payment receipt event kind would make things much easier - I proposed this in 2024 but it had no takeup - https://github.com/nostr-protocol/nips/pull/1339
We also chose to do things this way to put the burden on receiving wallets to reduce their payment failures.
I know this is not ideal - but I cannot think of a better way of doing it right now given the constraints.
Happy to hear suggestions.
This is a tradeoff because the zap receipt cannot be updated as it's not a replaceable event. The fact that we have multiple splits makes it complicated and even if we did wait for the result of each split - that would not render easily on other nostr clients.
My view is that a more flexible payment receipt event kind would make things much easier - I proposed this in 2024 but it had no takeup - https://github.com/nostr-protocol/nips/pull/1339
We also chose to do things this way to put the burden on receiving wallets to reduce their payment failures.
I know this is not ideal - but I cannot think of a better way of doing it right now given the constraints.
Happy to hear suggestions.
1❤️1
nostr:nprofile1qqswfa547pdmqkerzf2uen3agudc67wxffjmenqpge3dylc006fppys27zxn8 nostr:nprofile1qqs2wchuphy7lmvqpcqwrej0ljztp8vwsn0wm7fyscrsedtmdag279gwm547p
Fixed - we truncate nostr notes because they are clickable through to the thread page - I've disabled this for non-nostr boosts.
https://fountain.fm/episode/Hpc1pgNvvZGIBYjkGRQS
https://fountain.fm/episode/Hpc1pgNvvZGIBYjkGRQS
1
This week in London - the Podcast Standards Project met to discuss the adoption of new features that improve open podcasting for both listeners and creators.
Our goal is to keep podcasting open and ensure you always have choice of where to listen - without centralised platforms dictating the experience and forcing specific ad volumes or algorithms.
I am advocating within this group to use nostr as the social layer for podcasts - powering likes, comments, and social recommendations by using NIP-73 to canonically reference shows and episodes via their GUIDs - just like we do in @Fountain today where all of this data is open for anyone to use.
If you believe in keeping podcasting open - whilst enriching the experience to match the big platforms - help me advocate to the rest of the industry:
- use @Fountain and share feedback on what’s working and what’s not
- reach out to your favourite podcasts and tell them about nostr
- as a podcaster - ask your hosting company to support nostr
- repost / share this note with others who are interested
https://podstandards.org/2026/05/22/podcast-rss-nerds-unite-in-london/
Our goal is to keep podcasting open and ensure you always have choice of where to listen - without centralised platforms dictating the experience and forcing specific ad volumes or algorithms.
I am advocating within this group to use nostr as the social layer for podcasts - powering likes, comments, and social recommendations by using NIP-73 to canonically reference shows and episodes via their GUIDs - just like we do in @Fountain today where all of this data is open for anyone to use.
If you believe in keeping podcasting open - whilst enriching the experience to match the big platforms - help me advocate to the rest of the industry:
- use @Fountain and share feedback on what’s working and what’s not
- reach out to your favourite podcasts and tell them about nostr
- as a podcaster - ask your hosting company to support nostr
- repost / share this note with others who are interested
https://podstandards.org/2026/05/22/podcast-rss-nerds-unite-in-london/
21❤️4✊1❤️1👏1🔥1
❤️🔥❤️
2❤️5
Sent
Thanks!
So now I need a client that renders the onchain balance and a signer that can call sign_psbt?
So now I need a client that renders the onchain balance and a signer that can call sign_psbt?
@Alex Gleason can you send me one of these onchain zaps - curious about the receive experience - will zap you back NIP-57
2
nostr:nprofile1qqsx2wyjt6lmvc05rrvv05r5hm3w3t7h0pcpmkyswrpd4ymd2u09tscr0kfvc
Not a single one of these boosts arrived at the podcast. Additionally, over the past few months, several listeners have re...
Hi - it looks like keysend payments to your node ([email protected]) are intermittently failing.
For the top boost example on this episode - the 4,242 sats were sent by @GERONIMO with an NWC wallet connected to Fountain. When splits fail on a boost from an NWC wallet - we refund the split amount to the Lightning Address of the connected NWC wallet - and I can see the refund was processed so @GERONIMO should see a 4,284 refund payment in their NWC wallet - I can share the invoice and preimage for the refund if that's helpful.
The status of each payment split should be visible in the Fountain wallet for NWC transactions - so any user can check in the app and should see a REFUNDED status for any splits that failed. Transaction Reference IDs are also available on the transaction detail page.
If you would like me to check other specific examples - please send an email to [email protected] with the Transaction Reference ID and I can check them for you.
Let me know if that all makes sense.
For the top boost example on this episode - the 4,242 sats were sent by @GERONIMO with an NWC wallet connected to Fountain. When splits fail on a boost from an NWC wallet - we refund the split amount to the Lightning Address of the connected NWC wallet - and I can see the refund was processed so @GERONIMO should see a 4,284 refund payment in their NWC wallet - I can share the invoice and preimage for the refund if that's helpful.
The status of each payment split should be visible in the Fountain wallet for NWC transactions - so any user can check in the app and should see a REFUNDED status for any splits that failed. Transaction Reference IDs are also available on the transaction detail page.
If you would like me to check other specific examples - please send an email to [email protected] with the Transaction Reference ID and I can check them for you.
Let me know if that all makes sense.
1
The nostr:npub1cvcgs83gw6pcrhvtmlf8gdqaegx93qkznwry96jteqhh2cexgkfq45rtya podcast is exclusively powered by our Podcasting 2.0 supporters and nostr:npub1f5pre6wl6ad87vr4hr5wppqq30sh58m4p33mthnjreh03qa...
Amazing to see!
Please let me know if there’s anything Fountain can do to improve the experience either on the hosting side or app side.
Please let me know if there’s anything Fountain can do to improve the experience either on the hosting side or app side.
1🔥1
nostr:nprofile1qqsx2wyjt6lmvc05rrvv05r5hm3w3t7h0pcpmkyswrpd4ymd2u09tscr0kfvc is there any way to get Nostr notifications when a boost is sent to a podcast?
not at the moment - but you can go to the /activity tab on web to view latest activity for the show
1
