In your example, the rss podcast namespace payment splits are a requirement, as the current advertising based podcast industrial complex is built on opposing philosophy; namely knowing as much as possible about the end user of the download.
Cracking the code of easy listener on-boarding to lightning thus requires custodial payment solutions that in turn require kyc
This is the conundrum.
Podcast content creators need to monetize, censorship resistance is not important to them.
