Time for the board meeting! We're running with scissors live with episode 181! Freeze your Rodecaster!
🔥🍻🎙️🍾
Time for the board meeting! We're running with scissors live with episode 181! Freeze your Rodecaster!
🔥🍻🎙️🍾
@merryoscar @agates @ChadF @dave @js @ademan
Podcasting v4v needed a payment solution when fist concepted
Dave and I looked at all options. Bolt12 has always been the answer, with keysend as a ramp to it.
Lnpay and getalby made it easy for devs to incorporate it with an api.
That solution is going away, and the new solution requires work to integrate the breez SDK or greenlight api.
The frustration come from nostr telling us they have the solution when they actually don't. That's all.
@agates @adam @ChadF @dave @js @ademan
I also really don't understand why everyone is so against nostr.
Nostr and Podcasting 2.0 are not competitors - they are perfect partners and share the same goals:
- sending micropayments
- onboarding people to bitcoin + lightning wallets
- paying content creators
- allowing apps to share data so there are no walled gardens
I honestly haven't heard a single good argument on the boardroom to why nostr is bad.
I would love to come on and discuss this.
@agates @adam @ChadF @dave @js @ademan
I would love to come on and talk about all this.
Some initial thoughts:
- nwc supports sending keysend payments - so on the listener side if they have a wallet that supports nwc they can use it for podcasting 2.0 payments if the podcast app supports nwc
- as far as I'm aware BOLT12 is being actively worked on by all the lightning implementations - it's probably still a way off but I think it's definitely going to happen
@dave @agates @adam @ChadF @ademan
🤷♂️ Perhaps it would be worthwhile getting someone from alby or fountain on the show!
@js @agates @adam @ChadF @ademan Keysend allows push payments without having to generate an invoice, which puts Lightning on par with things like Venmo, PayPal, etc. The receiver of a payment having to generate an invoice is just always going to be a convoluted experience and lead to weird solutions like LNUrl.
The real solution is BOLT12, which nobody is working on because they are all obsessed with Nostr. And they’re only obsessed with Nostr because Jack/VC money is feeding it.
@agates @adam @ChadF @dave @ademan
exactly, that's what i mean by a wallet provider service as an alternative to self-hosting, a thing that Alby used to do but I guess cannot exist now
I'm ambivalent about the nwc protocol, it's pretty simple (I'd say simplistic) websocket stuff, and comes with the same caveats as the rest of the nostr specs - only lightly documented, riddled with typos etc, doesn't exactly spark confidence
As long as it can carry the same custom payloads (which I assume they can via the same blip mechanism), I don't know why it wouldn't work
Seems like the real need is for a wallet provider service for podcast listeners/publishers, but they'd be subject to compliance, so no one wants to do it
I don’t know about the keysend thing but I have NWC on my own node that I can connect to different Nostr apps and it seems to work well but I don’t know what the difference is.
Why the need for keysend again?
It looks like this is a way for the listener app to orchestrate lightning invoices/payments while steering clear of compliance stuff (which would fall on wallet providers, or "self" for self-hosted nodes I guess)
ie wouldn't you build on this if you were starting the value tag idea today?
https://blog.getalby.com/an-open-payment-api-for-podcast-apps/
I assume y’all are already familiar with nostr wallet connect? https://nwc.dev/
Integrates with a number of wallets including alby
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.