reply on: Real life example of Lightning Network censorship AKA “What's wrong with LN in one tweet” \ stacker news ~bitcoin

pull down to refresh

5 sats \ 2 replies \ @thrown OP 26 Dec 2021 \ parent \ on: Real life example of Lightning Network censorship AKA “What's wrong with LN in one tweet” bitcoin

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)

3 sats \ 1 reply \ @DarthCoin 27 Dec 2021

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

1 sat \ 0 replies \ @thrown OP 27 Dec 2021

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.