Post #1291738
2025-11-07 15:23 UTC
@merryoscar @francosolerio
There is a third way.
That host stores the metadata. Each app sends it to the host API found in the feed.
This works well for Fountain as a business. Since you're willing to store metadata, all the apps send it to your API, and if someone wants access to their metadata, they choose a host like Fountain that gives them that data. More people choose Fountain as a host because you offer more services.
Replies (2)
-
@StevenB@podcastindex.social 2025-11-07 15:28
@merryoscar @francosolerio If Fountain has an API, and especially if it's in the feed, I'll be one of the first ones to start sending metadata your way. I'm not able to host it on my own database, but would be more than happy to forward it along to a metadata service.
-
@merryoscar@podcastindex.social 2025-11-07 15:28
@StevenB @francosolerio 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