BITwise 🐳 >>= RIGHTish's avatar
BITwise 🐳 >>= RIGHTish gug@nostrplebs.com 3 months ago
But its just like orange pilling a business... Why should a business take the time to figure out how to accept bitcoin if only a couple ppl are asking for it. If a thousand ppl came and ask they'll certainly support it. Why should they add QoL options that nostriches would use if nostriches aren't using its basic functions Also another reason zaps and lnurl are not integrated is because of metadata. Keysend (current implementation) transfers that data. And reading off the Metadata during shows to recognize on air those who parted with their hard earned sats is an important part of value for value.
↑ Parent

Replies (4)

BITwise 🐳 >>= RIGHTish's avatar
BITwise 🐳 >>= RIGHTish gug@nostrplebs.com 3 months ago
My point is more along... if nostriches want NWC and lnurl support in this ecosystem then they need to be using the other apps or else why the fuck would they bother catering to nostriches? The PC2.0 ppl are just fine using keysend as they've been doing for years. Nostriches out here asking for handouts like toddlers. And cloud fodder I dont mean to be an ass or single you out, im just being bombastic to make a point.
cloud fodder's avatar
cloud fodder cloudfodder@rogue.earth 3 months ago
Is it a problem with the RSS feed not including a lightning address or something like that? Podverse is opensource, and while I don't feel like the pain of digging into their react native world and inspecting the RSS right now, I DID go and file a github issue(feature request) for displaying a QR. We WILL win, somehow. Cause open sauce.
GitHub
add ways to send lightning to pods without requiring alby · Issue #2218 · podverse/podverse-rn
When I go to a pod that supports lightning, I would like it if I could simply have it create an invoice and display a QR code with a "copy to clipb...
2 replies ↓
BITwise 🐳 >>= RIGHTish's avatar
BITwise 🐳 >>= RIGHTish gug@nostrplebs.com 3 months ago
The issue is with the underlying infrastructure of how these various lightning methods work (sorry about my terminology I only speak broken dev). Lnurl and nwc dont allow for enough characters to properly send all the Metadata. Theres talks of using it and referencing nostr where the Metadata is stored but that becomes a bit of a tangled web introducing a third service into the workflow. So because of that, pc2.0 developed everything originally on keysend. Unfortunately almost no wallets support keysend and thats stalling growth and adoption. It wasn't a problem at the start because they had a mostly nonbitcoiner community and could easily just point everyone to alby (until they switched to albyhub as a paid service)
1 replies ↓
↑