That's the big issue we as a community are trying to fix. The problem (and it can be a good problem if we do thisnright) is right now we are at crossroads where two worlds have collided (nostr and rss). We cam be very powerful together but we're too busy infighting over wavlake.
We need to figure out the tech stack that works for both nostriches and pc2.0 folks that prepares this space to scale (because if we get the tech right it will be a revolution in music bigger than napster) and moves all of us forward towards the future.
Login to reply
Replies (3)
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.
This is a wallet issue. Alby provided free wallets. They now provide code to host your own wallet, or paid wallets.
Fountain and Wavlake are using ZBD wallets. I don't know this to be true, but I suspect since both have investors involved, ZBD is one of those investors.
Most of the podcasting 2.0 feeds use keysend in their value block. Keysend isn't supported by most wallets. There's a move away from keysend towards lnurl, which will open up other wallets, but only if they allow NWC.
We're at a point that only companies with the cash flow to provide wallets or the infrastructure to support the wallets are able to do anything besides Alby.
And all that will eventually feed into the very centralization corporate capture problem we have today. We need to be better than that