fiatjaf's avatar
fiatjaf _@fiatjaf.com 1 year ago
I see, so the answer is the kind 31338? Both fanfares.io and npub.pro could both become RSS bridges sourcing from people's 31338 events instead of kind 1, and publishing a podcast could become a thing that doesn't require a platform, you just publish events and later you use any bridge out there to provide an RSS feed -- until podcast players start connecting to relays directly instead of using RSS (there is a PR to AntennaPod already, we just have to change the kind number and event format). I'm not interested in the Lightning-gated stuff for now, and I think that will be the last thing someone publishing a podcast will worry about, since podcast players won't support it, but I think in the future that could become interesting too.
↑ Parent

Replies (9)

fiatjaf's avatar
fiatjaf _@fiatjaf.com 1 year ago
Kind 31338 is vastly underspecified. "Audio events" is super generic. An audio message is completely different from a podcast episode and both are even more different than a song. I think it's awful that these things got lumped together in the same NIP.
1 replies ↓
arkinox's avatar
arkinox arkinox@team.fanfares.io 1 year ago
@Fanfares is built like this: RSS > Nostr on top Npub Pro sort of turns the flow optionally into this: Kind 1 notes > RSS > Nostr on top FanFares is only using the kind 31338 events for lightning gated podcasts, which won't exist in a typical RSS feed. So the podcast would have a free episode that talks about/links to the gated episode. This is what podcasts already do when they are posting "subscriber only" content. Generally, our approach is adding nostr on top of podcasting 2.0, not trying to replace it.
1 replies ↓
VictorieeMan's avatar
VictorieeMan VictorieeMan@victoriee.com 1 year ago
interesting nostr developments
fiatjaf's avatar fiatjaf
I see, so the answer is the kind 31338? Both fanfares.io and npub.pro could both become RSS bridges sourcing from people's 31338 events instead of kind 1, and publishing a podcast could become a thing that doesn't require a platform, you just publish events and later you use any bridge out there to provide an RSS feed -- until podcast players start connecting to relays directly instead of using RSS (there is a PR to AntennaPod already, we just have to change the kind number and event format). I'm not interested in the Lightning-gated stuff for now, and I think that will be the last thing someone publishing a podcast will worry about, since podcast players won't support it, but I think in the future that could become interesting too.
View quoted note →
Short Fiat's avatar
Short Fiat shortfiat@team.fanfares.io 1 year ago
The current sources of income for podcasters are sponsorship and fiat subscription. Both of these sources can be censored by monetary authorities. If a creator is getting paid in Bitcoin, then they don't even have to dox themselves in order to get paid. Value4value has made a start with this in terms of tipping. At FanFares, we are building on top to make audio content purchasable. Similar in many ways to buying a CD or record. Creators used to earn a lot of money when we had that system. It was basically a process of you pay for it and then you get it. They didn't have to put ads in their content to earn a living.
↑