>So their operators claim. But it's not clear why that would be true and I haven't seen any numbers to demonstrate it either. Have you?
Telegram had to survive Russia's attempt to ban it, so it evolved a number of strategies: using push notifications to deliver IP-adresses of not-yet-blocked servers, using socks-proxies, the evolution of the MTProto Proxy encrypted protocol, and finally resorting to steganography to mimic ordinary https traffic, thus evading the DPI.
The attempts of the state censorship agency to block the telegram servers were hilarious to watch: at one point they had 0.5% of the IPv4 address space banned, and broke a lot of stuff (AWS, Google, DigitalOcean, OVH, etc). Telegram was still working, of course.
IMO, the legal network and a reputation of always suing airlines are the most important things in this line of business.
For example, if you are seriously delayed while departing from an EU airport, you are entitled to a compensation. Inside the EU this mostly works, but consider the case when you live outside the EU and the non-EU airline basically tells you: "sue us".
I'm currently using the services of one of their competitors to try and extract 250 euros from one small airline that thinks that because they're outside the EU they can delay a flight for two days and not pay the legal amount.
I asked XXXXX,the NRO PSO, if fairing logos require White House approval. XXXXX said after the octopus logo (NROL-39), the White House threatened to require presidential approval if the NRO approved any more menacing logos.
This Latin approach has worked before and allowed one of my previous organizations to have the slogan "Doing God's work with other people's money" fly right through the approval process. [1]
[1]https://www.theatlantic.com/politics/archive/2012/02/youre-m...
I hope one of those planned locations will be somewhere in Eastern Europe. At the moment I measure a 44ms ping, which is just 1ms slower than 8.8.8.8, and 2ms faster than OpenDNS for this location.
Telegram had to survive Russia's attempt to ban it, so it evolved a number of strategies: using push notifications to deliver IP-adresses of not-yet-blocked servers, using socks-proxies, the evolution of the MTProto Proxy encrypted protocol, and finally resorting to steganography to mimic ordinary https traffic, thus evading the DPI.
The attempts of the state censorship agency to block the telegram servers were hilarious to watch: at one point they had 0.5% of the IPv4 address space banned, and broke a lot of stuff (AWS, Google, DigitalOcean, OVH, etc). Telegram was still working, of course.