Adam Curry promoted [podcastindex.org](podcastindex.org) which is the project page for what he calls Podcasting 2.0. It’s basically a namespace addition for RSS feeds that allows for inclusion of a value XML tag where a lightning node can be specified so creators can receive boosts (I.e. one time payments) and streaming payments per a specific interval. It’s called Value4Value and meant to give podcast creators a way to monetize the podcast without being concerned with finding ads to promote or possibly self censorship because an ad partner doesn’t approve of certain content. It’s a noble idea to preserve decentralized censorship free podcasting.
To enable this one has to obviously edit the RSS feeds, which most podcasters won’t be able to since they don’t self host but use a 3rd party podcasting service. To mitigate this, podcastindex.org has a list of all podcast to which you can add yours through podcasterwallet.com where a lightning node id can be entered. All apps/services using podcastindex.org as their feed source will then be served the feed and the new tag with the node id. Through a growing number of podcast apps and websites one can now listen to those Value4Value enabled podcasts and fund a wallet which will then be used to “stream” payments to the podcast creator and send boost payments.
It’s a pretty involved process for the podcast creator, most aren’t technically enough inclined to figure out how this all ties together. On top of that it uses lightning and you have to run a node or use a service that does that for you. So a pain in the but to develop for compared to the good old node RPC api.
Two thoughts: I think BCH is a better candidate for this for both podcast creators (no need to mess around with lightning) and developers. The other issue I have is that enabling Value4Value has to be done by modifying the RSS feed in a way most podcasters won’t be able to (hence the proxying by podcastindex.org) wouldn’t it be easier if podcasters could just add their BCH address somewhere in the episode description? This also has the added benefit that podcastindex’s feed API then doesn’t become the single point of failure.
Any thoughts on podcasting 2.0 in general or if it’s worth developing a site/app with BCH support?