@francosolerio @ericpp @dave @ChadF @podcastguru @sirtjthewrathful @adam to make it available to Helipad what could be the key to fetch metadata for a particular transaction? I guess the preimage and hash could work? Or maybe we should introduce some kind of special ids…

@ChadF @podcastguru @sirtjthewrathful @adam @dave Or Helipad could theoretically pull some data from Nostr. Or maybe podcast players would put a link to metadata into the bolt11 comment field and Helipad would pull that... I wonder what devs of Helipad think about all this.

@ChadF @podcastguru @sirtjthewrathful @adam @dave I wonder if it could be extended with a small HTTP server. The apps would send boost metadata to it...

@podcastguru @sirtjthewrathful @ChadF @adam @dave Regarding the Helipad thing that everyone seems to use - could someone explain to me what it is and how it works? Is it a standalone app or some web service or some Alby plugin or something else?

@podcastguru @sirtjthewrathful @ChadF @adam @dave It looks like the biggest concern on the podcasters' side right now is about the lack of metadata. We put the boostagram message into the comment field for bolt11, but that's often too short.

@ChadF @adam @dave @podcastguru Hopefully more podcasters will switch to lnaddress (Strike doesn't support keysend).

@dave @steven @podcastguru Jason was working with that on our side, maybe he remembers something. 😀

@russell @podcastguru Thank you for the suggestion! We use default native players on both Android and iOS and they seem to handle HLS just fine. We'll see what we can do about quality selection/switching.

@mikeneumann @Kolomona @StevenB @merryoscar @dovydas @adam @francosolerio @dave It's a small json file. /options wasn't really widely accepted, so the idea is to use /keysend now for exactly the same purpose. Here's an example: https://getalby.com/.well-known/keysend/alexrba

@Kolomona @StevenB @merryoscar @dovydas @adam @francosolerio @dave If you have a keysend address in something like https://getalby.com/.well-known/keysend/username then podcast players can detect that and prioritise keysend over bolt11. At least that's what we are doing in Podcast Guru (technically we're looking at the "/options" URL instead of "/keysend", but we'll change that soon).