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

nprofile1qqs9qgqfnvx3qmuyx0u8lyn5ht5lnzmxxf3qdkzjmncku90efnvhzxcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dssvn6xq

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub12qsqnxcdzphcgvlc07f8fwhflx9kvvnzqmv99h83dc2ljnxewyds4wrqfx

Show more details

Last Notes

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 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 15:30:41 UTC

- reply

@nprofile…myyh @nprofile…l26x
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 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: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-06 20:37:57 UTC

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 20:27:40 UTC

- reply

@nprofile…y5nd @nprofile…5yxp @nprofile…5x2e
He could do something like build his own .well-known routes on his webpage. So [email protected] would have a keysend route and an lnurlp route with the proper keysend custom value.

2025-11-06 19:55:21 UTC

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 UTC

- reply

@nprofile…z64c
Good idea, I'll change it.

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 17:52:38 UTC

- reply

@nprofile…amf2 @nprofile…5yxp
Oh yeah, encrypting with their password makes a lot of sense. Good call.
For a sending wallet, this seems like it could be a good solution. Only keep the number of sats you're willing to spend in it, that way if it gets compromised, you're not out too much.
It is cool that it's working in a web browser.

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 13:48:46 UTC

- reply

@nprofile…h82d
I'd like to hear @nprofile…6746 as a show guest soon.

2025-10-01 22:29:19 UTC

Hey @nprofile…h82d
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-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 16:52:35 UTC

- reply

@nprofile…6746 @nprofile…g5pf @nprofile…wuyh
The idea behind the lightning stuff and the value tag is great, but not everyone is as cool as we are. I love the idea of everyone gets their v4v split right there in the feed.

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-08-12 17:50:23 UTC

- reply

@nprofile…6746
It was the deciding factor for me as well. PC2.0 is primarily keysend, so most feeds are incompatible with NWC. It's a dealbreaker for any PC2.0 related stuff.

2025-07-24 16:11:34 UTC

- reply

@nprofile…w606
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-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-18 00:17:03 UTC

- reply

@nprofile…j90y @nprofile…3j0y @nprofile…h82d @nprofile…wuta
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 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-16 22:55:01 UTC

- reply

@nprofile…vu32 @nprofile…zn42 @nprofile…2d4u @nprofile…h82d
Power outage at my place due to storms. The perils of self hosting a node.

2025-06-08 15:56:44 UTC

- reply

@nprofile…6746
The Alby team really listens and I think cares. It started out at $21 a month, and dropped to less than $10. I host my own node and signed up for their $10 a month service, one for a backup and two because I want to support what they're doing.
Seriously, any app could host their own wallets like Fountain does using Alby's infrastructure, for $10 month. That's a huge deal.

2025-06-05 14:41:24 UTC

- reply

@nprofile…mp2c @nprofile…pvn3
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 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 16:05:01 UTC

- reply

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

- reply

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

- reply

@nprofile…ayy4 @nprofile…2d4u @nprofile…s2q5 @nprofile…zn42 @nprofile…r3p6 @nprofile…h82d
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 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:18:53 UTC

- reply

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

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:43:40 UTC

- reply

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

- reply

@nprofile…2d4u @nprofile…6746 @nprofile…s2q5
I appreciate you taking the other apps into consideration, but after a year, I think you have to do what's best for your vision and team.

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-27 15:08:16 UTC

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 UTC

- reply

@nprofile…mg8l
Click advanced, check public

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-14 16:51:56 UTC

- reply

@nprofile…xs2w @nprofile…6746 @nprofile…2802 @nprofile…pvn3 @nprofile…h82d @nprofile…zn42 @nprofile…wuyh
You mean all the Kool Kids don't you?

2025-05-14 13:49:11 UTC

- reply

@nprofile…2802 @nprofile…6746 @nprofile…r3p6 @nprofile…pvn3 @nprofile…h82d @nprofile…zn42
It's a unique url your wallet can generate that you paste into an app. It gives an app a way to connect with and control your wallet programmatically.

2025-05-13 19:43:08 UTC

- reply

@nprofile…r3p6 @nprofile…6746 @nprofile…2802 @nprofile…pvn3 @nprofile…h82d @nprofile…zn42
Two ways around this.
1) Send the important stuff in the comments field for the invoice request (200 char max, not all wallets support, get a better wallet)
2) Run a server that accepts post requests. I'm more than happy to send the TLV record to your server as an alternative. If only there was a tag that let me know where to send your metadata.

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 16:32:00 UTC

- reply

@nprofile…7u5z
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-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 23:03:39 UTC

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

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-08 01:34:35 UTC

- reply

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

2025-05-07 14:18:58 UTC

- reply

@nprofile…6746 @nprofile…h82d
With payment validation.
https://thesplitbox.com/metadata/68917e52-a12f-418d-bdcc-49fbc6fff657
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/466/979/873/356/479/original/d1b298717c9f117f.png

2025-05-07 14:15:43 UTC

- reply

@nprofile…f05c @nprofile…6746 @nprofile…h82d
Continue living in bliss.
It's totally a side project that doesn't need to be adopted by the everyone. However, it does serve a niche by allowing one QR code/lnadress to handle multiple splits.

2025-05-07 14:06:05 UTC

- reply

@nprofile…6746 @nprofile…h82d
This one lets you send sats to the PC2.0 channel level splits.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/466/931/244/144/561/original/3f1efee0a1a318c3.png

2025-05-06 16:35:36 UTC

- reply

@nprofile…992e
I wonder how many business owners think podcast apps are ran by huge companies instead of being another small business just like them.
I know before I got involved with PC2.0, that was my perception. Now I know it's usually a dude by himself or with 2.5 people building it out as a small business.
I bet a business with a podcast could get some prime visibility on some of the apps just by reaching out and introducing themselves.

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-02 19:26:24 UTC

The Funding Tag is your own sovereign linktr.ee
I'm pretty sure it can very easily be extended so it can be a direct clone, available in all apps.
Looking at these linktr.ees, if we add an img attribute, and something so you can tell the app what 'group' the item goes in, we pretty much have linktr.ee in the feed.
https://linktr.ee/hbo
https://linktr.ee/selenagomez
https://linktr.ee/hoe_math
https://linktr.ee/comedycentral
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/439/858/561/400/549/original/e2010aff208a0028.png

2025-05-02 19:25:58 UTC

The Funding Tag is your own sovereign linktr.ee
I'm pretty sure it can very easily be extended so it can be a direct clone, available in all apps.
Looking at these linktr.ees, if we add an img attribute, and something so you can tell the app what 'group' the item goes in, we pretty much have linktr.ee in the feed.
https://linktr.ee/comedycentral
https://linktr.ee/hbo
https://linktr.ee/selenagomez
https://linktr.ee/hoe_math
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/439/858/561/400/549/original/e2010aff208a0028.png

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-30 13:05:01 UTC

- reply

@nprofile…0a2a @nprofile…pvn3
I wonder if your time 'might' be better spent figuring out how to implement Hive in the value block. I don't know if it's a better solution, but perhaps it addresses some of the pain points we're having with lightning.
IMO, a perfect solution would need at at least:
SPLITS!!!!!!
Micropayments.
Easily convertible to fiat.
A dead simple wallet that a mid-wit can figure out and fund
Programmable.
An easy API for an app dev to figure out.
Anything else???

2025-04-29 22:36:20 UTC

- reply

@nprofile…cq0g I’m going to put that in my dating profile

2025-04-29 20:50:51 UTC

- reply

@nprofile…326g @nprofile…6746 @nprofile…2d4u
Might be a bad address in the feed. @nprofile…cq0g is updating it.

2025-04-29 20:39:59 UTC

- reply

@nprofile…326g @nprofile…6746
And look at all those splits going out back out!!!
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/423/181/871/190/636/original/8d6cb7af510c2219.png

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-29 13:22:02 UTC

- reply

@nprofile…mp2c @nprofile…mg8l @nprofile…6746 @nprofile…g5pf
In the valueblock, they see [email protected]
The app checks this route first to see if it returns a node address.
https://curiohoster.com/.well-known/keysend/steven
If not, fallback to this route
https://curiohoster.com/.well-known/lnurlp/steven
Notice how in the lnurlp route, it's using the getalby.com url for my callback. If I change my wallet provider, it's super easy for me to update my well-known info and not have to change any thing in any of the feeds.

2025-04-29 13:18:17 UTC

- reply

@nprofile…mp2c @nprofile…mg8l @nprofile…6746 @nprofile…g5pf
This is easily fixed, but the apps will have to take the lead.
[email protected] is all that's needed in the feed.
I control that site, so I can update what's returned anytime my wallet changes. A host could easily provide this for their customers.
If the apps look up keysend first, then fall back to lnurlp, this works flawlessly for all wallets. It's up to the apps to implement it that flow though.

2025-04-28 01:39:25 UTC

For any of you early adopters, Sovereign Feeds now supports the new Location tag attributes in the channel, item, and liveItem.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/413/033/452/549/657/original/7910744bc4b106e5.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