Steven Bell :pci: :pc2red:

Bug Reports Here:
https://t.me/+NCqewc8q0eU4NzYx

https://getalby.com/p/steven

Artisanal Coder.

You may know me from such apps as: LNBeats, The Split Kit, Sovereign Feeds, Music Side Project, CurioCaster, &
TranscriptSearchTool

Bug Reports: https://t.me/+NCqewc8q0eU4NzYx
GitHub: https://github.com/thebells1111/
LN Address: [email protected]
Nostr: npub1yvgrrzf4dnmu30qfhw95x87ruu0g2kpv3a64h8hpvqsre8qeuspsgd6pv9

Public Key

npub18a6x0kawfw7vjy097psqwy7v7ly4z5ac3u2tpqr3u3v2uvk467esdepny4

NIP-05 Address

[email protected]

Profile Code

nprofile1qqsr7ar8mwhyh0xfz8jlqcq8z0x00j232wug799sspc7gk9wxt2a0vcpqquclkw0

Publishing to

Author Public Key

npub18a6x0kawfw7vjy097psqwy7v7ly4z5ac3u2tpqr3u3v2uvk467esdepny4

Show more details

Last Notes

2026-07-29 16:53:39 GMT

- reply

Also, the bands want to get paid, and I'm not sure lightning is the best method anymore. It's proven to be complicated. Maybe some improvements to the funding tag, make it so it could be styled more like a link.tree page. Maybe a link to the merch store, paypal, and a QR code to the lightning wallet.
A way to make curating a playlist worth the time of the guys doing it. The ones doing it now are in it for love of the game.

2026-07-29 16:51:33 GMT

- reply

Why do people spend more on a hand carved wooden spoon than a machine made one? They're functionally the same, so why is one 25x the cost of the other?
I think AI is the CNC machine of our creativity, and people are going to want the imperfect human made thing over the perfect machine made thing.
I think a way to filter the AI music will be valuable, so a way to verify it was made by hand or curated playlists. The music shows have been a good way of filtering, but it's tough.

2026-07-29 16:26:33 GMT

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.

2026-07-29 12:44:44 GMT

RE: https://bne.social/@james/117001298295500215
Oooh, I hope he calls is rosstr
#note1cv9…62vq

2026-07-28 14:58:41 GMT

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.

2026-07-28 14:55:13 GMT

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.

2026-07-28 14:08:54 GMT

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...

2026-07-24 16:00:32 GMT

- reply

I tend to use my personal chatGPT or Gemini, or both. I find each has strengths and weaknesses, so depending on how in depth I'm going, will switch up. I'm doing the $20 per month chatGPT plan, and free Gemini. Most of my guys use chatGPT, but aren't super technical dudes. As a company, the guys using it for BIM/VDC prefer Claude, and are paying for an advanced model, but I don't know how much they're spending.

2026-07-24 15:23:57 GMT

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.
#note1hcf…97cn

2026-07-24 15:16:10 GMT

- reply

As an electrician, this is partially true. We do use it to help us understand a detail of a installation that may be unfamiliar. I recently used it because I was looking at a detail for some cathodic protection I was unfamiliar with, and asked it to explain it to me. It definitely is useful for broadly understanding concepts and asking follow-up questions.
For specifics, like calculating wire sizing or transformer sizing, it's still wrong often enough that I don't trust it.

2026-07-24 13:28:12 GMT

RE: https://podcastindex.social/@js/116975077957707089
Great article. Highly recommend anyone interested in the PC2.0 namespace read and consider this article.
#note1g9p…au2c

2026-07-23 14:28:00 GMT

- reply

I don't remember how many sats I've made. I'll always remember being part of the first liveItem show with Dave's appearance on Bowl after Bowl or Adam's first 'pirate radio' precursor to Boostagram Ball with Boost-In song requests. Those moments of community coming together to co-create are the most memorable for me.

2026-07-23 14:26:04 GMT

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.

2026-07-23 14:15:51 GMT

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.

2026-07-23 13:24:23 GMT

- reply

None of this is to say I dislike AI. I worry about what it will do to us, our ability to think new thoughts, our ability to trust ourselves. Like McLuhan says "The medium is the message." and I worry how this medium will change our minds. But I use AI every day, it's helped me learn new things, it's helped me quickly iterate ideas, it does grunt work for me, but I've also seen how it 'dumbs' some of my guys down, especially my junior guys, and I too have concerns.

2026-07-23 13:10:57 GMT

- reply

I also use it for coding and learning in general. It's been helping me out a lot with understanding music theory. Having something I can ask questions of and pose hypotheticals improves my understanding.
But, I get stressed with it with coding, because I don't exactly check the code. I copy, paste, and pray it works. Then I talk to the LLM, new code, rinse, repeat.
It's my fault, I could do code review, but my nature is to hit the easy button if I can.

2026-07-23 13:07:25 GMT

- reply

Another issue I have, is it's sycophantic, which I don't like. I know I'm a dumbass, and like having some pushback on my views, iron sharpens iron.
I can imagine two people having a disagreement, running to their LLMs, feeding it the scenario, and getting back a response about why they're correct and the other person is wrong and missing the point. That sort of cheerleading is dangerous, and I worry we're going to trust it more and more to our detriment.

2026-07-23 13:05:14 GMT

- reply

This goes back to another point in Friday's discussion. With the news, if you're an expert on something, you find the reporter is making stuff up, but then we have this thing in us that assumes they aren't making stuff up in other areas.
LLMs are those reporters making stuff up, and even in hard facts, like what size copper wire is acceptable for 400 Amps, it makes stuff up, so I have to assume it's making stuff up with areas not in my domain of expertise.

2026-07-23 13:02:04 GMT

- reply

I drop in a PDF showing panel schedules, and ask it to tell me what electrical loads are higher than 30 amps, and it confidently gives me a list of loads with their ampacity, and it's all made up.
The problem I have with LLMs, is if you know enough to double check it, it's often quicker to just look it up yourself rather than babysit it, and if you don't know enough, then you don't know when it's making stuff up. I'm simply not confident enough in it to trust it... yet.

2026-07-23 12:59:17 GMT

- reply

The other problem I've found with being wrong 50% of the time, is if you aren't an expert in the topic, you don't know it's wrong, and I've found many people treat the LLM as infallible.
I've had to tell my estimators they cannot use LLMs for asking electrical code calculations. I've asked it to size wires, thinking it's all hard data that's in charts, and it confidently makes stuff up. If I wasn't already familiar with the charts, it wouldn't even raise a red flag.

2026-05-14 02:42:07 GMT

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.

2026-03-19 02:50:36 GMT

@npub1p7v…qql0 @npub1wd7…8l2x
Are either of you planning on implementing liveValue into your apps? It's an unofficial tag, but CurioCaster and @npub1qvx…hseu 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

2025-11-14 18:29:18 GMT

- reply

Oh, that's good to know. How's the mobile experience connecting NWC?

2025-11-14 18:15:01 GMT

- reply

The only issue with NWC from an app perspective, is it also allows other wallets to connect. Other wallets that don't support keysend like Alby does. Users will be confused why they can connect their Primal Wallet but not be able to send a boost. Once most podcasts are lnaddress, NWC will make more sense for apps to support without having to deal with users blaming the app for their failed boosts.

2025-11-14 15:58:23 GMT

- reply

I mean you guys open source everything, so even though I'm running my own hub, your team did all the work to build out the software.

2025-11-14 14:28:20 GMT

- reply

https://getalby.com/lnurlp/podcastindex/callback

2025-11-14 14:26:09 GMT

- reply

Cool, so the Alby software, if everything is managed by me, can be ran independent of getalby.com. This means I can get all the benefits of the team's development while avoiding any geo-restrictions the team may need to implement on their domain due to world politics.

2025-11-14 13:24:30 GMT

- reply

@npub1glq…4zwa I love everything Alby has done. You guys kept lightning payments going in PC2.0 when LNPay stopped, and I won't forget that. But...
Even with a self-hosted node, it seems like I'm required to use getalby.com for my lnurlp info. Maybe there's a way so it's truly sovereign and even setting up my webhooks and lnurlp callback can be from my own domain, but I haven't been able to figure it out, so I still have to link my hub with getalby.com.

2025-11-09 14:35:09 GMT

- reply

Is he looking for the easiest? Wavlake, they take care of all the infrastructure, hosting, and provide a wallet.
If he already has an Alby wallet and can follow a 15 minute tutorial, there are easy self-hosting ways of doing it.
Depends on your goals.

2025-11-07 18:11:53 GMT

- reply

Okay, then an app gets a pubkey, puts in in their .well-known/npub or something, and the private relay could easily check and whitelist legit npubs.
I don't like nostr's flat array data structure, but that's a minor thing.
I care about a podcaster's privacy, and the apps not being responsible for hosting the podcaster's metadata. The hosts (you know, the one's charging a podcaster $15 a month) should be responsible for hosting the metadata.

2025-11-07 18:05:51 GMT

- reply

Can I have a private relay that public apps can post to, or would they need some secret way to post to the private relay?

2025-11-07 18:05:03 GMT

- reply

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

2025-11-07 18:00:32 GMT

- reply

Totally agree. I think hosting a server to send the metadata to is no different than hosting a relay.
Unlike a relay though, a server has privacy built into it, and the self-hoster's would be able to figure out how to host their own metadata server, and those who can't can sign up with a hosting company or service that handles it for them.
Fundamentally, I don't see your nostr solution as being much different than a meta server. It's an app sending signed data to a server.

2025-11-07 17:55:22 GMT

- reply

If I'm understanding your proposal correctly, the apps "host" the metadata?

2025-11-07 17:37:14 GMT

- reply

And if I wanted my metadata to be private, is that possible with nostr?

2025-11-07 17:33:37 GMT

- reply

Doesn't the podcaster need to know the relay the app is sending to so they can see data?
If I post something on Damus relay, and that's the only relay I'm connected to, and you're not connected to Damus relay, then you're not able to see what I posted.
Am I understanding nostr correctly, I can only see stuff from you if we're both connected to at least one similar relay?

2025-11-07 17:29:56 GMT

- reply

So, you're suggesting a url in the feed that connects to a server(relay) of the podcaster's choosing, and then all of the apps verify payment, create the metadata, sign the metadata, then send it to that server(relay)?

2025-11-07 17:27:19 GMT

- reply

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

2025-11-07 17:27:13 GMT

- reply

Am I missing some steps on how the podcaster fetches/sees all of their metadata?
1. Listener authorizes Boostagram
2. App builds metadata, stores it in a database, and creates url that returns metadata
3. App connects to listeners wallet, and sends payment with metadata url in the message
4. Wallet keeps list of payment urls like Alby does

2025-11-07 17:19:40 GMT

- reply

How would the app know what relay(s) the podcaster wants the note posted to?

2025-11-07 16:38:31 GMT

- reply

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?

2025-11-07 16:33:28 GMT

- reply

I'd love for the wallet services to support this, but given their history of support with keysend, I'm skeptical.

2025-11-07 15:40:49 GMT

- reply

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 it over, but maintaining a database for metadata isn't something I'm able to do right now.

2025-11-07 15:30:41 GMT

- reply

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.

2025-11-07 15:28:32 GMT

- reply

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.

2025-11-07 15:23:48 GMT

- reply

There is a third way.
That host stores the metadata. Each app sends it to the host API found in the feed.
This works well for Fountain as a business. Since you're willing to store metadata, all the apps send it to your API, and if someone wants access to their metadata, they choose a host like Fountain that gives them that data. More people choose Fountain as a host because you offer more services.

2025-11-07 15:07:30 GMT

- reply

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?

2025-11-07 14:59:34 GMT

- reply

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 an host and app company, this works for you, but it won't work for me or @npub18pr…4h6r (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.)

2025-11-07 14:53:48 GMT

- reply

With this solution, will the apps be expected to maintain a database and schema for podcasters to use to fetch their metadata?

2025-11-06 20:37:57 GMT

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.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/115/504/666/278/890/974/original/c1ecf71596d89457.png

2025-11-06 19:55:21 GMT

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.

2025-11-04 14:00:20 GMT

- reply

Good idea, I'll change it.

2025-11-04 03:33:22 GMT

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.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/115/489/315/734/933/194/original/5d4a47d18b08dd22.png

2025-11-01 21:36:28 GMT

- reply

There's webhooks and api access tokens you can use. It's basically how the split box was built, which is a Rube Goldberg of a payment forwarder built around Alby's API.
Happy to answer any questions you have.
https://getalby.com/developer

2025-10-10 13:48:46 GMT

- reply

I'd like to hear @npub1e88…nva7 as a show guest soon.

2025-10-01 22:29:19 GMT

Hey @npub1rcn…dw4h
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.

2025-09-29 15:26:15 GMT

- reply

It's an option to insert a value block into your feed data being returned from the Index. The idea was to let podcasters be able to get a value block early on before many hosts were supporting in order to show the hosts that podcasters did indeed want it. Many hosts now support the value block, so if a podcaster wants one, they can switch to using a modern day podcast host.

2025-09-29 12:51:15 GMT

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.

2025-07-24 16:11:34 GMT

- reply

Click the podcast you want to subscribe to, then it should show up unless you're already subscribed.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/909/084/464/731/731/original/8c9948751933a696.png

2025-07-12 13:14:55 GMT

- reply

https://dribbble.com/hkoehler/shots

2025-07-04 00:15:45 GMT

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/

2025-06-18 00:17:03 GMT

- reply

I know it's not part of the spec, but something that would also be nice is an imageUrl. That way an app can display the image and the title without doing a bunch of calls to the feed and parsing it, only when the person actually clicks the item.

2025-06-17 13:40:47 GMT

- reply

Totally agree. Very confusing example.
I think at a minimum, all examples should include a bare minimum example, and a kitchen sink example. (Says the guy that won't be updating the repo)

2025-06-17 12:12:37 GMT

- reply

The podroll spec at first glance is confusing, but I think it's technically correct. podroll has a list of remoteItems. Click the remoteItem link, and it shows that those have feedGuid required and a bunch of optional attributes.
https://podcasting2.org/docs/podcast-namespace/tags/remote-item

2025-06-16 22:55:01 GMT

- reply

Power outage at my place due to storms. The perils of self hosting a node.

2025-06-07 12:41:30 GMT

- reply

The NWC is huge. It's one of the reasons I've been pushing to move away from the node in the valueBlock and just using the lnaddress. You can still use keysend lnaddress with the .well-known/keysend route, but a lot of the nwc wallets don't support keysend yet, so the apps would start needing to support lnurlp as well. But the idea of bringing your wallet of choice into any app is so ideal.

2025-06-05 19:57:11 GMT

- reply

You guys move so fast I have troubles keeping up with everything Hub can do.
Now my lnurl is [email protected], so to get an invoice I use the getalby.com server. I think I was also using the easier setup as demonstration on how easy it is to use Alby Hub, so I don't have the full block chain, I'm using the Alby hosted block chain. That also may be part of my issue.
Ideally, my lnurl could be [email protected] and the invoice request goes to `https://badass.com/lnurlp/steven/callback`

2025-06-05 14:41:24 GMT

- reply

Are there any plans to decouple AlbyHub from getalby.com? Like I can have my own server I log into into instead of getalby.com to setup webhooks and my .well-known and invoice callbacks.
That's really the only downside I've seen with AlbyHub. If getalby.com goes down, there's a lot of functionality that goes away until it's back up.

2025-06-05 14:23:56 GMT

- reply

No Alby shade from me. You guys have done a tremendous amount for the PC2.0 community, so I'm not sure why all the hate for a FOSS product.
And you're right, you're not the only wallet provider that has to block certain regions for whatever legal reasons you have, but you are the only one I'm aware of that let's you host stuff yourself.

2025-06-04 15:34:56 GMT

- reply

Would be great to have more options!
Alby Hub is currently the only keysend wallet I'm aware of that has an API that lets apps tie into a user's wallet. The only other keysend wallet option would be the app dev hosting their own in app wallets, and I'm not interested in that.

2025-05-31 12:57:52 GMT

- reply

4 is the big one. Fountain happens to run their own relay, so it would end up becoming the de facto one most people used. Any one can run a relay, it’s just a server, but if we’re going to require people to run a server or use their host’s server, I’d prefer we’re doing it on REST server instead of a nostr server.
Storing and displaying TLV records has always required a server, the wallet providers just handled that for us.

2025-05-31 12:53:29 GMT

- reply

1) I don’t like that the data is sent as a flat array
2) it’s the Wild West, want to make a podcast event, maybe someone has shear done that, why reinvent the wheel? Which NIP do you look at, which kind should I use, I don’t know, everyone is just making stuff up,
3) Highly inefficient. Want to find a list of events, query every relay, get all the events sent back, and every relay sends duplicates.
4) Want a specific message, you better know star relay its stored on.

2025-05-30 16:05:01 GMT

- reply

Here's a list of almost 6000 albums that show artists want music over RSS.
https://lnbeats.b-cdn.net/musicfeed.xml

2025-05-30 15:28:58 GMT

- reply

Again, my suggestion is a server the podcaster or host controls that the data gets sent to. It's private, they can choose their own method of storage or display of the data, and if they choose to make it public, their server can very easily repost it as a nostr note. It seems like a good solution that offers the most control and flexibility. The down side is it requires a server to send to, but RSS requires a server to serve the files anyway, so it's not a big lift.

2025-05-30 15:15:25 GMT

- reply

I’m not a big fan of using nostr as it’s a public protocol and anyone can view the notes and metadata. I’ve always valued privacy. Also, having built stuff for nostr, I think it’s a terminally flawed protocol, but I can definitely understand the appeal of it, especially considering Fountains goal of being a nostr app. If that’s the direction most people want to go, I’ll follow.

2025-05-28 12:56:14 GMT

- reply

I totally agree, and the valueBlock is extremely open. The competing goals of interoperability and being open to other protocols is a a two edged sword for sure.

2025-05-28 12:46:55 GMT

- reply

I would also like to see some sort of alternate address as well. Not even as a transitionary thing. Something like two keysends could even work, so one is a fallback if your node goes down. Or lnaddress/monero, and your feed works in a lightning app or a monero app.

2025-05-28 12:42:09 GMT

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.

2025-05-28 12:18:53 GMT

- reply

I don't always agree with the decisions you make. I'm not your target audience, but you have both always been very considerate of this community, and I respect that. My recommendation, do what's best for you and your business. I know you guys want to focus on nostr, and lnaddress is the way forward with that. You're in spec, so move forward with it. That's my 2 cents.
@npub1unc…6rz6 @npub1fmx…wp74 @npub18pr…4h6r

2025-05-28 12:14:31 GMT

- reply

This won't effect anyone but Fountain Blue users. If you like your keysend, you can keep your keysend. Some apps that won't work with lnaddress won't be able to be used to send payments to any splits that are lnaddress. This has been the case for a year now. In the future, I'm sure some apps will be lnaddress only, and you won't be able to receive value from those apps. We all have to make decisions with the compromises we want.
@npub1cwm…wcs6 @npub1gfn…mk8j @npub1fmx…wp74 @npub18pr…4h6r @npub1rcn…dw4h

2025-05-27 22:56:12 GMT

- reply

I agree, we need to consolidate on a solution. I’ve said my piece about the direction this should go, which is a meta server url in the feed to send the data to, but I don’t want to get involved in any more in fighting. We’ve stagnated because nobody can agree on anything any more, and we’ve already started splintering. Whatever everyone decides on, I’ll start sending the metadata for lnaddress there.
@npub1cwm…wcs6 @npub1gfn…mk8j @npub1rcn…dw4h @npub1fmx…wp74

2025-05-27 20:51:51 GMT

- reply

Is your main beef with the metadata, or do you have other issues with lnaddress?
If there was an agreed upon way to handle getting metadata to a podcaster that wasn't via a TLV record, would you support it?
Is there anything technically stopping you from supporting lnaddress running serverless, or is it a preference thing you have?
@npub1cwm…wcs6 @npub1gfn…mk8j @npub1rcn…dw4h @npub1fmx…wp74

2025-05-27 17:43:40 GMT

- reply

I'm pretty sure the options stuff was dropped completely by everyone. Probably needs to be removed from the Index github before it causes more confusion.

2025-05-27 17:42:15 GMT

- reply

v4v isn't metadata. v4v was PayPal and checks and gold coins and any other way you want to support a show, well before we started lightning payments.
But this does break the metadata, I agree. And I've tried to suggest solutions to address that. However, lnaddress is the direction everyone but PC2.0 is going. As much as I hate it, I can't deny it. I prefer keysend, I've just conceded that we've lost that battle.

2025-05-27 17:37:46 GMT

- reply

The reality is, the spec is very open. Fountain could've chosen to not support lightning at all and gone all in on Hive or Monero, and the spec allows it. Then we'd have to decide if we want to build an app that supports the Hive or Monero protocol, because there would be valid RSS feeds using something besides lightning for listener support.

2025-05-27 17:35:39 GMT

- reply

You're not being forced to do anything. It's your choice if you want to support that part of the spec or not.
There is no simple solution, but holding onto keysend isn't the solution either. Very few wallets support it.
We chose Betamax, it's a superior solution. The rest of the world chose VHS. We can hold onto Betamax if we want to, but nobody else is going to.

2025-05-27 16:19:25 GMT

- reply

It's been in the spec for almost a year now. I think any of the apps wanting to do it have had ample time.
I actually think this is a good move, and you guys should move forward with it with your transition, that way you don't have to go back and update your feeds later.

2025-05-27 15:10:25 GMT

@npub1cwm…wcs6 @npub1gfn…mk8j I heard Fountain Blue is going to be lnaddress exclusively. Is this true?
If so, the other apps are going to really want to start implementing lnaddress support, or there's going to be a lot of podcasts their app doesn't do lightning payments for.

2025-05-27 15:08:16 GMT

Since Fountain Blue is about to be a thing, and Fountain was the main player using Podcaster Wallet, can we pretty please consider deprecating the Podcaster Wallet?
I really want to get to just needing to fetch the feed to get all the value block info.

2025-05-19 17:00:20 GMT

- reply

Click advanced, check public

2025-05-16 15:20:14 GMT

- reply

You can add it manually in the Manual edit in SF.
I can add it. But it adds to bloat.
I'm a podcaster. I see a field for title and another one for itunes:title.
Here's what I'm thinking:
WTF is this?
Which one am I suppose to use?
Why not just have one thing called title?
This is so confusing. This host sucks.
As a hosting provider, I want to avoid that, so I simplify. Maybe they don't get the full functionality. They don't care. They want ease.

2025-05-13 17:40:29 GMT

- reply

The options proposal got scrapped, so I fell back to looking up keysend first, as it accomplishes what options was trying to do.

2025-05-13 17:31:29 GMT

- reply

One thing I've been doing as a courtesy with lnaddress addresses, is do a .well-known/keysend look up first based on their lnaddress. If it returns an address, I'll send the boost over keysend so they get the TLV record, if not, I fall back to the lnurlp lookup and request and invoice.

2025-05-13 16:32:00 GMT

- reply

The mentality that I'm giving this away instead of selling it because it engages a different part of your brain is spot on. I don't do v4v because it's the best economic model, I do it because it's a healthy mental model for what it is I'm aiming to build.

2025-05-12 19:46:04 GMT

I'm not sure this got noticed from a few months ago, so I'm bumping it for any of the apps that may be interested in it.
https://github.com/Podcastindex-org/ulid
It was super easy to implement. I pretty much just copied it from the Podcast Index website github.

2025-05-11 04:25:24 GMT

- reply

My hats off the Podcasting 2.0 community. They really understand what v4v is all about. This event was a hallmark of the time, talent, treasure model, and I couldn't be more proud of what was accomplished tonight.

2025-05-11 04:22:35 GMT

We just stress tested The Split Box. It was able to support the Satellite Spotlight, an event that sent 2.2 million sats worth of boosts, 1.2 million of them being through TSB.
The means the listener was able to scan a QR code from the wallet of their choice, and over 20 splits were handled on the backend.
This means you can paste your QR code on fliers, merch, the drumkit, and your fans can boost from the wallet of their choosing and each band member gets their split.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/487/271/805/313/365/original/18cf4b792babf55c.png

2025-05-10 23:03:39 GMT

It has begun!
https://www.thesplitkit.com/spotlight25

2025-05-10 21:33:13 GMT

4 Bands, Boost Babes, a leaderboard, zaps, QR codes for CashApp, use your own Alby wallet, super chats, splits to the crew, easter eggs based on boost amounts, it's all here.
https://www.thesplitkit.com/spotlight25
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/485/658/660/124/823/original/eb89215b8089d1c3.png
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/485/664/201/004/815/original/603ae0f35fb6f2fe.png
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/485/665/708/068/031/original/6d1402ee8ca6ef78.png
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/485/667/569/008/132/original/cd49019598c23ffa.png

2025-05-08 01:34:35 GMT

- reply

That’s exactly what that means. Tried it out, it works for any app that uses lnaddress and looks up the .well-known route.
https://cash.app/.well-known/lnurlp/curiocaster