Oscar Merry

Building Fountain - https://www.fountain.fm

Public Key

npub1kyzsft68lxql9s6v0vzn3et9ectcxjen6ltfehqxe0hy5ky40prslcrpu9

NIP-05 Address

Profile Code

nprofile1qqstzpgy4arlnq0jcdx8kpfcu4juu9urfvea045umsrvhmj2tz2hs3cpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsh3drpr

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1kyzsft68lxql9s6v0vzn3et9ectcxjen6ltfehqxe0hy5ky40prslcrpu9

Show more details

Last Notes

2026-05-21 14:30:57 GMT

- reply

@nprofile…ax8n @nprofile…pwsh @nprofile…9dpf @nprofile…jks4 @nprofile…x5pc
I haven’t made a final decision on this - that’s why I’m posting here.
I’m also trying to create less work for myself and simplify the Fountain codebase which will improve other aspects of reliability around music.
I guess my real question is - what are the currently used demu tools and what are their reasons for not supporting publisher feeds?

2026-05-21 14:17:31 GMT

- reply

@nprofile…pwsh @nprofile…ax8n @nprofile…9dpf @nprofile…jks4 @nprofile…x5pc
I know it's maybe a drastic step - but if we don't take these steps every now and again none of the tools will have any incentive to add publisher feed support.

2026-05-19 15:12:49 GMT

- reply

@nprofile…pwsh @nprofile…x5pc thanks!
one other question - do you know if the album feeds without publisher feeds are old ones - and now most of the tools supporting music publishing do create publisher feeds?
or do most of the demu solutions still not create publisher feeds by default?

2026-05-19 13:32:06 GMT

@nprofile…x5pc
Do you have a sense of how many music feeds there are without a corresponding artist publisher feed?
I am working on re-doing some of our music indexing logic and excluding music feeds without publisher remote items would make things much simpler.
From my perspective having an album feed without a publisher feed doesn't really make sense but maybe I'm excluding a lot of music?

2026-05-05 21:50:54 GMT

- reply

@nprofile…pwsh
Great! I've deployed the change now so it should work on all app versions.
Sorry about the issue and let me know if there's any other area you think we could improve.

2026-03-04 19:05:24 GMT

- reply

@nprofile…td70 great thanks!

2026-03-04 16:45:39 GMT

- reply

@nprofile…td70 no we don't

2026-03-04 15:42:45 GMT

@nprofile…td70 quick question on the API - this feed displays only 4 episodes - https://podcastindex.org/podcast/310504
But the API returns many more - which I think are old ones that are no longer in the feed.
Is there some hidden 'deleted' field that you have in the database but not returned in the API response - if so would it be possible to add this to the API response? (/episodes/byfeedid)

2026-02-27 12:56:46 GMT

- reply

@nprofile…sk9g can you please share the link for the show / episode you are seeing this error with?

2026-02-24 21:32:04 GMT

- reply

@nprofile…zv63
yeah something like this could definitely work - the only downside is that for people self-hosting they would have to host the service that does this
for example - if you self-host your feed and use Strike to receive boosts and streams - this wouldn't work
my thinking with the current rss::payment spec was that even though it's a bit more of a lift for apps - it works with any wallet

2026-02-24 21:23:16 GMT

- reply

@nprofile…zv63
we could - there's just the question of how to avoid fake data if anyone can post payment metadata to a public API endpoint
with the rss::payment spec the url to fetch the metadata originates in the payment comment - so there is a direct tie to the actual payment and since apps host the full metadata on a url their reputation is at stake if they fake data
I am open to exploring solutions to this where apps don't have to host the payment urls - and promise I won't mention nostr 😅

2026-02-24 21:17:40 GMT

- reply

@nprofile…zv63 yep - we fetch it from the 'x-rss-payment' header that is returned in the URL - https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/examples/value/metadata.md#implementation

2026-02-24 21:13:24 GMT

- reply

@nprofile…zv63
If an app implements the rss::payment metadata spec like Fountain and Castamatic do it works:
https://podcastindex.social/@merryoscar/116120033419028522

2026-02-24 21:08:21 GMT

- reply

@nprofile…zv63
Personally I would rather trust metadata hosted by an app than metadata sent to an open API in the feed - but happy to look at any proposals people have and try and work together to solve this for apps that don't want to host payment metadata.

2026-02-24 21:07:50 GMT

- reply

@nprofile…zv63
Fountain does this for our hosting customers - we accept payments from any app - either Keysend or Lightning Address - and aggregate payment stats and metadata in our dashboard - https://fountain.fm/podcasters
This is why I have been advocating for the rss::payment metadata spec because it's simple to implement and we can read the metadata from the x-rss-payment header and use this for our stats.

2026-02-24 19:18:14 GMT

- reply

@nprofile…lm4c
Congrats Franco - great to see the NWC + BoostBox metadata integrations!
https://cdn.masto.host/podcastindexsocial/media_attachments/files/116/127/212/933/222/291/original/dbb588faf87beadb.jpg

2026-02-23 09:56:33 GMT

- reply

@nprofile…w0mx thank you! 🙏

2026-02-23 08:55:04 GMT

- reply

@nprofile…w0mx
"Theoretically, though, this does mean that the same HLS feed should work if you were to put it into an alternateEnclosure for other podcast apps, and should also work just fine on Android or other devices. There’s nothing proprietary here - just a carefully constructed HLS master playlist. And that’s good news for all of us."
Great to hear!
At Fountain we have many podcasters publishing HLS video with every episode. @nprofile…w0mx any thoughts on the best way to contact Apple?

2026-02-22 14:51:52 GMT

- reply

@nprofile…x5pc
This boostbox server follows the rss::payment metadata spec exactly - https://github.com/noblepayne/boostbox
so if you're using that everything should line up - it's just that many of the guids are optional so you just need to make sure you're adding as many as possible

2026-02-22 13:48:07 GMT

- reply

@nprofile…x5pc is there a reason this metadata does not include the feed_guid?
https://boostbox.cloud/boost/01KHY044DQE27T5MEQ7J6GJCBV
Ideally we have both feed_guid and item_guid to be 100% sure we are matching and applying support stats to the right episode.

2026-02-20 18:34:59 GMT

- reply

@nprofile…x5pc thanks I've found the issue - give me a bit more time to add a fix and I'll follow up soon and you can test again - shouldn't be too long I just always need to be careful when changing payment logic

2026-02-20 18:11:56 GMT

- reply

@nprofile…x5pc sorry I meant the reference id from the receiving fountain wallet (first screenshot)

2026-02-20 17:47:27 GMT

- reply

@nprofile…x5pc can you send me the reference id and I can check why this is not displaying as a boost in the fountain wallet

2026-02-20 15:07:04 GMT

- reply

@nprofile…x5pc yes I think defaulting to lnurl is a good idea

2026-02-19 09:12:13 GMT

- reply

@nprofile…w0mx
Totally agree James - this <metaBoost> spec has been around since 2024 and no-one has implemented it because it's overly complex.
The rss::payment metadata spec is simple and we have 2 apps that have implemented and 2 more that are working on it.
We need to all align on this if we want to re-energise open podcast payments.

2026-02-02 13:31:14 GMT

- reply

@nprofile…kdmg @nprofile…w0mx @nprofile…cn7u
@nprofile…kdmg I know it's probably annoying but would it be a massive amount of work for you guys to switch to the same spec Fountain and Castamatic are using?
https://github.com/Podcastindex-org/podcast-namespace/pull/734
I think we would really turn a corner if we could all align here!

2026-01-29 08:48:17 GMT

- reply

@nprofile…x5pc thanks Chad - will reach out to them and get this sorted

2026-01-20 16:04:53 GMT

- reply

@nprofile…x5pc @nprofile…zv67 @nprofile…05ue
I would suggest leaving the feed as medium="music" and the video in the alternate enclosure - we can add support for music videos this way

2026-01-20 14:38:16 GMT

- reply

@nprofile…05ue @nprofile…x5pc
Yes we only support alternate enclosure video for podcasts - not music.
I don't think alternate enclosure should be used for external platform links - shouldn't we use <podcast:contentLink> for that?
https://podcasting2.org/docs/podcast-namespace/tags/content-link

2026-01-20 14:34:01 GMT

- reply

@nprofile…x5pc @nprofile…05ue
We don't currently support alternate enclosure for music feeds - this is something we will look into adding.

2026-01-16 10:02:18 GMT

- reply

@nprofile…d65z @nprofile…8t76 @nprofile…x5pc @nprofile…lm4c @nprofile…7epg @nprofile…td70
keysend was never killed but very few lightning wallets support it - continuing to use keysend for open podcast payments is incredibly confusing for new podcasters and listeners because they need to learn about the technical differences between keysend / bolt11 / lnurl - when really all they should need to do is "go find a lightning wallet" and add the lightning address to your feed

2026-01-11 11:24:35 GMT

- reply

@nprofile…vfcp aah yes you're right we were only submitting the album feeds not the publisher feed - I've done that now and it's all working - https://alpha.podverse.fm/artist/zp7I1ZDtz9

2026-01-09 15:19:34 GMT

- reply

also fyi @nprofile…vfcp I tried searching for these guys on the new podverse web alpha - found their album feeds - but then I couldn't find a way to get to their artist page - not sure if that's still in the works but thought I'd let you know

2026-01-09 15:05:02 GMT

New French Symphonic Metal band Hartlight now available on Fountain and any supporting Podcasting 2.0 music player.
Check out their music and give them a welcome boost!
https://fountain.fm/artist/BHQT3YDR59zGumqz9RVO
https://podcastindex.org/podcast/7648720

2025-12-31 11:07:51 GMT

FYI @nprofile…wsp3 we are seeing LNURL payment failures to the main No Agenda Show split: [email protected]
{
"status": "ERROR",
"reason": "Invalid amount, minimum is 100 and maximum is 16000000"
}
What's strange is the other strike lnaddress splits are all working despite them having lower splits:
[email protected]
[email protected]
Maybe caused by a setting in Strike? Is your "Receive currency" set to Bitcoin in settings? Maybe the minimum only applies when receiving USD?

2025-12-30 16:01:53 GMT

- reply

@nprofile…l26x @nprofile…4vsz
yep that makes sense 👍

2025-12-30 15:57:49 GMT

- reply

@nprofile…l26x @nprofile…4vsz
yeah there is definitely a trade-off between keeping full split records + amount of data - ultimately if streaming payments per minute with splits grows 1000x in volume we might have to figure something else out - but for now I think this approach best preserves all the data we had in the keysend TLVs

2025-12-30 15:51:18 GMT

- reply

@nprofile…l26x @nprofile…4vsz
currently we create a different payment record for each split - but link them with a "group" id which is also in the metadata

2025-12-23 15:40:27 GMT

Fountain 1.4.4 is now live 📲
We've made some major improvements to CarPlay and Android Auto - just in time for your drive home for Christmas.
You can now play podcasts or music saved to your library, or explore recommendations from people you follow on Nostr, all without touching your phone.
https://primal.net/e/nevent1qqsfkksx0ydjrs8t30s3jwkvwf5jkw3s696c4wg88e4f0lrp5zje57qzv4ahk
https://blog.fountain.fm/p/1-4-4

2025-12-20 23:03:29 GMT

If anyone here listens to podcasts mostly in the car - we would love some help testing our new CarPlay / AndroidAuto experience that’s now available in beta with Fountain 1.4.4.
The new Fountain experience in the car much better than previous versions - but we really need help testing it before general release.
Beta links are available in our telegram group - https://t.me/+ZMnGthLREYQ3N2Rk
Please do jump in and give it a quick test in the car if you have a spare 5 mins this weekend! 🙏

2025-12-19 14:40:17 GMT

Fountain 1.4.2 is now live 📲
Based on your feedback, we made a couple of improvements to the library.
You can now see a grid view of your shows and get to the filtered episode list in one tap.
https://x.com/fountain_app/status/2002024723345969565
https://primal.net/e/nevent1qqspezfm7tsyspzrcrdv6c8x7d3aaspal3etnd6aj6xrha6z3mnqupc0j9apq

2025-12-17 10:52:57 GMT

- reply

@nprofile…5yxp thanks for the report - this is fixed

2025-12-15 18:12:31 GMT

@nprofile…dzgg
Is there a way to generate pod.link episode links via some kind of url param or API?

2025-12-15 09:54:25 GMT

- reply

@nprofile…kdkm great to hear! thanks again for the bug report!

2025-12-14 14:42:40 GMT

- reply

@nprofile…kdkm we have a new version 1.4.1 which is now live - although we weren't able to replicate the issue - we've made an update to the layout logic this screen which we believe will fix the issue - can you let me know if you're still experiencing it on 1.4.1?

2025-12-13 13:23:00 GMT

- reply

@nprofile…kdkm
Thanks for the bug report - I'm just testing now on an iPhone16 simulator and I can't seem to replicate this.
Is it a regular iPhone16 or Plus / Pro / Pro Max?

2025-12-12 18:01:37 GMT

- reply

@nprofile…wsn5
no not currently - we only support incoming NWC connections - so you can use an external wallet in Fountain
we hope this showcases to other podcast apps that NWC is a great option for letting users choose what wallet they want to use

2025-12-12 17:38:34 GMT

Fountain 1.4 is now live, and we've completely redesigned the Fountain wallet, made UX improvements to payments across the app and added some highly-requested features:
💜 Nostr Wallet Connect
⚡️ Pay Lightning Address
⬆️ Withdraw to Strike
💳 Choose Payment Method
https://x.com/fountain_app/status/1999529230527316390
https://primal.net/e/nevent1qqst57g7829mur9phklus5zd7gffy8f49h6m5s3l4sy668qvm2sgyscgpkpvs
https://blog.fountain.fm/p/1-4

2025-12-12 13:47:46 GMT

- reply

@nprofile…5yxp
This is fixed now - for both the above feed and for future new releases updating publisher feeds.
Thanks for reporting the issue!

2025-12-12 13:28:00 GMT

- reply

@nprofile…5yxp
Thanks Chad - this looks like a bug - will fix today and report back

2025-12-08 20:23:49 GMT

- reply

@nprofile…y5nd would love to see a short video walkthrough of how you are working with the model in your IDE!

2025-12-04 22:50:17 GMT

We published a blog post on video podcasts using the new <podcast:alternateEnclosure> tag - https://blog.fountain.fm/p/video-podcasts
Would appreciate some shares and also feedback on our new web video experience (works with any video alternate enclosure feed) - https://fountain.fm/episode/bb3MURtHHVbPFkvvDpTc
X - https://x.com/fountain_app/status/1996712018779283599
Nostr - https://primal.net/e/nevent1qqsqs0c0hft3474phgkejj7vk68ly4cyln4xlm50rvx5c2wkdajdkmqdptxnf

2025-12-03 17:22:32 GMT

- reply

@nprofile…28le
what nostr spec are you using for favourites?

2025-11-19 14:26:38 GMT

- reply

@nprofile…5yxp publisher feeds have a guid - and adding these tags allows you to query all the nostr events related to a specific artist

2025-11-14 13:39:59 GMT

- reply

@nprofile…5yxp aah ok interesting - so there's no way to paste in an invoice from clipboard?

2025-11-14 13:27:06 GMT

- reply

@nprofile…5yxp
Nice! So people could top up their Fountain wallet with their cash balance on CashApp? That's interesting because it removes the cognitive step of having to choose to buy bitcoin.

2025-11-14 13:13:04 GMT

- reply

@nprofile…sxxr @nprofile…y5nd @nprofile…wsp3 @nprofile…9ap7
It looks like the lnaddress for this episode item split is invalid:
podcastindex.getalby.com
should be [email protected] rather than a . between handle and domain

2025-11-13 10:54:54 GMT

- reply

@nprofile…5yxp cool! let me know if you see this option in the UI and get a chance to test (I'm sure UK will be a bit behind)

2025-11-13 10:54:07 GMT

- reply

@nprofile…9ap7 @nprofile…25h2 we don't unfortunately - we discontinued Fountain Radio - the infrastructure was slightly messy - hoping to re-build in the future!

2025-11-07 18:09:29 GMT

FYI guys going to be away for the next hour or so - but please do keep posting questions / comments as I really want to continue this discussion so we can all come to an agreement!

2025-11-07 18:08:02 GMT

- reply

@nprofile…xefh @nprofile…vwpk yes you could do this easily

2025-11-07 18:06:32 GMT

- reply

@nprofile…vwpk @nprofile…xefh
you could have a relay that only a certain set of app pubkeys could publish to

2025-11-07 17:49:40 GMT

- reply

@nprofile…wsn5 @nprofile…vwpk
private metadata that is only visible to the podcaster is a whole other problem that is much harder - and if we try and solve it at the same time as getting the basics working - it's doubtful we'll get anywhere
but we can always come back to this

2025-11-07 17:48:24 GMT

- reply

@nprofile…vwpk
I think Podcasters fit into 2 categories:
- those that will never get into the tech layer themselves - they will use a service like Fountain / Alby / their hosting company - and these companies will handle indexing podcast related nostr notes from all relays (this is what we do)
- those that are self-hosting / interested in the tech - and they would be able to figure out how to query multiple relays - and put an additional tag in their feed signposting which relay to use

2025-11-07 17:31:37 GMT

- reply

@nprofile…vwpk
yes - but importantly by using nostr there is the benefit that everything still works if there is no explicit url in the feed

2025-11-07 17:27:19 GMT

- reply

@nprofile…vwpk this could easily be added to the feed:
<podcast:nostr npub="..." relays="...">
But in reality right now because it's early we can just pick a set of relays that we all agree to publish to. The events can always be re-synced to other relays later.

2025-11-07 17:15:12 GMT

Also - what's funny about all of this is that nostr literally solves every problem that has been brought up because there are no servers required and it has built in signing of events. It also has the added benefit of cross-app comments, likes, replies etc.
The community here has clearly rejected nostr which is why I have proposed this alternative.
But if you want to take a look at my previous proposal it is here - https://primal.net/merryoscar/open-podcast-payments-with-bitcoin-and-nostr

2025-11-07 17:09:09 GMT

- reply

@nprofile…vwpk @nprofile…5yxp @nprofile…9ap7 @nprofile…l26x
We're not putting it all on the wallets because this spec is just a URL - anyone can generate the URL - apps, wallet services, or third parties.

2025-11-07 17:04:53 GMT

- reply

@nprofile…vwpk @nprofile…5yxp @nprofile…9ap7 @nprofile…l26x
Clickable is a nice to have but you're right does not matter in the long term.
The important part of this is that any receiving wallet if they choose to can parse the full payment metadata with only the text in the description field.
For something like Alby Hub - it will be much easier for them to parse this data from the BOLT11 description as opposed to setting up a dedicated HTTP server to receive from podcast apps.

2025-11-07 16:57:48 GMT

- reply

@nprofile…5yxp @nprofile…9ap7 @nprofile…vwpk @nprofile…l26x
Should be easy for Alby to make the links clickable - here's the part of their code that renders the invoice description - https://github.com/getAlby/go/blob/master/pages/Transaction.tsx#L172

2025-11-07 16:49:59 GMT

- reply

@nprofile…9ap7 @nprofile…vwpk @nprofile…l26x
Yep just sent you a test payment - this is what it looks like receiving to my Primal wallet - which shows the link as clickable which is nice:
https://cdn.masto.host/podcastindexsocial/media_attachments/files/115/509/440/403/290/527/original/4569ab6694fbc041.jpg

2025-11-07 16:37:34 GMT

- reply

@nprofile…9ap7 @nprofile…vwpk @nprofile…l26x
ok great - yeah that would be really useful - and also a great addition to OP3 analytics perhaps?

2025-11-07 16:34:46 GMT

- reply

@nprofile…9ap7 @nprofile…vwpk @nprofile…l26x
That would be amazing John - we'd also be happy to offer this service - but I think it makes it feel slightly weird if one app is hosting the payments for all the others.
The cool thing about this proposal is that if an app includes a URL in the BOLT11 invoice like:
rss::payment:boost op3.dev/payment/123
Anyone can parse the metadata and do whatever they want with it.
I do think services like this should have either an API key or signature to prevent spam

2025-11-07 15:31:20 GMT

- reply

@nprofile…vwpk @nprofile…l26x
Also if the API is in the feed - how do you validate that the payment actually happened?
The good thing about the app generating these URLs is that they know at the time of sending that the payment actually happened.
Fountain / others could still create an API for apps to use - but they would need to have an API key that is trusted.

2025-11-07 15:28:37 GMT

- reply

@nprofile…vwpk @nprofile…l26x
I think the problem with relying on the host feed having an API in it is that people that are self-hosting need to run a server and database.
I think it's much easier for an app to do this than someone self-hosting a feed.
Fountain / others could provide a service like this - but in my view it should be the sending app that uses this service to generate a URL for the payment description

2025-11-07 15:21:05 GMT

- reply

@nprofile…vwpk @nprofile…l26x
- if the app chooses to store the metadata they can serve it via their own url
- if the app doesn't want to save the metadata in their own database - other services can do this - wallets or analytics services that provide some kind of API that returns a URL
If neither the app or wallet service wants to store podcast payment metadata - then we're kind of stuck no matter what the spec is

2025-11-07 15:05:04 GMT

- reply

@nprofile…vwpk @nprofile…l26x
Because this approach is just a prefix + URL - really anyone can provide the URL to the sending app.
Podcasters can choose which wallet they want to use to receive - and wallets can programatically parse the metadata and store a copy of it.
So there are multiple options:
- app could store metadata and serve url
- sending wallet service api could provide url for app to use

2025-11-07 14:55:29 GMT

- reply

@nprofile…vwpk
Yes apps or wallet services will need to serve these links - Fountain might provide an API for this as a stop-gap

2025-11-07 14:53:22 GMT

- reply

Here's an example payment link - https://fountain.fm/episode/JCIzq3VyFKQVkEzVNA8v?payment=5XIAt66P29Iv6rjSTZUB
And here's how you can query the JSON programatically via curl:
curl -I -s -o /dev/null -w '%header{x-rss-payment}' 'https://fountain.fm/episode/JCIzq3VyFKQVkEzVNA8v?payment=5XIAt66P29Iv6rjSTZUB'
(note this is URI encoded JSON string)

2025-11-07 14:51:24 GMT

I know my previous nostr-based payment metadata solution didn't really get adoption from other PC20 apps - so me and @nprofile…q064 have come up with a much simpler solution for LNAddress payment metadata:
https://github.com/Podcastindex-org/podcast-namespace/pull/734
TLDR - we use the BOLT11 invoice description field to add a rss::payment prefix along with a URL that returns the full metadata in a x-rss-payment header.
From today all LNAddress payments sent from Fountain will use this metadata approach - so feel free to start testing!

2025-11-05 08:59:53 GMT

- reply

@nprofile…sxxr @nprofile…nxqw yes

2025-11-04 18:47:03 GMT

- reply

@nprofile…sxxr yes - any fountain lightning address

2025-10-30 12:22:21 GMT

- reply

@nprofile…l26x @nprofile…ge5x @nprofile…2q02 @nprofile…r5z7
testing on a wifi router with dns ad-blocking

2025-10-30 12:04:51 GMT

- reply

@nprofile…ge5x @nprofile…l26x @nprofile…2q02 @nprofile…r5z7 @nprofile…wy29
This episode also doesn't play in the overcast mobile app if you have an ad-blocker enabled - https://overcast.fm/+AAIwMffebR0
@nprofile…ge5x are you able to play this in overcast with an ad-blocker?
I don't see any error messages it just has an infinite spinner.

2025-10-30 11:55:03 GMT

- reply

@nprofile…ge5x @nprofile…l26x @nprofile…2q02 @nprofile…r5z7 @nprofile…wy29
Also this overcast link for the other Glenn Beck feed doesn't play in brave - https://overcast.fm/+AAIwMffebR0
seems to be verifi.podscribe.com that is blocking

2025-10-30 11:50:00 GMT

- reply

@nprofile…ge5x @nprofile…l26x @nprofile…2q02 @nprofile…r5z7 @nprofile…wy29
ok great thanks - I'll look into updating our playback error handling to give a contextual error message
this is the example glenn beck show on pocketcasts - https://pocketcasts.com/podcast/the-glenn-beck-podcast/0b49bf90-b88c-0138-e6e2-0acc26574db2
(doesn't play in brave)

2025-10-30 11:34:27 GMT

Is anyone else seeing episode audio issues with ART19 / ARTTRK hosted shows when using ad blockers / VPN?
For example this one - https://podcastindex.org/podcast/2434774
- doesn't play on podcastindex with brave
- doesn't play on pocketcasts with ad-blocker enabled
- doesn't play in fountain with ad-blocker enabled
cc @nprofile…l26x @nprofile…2q02 @nprofile…ge5x @nprofile…r5z7

2025-10-22 08:50:40 GMT

- reply

@nprofile…5yxp
They are based on the Fountain account Lightning Address - this user hasn't changed theirs which is why it's still the default - I'll reach out to them and ask 👍

2025-10-14 12:12:13 GMT

- reply

@nprofile…fhrz great video!

2025-10-06 16:55:54 GMT

- reply

@nprofile…6746
since the zap receipts are signed - you can choose to trust the signer e.g. fountain pubkey or your app pubkey
if your app signs zap receipts we can trust by default - then if anyone notices fake zaps - you lose trust - same for other apps that publish receipts this way
note this is a short term approach until keysend is gone - long term if every lnaddress split publishes there own receipts you can embed multiple receipts in a note - which is cool because splits can be displayed

2025-10-06 16:24:58 GMT

- reply

@nprofile…6746
yes you can - technically you can create a zap receipt without the lightning invoice + preimage
what we do is create one for all the splits combined
one thing to note - I would advise doing this server side so that the pubkey that is signing the zap receipt can be "trusted" to not sign fake receipts

2025-10-06 10:43:06 GMT

- reply

@nprofile…6746 nice!!
I think the final step is to add an embedded zap receipt into the note - then we can parse it and show the satoshi amount natively.

2025-10-03 18:41:10 GMT

- reply

@nprofile…vu32 yes we support music hosting - more info here - https://fountain.fm/artists

2025-10-03 18:23:11 GMT

New Track from Suzanne Santo:
https://primal.net/e/nevent1qqszjxw7rlgxtrx8hqgejedetm65cnfrgrk0dxzxev6e90y6g2qd7qskzf8wc
https://fountain.fm/track/mZ8ci07BjsjT5XriuZCv

2025-10-03 18:11:06 GMT

- reply

@nprofile…pvn3 @nprofile…n7gm yes - we are using lnaddress by default for all feeds - but still have the option to add keysend splits - although it's under advanced settings

2025-10-03 18:02:26 GMT

- reply

@nprofile…n7gm @nprofile…pvn3 Fountain fully supports lnaddress

2025-10-02 17:55:59 GMT

We published an article on music distribution via RSS:
https://primal.net/e/nevent1qqs8ww0c0j65a6u4chep8dynmedc9vc6qe6zx092g27h4smz8afttcg5r8ycx
Please share / let me know if any feedback on how we've tried to explain things in a non-technical way!

2025-09-11 16:43:25 GMT

I've written an article / guide on how Fountain publishes podcast payment metadata using nostr - https://primal.net/merryoscar/open-podcast-payments-with-bitcoin-and-nostr
I know not everyone's sold on nostr - but this approach is working today and allows podcast payments to display in other nostr clients (see example in the article) - there's no reason we can't have the same interop between podcast apps.
I know @nprofile…6746 and @nprofile…pvn3 are experimenting which is great to see.
I'm also working on a JS library with sample code - will share soon.

2025-09-08 16:02:19 GMT

- reply

@nprofile…zn42 @nprofile…pvn3 @nprofile…6746 @nprofile…j90y
For apps that want to use this approach - it's very easy and only requires modifying the LNURL payment request slightly to include a zap request - doing this does not require you to add nostr profiles - this is optional.
Most Lightning Address wallets support zap receipts (Fountain, Alby, Strike, Coinos) etc - so you get the verification built in.

2025-09-08 15:56:16 GMT

- reply

@nprofile…zn42 @nprofile…pvn3 @nprofile…6746 @nprofile…j90y
- the kind 30090 generic payment solution was just an idea and we are not currently using it - mainly because no-one else was interested in it
- what fountain is using in production today is nostr kind 9735 zap receipts for payments, and kind 1 notes for comments / replies
- we use nostr NIP-73 i tags with podcast feed + episode guids so that anyone can query events for any feed / item - you can try this on our relay with kind 1 / 9735