6 sats \ 6 replies \ @k00b 25 Dec 2021 \ on: Real life example of Lightning Network censorship AKA “What's wrong with LN in one tweet” bitcoin
This isn’t a problem with LN. It’s a problem with one dude that’s mostly mitigated with privacy best practices.
It’s kind of like a guy kicking you out of his house and you’re like “well, that’s what’s wrong with houses.”
I understand what you mean, but an individual house isn’t part of a transportation network. I’m not an expert but tell me what you think of the below:
Imagine if roads are privatized. Eventually the majority of roads will be owned by just a few corporations (because you can only make money at large scale). Now all of the sudden being kicked off is a lot more of a problem. Especially if multiple of these corporations agree on kicking you off.
reply
This is false tho, because there is no "monopoly control", there is nothing preventing anyone else from spinning up routing nodes.
Any corp that tried to "corner the market for purposes of censorship" would trivially be routed around.
To present it another way: Why hasn't this happened with SMTP yet? Why isn't there 1 mega-corp who dominates and censors email?
reply
To present it another way: Why hasn't this happened with SMTP yet? Why isn't there 1 mega-corp who dominates and censors email?
There is. It's called Gmail. Effectively, Google controls the entire email protocol.
Just ask anyone that runs their own email server and is considered spam by Gmail (even though their server is perfectly compliant by SMTP standards)
reply
This is damn true!
I run several email servers, self hosted, with all dmarc, dkim, spf etc specifications OK and google still reject my emails because my IP is in a range from the ISP that is doing spams.
So if I have for example 193.45.50.1 and another IP from the same ISP`have 193.45.50.2, the entire block is put into spam list.
ISPs doesn't give a shit, even if you put an incident, google doesn't give a shit.
As you said is a tacit conspiracy between ISP and google to push email servbers to be hosted on their servers/IPs so they can control you more.
fucking nightmare
reply
This is why these things need to be ensured / fixed on the protocol level.
Consolidation is inevitable because humans are lazy and prefer to just pay someone else to handle it.
But I suppose one way to try to ensure decentralization is to make self-hosting as easy as possible and as early as possible, before consolidation can happen.
reply
Your analogy is better. However, software roads probably don’t approximate physical ones - way less scarcity … either way, this sucks and it’s why privacy is harped over and over in ln protocol dev. Hopefully we’ll solve this.
reply