Nostr could definitely fix this but in a manual sort of way for now… there might be other methods I’m not aware of yet.

Reply to this note

Please Login to reply.

Discussion

I think we'll get there. A centralized option is to have bots thay can read the rss feed and auto split out the incoming zap... but then theres all the obvious centralized bot issues

Splits work great with nwc, you can even “stream” zaps without keysend. At one point I was splitting zap streams every 5 seconds

I like that. Now that you invoked keysend... i have a question for you. Can you make some logic on the back end such that it can pick the correct address type based off the senders wallet and whats listed in the rss? It wont fix everything but will fix a chunk of problems going forward... ill explain.

Right now theres a problem in that the huge rss library is all full of keysend addresses. So paying from a lnaddress to keysend (and vice versa) will return an error. Many dont want to move forward with lnaddress because they don't want to be the one feed thats lmaddress. Most paying users are already paying with keysend, so they don't wanna fuck themselves and miss the bulk of payments.

But this reluctance is also the very thing keeping things moving forward. (Well theres also the issue of full metadata not being passed with lnaddress because lnaddress doesnt allow a large enough text field. But this may be solved by nostr:nprofile1qqswfa547pdmqkerzf2uen3agudc67wxffjmenqpge3dylc006fppyspp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqgkwaehxw309aex2mrp0yh8qunfd4skctnwv46qa3xytq's metadata implementation)

So there needs to be a transition... a period when, artists can list a primary and secondary wallet (say a keysend and an lnaddress), then when a user pays with a wallet, the back end logic matches the right recipient. This would not magically fix everything but at least it gives a backwards compatible path forward.

I’m happy to implement anything you need in the bounds of what current tech allows. But it’s also a good exercise to see what’s missing so new tech can be developed or adapted to serve specific needs.