@nprofile1q... @nprofile1q... @nprofile1q... @nprofile1q... @nprofile1q... Castamatic resolves both channels just fine, custom domains included. I just verified [email protected] returns both lnurlp and keysend. No Alby/Fountain hardcoding.

When an address offers both I go with LNURL-pay: when the push was to move past keysend (P2.0 show: ”not deprecated, but effectively so"), the direction from the Fountain/Alby folks was to prioritize the address lookup: https://github.com/Podcastindex-org/podcast-namespace/discussions/576#discussioncomment-7787922

@nprofile1q... Great. I'll study it during my vacations, I'd like to integrate it into Castaping service.

@nprofile1q... are you sending sats via lightning or stablecoins?

@nprofile1q... Spark/Breez is neat and self-custodial, but there's a V4V blocker: a native Spark transfer carries no metadata: just address + amount + token id. No memo/comment field in the protocol or the Breez SDK, so nowhere for a boostagram (or a link to one), and no in-band id to match off-chain metadata. Lightning has the keysend TLV 7629169 and LNURL comment for this; Spark has neither. Spark is alpha, we as a interest group should push for a payer-note field before native-Spark V4V makes sense.

@nprofile1q... @nprofile1q... @nprofile1q... What puzzles me most is how anyone can think it’s reasonable to lump together under the same “podcasting” label formats with completely different consumption patterns, and therefore completely different CPMs, especially when the stated goal is to unify the advertising market around them.

“Put your ads here, it’s a podcast, $60 CPM. Or put them over there, it’s also a podcast, $4 CPM”. WTF?

@nprofile1q... @nprofile1q... Ciao Alberto, on my show we have a recurring segment “This Week in Piracy Shield”… 😄

https://cdn.masto.host/podcastindexsocial/media_attachments/files/116/549/409/791/300/142/original/6159b9217676da18.mp3

@nprofile1q... @nprofile1q... @nprofile1q... thank you

@nprofile1q... @nprofile1q... @nprofile1q... bug confirmed. Fixing it now, I hope it will be in the store in a few days.

@nprofile1q... thank you chad, that would be great

@nprofile1q... @nprofile1q... Hello Eric. It should already be there, or at least it was. Maybe a bug. Are you sending LnURLp or keysend?

@nprofile1q... yes, the memory leak was pretty bad on older device because if memory constraints. Now it's fixed, so it should improve a lot. Also chapters generation is based on Apple Intelligence, so I have no way to make it work on older phones.