Oooh, I hope he calls is rosstr
Remote
Steven Bell 
@StevenB@podcastindex.social
mastodon 4.7.3Bug Reports Here:
https://t.me/+NCqewc8q0eU4NzYx
Artisanal Coder.
You may know me from such apps as: LNBeats, The Split Kit, Sovereign Feeds, Music Side Project, CurioCaster, &
TranscriptSearchTool
423 Followers
187 Following
41 Posts
Joined January 30, 2021
Bug Reports:
GitHub:
LN Address:
steven@getalby.com
Nostr:
npub1yvgrrzf4dnmu30qfhw95x87ruu0g2kpv3a64h8hpvqsre8qeuspsgd6pv9
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 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'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.
RE: @mgdell@podcastindex.social
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.
Great article. Highly recommend anyone interested in the PC2.0 namespace read and consider this article.
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.
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...
@mitch@podcastindex.social @martin@podcastindex.social
Are either of you planning on implementing liveValue into your apps? It's an unofficial tag, but CurioCaster and @podcastguru@podcastindex.social 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
Replying to
@ericpp@podcastindex.social
I was going to take a look at the code for podping.watch to add something to monitor the Hive chain, but if you're interested, here's the repos.
https://github.com/thebells1111/podping
https://github.com/stevencrader/podping-hivewatcher-js
Replying to
@mitch @martin @podcastguruhttps://curiocaster.com/rss/feed.xml
https://podcastindex.org/podcast/4935828
The picture shows the test tag. I have a socket connection going 24/7 that broadcast a new liveValue every 30 seconds. Just connect to the socket and parse the JSON that's returned.
I opened up my CashApp wallet, and see all of this rss::payment::stream and rss:payment::boost gobbledygook.
What am I suppose to do with that?
Comb through it and click each one so I can get the metadata and read a boostagram?
Replying to
@merryoscar @francosolerio
So if the listener sends a lunrlp Boost, how does the wallet get the metadata from the app? What will the app have to do to make all of this work?
Replying to
@merryoscar
I guess this becomes a question of who's responsible for hosting/storing a podcaster's metadata, the podcaster/host or each app?
Being both a host and app company, this works for you, but it won't work for me or @francosolerio (who I don't think runs a backend)
(I hope this doesn't come across as confrontational, more just pointing out a concern. I'm glad you guys are working on a solution.)
Replying to
@merryoscar @ericpp @francosolerio @alecksgates
But Alby already supports keysend, so Alby supporting it doesn't buy us anything.
Since the goal seems to be easy wallets, would CashApp and Strike support it is the bigger question?
Replying to
@merryoscar @alecksgates @ericpp @francosolerio @js
5. Some program is able to read this list of payment urls
6. Program fetches each of the metadatas from the various apps and consolidates them
7. Program creates UI that makes viewing metadata easier for podcaster
Replying to
@merryoscar @francosolerio
I'm not going to be able to store metadata for a podcaster's service of choice to fetch from. I suspect others won't either. This means that any boostagrams from apps that don't have a back end simply get missed.
If Fountain does do an API as a stop gap, I'll happily sign up for an API key and send the metadata, but maintaining a database for metadata isn't something I'm able to do right now.
Replying to
@merryoscar @francosolerio
I'm not sure we're particularly concerned with self-hosters much. Most people don't self-host, aren't interested in it, and those that do are already mostly tech savvy and end up running their own servers anyway.
Replying to
@merryoscar
If I send a Bolt 11 payment from a non-Fountain app, how does Fountain get the metadata?
Replying to
@merryoscar @ChadF @js @francosolerio
Does clickable even really matter? It's not like the podcaster is going to be clicking every single payment that comes in, this will ultimately be handled by a program that fetches and consolidates the payment data from all the apps.
And if they need a program that does all of that, then they'll need a server, at which point, let's cut the fetching step out and have the apps send it straight to the server.
Replying to
@merryoscar @alecksgates @ericpp @francosolerio @js
Correct me if I'm misunderstanding,
but in that case, I would:
1. send the metadata from my app to someone else's server to host
2. that server would send me a url to access the data
3. I would make the payment and include the url in the description
4. I would send verification of payment back to the hosting server
Here's a potentially good use for AI in a podcast app. 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.
Replying to
@merryoscar @alecksgates @ericpp @francosolerio @js
If I'm understanding your proposal correctly, the apps "host" the metadata?
Replying to
@theDanielJLewis
Host the metadata for the podcasters. The comment is in the metadata. You set up an end point in your feed, I’ll send you the data.
Replying to
@merryoscar
1) I send you the data, you send me a unique url
2) I send the payment and include the unique url in the message.
3) Fountain hosted wallets get the payment with the message, look in the database to find the metadata that's tied to that unique url found in the message and marks it as paid or verified.
4) You don't have to trust any of the apps, just that your wallet got the payment with the unique url generated by your server.
Replying to
@mitch @martin @podcastguru
The JSON structure has a bunch of stuff that isn't needed for most apps, it's internal stuff I use with The Split Kit to talk to other programs (like mAirList), so don't get too hung up on that structure.
I suspect that structure will change as we brainstorm. What I'd like for us to agree on is how things like Title/Song, Author/Band, Podcast/Album should be labeled so everyone is on the same page.
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.
Replying to
@merryoscar @ChadF @js @francosolerio
Isn't AlbyHub a dedicated server to receive from podcast apps?
This seems like we're once again putting all the metadata storage on the wallets, which keysend already does.
If we're having to rely on wallets playing nice, I'm not sure what this buys us.
Replying to
@merryoscar @dovydas
With this solution, will the apps be expected to maintain a database and schema for podcasters to use to fetch their metadata?
Replying to
@mitch @martin @podcastguru
I agree on the RSS naming conventions, so would like to come up with a json file structure we all agree on.
Replying to
@merryoscar @francosolerio
If Fountain has an API, and especially if it's in the feed, I'll be one of the first ones to start sending metadata your way.
I'm not able to host it on my own database, but would be more than happy to forward it along to a metadata service.
Replying to
@merryoscar
Yeah, I'm pretty sure this would work with Strike too.
https://docs.strike.me/webhooks/setting-up-webhooks/
Replying to
@merryoscar @ericpp @francosolerio @alecksgates
I'd love for the wallet services to support this, but given their history of support with keysend, I'm skeptical.