31 sats \ 0 replies \ @jeff 6 Nov 2022
I think agree. The data- and permission-model right now, steers application devs towards building custodian solutions, even though it is more work, risk and shittier UX at an ecosystem level.
All these folks talking about likes being swapped out for sats (like on SN), the only way that really works, with the architecture and implementations that exist today, are if users (at least either the payer or payee) give up custody.
reply
51 sats \ 0 replies \ @tomlaies 6 Nov 2022
Why not build the Lightning Network itself? Or build using the Lightning Network.
We do not have to build higer and higher Jenga Towers before we see the really amazing scaling effect of Lightning playing out themselves.
reply
43 sats \ 0 replies \ @chungkingexpress 6 Nov 2022
Anyone got any more info on the idea that there needs to be some changes to the way apple etc handles background app / processes for mobile non-custodial lightning to be a reality? I understand that these apps require the lightning wallet to be open and in the foreground to be able to "receive" properly.
reply
0 sats \ 1 reply \ @kr OP 5 Nov 2022
does anyone here know of other solutions to the issue Lyle is referring to (programmatic spending from one’s node)?
seems like it could unlock more non-custodial LN adoption if implemented.
reply
63 sats \ 0 replies \ @rheedi0 6 Nov 2022
The closest approximation to a solution that I've seen is the budget/allowance feature on Alby. Basically once you've authorized the wallet to spend on a particular site, it will execute those spends upon a user's action without requesting explicit permission -- up until you hit the user's limit set for the site. I think this strikes a good balance between UX and security of a user's funds. There is still some risk, but at least it's hedged.
reply