Post #1573302

2025-11-07 17:57 UTC

@StevenB @alecksgates @ericpp @francosolerio @js yes the easiest way to implement this is that the apps host the metadata via their own content urls - just like we are doing here - https://fountain.fm/episode/JCIzq3VyFKQVkEzVNA8v?payment=5XIAt66P29Iv6rjSTZUB and I believe @podcastguru were experimenting with however - for apps that don't have a server - this proposal still caters for them because any third party service could generate the url for the app to use when sending the payment

Replies (1)

@StevenB@podcastindex.social 2025-11-07 18:05

@merryoscar @alecksgates @ericpp @francosolerio @js Correct me if I'm misunderstanding, but in that case, I would: 1. send the metadata from my app to someone else's server to host 2. that server would send me a url to access the data 3. I would make the payment and include the url in the description 4. I would send verification of payment back to the hosting server

Open ##1573303