Posts by algrid@podcastindex.social
(DIR) Post #AvqQd1LM1AZvVXVa1w by algrid@podcastindex.social
2025-07-05T23:01:46Z
0 likes, 0 repeats
@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.
(DIR) Post #AvqQd2XnYO7vEQL248 by algrid@podcastindex.social
2025-07-05T23:04:12Z
0 likes, 0 repeats
@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?
(DIR) Post #AvqQd42fz4Q7sTnCpk by algrid@podcastindex.social
2025-07-05T23:43:07Z
0 likes, 0 repeats
@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...
(DIR) Post #AvqQd4m3GMiU9D1RYm by algrid@podcastindex.social
2025-07-05T23:45:15Z
0 likes, 0 repeats
@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.
(DIR) Post #AvxUl5c9mXY8zgBqts by algrid@podcastindex.social
2025-07-09T13:45:04Z
0 likes, 0 repeats
@dave It used to be a simple text/link. Did it evolve into something bigger/more specialised?
(DIR) Post #AwUS2PC8cePqw1MwAC by algrid@podcastindex.social
2025-07-06T15:05:38Z
0 likes, 0 repeats
@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…
(DIR) Post #AwUS2VstkaBXgNQAe8 by algrid@podcastindex.social
2025-07-24T14:21:06Z
0 likes, 0 repeats
@ChadF @ericpp @francosolerio @dave @podcastguru @sirtjthewrathful @adam That's really useful, thank you for sharing it!
(DIR) Post #AwUS2WlqSI8aQn83I8 by algrid@podcastindex.social
2025-07-24T14:21:41Z
0 likes, 0 repeats
@ChadF @ericpp @francosolerio @dave @podcastguru @sirtjthewrathful @adam btw, https://btcpay.podtards.com/.well-known/lnurlp/chadf seems to not work - returns HTTP code 502 to me.
(DIR) Post #AyOuX0ZaH8oN9MeyLw by algrid@podcastindex.social
2025-09-20T14:55:18Z
0 likes, 0 repeats
@dave we do support HLS for a long time already. But we don’t support alt enclosure. It requires adding the choice which URL to play/download into the UI. Or we have to decide that automatically… Kind of complicates the UX and app’s logic.
(DIR) Post #AyoX6nqIXtQ8iSbAum by algrid@podcastindex.social
2025-10-02T14:21:27Z
0 likes, 0 repeats
Are there any podcasts still using/having Atom feeds? Or pretty much everyone is on RSS 2.0 now?
(DIR) Post #AyoX6pTgSwWHmu28wa by algrid@podcastindex.social
2025-10-02T14:24:14Z
0 likes, 0 repeats
I'm looking at YouTube feeds which are in Atom format, but their "application/x-shockwave-flash" media type makes them basically useless for any podcast player, unless that podcast player simply loads a web view with YouTube web player.
(DIR) Post #AzTDBQCjpJxtFXNPzU by algrid@podcastindex.social
2025-10-22T13:32:46Z
0 likes, 0 repeats
Podcasting 2.0 Episode 238 has an alternateEnclosure tag that points to https://hls.podcastindex.org/pc20_236.m3u8 which is for Episode 236 as far as I can tell. It that a mistake or I'm missing something? @dave
(DIR) Post #AzTLaiaJQSnh7yybsO by algrid@podcastindex.social
2025-10-22T16:09:28Z
0 likes, 0 repeats
@dave @adam also type="application.x-mpegURL" should probably be type="application/x-mpegURL". It's correct in one place, but for other alternateEnclosure tags it's with "." instead of "/".
(DIR) Post #AzmBUv7QhU7lr9SLku by algrid@podcastindex.social
2025-10-31T18:15:52Z
0 likes, 0 repeats
@dave No HLS/video today?
(DIR) Post #B0x6DIHVbHS40LdNlg by algrid@podcastindex.social
2025-12-05T20:04:59Z
0 likes, 0 repeats
@dave @adam Is there a reason why you keep alternateEnclosure with an inactive HLS stream for Podcasting 2.0 liveItems? We're preparing a new version of Podcast Guru that automatically picks up and uses alternateEnclosure if it's present and it's an HLS stream. As a result our beta version now plays a short "This stream is offline" video instead of proper live stream. I wonder if we should address that somehow or it's just a mistake in the RSS feed...
(DIR) Post #B0yJVcd2BKTasvjT6m by algrid@podcastindex.social
2025-12-06T12:34:16Z
0 likes, 0 repeats
@adam @dave No problem, thank you!
(DIR) Post #B2LWj9C1BBzr0VXXqy by algrid@podcastindex.social
2026-01-16T13:55:53Z
0 likes, 0 repeats
@ChadF @UpBEATs When I try it, the PodcastIndex LN Test Wallet resolves to a keysend address, but the payment fails with Alby API returning {"error":true,"code":6,"message":"NodeError: PaymentSendingFailed: Failed to send the given payment."}
(DIR) Post #B32vM5Zkkm3Kph7ILA by algrid@podcastindex.social
2026-01-31T19:23:54Z
0 likes, 0 repeats
@podcastguru @dave @james @samsethi @merryoscar @adam If I recall correctly we have a boost vs stream flag in our metadata (basically it’s the same metadata that’s going with keysend payments). If that helps..
(DIR) Post #B32vM879JZxGhqkzfk by algrid@podcastindex.social
2026-01-31T22:20:07Z
0 likes, 0 repeats
@james @podcastguru @dave @samsethi @merryoscar @adam yes, in our case the information is inside the json that you can fetch by accessing the url following V4V. The description field can be too short to put actual data there, that’s why we only put a url there.
(DIR) Post #B32vM9xITBGKPsA9aq by algrid@podcastindex.social
2026-02-02T13:13:15Z
0 likes, 0 repeats
@james @podcastguru yes, I guess we should be able to enable CORS there, thanks for the reminder. And we'll see what we can do about the data format. Not sure about completely changing it to the Fountain spec, but we can try to include a hint into the bolt11 description to distinguish boost vs stream payments. Like V4VB:... or V4VS:... prefix depending on the case or something like that.