There are a few underappreciated CLN-specific gems:
* commando and runes.
* sql plugin for complex queries
* JSON field filtering to reduce returned data.
On the internal side:
* the deprecation system which gracefully allows scheduled feature disabling.
* the runtime memory leak detection system.
* the generation of docs and complete testing of JSON schemas for our APIs.
There are probably other minor wonders that I've forgotten about. These are the ones that are on the top of my head!
what's this for?
"Filter to peer to apply to any successful result" ?
JSON-RPC tunnelled over the lightning protocol. Only one hop though (so you can know the peerid, thanks to cryptography).
Filter is the filter to apply to the returned result (on the server side, to save bandwidth)
is the filter the sql stuff? its not clear what this value should be from the docs
I'm confused. The filter simply restricts what parts of the JSON are returned. This can save significant bandwidth in some cases (eg listchannels but you just want the features).
got it, i just was confused when i saw it for the first time in the commando docs the other day since it wasn’t there when i first implemented lnsocket 3 years ago…
Yes, I added it because without explicit support as a cmdline option you would get client-side filtering, which saves nothing, really.
