Oddbean new post about | logout
▲ ▼
mleku | 5 days ago (raw) | root | parent | reply | flag +1 
 i don't think they get to control, only to restrict, there's a difference, and if they do that too much they risk losing your subscription

same with the cloud VPS and same with the DNS registrar, and same with the ISP - ok, in some places all of these things have a high cost to give the old provider a GFY but when you get mad that is worth the price of the fuck you money and well that's part of why bitcoin anyway
▲ ▼
ChipTuner | 5 days ago (raw) | root | parent | reply | flag +2 
 > i don't think they get to control, only to restrict, there's a difference, and if they do that too much they risk losing your subscription
Right, but if every provider does it, then where are you going to switch to? For instance port 25 incoming and outgoing traffic is blocked by default on every cloud service I've worked with in the US. You must express written formal request to open port 25 and submit a KYC. 

This is because government has laws in place to restrict this, but what are my choices?
▲ ▼
mleku | 5 days ago (raw) | root | parent | reply | flag +1 
 my VPS in bulgaria also restricts port 25 but i have zero interest in doing SMTP service anyway... my workaround for this specific case would be that the middleware or client side would have a wireguard extension to access a private network for this, and that would satisfy the auth requirement that is the reason for this restriction

SMTP is broken, utterly, it's the main reason why google has monopolised email