Oddbean new post about login | logout LN zaps were the scenic route we needed to arrive to ecash zaps
@0xchat and cashu.me very foward and advanced in that direction friend. Hope to see soon #Cashu in @Highlighter
And @corndalorian thought being self custodial with lightning was difficult.
lol it’s not difficult if you know how to use bitcoin and lightning. It’s just expensive and difficult for the other 99.9999999% of the world who we want to onboard to nostr. Ecash is custodial lightning with more steps. It doesn’t solve anything for those who want easy self-custody so it’s incorrect to even bring it up.
My point is that if self custody for everyone is the goal this is going the wrong direction. I support individual self custody for all and want to see more of the devs working on solutions that make that easier instead of another custodial solution. I'd be working on ark right now if I were a dev, but I'm not.
Individual self custody is a great thing. It’s also unnecessary for pocket change amounts of money. Decide your own risk levels of course, what you’re comfortable losing. But it’s foolish to demand that people use 100% only self custodial solutions when they’re sure to lose more money in the process than they would leaving a few bucks on a custodial wallet or mint.
Individual full self custody zaps is at least possible with LN but isn't with ecash. I do understand the tradeoffs, I use alby for zaps even though I run my own lightning node as anyone can look and see. The community seems to have moved away from the idea of staging custody and security based on amount to all or nothing in the posts I read. I'm happy with staging, it is an effective and pragmatic approach. I want devs to work on making it easier to self custody smaller higher turnover amounts instead of constantly swapping out one custodial solution for another. It is an illusion of progress where there is only wasted effort.
And it’s trusted model 😏 https://image.nostr.build/35500cc5e8fa1d23a15f53ce3048dd7598fb62d6e4444938ae379784ca8b9831.jpg
Holesail is truly peer to peer and does not need centralised servers. Also make your connectors strong, long and super random or use auto generated random keys, that will prevent collision.
How? When I type “holesail holesailMCServer420” and then send a GET request to localhost:8989, how does it find the ip address of the server that used the same connector? Also, can the connector be a public-private keypair or a string/string-hash pair? Because I want others to send requests to my server without being able to try taking over other peoples’ the requests.
When you do holesail CONNECTOR, it generates a hash that is also your location in the distributed hash table, atm there are two public nodes run by hopepunch team which lets you in on the mesh network of peers. Anyone can run a public nodes, and it's only used for initially finding first few peers after that other peers tell you where your "peer" is located. To stop people from taking over, you need to use key, which are automatically generated. holesail --live 5000 will give you a key
Would also be a great place to drop the video of that dude breaking down Kademlia. Actually, I have it saved lol https://youtu.be/1QdKhNpsj8M?si=iyBPHCuwPld9SLm6
Would be really cool to have an @umbrel app that creates reverse-proxy to the LNBits app, and some instruction how to build a project on Vercel or Firebase with a lambda function that forwards every request to your home LNBits. The major pain with LNBits behind NAT is to actually let others use it outside your home WIFI.
in the meantime, it can always be easily installed by ssh'ing in. although id imagine getting it working with containers is a pain
