Posts by StevenB@podcastindex.social
(DIR) Post #Ats049NVj9LYVTZJWS by StevenB@podcastindex.social
2025-05-08T01:34:35Z
0 likes, 0 repeats
@theDanielJLewis @dave 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
(DIR) Post #AtxvwIRgtg8TRaHbWK by StevenB@podcastindex.social
2025-05-10T23:03:39Z
0 likes, 0 repeats
It has begun!https://www.thesplitkit.com/spotlight25
(DIR) Post #Au43ByZCRHud3FyiG0 by StevenB@podcastindex.social
2025-05-13T12:09:33Z
0 likes, 1 repeats
@ChadF @algrid @ericpp @dave @adam 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.
(DIR) Post #Au43BzHrlDdpHmsNsW by StevenB@podcastindex.social
2025-05-13T12:17:31Z
0 likes, 0 repeats
@ChadF @algrid @ericpp @dave @adam 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.
(DIR) Post #AuXGgcY4QNzZTXgxNY by StevenB@podcastindex.social
2025-05-27T15:10:25Z
0 likes, 0 repeats
@merryoscar @dovydas 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.
(DIR) Post #AuXGgewxUp5YvJLrRw by StevenB@podcastindex.social
2025-05-27T16:19:25Z
0 likes, 0 repeats
@merryoscar @dovydas 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.
(DIR) Post #AuXGggi8wsQUNwR3dQ by StevenB@podcastindex.social
2025-05-27T17:35:39Z
0 likes, 0 repeats
@francosolerio @merryoscar @dovydas @dave 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.
(DIR) Post #AuXGghdZVMMbG3Iv9E by StevenB@podcastindex.social
2025-05-27T17:37:46Z
0 likes, 0 repeats
@francosolerio @merryoscar @dovydas @dave 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.
(DIR) Post #AuXGgj4CBrFpgulhHk by StevenB@podcastindex.social
2025-05-27T17:42:15Z
0 likes, 0 repeats
@francosolerio @merryoscar @dovydas @dave 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.
(DIR) Post #AuXGgl14wPwvjpKEhk by StevenB@podcastindex.social
2025-05-27T20:51:51Z
0 likes, 0 repeats
@francosolerio 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?@merryoscar @dovydas @dave @adam
(DIR) Post #AuXGgmlYR6ihAG4rmi by StevenB@podcastindex.social
2025-05-27T22:56:12Z
0 likes, 0 repeats
@francosolerioI 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.@merryoscar @dovydas @dave @adam
(DIR) Post #AucSVTV3MXShSDiZJg by StevenB@podcastindex.social
2025-05-28T12:42:09Z
0 likes, 0 repeats
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.
(DIR) Post #AucSVWLwkqxaIqTq2S by StevenB@podcastindex.social
2025-05-28T12:56:14Z
0 likes, 0 repeats
@chrislw 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.
(DIR) Post #AuciGoSMlKnjNBUXK4 by StevenB@podcastindex.social
2025-05-30T15:15:25Z
0 likes, 0 repeats
@adam @chrislw 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.
(DIR) Post #AyhdDvQdyhSptEeuq8 by StevenB@podcastindex.social
2025-09-29T12:57:39Z
0 likes, 0 repeats
@ChadF @james @samsethi The way I was doing it with The Split Box is when you send a payment in, the metadata was sent to my server and stored, a link to the metadata was generated, and the comment sent to the lnurl address was the link to the metadata.
(DIR) Post #AyhdE2PU1Ph9XfAaVE by StevenB@podcastindex.social
2025-09-29T12:59:40Z
0 likes, 0 repeats
@ChadF @james @samsethi The Split Box was largely based on @alecksgates metaBoost, which I think is the most versatile way to handle metadata.
(DIR) Post #Az4GrzMWwWmXMZwpge by StevenB@podcastindex.social
2025-10-10T13:48:46Z
0 likes, 0 repeats
@dave I'd like to hear @ChadF as a show guest soon.
(DIR) Post #AzVOPqusnRXhxg1pqa by StevenB@podcastindex.social
2025-10-23T15:02:13Z
0 likes, 0 repeats
@ChadF 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.
(DIR) Post #AzoXur3P1TpQ5OGR96 by StevenB@podcastindex.social
2025-11-01T21:36:28Z
0 likes, 0 repeats
@adam @dave 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
(DIR) Post #B0EtUQz4ievuEysfIm by StevenB@podcastindex.social
2025-11-14T14:28:20Z
0 likes, 0 repeats
@csb @adam @merryoscar @dave @js https://getalby.com/lnurlp/podcastindex/callback