Alex (Podcast Guru)

Public Key

npub10lzhk0n62my24p0u0zqw489j4lgkxxlzpwqs0xzazjxqj54t6y3s0jtuwr

NIP-05 Address

algrid_at_podcastindex.social@momostr.pink

Profile Code

nprofile1qqs8l3tm8ea9dj92sh783q82nje2l5trr03qhqg8npw3frqf224azgcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsxfxwa0

Publishing to

saltivka.org

relay.damus.io

nos.lol

Author Public Key

npub10lzhk0n62my24p0u0zqw489j4lgkxxlzpwqs0xzazjxqj54t6y3s0jtuwr

Show more details

Last Notes

2025-01-21 17:59:41 UTC

- reply

I can see occasional "URLSessionTask failed with error: cannot decode raw data" in our iOS logs. Which can be related to compression in theory. It's really rare and I can't reproduce it. Will keep an eye on it though.

2025-01-19 16:24:21 UTC

- reply

For keysend payments we send the data as usual, but for bolt11 we send no data at all currently. There's no universally accepted way of doing it. Once the community agrees on something, we'll definitely add it.

2024-09-03 15:34:34 UTC

- reply

But I'm not sure... One of the reasons we did not add it is that we don't have a 100% guarantee that your sats weren't sent when we have such a "failed" boost. If network fails after we sent a payment request and before we got a response, Alby could execute the payment, but the app will register an error. It's a rare situation, but it can happen.

2024-09-03 15:30:10 UTC

- reply

If it's about the situation when the whole boost is marked as "failed" (like on the picture), then in theory we could add a "Retry" button.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/113/074/330/020/007/818/original/b62e9508ba7edea5.png

2024-09-03 14:17:25 UTC

- reply

When payments fail for some recipients it's usually because the address is incorrect (probably outdated). Alby API reports failure when we try to send sats to them. Podcasters should update their feeds and indicate correct addresses to solve that.

2024-08-27 14:57:38 UTC

- reply

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

2024-08-27 14:49:55 UTC

@npub1rcn…dw4h 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?