Current project: open channels and learn about liquidity and fees.
Here's a 25-minute presentation on Podcasting 2.0 and Value for Value:
(0:32) Applications of crowdsourcing
(3:12) Amanda Palmer: To ask without shame (2013)
(4:55) Adam Curry: Podcasting (2000) in the RSS specification (2004)
(5:30) First podcast index, absorbed into iTunes
(6:09) Creating an RSS file
(7:12) Podcasting 2.0 (2020)
(8:21) Incorporation of the Lightning network
(9:43) Medium tag
(10:03) valueRecipient tag
(11:12) Music album as podcast: Stay Awhile
(11:41) How to get a modern podcast app
(11:57) Value for Value and the No Agenda Show
(13:02) My first V4V projects
(13:13) Curiocaster: Podcasting 2.0 player that runs in your browser
(13:40) Setting up a Lightning node on a Raspberry Pi computer (RaspiBlitz)
(14:25) Satoshis (100 million Satoshis = 1 Bitcoin)
(16:51) Public key goes into Value block
(16:56) Helipad monitors incoming donations
(19:34) Demo of sending sats (from Curiocaster) and then seeing them come into the node (in Helipad)
(22:21) musiccasting.org - --onboarding musicians to Podcasting 2.0 and Value for Value
(23:00) Podcasting 2.0 podcast with background tracks for some of the songs that are included in Jim Beloff's classic, THE DAILY UKULELE, published by Hal Leonard.
(23:26) SongSync app---Value for Value project to support synchronizing lyrics on phones
An open, independent podcasting ecosystem with a Bitcoin payment system option and inspired by the Value for Value support model.
Podcast Index is a software developer focused partnership that provides tools and data to anyone who aspires to create new and exciting Podcast experiences without the heavy lifting of indexing, aggregation and data management.
Podcasting 2.0 podcast: Dave and Adam's board meeting for developers, hosting companies, and content creators
AbleKraft podcast: Able and Spencer report on their pioneering work with Decentralized Music (DeMu) to support music production with avant-garde distribution
You'll need a node to receive Bitcoin from supporters. I decided to get an operate a Lightning node running on a Raspberry Pi computer. I have also set up a second node using the Voltage service. I will still need to open channels and maintain liquidity, but the node itself should be more robust.
Try Alby, an easy way for creators to receive v4v in-browser payments and boostagrams
. The Voltage website says that the quality of a channel depends on how central it is to the wider network, and that the channels that peer has going out are on average the same size or bigger than the channel you have with them. You can see stats on Terminal Web and Amboss.
The greater quantity of channels you have open, the greater the chance will succeed. About 10 channels is the sweet spot. The dependability of your peers depends on how much of the time they are online.
Liquidity - After opening a channel you have to create some liquidity by transferring sats to the remote side if you want to receive sats, and sats on your local side if you want to send them
Loop - a service provided by Lightning Labs to user on-chain transactions to maintain liquidity, allowing you to adjust your channel balances, to move local side to remote side balances, or vice versa
Balancing - If a channel only has liquidity on one side and someone tries to route through this channel in the "wrong" direction - the payment will fail