@StevenB

As a service aggregating payment stats - 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.

@merryoscar

If I send a Bolt 11 payment from a non-Fountain app, how does Fountain get the metadata?

@StevenB

If an app implements the rss::payment metadata spec like Fountain and Castamatic do it works:

Oscar Merry (@merryoscar@podcastindex.social)

Attached: 1 image @ChadF @mitch @francosolerio great - here's what it will look like in the next fountain app version 1.4.9 that should be live in the next 48 hours - it includes app_name and sender_name:

PodcastIndex Social (podcastindex.social)

@theDanielJLewis

Host the metadata for the podcasters. The comment is in the metadata. You set up an end point in your feed, I’ll send you the data.

@merryoscar

So the app hosts the metadata, and Fountain fetches it?

@StevenB 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

@merryoscar why can’t we skip the fetching part and I just send it to you direct?

@StevenB

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

@merryoscar

1) I send you the data, you send me a unique url
2) I send the payment and include the unique url in the message.
3) Fountain hosted wallets get the payment with the message, look in the database to find the metadata that's tied to that unique url found in the message and marks it as paid or verified.
4) You don't have to trust any of the apps, just that your wallet got the payment with the unique url generated by your server.

@StevenB

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

@merryoscar

My thinking is if the podcaster wants his metadata, he can get some skin in the game and host it himself or pay for hosting instead of relying on the apps to run his business for him.

Maybe they should host with Fountain if they want their metadata.

And I think Strike has a Webhook api. I know Alby does.

@merryoscar

Yeah, I'm pretty sure this would work with Strike too.

Setting up webhooks | Strike API Documentation

Setting up a webhook involves a multi-step process. It includes identifying your desired trigger-event, creating a webhook endpoint, setting up a webhook subscription, and enabling your application to monitor and respond to the webhook.

(docs.strike.me)

@StevenB @merryoscar Excellent point about the apps.