Why are none of the PC2.0 hosting companies stepping up to host metadata for their podcasters?
-
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 you could build a badass dashboard to show your podcasters their stats.
I'm more than happy POSTing for your podcasters, but I'm not interested in HOSTing.
@StevenB I host chapters for podcasters with PodChapters.com.
And someday when our group finally takes cross-app seriously, I'd like to offer hosting for those with Podgagement.com.
-
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.
-
If I send a Bolt 11 payment from a non-Fountain app, how does Fountain get the metadata?
-
If I send a Bolt 11 payment from a non-Fountain app, how does Fountain get the metadata?
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)
-
@StevenB I host chapters for podcasters with PodChapters.com.
And someday when our group finally takes cross-app seriously, I'd like to offer hosting for those with Podgagement.com.
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.
-
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)
So the app hosts the metadata, and Fountain fetches it?
-
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
-
@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?
-
@merryoscar why can’t we skip the fetching part and I just send it to you direct?
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) 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. -
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.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
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.
-
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.
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)
-
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.
@StevenB @merryoscar Excellent point about the apps.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register LoginWelcome To Podcasting.Chat!
This forum is for podcasters, podcast guests, and podcast enthusiasts alike to share tips, tricks, and their love of the medium.
This forum is fully federated, so you are able to contribute to any discussion here through your own software of choice (e.g. Mastodon, Misskey, Lemmy, Piefed, etc.). So you can sign up for an account here and it federates around the Fediverse. You can also follow feeds and topics from your other Fedi-enabled accounts.
Recent Posts
-
I need another event where I can test out this scavenger hunt web app that I built last year.
I made a bunch of edits to it over the weekend, and it should be a lot easier for folks to take and host their own version with their own game!
Now I need to do real testing with NFC tags (something that I skipped for security purposes the first time), and tag a proper release.
-
#Holos 1.0.0-rc-3 has been published. This release now integrates #HolosDiscover for searches and to display trending. You can also block domains and sync remote blocking lists of domains. You can also import your list of blocked accounts. Account deletion is now possible through the app.
More about this release: https://codeberg.org/tom79/Holos-App/releases/tag/1.0.0-rc-3
Download: https://framadrive.org/s/b68BB42Rf5ogW8o
-
-
exactly , also many incorrect modifications but fasteR iterations than in biological evolution
