Steven Bell :pci: :pc2red:

I'm going to stop hosting and maintaining LNBeats. If anyone is interested in taking over the project or domain, let me know and we can start the transfer.

RE: https://bne.social/@james/117001298295500215

Oooh, I hope he calls is rosstr

Here's a potentially good use for AI. Fuzzy searching. Remember when Curry and The Keeper was hard to find in the Index because it was Curry & The Keeper? A fuzzy search would totally fix that, and AI may be able to autocorrect the query or send multiple potential queries to the Index to hopefully get the right podcast back in the search results.

I'm brainstorming something. For chapters, it's tied to a timestamp, which is cool, but the same idea can be modified so it's not tied to a timestamp and you have swipable photos, sort of like IG. So you could be listening to a photographer telling a story about their photoshoot and you're swiping on the photos, but if there's one you want to spend more time on, you don't have a timestamp auto changing the photo.

Maybe my algorithm knows what I'm interested in right now, maybe it's the current zeitgeist, I'm not sure. I've been seeing more and more stuff talking about quitting social media because it's changed from a feed of people and interest you followed to an algorithm that pushes content on you.

Somehow, I think decentralization and RSS feeds is the best solution to this for most media; blogs, podcasts, reels, video...

RE: https://podcastindex.social/@mgdell/116975387175649551

Must be something in the air with so many people thinking about what podcasting is and what it can be.

Another great article for PC2.0 advocates to consider.

RE: https://podcastindex.social/@js/116975077957707089

Great article. Highly recommend anyone interested in the PC2.0 namespace read and consider this article.

Reflecting on the last few years of podcasting, the innovations that have excited me the most were liveItem and boostagrams. I think it's because of the ability to turn the listeners into participants, to make a show interactive, to create a community. It turned podcasting from a consumption of content into a co-creation and comradery.

I've been thinking about podcasting, AI, and algorithms. I can definitely see the appeal of an app using AI to create a custom feed. It's what the algorithms do, and I'll be honest, I like when the algorithm introduces me to something I love but otherwise wouldn't have been aware of.

But, part of me also likes not having an algorithm, having to be conscious of my decisions, be aware of what I'm choosing to listen to. Right now, the nature of podcasting still maintains that.

I’ve been doing some vibe coding. It’s faster… I think. But it’s exhausting. I can’t quite place my finger on what it is. It almost feels like I’m in a constant argument “No, not that, this, and why did you change the styling. Go back to the old style.” When I’m done, I don’t feel relief like I did when I solved a problem. It’s almost a quiet resignation, like “Well, I’m glad that’s over.” I somehow feel more mentally drained and wonder what exactly I’m trading in for the speed.

Are either of you planning on implementing liveValue into your apps? It's an unofficial tag, but CurioCaster and

support it.

Think of it as a live chapters block and live value block that gets sent over a websocket during a live show.

I'd like to discuss a format that makes sense and modify the proposal so everyone can agree on a good format for the tag

https://github.com/Podcastindex-org/podcast-namespace/discussions/547#discussioncomment-16201182

Why are none of the PC2.0 hosting companies stepping up to host metadata for their podcasters?

As an app dev, I'd be more than happy to POST the metadata that was in a TLV record to your server so you could build a badass dashboard to show your podcasters their stats.

I'm more than happy POSTing for your podcasters, but I'm not interested in HOSTing.

I opened up my CashApp wallet, and see all of this ::rss stream:: gobbledygook.

What am I suppose to do with that? Comb through it and click each one so I can get the metadata?

Here you go dude, an easy place to send your podpings.

https://podping.me/

What's cool about this, is you can use Alby or Fountain or whatever wallet you want, and if you change your wallet, you don't have to change your feed.

https://getalby.com/.well-known/lnurlp/podcastindex

In this case, the callback is an Alby route, but it could've just as easily been a Fountain or Wavlake wallet.

Having apps that support both keysend and lnurl, my process when I see something like [email protected] in the value block is to first check the .well-known/keysend route, and if that returns something, then I send the TLV to the keysend route. If I get an error, then I fall back to lnurl with just the boostagram sent.

I'm hoping that encourages people wanting TLV record and keysend to use their Lightning Address in the feed.

Doing my part to help encourage the transition to lnaddress. SF now strongly encourages using lnaddress with warnings to update addresses.

As always, updates to SF may cause some issues with your feed, so there's always the fallback to

https://stable.sovereignfeeds.com/

which only gets updated when updates to SF are bug free for several months.

Hey

How's it going?

I know you're busy, but there's 6596 music feeds in the Index now.

Can you believe it?

/podcasts/bymedium?medium=music&max=10000 is pretty sweet, but it returns 7mb of data every time. That really adds up.

I don't need every album when a user loads LNBeats, just the ones that have been updated/added since their last visit.

You know what would be sweet?

Adding a since param to the query.

If we're shifting towards no longer supporting keysend, maybe the quickest way to get a large number of feeds to shift is to discontinue Podcaster Wallet, which are all still using keysend.

I have a friend looking for a job. She does mostly front end work. If any of your companies are hiring, I'll send her your way. https://www.linkedin.com/in/haliekoehler/

I understand something like being lnaddress exclusive is going to be different than how things have been done before. But different payment options have been available since the creation of the valueBlock. At any point, someone could've decided to use Hive or Monero as their payment protocol. Any podcaster choosing that payment method would not be able to receive value from some apps, or the app would've had to build for a different payment type. lnaddress only is fundamentally no different.