Oddbean

I'm asking for the ideal solution, not something that "works for now" (I'm not saying that kind:1s with URLs on them aren't the ideal solution), so I'm interested in what @arkinox is doing. Do you have more information?

Wait a minute .. a podcast page is NOT essentially for listening to the podcasts .. I mean how many times we go to https://www.noagendashow.net/ to listen to Adam Curry ! Even if there is a play option , people would still listen on Fountain or Wavelake - because no one listens to just one podcast and the features available on say #Fountain can't be ( and shouldn't be) replicated on individual podcast website... Feature creep and overlaod .. A podcast page is simply for the die hard fans , to may be get the transcripts , merch or bonus content .. and show links to the popular podcast aggregators .. Every podcaster is on social . . What I thought of npub podcast theme is that all the conversations that a podcaster is driving - to say promote the show ( on #nostr) should be available to fans on podcast page .. In addition , anyone should be able to set up a podcast page - even if the podcast is on say Spotify .. I mean Rogan can't move his content to #nostr podcasts but nothing stops him joining nostr to promote his content .. we want to give him a free page .. so that his Spotify die hard listeners arrive at nostr .. to interact .. and like him to millions of padcasters locked into Apple , Google and elsewhere ..

GM @fiatjaf. Today you can upload a podcast audio file to https://fanfares.io 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.io 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 https://github.com/nostr-protocol/nips/pull/1043 . 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.

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.

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.

We will support whichever kind is used for podcasts to provide RSS feeds until apps start fetching from relays directly. I agree podcast is very different from generic "audio" or a "song", because for starters these days it's very often a video...

Why not support RSS-feed and allow zapping to the address in the feed? For example, the author item is there (an email-address). Maybe there’s a place to put the zap address directly or just use the email-field and associate it with the author’s zap address. https://www.rssboard.org/rss-specification#hrelementsOfLtitemgt

But that’s the “standard” at the moment. Could be worse such as Spotify, Youtube etc. gatekeeping most of them. Why not allow something and improve later. There are millions of existing podcasts waiting to be zapped )

#nostr should provide a way to consume rss ( like any other aggregator ) .. let the content be where it is .. And also a social layer to capture all the conversations around episode , podcaster , merch , promotions - the podcast website through npub pro .. People should be able to listen to any podcast through supporting clients - such as #Amethyst .. comment on them ..zap them .. or they may use more sophisticated clients such as Fountain .. for say subscriptions .. history etc ..

Maybe we didn't need Nostr in the first place, everybody could just have blogs and provide RSS feeds! Reader clients could keep track of all the blogs you followed and aggregate all the RSS feeds in a unified feed. And then in order to comment on other people's posts we would post to our own RSS feed and send an HTTP request to the original poster so they would notice and read and display our comment with a link to our blog? And people didn't even have to host their own servers, they could just rely on commodity blog providers that would host things on their behalf! This could have been huge! And the best part: it's all HTTP and HTML, so we know it will be loved by all developers and scale to millions! https://indieweb.org/Webmention Join us and help make this dream a reality!

I see your point .. just wanted to clarify if we are trying to bring in millions of podcasts - to give nostr social users a richer experience -- OR - the goal is to create "podcasting 3.0 - nostr edition" .. Both are sacred goals ! On second thought - I guess it is better to fix podcasting (once for all ) rather than doing a duck-tape .. cuz broken system is anyway working with likes of Apple and Google .. It is not that people dont have access ... might as well strive for something good !

nostr:nprofile1qqsd0kqsnmjrv47wvpt2mfr9xqrthdjp7v09p6zjgd5pcfey2puprmqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqfrwaehxw309aex2mrp0ykhvetjd9nxjety9ejx2umrdphk7mrfdenjuatnqyt8wumn8ghj7mn0wd68ytnwdahkuetn9e3k7mg0jpfq2 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.

I know but that's a huge paradigm shift for not only podcasters but every person who listens to them. I think the winning strategy is to build on top of podcasting 2.0 with nostr. We have some great ideas we are building out. I think everyone is going to like it. Except maybe you 😆🫡 haha

I agree with you nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp, there are many possibilities with bridging RSS. FanFares will be loading all audio type events for people to discover.

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.