Live data from Hacker News

Russia Bans 1.8M Amazon and Google IPs in Attempt to Block Telegram

bleepingcomputer.com

201–210 of 228 posts

Re: Russia Bans 1.8M Amazon and Google IPs in Attempt to Block Telegram

#202
post #37

Earlier quoted context omitted.

Because the Russian government can read all non-E2EE conversations (so 99% of them) on Telegram and is hoping to drive adoption overseas with this PR stunt. None of the other messengers you mentioned are designed to work like this (not 100% sure about Viber), the ability of operators to read most of the conversations on the platform is very much unique to Telegram. It's really not a coincidence that the Russian gover…

Do you have any proof?

What would you like me to prove?

That Telegram has handed their keys to the Russian government? Difficult, but unnecessary.

That Telegram was deliberately designed in a manner which enables its owners to easily hand over the keys to the government? Easy to prove, Signal and Whatsapp do not share the same surveillance features.

Re: Russia Bans 1.8M Amazon and Google IPs in Attempt to Block Telegram

#203
post #127

Earlier quoted context omitted.

Usually Russia don't play that smart. Wondering how would they replace those services.

It would actually seem like an ideal way to force the adoption of native cloud service replacements (regardless of quality or competitiveness of the offering). Russia has tended to go that way with most things, whether Mail.ru, VK or Yandex. Russia has a very long history of being insular like that and the powers that have dominated Russia the last century have a vested interest in keeping it that way.

The only reason why local hosters are making money is local personal data law which restricts that PD of russian citizen should be stored inside Russia, because their prices and level of service is non-competitive to i.e. DO or OVH.

Re: Russia Bans 1.8M Amazon and Google IPs in Attempt to Block Telegram

#204
post #146
post #75

Earlier quoted context omitted.

If IPv6 was used Russia would ban address ranges instead.

I think he meant that only Telegram would be be blocked instead of possibly affecting half of the Internet on the way there. For Telegram it wouldn't be any better.

They would still be blocking the IPv6 netblocks assigned to Amazon and Google, only it would be easier because the blocks would be more contiguous.

Re: Russia Bans 1.8M Amazon and Google IPs in Attempt to Block Telegram

#205
post #147
post #120

Earlier quoted context omitted.

One argument might be "because Signal * has (almost) no tests, * has no CI (at least I could find none), * lacks some basic features competitors have, * sometimes doesn't ring when you call, and * they just closed all 1100 open issues without reading their contents [1]." Don't get me wrong, I think Signal is a great idea and have contributed some code to it, but these look like some red flags to me. Obviously hard to…

Good points, but I think it's good to mention that Telegram is actually open source: https://telegram.org/apps#source-code

It's actually dated-source. The source code they occasionally publish is always months beyond the recent release.

Re: Russia Bans 1.8M Amazon and Google IPs in Attempt to Block Telegram

#206
post #178

Earlier quoted context omitted.

So much misinformation in the replies here. Russians do make up a huge list of telegrams overall userbase. But most importantly, whatsapp and viber are end to end encrypted. Whatsapp uses signal. Viber uses a signal inspired encryption format. The common ground between both is that every single message is encrypted using a different secret key that is deleted after the message is received and decrypted on the device.…

Just wanted to note that Telegram still supports E2EE in their secret chats. It's just less convenient.

For unknown reason user verification (for secret chats) is awful and almost useless in practice. Telegram itself reimplemented this specific bit much much better - for video chats

Re: Russia Bans 1.8M Amazon and Google IPs in Attempt to Block Telegram

#207
post #120

Earlier quoted context omitted.

One argument might be "because Signal * has (almost) no tests, * has no CI (at least I could find none), * lacks some basic features competitors have, * sometimes doesn't ring when you call, and * they just closed all 1100 open issues without reading their contents [1]." Don't get me wrong, I think Signal is a great idea and have contributed some code to it, but these look like some red flags to me. Obviously hard to…

All those issues were closed, as it is explained in your link, because they lacked debug logs/steps to reproduce the problem/etc. It's not feasible to dedicate enormous amounts of resources to try to address those issues. You're welcome to re-open them, properly this time, if you want.

That is wrong. If you read the thread, you would immediately see that, as I give examples there of how issues that were in the middle of being tested by users were closed, and that were acknowledged as real issues by the developers days before.

Re: Russia Bans 1.8M Amazon and Google IPs in Attempt to Block Telegram

#208
post #166
post #147

Earlier quoted context omitted.

Good points, but I think it's good to mention that Telegram is actually open source: https://telegram.org/apps#source-code

No, it's not. Telegram clients are; telegram, as a service - the server component - is not.

Further, the Android app doesn't have an issue tracker. According to [1] and links in there it was removed without explanation.

[1] https://github.com/telegramdesktop/tdesktop/issues/1137

Re: Russia Bans 1.8M Amazon and Google IPs in Attempt to Block Telegram

#209
post #3
post #2

Insane! Telegram is blocked in my country too but they didn't block millions of IPs I think to achieve that!

From TFA, Telegram moved to the Amazon and Google clouds to work around the ban, so they needed to block those addresses.

Thanks for the information

Re: Russia Bans 1.8M Amazon and Google IPs in Attempt to Block Telegram

#210

Earlier quoted context omitted.

> WhatsApp and Messenger content. (emphasis mine) Isn't WhatsApp supposed to be end-to-end encrypted making it next to impossible even for developers (Facebook Inc. in this case) to access the transmitted messages' content?

Wasn't it WhatsApp that sent a key back to Facebook servers? Technically it's end-to-end encrypted, but Facebook could decrypt it if they really wanted to.

Do you have a source for this claim?

It does not sound correct.

Post reply on HN