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

Public Key

npub12qsqnxcdzphcgvlc07f8fwhflx9kvvnzqmv99h83dc2ljnxewyds4wrqfx

NIP-05 Address

[email protected]

Profile Code

nprofile1qqs9qgqfnvx3qmuyx0u8lyn5ht5lnzmxxf3qdkzjmncku90efnvhzxcpz4mhxue69uhhyetvv9ujuerfw36x7tnsw43qz9thwden5te0wfjkccte9ekk7um5wgh8qatz46daxw

Publishing to

relay.ditto.pub

relay.mostr.pub

relay.nostr.net

Author Public Key

npub12qsqnxcdzphcgvlc07f8fwhflx9kvvnzqmv99h83dc2ljnxewyds4wrqfx

Show more details

Last Notes

2026-05-14 02:42:07 UTC

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-27 17:09:45 UTC

- reply

@nprofile…cyex @nprofile…x5pc @nprofile…td70
Can't argue with this.
https://deathbyclawd.com/?url=lnbeats.com
https://cdn.masto.host/podcastindexsocial/media_attachments/files/116/302/240/945/570/345/original/ba66241d2fb9684c.png

2026-03-23 15:45:49 UTC

- reply

@nprofile…8576
It's still happening.
https://v4vmusic.com/
https://cdn.masto.host/podcastindexsocial/media_attachments/files/116/279/262/944/496/050/original/0b47ec15afe0317a.png

2026-03-23 15:44:42 UTC

It's still happening.
https://v4vmusic.com/
https://cdn.masto.host/podcastindexsocial/media_attachments/files/116/279/257/597/424/709/original/00770dd4c446d550.png

2026-03-19 18:14:40 UTC

- reply

@nprofile…vfcp @nprofile…zpdn @nprofile…cn7u
https://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.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/116/257/197/868/547/192/original/3e5376a2d1ebe726.png

2026-03-19 14:39:03 UTC

- reply

@nprofile…vfcp @nprofile…zpdn @nprofile…cn7u
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 to 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.

2026-03-19 14:34:10 UTC

- reply

@nprofile…vfcp @nprofile…zpdn @nprofile…cn7u
I'll try to put together a working livestream feed in a few days with dummy liveValue tag that changes every 30seconds so you can test and develop.
I also have this which is just an html file with some JS so you can see what's going on under the hood on the client side.
https://codepen.io/editor/S-B-the-typescripter/pen/019d0407-7f0c-750f-9c76-1ab1520f1c6d

2026-03-19 14:31:04 UTC

- reply

@nprofile…vfcp @nprofile…zpdn @nprofile…cn7u
I agree on the RSS naming conventions, so would like to come up with a json file structure we all agree on.

2026-03-19 02:50:36 UTC

@nprofile…vfcp @nprofile…zpdn
Are either of you planning on implementing liveValue into your apps? It's an unofficial tag, but CurioCaster and @nprofile…cn7u 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

2026-02-24 21:47:15 UTC

- reply

@nprofile…k8p7
Yeah, I'm pretty sure this would work with Strike too.
https://docs.strike.me/webhooks/setting-up-webhooks/

2026-02-24 21:36:08 UTC

- reply

@nprofile…k8p7
My thinking is if the podcaster wants his metadata, he can get some skin in the game and host it himself or pay for hosting instead of relying on the apps to run his business for him.
Maybe they should host with Fountain if they want their metadata.
And I think Strike has a Webhook api. I know Alby does.

2026-02-24 21:27:55 UTC

- reply

@nprofile…k8p7
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.

2026-02-24 21:19:24 UTC

- reply

@nprofile…k8p7 why can’t we skip the fetching part and I just send it to you direct?

2026-02-24 21:14:42 UTC

- reply

@nprofile…k8p7
So the app hosts the metadata, and Fountain fetches it?

2026-02-24 21:13:29 UTC

- reply

@nprofile…8zna
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.

2026-02-24 21:11:59 UTC

- reply

@nprofile…k8p7
If I send a Bolt 11 payment from a non-Fountain app, how does Fountain get the metadata?

2026-02-24 20:35:00 UTC

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.

2026-02-24 20:05:38 UTC

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?

2026-02-24 14:05:32 UTC

- reply

@nprofile…lm4c @nprofile…x5pc
This seems like a perfect opportunity for a hosting company like Fountain or Truefans to offer a service that would entice podcasters to partner with them.
"Sign up for my hosting and we'll store all your metadata and create a sweet dashboard to display your stats and messages."

2026-02-24 14:01:49 UTC

- reply

@nprofile…lm4c @nprofile…x5pc
If we set the motion in the wrong direction, we may never actually get to where we should. In this case, it seems better to not move than to move in the wrong direction. The first host to offer metadata hosting will will be able to offer a service that no other host is, but the apps doing it for the host only allows them to drag their feet longer.

2026-02-24 13:47:23 UTC

- reply

@nprofile…lm4c @nprofile…x5pc
This whole business of having 20 different apps all hosting their own messages is stupid. The podcaster ends up needing a server anyway to go through all the invoices, fetch each message from each app, then display it in a user friendly way. If they're going to need a server to do that anyway, let's cut out the part where each app stores their metadata and the app can just send the metadata straight to their server instead.

2026-02-24 13:45:40 UTC

- reply

@nprofile…lm4c @nprofile…x5pc
This isn't the responsibility of the Index or the apps. This is the responsibility of the podcaster. If they want their messages, they should figure out how to receive and host them or hire a host that does.

2026-02-22 20:17:15 UTC

- reply

@nprofile…x5pc
The way the BoostBox should work is you POST the TLV record to the url in the feed. BB will return a unique link and/or identifier to the app. The app then makes the payment and includes that link or identifier in the payment message. With something like a Webhook, when the payment goes through, the BoostBox would be notified through the Hook with the unique identifier to verify the TLV is valid and tied to the payment. The link could also be used by the splits to look up the TLV.

2026-02-20 16:07:06 UTC

- reply

@nprofile…ax8n
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

2026-02-20 15:50:35 UTC

- reply

@nprofile…peg3
podping.cloud/?url=

2026-02-20 15:47:19 UTC

@nprofile…7fxa
Here you go dude, an easy place to send your podpings.
https://podping.me/

2025-11-14 18:29:18 UTC

- reply

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

2025-11-14 18:15:01 UTC

- reply

@nprofile…amf2 @nprofile…60s3 @nprofile…pnt8
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 UTC

- reply

@nprofile…60s3 @nprofile…amf2 @nprofile…pnt8
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:26:09 UTC

- reply

@nprofile…60s3 @nprofile…amf2 @nprofile…pnt8
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 UTC

- reply

@nprofile…amf2 @nprofile…pnt8
@nprofile…60s3 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-07 18:11:53 UTC

- reply

@nprofile…myyh @nprofile…xefh
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 UTC

- reply

@nprofile…xefh @nprofile…myyh
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:00:32 UTC

- reply

@nprofile…myyh
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:37:14 UTC

- reply

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

2025-11-07 17:33:37 UTC

- reply

@nprofile…myyh
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 UTC

- reply

@nprofile…myyh
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:19:40 UTC

- reply

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

2025-11-07 17:07:18 UTC

- reply

@nprofile…myyh @nprofile…5yxp @nprofile…9ap7 @nprofile…l26x
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.

2025-11-07 17:02:25 UTC

- reply

@nprofile…myyh @nprofile…5yxp @nprofile…9ap7 @nprofile…l26x
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.

2025-11-07 15:28:32 UTC

- reply

@nprofile…myyh @nprofile…l26x
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 UTC

- reply

@nprofile…myyh @nprofile…l26x
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 UTC

- reply

@nprofile…myyh @nprofile…l26x
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 UTC

- reply

@nprofile…myyh
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 @nprofile…l26x (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 UTC

- reply

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

2025-11-04 12:23:30 UTC

- reply

@nprofile…5yxp @nprofile…9cyh
Reliability is probably the same as keysend, but like Chad said, it allows more people to send boosts since there will be more wallet options to choose from.
There are many downsides to lnaddress, but those don't really matter if there's very little support for keysend, and sometimes we just have to go where the winds are blowing.

2025-11-04 03:33:22 UTC

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 UTC

- reply

@nprofile…wsp3 @nprofile…y5nd
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-23 15:02:13 UTC

- reply

@nprofile…5yxp
Ok, this is pretty cool.
It does store the recovery phase unencrypted in local storage. I'm sure there's some ways to work around that and store it in a secure cookie and to encrypt it, but it seems very promising.
Log in is with your recovery phrase, so it's not Gene's Mom ready, but it is something cool to mess around with.
I'm really glad you've got the coding bug Chad, you've been suggesting/doing some cool stuff lately.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/115/424/078/689/604/134/original/08db0a3ce399c3ea.png

2025-10-10 19:35:26 UTC

- reply

@nprofile…6746
I hear you brother, hence the slow down in my own development. The exhaustion is real. I like Alby and will continue to support it, which means my apps won't be for everyone. I'm okay with that.

2025-10-10 15:46:36 UTC

- reply

@nprofile…6746 @nprofile…h82d
I'm more and more convinced that the solution is adding some more attributes to the funding tag. That combined with a publisher feed and you now have RSS based linktr.ee profiles.
It ends up doing away with streaming sats in most apps, and sadly, the app devs can't cut themselves into the value stream anymore, but it does allow the podcaster to be supported using any payment system they desire.

2025-09-10 03:33:55 UTC

- reply

@nprofile…anun @nprofile…6746
I'm still convinced an HTTP API is the best and simplest solution, and solves most problems. Want it private, don't publish it, what it on Hive, push it to Hive, want it on nostr, push it to nostr... once you have the data on your server, it's yours to store and send anywhere you want. People wanting to make a buck still can, host a metadata server on other's behalf, create a bunch of options for how the boostagrams are stored and shared, charge some money for your service.

2025-09-09 21:03:07 UTC

- reply

@nprofile…6746
I think the first question to ask, is do we want metadata to be public or private?
I'm not entirely sure I want you guys to know how many hours of Girl Boner Radio I listen to.
But, maybe metadata should be public. It would be pretty cool to let the data nerds do their thing and see what real stats are.

2025-08-19 14:52:43 UTC

- reply

@nprofile…6746 @nprofile…g5pf @nprofile…wuyh
As far as I can see, it's the only reasonable way to get the apps to support all of the methods a publisher might have for v4v. It's too much to ask for an app to support lnaddress, keysend, Bolt12, monero, stable coin, PayPal, Cash App, Patreon...
But a link to that page for a publisher makes perfect sense. I know originally, do everything in app seamlessly. I'm not so sure that's the best approach anymore.

2025-08-19 13:30:34 UTC

- reply

@nprofile…6746 @nprofile…g5pf @nprofile…wuyh
My vision for funding has more to do with the publisher feed than the funding tag.
A publisher feed could have the funding tag with all of the ways to support v4v. An app would then simply need to support displaying the publisher feed, and the listener could click which ever support method they choose. The app doesn't need to support every method, just a link to a site that supports that method.

2025-07-17 12:45:18 UTC

- reply

@nprofile…6746
For the love of easy sats is a root of all kinds of evil.

2025-07-12 13:14:55 UTC

- reply

@nprofile…mg8l
https://dribbble.com/hkoehler/shots

2025-07-04 00:15:45 UTC

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-17 13:40:47 UTC

- reply

@nprofile…j90y @nprofile…3j0y @nprofile…h82d
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 UTC

- reply

@nprofile…j90y @nprofile…3j0y @nprofile…h82d
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-05 14:23:56 UTC

- reply

@nprofile…mp2c @nprofile…pvn3
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 UTC

- reply

@nprofile…pvn3 @nprofile…0a2a
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 UTC

- reply

@nprofile…r3p6
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 UTC

- reply

@nprofile…r3p6
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 15:15:25 UTC

- reply

@nprofile…zn42 @nprofile…27yh
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 UTC

- reply

@nprofile…27yh
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:42:09 UTC

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:15:12 UTC

- reply

@nprofile…6746
feedGuid and itemGuid for remoteItems

2025-05-28 12:14:31 UTC

- reply

@nprofile…ayy4 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.
@nprofile…2d4u @nprofile…s2q5 @nprofile…zn42 @nprofile…r3p6 @nprofile…h82d

2025-05-27 22:56:12 UTC

- reply

@nprofile…r3p6
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.
@nprofile…2d4u @nprofile…s2q5 @nprofile…h82d @nprofile…zn42

2025-05-27 20:51:51 UTC

- reply

@nprofile…r3p6
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?
@nprofile…2d4u @nprofile…s2q5 @nprofile…h82d @nprofile…zn42

2025-05-27 17:42:15 UTC

- reply

@nprofile…r3p6 @nprofile…2d4u @nprofile…s2q5 @nprofile…h82d
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 UTC

- reply

@nprofile…r3p6 @nprofile…2d4u @nprofile…s2q5 @nprofile…h82d
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 UTC

- reply

@nprofile…r3p6 @nprofile…2d4u @nprofile…s2q5 @nprofile…h82d
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 UTC

- reply

@nprofile…2d4u @nprofile…s2q5
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 UTC

@nprofile…2d4u @nprofile…s2q5 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-16 17:04:07 UTC

- reply

@nprofile…nza4
This was a very unique and lovely experience.

2025-05-16 15:20:14 UTC

- reply

@nprofile…ayy4 @nprofile…mg8l
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 UTC

- reply

@nprofile…2802
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 UTC

- reply

@nprofile…2802
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 12:17:31 UTC

- reply

@nprofile…6746 @nprofile…2802 @nprofile…pvn3 @nprofile…h82d @nprofile…zn42
The problem on the podcaster side is they lose the TLV record (comments, if the wallet allows are limited to 200 or so characters). I don't know how much of the TLV is needed, but stuff like remoteItem is usual for something like a music show.
There are solutions to this as well. The podcaster could have a TLV hosting service they use that the app sends the record to. This has other problems, but those are solvable too using Webhooks to verify payments.

2025-05-13 12:09:33 UTC

- reply

@nprofile…6746 @nprofile…2802 @nprofile…pvn3 @nprofile…h82d @nprofile…zn42
I would love for a push to be made that keysend is deprecated and valueblocks should have lnaddress. It's the direction things are going, we should to.
The difficulty on the app side is simply the number of network calls that need to be made. For a mobile app, there's worries that it will drain the battery, but it can be done without a server.

2025-05-12 19:46:04 UTC

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 UTC

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

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 21:33:13 UTC

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-06 12:29:32 UTC

- reply

@nprofile…mg8l @nprofile…fhff @nprofile…vn9x
Imagine this, it has a time stamp or audio url on it as well, so you can walk to an area, geofence recognizes where you are, and it jumps to that spot in the audio and starts playing. It would be like a choose your own adventure podcast.

2025-05-01 12:00:53 UTC

- reply

@nprofile…cguj
You free to jump on a call later tonight? I can walk you through things and answer any questions.

2025-04-29 19:57:11 UTC

It's coming.... 5/10/25
One QR to rule them all,
one QR to find them,
One QR to bring them all
and in the darkness bind them.
One QR code, multiple splits, splits can change on your command, in real time.
Verify the splits were made.
https://thesplitbox.com/metadata/d5def5f7-63da-4292-9ff8-18fb7fdc18fe
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/423/002/595/551/910/original/25c6abe7538747ca.png

2025-04-25 03:05:27 UTC

- reply

@nprofile…h82d
Have you settled on a Boost solution? I’m using webLN, but that means needing a browser plugin. The lack of boost options is sort of a bummer for embeddable players on someone else’s site.

2025-04-25 03:03:34 UTC

- reply

@nprofile…h82d
I understand. Looks like we had similar ideas. I ended up creating a player.css sheet that lets people change the css variables in the root element for styling. I don’t know if it’s any help for what you’re doing, but here’s my embedded web player built in Svelte that’s compiles to a web component.
https://github.com/thebells1111/embedded-player

2025-04-21 16:18:52 UTC

- reply

@nprofile…6746 @nprofile…h82d
I can't wait until the day AI answers in memes that we can paste into our socials.

2025-04-21 13:57:20 UTC

- reply

@nprofile…h82d
Only 12-24 months to go... according to AI.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/376/299/666/375/539/original/e1e398bbbc685e9e.png

2025-04-20 21:42:41 UTC

One thing I’d like to see the apps adopts is checking a lnaddress to see if it supports keysend first. This could really help with the transition from keysend to lnaddress.
In my value block, I put [email protected] which supports keysend and lnurlp, so it should work in keysend only apps, and lnurlp apps, and I don’t have to worry about being the TLV record, because if the app supports it, they send it to my keysend .well-known.

2025-04-01 14:57:37 UTC

- reply

@nprofile…6746
Thanks for the update. Give it a shot now.

2025-04-01 13:53:44 UTC

- reply

@nprofile…v2ca
I also have this https://github.com/thebells1111/live-updates
which a bare bones server/client than anyone should be able to use to build their own broadcasting system. As long as we all agree on the same json format, TSK doesn't need to be the only app sending out liveEvents.

2025-04-01 13:23:43 UTC

- reply

@nprofile…v2ca
Nah, it's all open sourced, and @nprofile…pvn3 knows what's going on with it.
It's not a single point of failure by design, I'm just the only one doing anything with it right now.
It is literally a json file over a websocket. I don't know how to make it anymore open than that.
https://github.com/thebells1111/curiohoster
https://github.com/thebells1111/thesplitkit

2025-04-01 13:20:48 UTC

- reply

@nprofile…326g @nprofile…v2ca
Then when we did live music and VTS, I though I could mod it to change albums instead of speakers. I just kind of tacked it on, then Boo-bury got involved, and it's turned into the Rube Goldberg machine you find today.
2/2

2025-04-01 13:20:12 UTC

- reply

@nprofile…326g @nprofile…v2ca
It actually started as an idea I had when Adam and Dave where talking about doing a Bitcoin conference, I wanted a way to change the picture on a screen of who was talking and update the QR code with their lightning address so the current speaker could be boosted in real time.
1/2

2025-04-01 13:02:55 UTC

- reply

@nprofile…v2ca TSK is quite a bit more than a broadcaster for liveEvents. If someone one just interested in sending liveEvents, they totally can without using TSK. It's just a json file sent of a websocket.
I suppose someone could use my socket server rather than setting up their own, and their app sends the correct message to TSK, and then TSK rebroadcasts to all the clients, but I'd have to quite a bit of work to change how my authorization for who's allowed to send updates works.