@Oscar Merry
Building Fountain - https://www.fountain.fm
Relays (1)
- wss://relay.ditto.pub – read & write
Recent Notes
@nprofile1q... 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)
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)
1
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqzyl794m0xt2k5e94gslj0yzv5uex9y7l33zy74ww3z507hsle92spmk8p7
bro, I have 1.2 gigabit / second internet broadband
but your appy app fountain keep...
@nprofile1q... can you please share the link for the show / episode you are seeing this error with?
1
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqzyl794m0xt2k5e94gslj0yzv5uex9y7l33zy74ww3z507hsle92spmk8p7
1) I send you the data, you send me a unique url
2) I send the payment and include t...
@nprofile1q...
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
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
1
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqzyl794m0xt2k5e94gslj0yzv5uex9y7l33zy74ww3z507hsle92spmk8p7 why can’t we skip the fetching part and I just send it to you direct?
@nprofile1q...
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 😅
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 😅
1
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqzyl794m0xt2k5e94gslj0yzv5uex9y7l33zy74ww3z507hsle92spmk8p7
So the app hosts the metadata, and Fountain fetches it?
@nprofile1q... 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
1
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqzyl794m0xt2k5e94gslj0yzv5uex9y7l33zy74ww3z507hsle92spmk8p7
If I send a Bolt 11 payment from a non-Fountain app, how does Fountain get the metad...
@nprofile1q...
If an app implements the rss::payment metadata spec like Fountain and Castamatic do it works:
https://podcastindex.social/@merryoscar/116120033419028522
If an app implements the rss::payment metadata spec like Fountain and Castamatic do it works:
https://podcastindex.social/@merryoscar/116120033419028522
1
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqvpkystedk2lldqlkkyd084tj5e39rpxn7lad6qeq9uka7kfw9jrs2pzv63
Fountain does this for our hosting customers - we accept payments from any app - eit...
@nprofile1q...
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.
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.
Why are none of the PC2.0 hosting companies stepping up to host metadata for their podcasters?
As an app dev, I'd be more than happy to POST the metadata that was in a TLV record to your server so y...
@nprofile1q...
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.
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.
2
