Alex (Podcast Guru)

Public Key

npub1uvhgq8c4n0lz9xkw9f36whkg4ly6u4uulcw8684fctnl4xejmm8s8hs2x4

NIP-05 Address

algrid@podcastindex-social.mostr.pub

Profile Code

nprofile1qqswxt5qru2ehl3znt8z5ca8tmy2ljdw27w0u8rar65u9el6nvedancpz4mhxue69uhhyetvv9ujuerfw36x7tnsw43qms8plk

Publishing to

relay.ditto.pub

Author Public Key

npub1uvhgq8c4n0lz9xkw9f36whkg4ly6u4uulcw8684fctnl4xejmm8s8hs2x4

Show more details

Last Notes

2026-02-09 16:04:17 UTC

- reply

@nprofile…w0mx @nprofile…cn7u @nprofile…k8p7 @nprofile…ax8n I hope it won't break the Helipad integration, anyway, I will let you know when/how we change it (hopefully soon).

2026-02-09 16:02:40 UTC

- reply

@nprofile…k8p7 @nprofile…w0mx @nprofile…cn7u we'll keep our own format for now, but we'll see in the future, I'm not excluding anything.. :)

2026-02-09 15:57:26 UTC

- reply

@nprofile…w0mx @nprofile…cn7u @nprofile…k8p7 That should be possible, I will work on it. It will have to wait for the next update of Podcast Guru for iOS and Android though (old app versions will keep sending it in the old format).

2026-02-02 13:13:15 UTC

- reply

@nprofile…w0mx @nprofile…cn7u 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.

2026-01-31 22:20:07 UTC

- reply

@nprofile…w0mx @nprofile…cn7u @nprofile…td70 @nprofile…dffe @nprofile…k8p7 @nprofile…7epg 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.

2026-01-31 19:23:54 UTC

- reply

@nprofile…cn7u @nprofile…td70 @nprofile…w0mx @nprofile…dffe @nprofile…k8p7 @nprofile…7epg 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..

2026-01-14 10:38:22 UTC

- reply

@nprofile…dcmx @nprofile…w0mx @nprofile…peg3 Thank you! That's exactly what I need for testing :)

2026-01-13 16:55:35 UTC

Haven't found a single podcast having podcast:socialInteract at the channel level. No one does that?

2025-12-05 20:04:59 UTC

@nprofile…y5nd @nprofile…wsp3 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...

2025-10-31 18:15:52 UTC

- reply

@nprofile…y5nd No HLS/video today?

2025-10-14 20:20:25 UTC

How does V4V metadata look on the podcasters' side when sats streaming is used? Does it look like a bunch of small boost entries? Or maybe Helipad somehow combines multiple stream payments into one entry? @nprofile…amf2 @nprofile…5yxp

2025-10-11 20:48:48 UTC

- reply

@nprofile…6746 @nprofile…ye27 It fails on the XML parsing stage. The title and description fields contain raw ampersand symbol, which is not allowed in XML. It should be escaped: &

2025-10-11 20:19:09 UTC

- reply

@nprofile…6746 @nprofile…ye27 Yes, we added support for remoteItem-based playlists a while ago. If you send me the feed URL that doesn't work, I can check what's wrong with it.

2025-10-02 14:24:14 UTC

- reply

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.

2025-10-02 14:21:27 UTC

Are there any podcasts still using/having Atom feeds? Or pretty much everyone is on RSS 2.0 now?

2025-08-23 17:47:27 UTC

- reply

@nprofile…6746 Two separate podcast:value tags with different type/method would work better, I guess. To avoid confusion during splits calculation.

2025-08-20 09:47:00 UTC

- reply

@nprofile…r3p6 @nprofile…6746 @nprofile…mp2c something very close to that, I will post an example when we have a prototype running.

2025-08-18 20:51:46 UTC

- reply

@nprofile…6746 Awesome, thank you!

2025-08-18 16:54:49 UTC

- reply

@nprofile…pvn3 @nprofile…mp2c @nprofile…6746 Valid concerns. Having a whitelist for such URLs and a VPN or Tor as you said for those who really don't want to disclose their IP should mitigate that.

2025-08-18 16:41:48 UTC

- reply

@nprofile…pvn3 @nprofile…mp2c @nprofile…6746 We're going to put a link to the metadata json file into the comment field. Maybe we'll prefix it with something to make it detectable. Something like "V4V: https://link.to.metadata".

2025-08-18 16:23:11 UTC

- reply

@nprofile…mp2c @nprofile…6746 @nprofile…pvn3 do you have any experience with bolt11 transactions in Helipad? Is the bolt11 comment always present in transaction data (if it was included during the invoice generation)?

2025-08-18 16:18:20 UTC

- reply

@nprofile…6746 @nprofile…mp2c Thanks, but I can do that on my side too, just hack it programmatically. That's a good idea: at least I will be able to test it with our own Strike and Alby wallets.

2025-08-18 16:16:04 UTC

- reply

@nprofile…mp2c @nprofile…6746 Thank you for the clarification. So what I see as a sender isn't a good indicator. Regarding the description vs comment - can I, as a sender, somehow set the description? Or it's exclusively set by the receiver side when an invoice is created?

2025-08-18 16:01:13 UTC

- reply

@nprofile…6746 @nprofile…mp2c We're going to put a link to full transaction metadata into the bolt11 comment field, but we want to make sure that people will be able to see it at the receiving end.

2025-08-18 15:56:49 UTC

- reply

@nprofile…6746 @nprofile…mp2c Thank you! That's keysend as far as I can see. Could you check bolt11 transactions (maybe later when you have a chance)?

2025-08-18 15:21:51 UTC

- reply

@nprofile…6746 @nprofile…mp2c are bolt11 comments supposed to be always displayed by Alby Hub in transaction details? Or it can be something on the wallets side?

2025-08-18 15:20:03 UTC

- reply

@nprofile…6746 The behaviour in my Alby Hub is a bit strange: I can only see the comment string for Zeus (prepended with "ZEUS Pay:"). No comment is displayed for Strike and Primal. And even for Zeus it looks like it's not coming through 100% of times.

2025-08-18 15:17:13 UTC

@nprofile…6746 I'm using your LNURL testing feed to test how bolt11 comments are handled/displayed. Putting a dummy URL into the comment field now. Can you see it at your end?

2025-07-24 14:58:32 UTC

- reply

@nprofile…6746 @nprofile…6wtl That's cool, thank you!

2025-07-19 16:21:11 UTC

- reply

@nprofile…6746 @nprofile…r3p6 @nprofile…0z88 if it's for OAuth with Alby you should register your callback URL and get a clientId for your project. I'm not sure it can be done in their web interface or you need some assistance from them. In our case they helped us and did it for us manually if I recall correctly, but it was quite a while ago.

2025-07-14 10:18:40 UTC

- reply

@nprofile…3wj7 I get "java.net.SocketTimeoutException: failed to connect to live.beer-n-gear.com/47.223.49.201 (port 8443) from /192.168.0.12 (port 33190) after 8000ms" when I try it on Android.

2025-07-09 13:45:04 UTC

- reply

@nprofile…h82d It used to be a simple text/link. Did it evolve into something bigger/more specialised?

2025-07-08 21:16:25 UTC

- reply

@nprofile…pvn3 @nprofile…r3p6 @nprofile…h82d @nprofile…6746 @nprofile…ye27 @nprofile…wuyh @nprofile…zn42 DDoS is always a really hard thing to fight. Sometimes it’s better just to wait for it to happen instead of trying to prepare for everything in advance. 😂 But in this case at your side you could probably just have a white list of acceptable hosts discarding all the other.

2025-07-08 17:05:26 UTC

- reply

@nprofile…pvn3 @nprofile…r3p6 @nprofile…h82d @nprofile…6746 @nprofile…ye27 @nprofile…wuyh @nprofile…zn42 we will probably try to implement it. Will store the metadata on our backend and will put the corresponding link into the bolt11 comment.

2025-07-06 15:05:38 UTC

- reply

@nprofile…r3p6 @nprofile…pvn3 @nprofile…h82d @nprofile…6746 @nprofile…ye27 @nprofile…wuyh @nprofile…zn42 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…

2025-07-05 23:45:15 UTC

- reply

@nprofile…6746 @nprofile…ye27 @nprofile…wuyh @nprofile…zn42 @nprofile…h82d 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.

2025-07-05 23:43:07 UTC

- reply

@nprofile…6746 @nprofile…ye27 @nprofile…wuyh @nprofile…zn42 @nprofile…h82d I wonder if it could be extended with a small HTTP server. The apps would send boost metadata to it...

2025-07-05 23:04:12 UTC

- reply

@nprofile…ye27 @nprofile…wuyh @nprofile…6746 @nprofile…zn42 @nprofile…h82d 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?

2025-07-05 23:01:46 UTC

- reply

@nprofile…ye27 @nprofile…wuyh @nprofile…6746 @nprofile…zn42 @nprofile…h82d It looks like the biggest concert 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.

2025-07-03 09:38:44 UTC

- reply

@nprofile…6746 @nprofile…zn42 @nprofile…h82d @nprofile…ye27 Hopefully more podcasters will switch to lnaddress (Strike doesn't support keysend).

2025-06-23 14:01:52 UTC

- reply

@nprofile…h82d @nprofile…zpec @nprofile…ye27 Jason was working with that on our side, maybe he remembers something. 😀

2025-05-29 10:14:20 UTC

- reply

@nprofile…326g @nprofile…ayy4 @nprofile…7xwn @nprofile…2d4u @nprofile…s2q5 @nprofile…zn42 @nprofile…r3p6 @nprofile…h82d 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

2025-05-28 14:01:06 UTC

- reply

@nprofile…ayy4 @nprofile…7xwn @nprofile…2d4u @nprofile…s2q5 @nprofile…zn42 @nprofile…r3p6 @nprofile…h82d 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).

2025-05-28 13:44:23 UTC

- reply

@nprofile…mp2c @nprofile…pvn3 We use it to determine if a podcaster can accept keysend payments. If both user's wallet & receiving side can do keysend, then it's the preferred way - to be able to send the boost metadata in TLV.

2025-05-27 17:45:27 UTC

- reply

@nprofile…pvn3 yes, I know about the "/keysend", but I was under the impression that "/options" used to work. We're still using it, though switching to "/keysend" is in our immediate plans.

2025-05-27 17:39:48 UTC

Was the "options" query support already removed by Alby? I mean https://getalby.com/.well-known/lnurlp/username/options

2025-05-14 13:32:08 UTC

- reply

@nprofile…6746 @nprofile…r3p6 @nprofile…7xwn @nprofile…pvn3 @nprofile…h82d @nprofile…zn42 What is NWC? Is it a protocol for work with crypto wallets? Or some kind of middleware that needs to be deployed somewhere?

2025-05-14 10:29:36 UTC

- reply

@nprofile…r3p6 @nprofile…7xwn @nprofile…6746 @nprofile…pvn3 @nprofile…h82d @nprofile…zn42 Alby also supports bolt11, so technically there's no need to switch (if you use Alby). Otherwise I agree, it's not easy...

2025-05-14 10:12:22 UTC

- reply

@nprofile…r3p6 @nprofile…7xwn @nprofile…6746 @nprofile…pvn3 @nprofile…h82d @nprofile…zn42 I think it should be possible to switch to lnaddress keeping the compatibility with the previous approach. .well-known/keysend (or the "options" file) should help with that. Podcasters shouldn't loose anything in terms of functionality. I mean getting more payments even without TLV is better than nothing. And old payments when keysend is supported will keep coming with TLV.

2025-05-14 09:53:50 UTC

- reply

@nprofile…r3p6 @nprofile…7xwn @nprofile…6746 @nprofile…pvn3 @nprofile…h82d @nprofile…zn42 If listener's wallet doesn't support keysend then it's a bolt11 payment (no TLV) or nothing. For such cases metadata can go to the comment field or maybe eventually we'll agree on a different solution for metadata (separate HTTP server or nostr or something else...).

2025-05-13 17:41:44 UTC

- reply

@nprofile…7xwn Oh, I didn't know that, thanks! I may need to change my code too then.

2025-05-13 17:38:12 UTC

- reply

@nprofile…7xwn I'm doing a similar thing (only trying the "options" request instead of "/keysend" if I recall correctly). But in this case I'm testing integration with Strike which only supports bolt11.

2025-05-13 17:35:26 UTC

- reply

@nprofile…g5pf I was able to find one: "Randy Black (Strike)", it seems to work. 😀

2025-05-13 17:25:36 UTC

At least Podcasting 2.0 has a couple of "lnaddress" recipients. 🙃 Are there any other podcasts with V4V recipients using "lnaddress"?
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/501/688/731/881/834/original/ec6434303d6caea7.png

2025-05-13 14:13:30 UTC

- reply

@nprofile…pvn3 @nprofile…6746 @nprofile…7xwn I see, so the webserver talking to the lightning node and generating invoices can be the missing part. That makes sense.

2025-05-13 14:05:12 UTC

- reply

@nprofile…9a0n If you can send me your lnaddress I can try to do a tiny payment from Alby or Strike and see if I'm getting an error there. Or if you think it's about the xml tags being incorrect I can take a look and test it too.

2025-05-13 13:59:19 UTC

- reply

@nprofile…7xwn @nprofile…6746 @nprofile…pvn3 @nprofile…h82d @nprofile…zn42 I just hope that for podcasters supporting lnaddress isn't a big problem - I don't know how it looks technically on their side. Like if they have an AlbyHub node, it should support lnaddress, is that correct?

2025-05-13 13:57:05 UTC

- reply

@nprofile…7xwn @nprofile…6746 @nprofile…pvn3 @nprofile…h82d @nprofile…zn42 I agree. Technically keysend is nice, but I think it's more important to allow V4V payments from as many payment providers/wallets as possible. And lnaddress/bolt11 looks like a step in that direction.

2025-05-13 10:37:37 UTC

- reply

@nprofile…6746 @nprofile…7xwn @nprofile…pvn3 I don't really understand in details how it works, but people running their own nodes - can't they accept lnaddress/bolt11 payments? I thought that's kind of a standard thing that most should support.

2025-05-13 10:01:30 UTC

- reply

I'm asking because we're making a good progress implementing our integration with Strike, but they only support bolt11 payments.

2025-05-13 10:00:07 UTC

I'm wondering what's limiting the lnaddress adoption for V4V currently? Are the podcasters unwilling to switch to it because podcast players may not support it or are there any other problems?

2025-05-09 10:58:07 UTC

- reply

@nprofile…v2ca @nprofile…h82d @nprofile…mg8l Works in Podcast Guru
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/477/516/213/379/597/original/f25c7143376cb7fe.png

2025-04-24 15:10:31 UTC

- reply

@nprofile…26p9 AI we deserve 😂

2025-04-15 12:20:03 UTC

- reply

@nprofile…2d4u @nprofile…srvr @nprofile…ye27 @nprofile…3ram @nprofile…7xwn @nprofile…7te3 @nprofile…r3p6 We do support it in Podcast Guru.

2025-04-08 16:56:21 UTC

- reply

@nprofile…h82d sorry to bother you again with it, did you have a chance to take a look at that request?

2025-04-04 09:42:05 UTC

- reply

@nprofile…6mrn I'm talking about the normal feeds. Some of them don't wrap the remoteItem tag into the publisher tag:
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/279/033/994/427/783/original/012d68cccf3bfb3b.png

2025-04-03 16:56:59 UTC

Regarding the "publisher" feeds: some podcasters don't put the "publisher" tag into the feed, instead they just add a "remoteItem" on the "channel" level with medium="publisher". 🤔

2025-03-31 15:24:48 UTC

- reply

@nprofile…v2ca @nprofile…3ram @nprofile…h82d @nprofile…2d4u That's really interesting. I wonder if hosters who add dynamic ads can (or maybe do) use that header to prevent players from breaking when the served dynamic ad suddenly changes?

2025-03-31 10:48:31 UTC

- reply

@nprofile…h82d Sure, sent to the "info" email. 😀

2025-03-28 17:24:26 UTC

- reply

@nprofile…h82d btw, does that batch endpoint have a limit number of requested podcasts? I'm hitting it with 238 of ids right now and get only 26 podcasts in return 🙂

2025-03-28 16:44:23 UTC

- reply

@nprofile…h82d @nprofile…ye27 non-unique "guids" are real PITA 😖

2025-03-28 16:42:13 UTC

- reply

@nprofile…h82d @nprofile…ye27 getting some duplicates with the same guids like this one:
guid=66162162-76b3-54c2-b519-096ccd887a6f, feedUrl=https://music.behindthesch3m3s.com/wp-content/uploads/Empath Eyes/East To West/east to west.xml
guid=66162162-76b3-54c2-b519-096ccd887a6f, feedUrl=https://music.behindthesch3m3s.com/wp-content/uploads/Empath%20Eyes/East%20To%20West/east%20to%20west.xml

2025-03-28 10:29:06 UTC

- reply

@nprofile…h82d @nprofile…ye27 I didn't know that you have a guid batch endpoint. Will switch to it instead of individual requests, it's going to be a great improvement!

2025-03-28 10:27:17 UTC

- reply

@nprofile…h82d @nprofile…ye27 no, not from PI. We're getting 429 fetching a ton of RSS feeds from wavlake.com.

2025-03-27 19:03:56 UTC

- reply

@nprofile…h82d hah, interesting 🙃

2025-03-26 23:11:50 UTC

- reply

@nprofile…h82d does speak:never work? https://www.w3.org/TR/css-speech-1/#speaking-props-speak

2025-03-26 18:42:19 UTC

Playlists based on remote items when they are big are really hard to handle. When you are trying to "resolve" all the episodes at once you end up downloading 100s of feeds and eventually get hit by HTTP 429 (too many requests). You can "resolve" the episodes dynamically when they are displayed, but this approach has it own limitations. I wonder if it would be better to also include some actual episode info in addition to the feedGuid/itemGuid?

2025-03-17 20:16:30 UTC

- reply

@nprofile…6746 @nprofile…srvr @nprofile…mjk8 just a typo in the RSS feed, they missed a decimal point in the duration value.

2025-03-17 20:08:25 UTC

- reply

@nprofile…6746 @nprofile…srvr @nprofile…mjk8 Causes this in Podcast Guru (though it's for time splits, not chapters)
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/179/578/136/832/064/original/32fdc8a4564ca1b1.png

2025-03-17 19:59:55 UTC

- reply

@nprofile…6746 @nprofile…srvr @nprofile…mjk8 looks like the duration is wrong in the second timesplit for that episode (not sure if it's related)
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/179/537/771/947/831/original/ea97baae1a2b67c7.png

2025-03-16 19:53:41 UTC

- reply

@nprofile…ayy4 @nprofile…h82d Awesome, thank you!

2025-03-16 19:45:46 UTC

- reply

@nprofile…ayy4 @nprofile…h82d Thanks! Can confirm that it works on my side now.
Btw, can you share a couple of other such feeds if you know any? I need it for testing.

2025-03-16 19:34:35 UTC

The "Boostagram Ball Playlist 1 to 25" feed contains a wrong podcast namespace: xmlns:podcast="https://github.com/Playlistindex-org/podcast-namespace/blob/main/docs/1.0.md" (it contains "Playlistindex-org" instead of "Podcastindex-org"). Took me some time to figure out why the parsing was breaking 🙃 @nprofile…h82d @nprofile…ayy4

2025-03-05 17:57:04 UTC

- reply

@nprofile…s2q5 awesome, thank you!

2025-03-05 17:46:03 UTC

- reply

@nprofile…s2q5 Thank you! Do I understand correctly that those feeds are the "publisher" feeds and there are some other feeds that point to them in their podcast:publisher tags?

2025-03-05 16:53:28 UTC

Can someone suggest me any RSS feeds using the podcast:publisher tag? Adding support for it right now.

2025-02-16 17:09:39 UTC

- reply

@nprofile…7xwn @nprofile…wuyh What we're doing: we use the info from the feed (because we have it cached or fetch it anyway). And if the feed has no value block - only then we make a call to the Index.

2025-02-15 13:40:13 UTC

- reply

@nprofile…7xwn @nprofile…wuyh hmm, I always considered the feed to be the primary source of truth and the Index is rather a workaround for those who are unable to include the relevant information into the feed.

2025-02-12 19:07:17 UTC

- reply

@nprofile…zn42 That's great! 😅 Adding basic V4V info to the "comment" field for bolt11 payments.

2025-02-06 18:28:05 UTC

- reply

@nprofile…7xwn Yep, we got a business account there. Just had a meeting with them, hopefully we'll be able to implement OAuth & integrate their API.

2025-02-06 18:24:59 UTC

- reply

@nprofile…7xwn oh, I didn't know about .well-known/keysend. In theory it should be the same keysend address as in the options.

2025-02-06 17:49:16 UTC

- reply

@nprofile…7xwn I think the original idea with lnurlp options lookup wasn't that bad. The main method of accepting lightning could become bolt11, but those who support keysend could make it resolvable too and apps could dynamically detect that.

2025-01-06 15:57:04 UTC

- reply

@nprofile…7xwn @nprofile…3ram hmm, I would expect Steven's version to be the correct one. podcast:valueTimeSplit at the top (channel) level is a bit strange. But maybe I'm missing something, we don't support it yet in Podcast Guru.

2024-12-16 14:50:59 UTC

- reply

@nprofile…7xwn ouch, I don't even know what's that. Some US tax system stuff?

2024-12-10 12:41:58 UTC

- reply

@nprofile…2d4u @nprofile…mp2c does lnaddress necessarily mean bolt11? I thought the options file can specify several options, like both bolt11 and keysend so that the paying side can decide which one it prefers/can use.

2024-12-10 10:50:48 UTC

Regarding the "method" attribute of the podcast:value tag. In the specs it's marked as required. We used to have "keysend" there. Now that people are transitioning to lnaddress - do we omit the "method" at the podcast:value level completely? Fountain Radio feed doesn't have it. @nprofile…2d4u @nprofile…h82d @nprofile…7xwn

2024-12-06 14:35:55 UTC

- reply

@nprofile…7xwn and one also needs to get a "business account" from them as far as I understand.

2024-08-27 14:57:38 UTC

- reply

@npub1ln5…xyw6 Thanks! I can see the update for 1552623721. But 1521703224 still returns an incorrect feed URL.

2024-08-27 14:49:55 UTC

@npub1ln5…xyw6 Hi! We had been contacted recently by a couple of podcast authors about incorrect/outdated data for their podcasts. The data comes from podcastindex.org API. What's the right way for podcast authors to update their data?

2024-07-10 14:31:48 UTC

This week we had several users complaining about their podcasts (audio files actually) becoming inaccessible. This happens for podcasts redirecting to mgln.ai. Apparently some ad block/firewall software blocks that host. Particularly I can see NordVPN's Threat Protection mentioned in the logs that I have. I guess they don't like that this host is used for analytics or something like that...