pull down to refresh

turned out to essentially be a protocol for custodians
LNURL became a protocol for custodians, because the setup lift is too high for casuals. Pub/CLINK solves that for self-sustodians.
centralized applications
Pub is DE-centralizing, by being self-hosted software hitting a new lower bound on setup lift.
Not sure if you're trying to be funny by comparing self-hosted Lightning node software to Bitcoin consensus changes based around at-scale central-coordinators.
By your logic Bitcoin Core is itself a centralized application.
I'll assume it was a bad joke and you're not that retarded.
0 sats \ 1 reply \ @ek 1h
Cool, you dodged my question about how you designed CLINK and instead started talking about Pub. Reads like what I said is true, but you're too embarrassed to admit it here.
For other readers, here is my discussion with him on GitHub about this issue.
reply
Pub is the CLINK reference server, CLINK is a protocol of Pub philosophy, no high-friction web-server required, maximum distribution.
Subscriptions are one functionality, and yes people subscribe to services. Your landscaper provides a service you subscribe to, and he invoices you periodically for that service. CLINK also does ad-hoc.
How is that catering to a custodian? How is enabling small business that functionality in disintermediated way, when it hasn't been available, centralizing over decentralizing?
The only embarrassment here is your desperate attempt find an equivalency to NGO astroturf and being a person in a technical position with zero grasp of architecture.
Are you too embarassed to admit that you're actually not that technical and the average landscaper running a VPS threatens your ego? that the elitist NGO gatekeepers who want at-scale centralized neobank solutions are your idols?
reply