arkinox's avatar
arkinox arkinox@team.fanfares.io 1 year ago
GM @fiatjaf. Today you can upload a podcast audio file to
Fanfares
Fanfares - Sell your content for zaps
The Internet Money Era of Publishing
 and it will be lightning-gated; each person must pay for it via lightning before they can listen. Once it is unlocked, it belongs to your pubkey and you can listen any time. As a podcaster, you must use Alby to receive zaps, and listeners must pay via Alby, which is a major weakness of the current FanFares platform we will be fixing. We are working on a big version 2 of @Fanfares which will be able to utilize any lightning provider in addition to a bunch of awesome new nostr+podcasting features, and when we launch it we will have to migrate the existing lightning-gated podcasts because v2 will be using the new kind 31338 from the audio track PR
GitHub
Add audio track NIP by staab · Pull Request #1043 · nostr-protocol/nips
Prior art: 32123 published by wavlake do zap splits wrong and are not published by the artist. Metadata is also json-encoded in the content. 31337...
 . We will try to make this migration as seamless as possible. FanFares doesn't currently create an RSS feed for you, so it is currently intended to be used by those who have an existing RSS feed and want to direct listeners to an exclusive piece of paid content with their free content. If you publish kind 1 notes with media urls, npub.pro will create an RSS feed from that for you. Always happy to go into more detail. Thanks for the inquiry.
↑ Parent

Replies (6)

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.
7 replies ↓
fiatjaf's avatar
fiatjaf _@fiatjaf.com 1 year ago
How is fanfares.io doing Lightning-gated content? Is it a platform-specific proprietary thing or a supposedly-interoperable Nostr thing?
1 replies ↓
arkinox's avatar
arkinox arkinox@team.fanfares.io 1 year ago
Right now the lightning gate is proprietary. In the future it will be totally different architecture, totally open source, DVM-based, and handle purchases via zaps.
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 ↓
↑