I have. LN is a dumpster fire of complexity and overhead. As you said, well it's a Layer 2 system so that's how it goes. I just mean to say it's going to take far more work than nostr to reach maturity. Why does it require curl to interact with my Bitcoin Core node and Core Lighting to access all features? In some cases it feels like I would be better off and safer doing it myself. But seriously, there are like 4 developers working on anything at the core. @Rusty Russell being of the few. When I was invited to look at Umbrel, I realized they built their own, and with no fault of their own, it's a fairly complicated mess that the average self-hosted is unprepared to manage correctly.
Exactly. That's the problem. That's why I only spend time with core lightning. We need more than 4 developers. and we need to spend more time reading and reviewing stuff like this (https://reyify.com/blog/adaptors-generalised/) instead of this stupid top layer app stuff, which is what seems to grab people's attention. But perhaps, that is asking too much brain power from folks.
> instead of this stupid top layer app stuff, which is what seems to grab people's attention. Any examples?
Wallets, probably.
lightning's great difficulty is the basis in source routing, and i can't think of a way around that and i've thought a lot about it and on top of that, there is this mentality among bitcoiners that privacy is very important, so the protocol doesn't include adequate advertising of channel state i think that the thing that will tip LN over to big times is going to be when people realise the LN node should be advertising channel state, and i'm gonna strand by that position until someone gives me a good reason why not there simply is no way to do path routing on bitcoin state, there is a for real anathema between the two things, bitcoin transactions and path routing
I have never used curl to access my CLN node?
Oh hello! High profile npubs don't tend to respond when tagged like this. > I have never used curl to access my CLN node? Why not? it's fun :) Using front-end tools like RTL miss certain things. In this specific example, it was getting the currently synced block height, during an initial block download. I'm interchanging curl for lightning-cli