RU version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
93% Positive
Analyzed from 846 words in the discussion.
Trending Topics
#telegram#data#https#coast#more#servers#channels#different#centers#politically

Discussion (26 Comments)Read Original on HackerNews
Also, it looks like it's easy enough to ID your DC on their API, though I haven't tried it yet (more of a Matrix Stan personally): https://core.telegram.org/method/help.getConfig
Any DC may refuse a request and force the client to switch DC.
Profile URL doesn't show where messages/chats/channels are stored, as telegram has two dedicated DCs mostly for media. The rest DCs allow media with bandwidth being throttled.
[1] - https://telegram.org/privacy
Something like this:
I love mentioning the UK in these kind of discussions because the pushback is biggest every time the Crown is mentioned, and ultimately US/CA/NZ/AUS are all colonies under the King.Really cool to see realpolitik mapped out like this. It also highlights the problem of metadata with these kind of topics.
Why not a sticky master election per user, and have no special data centers?
You are suggesting to develop a compicated solution (spend money) when current simple one is working ok without any elections.
If you're feeling any better latency on the west coast it's more likely to be placebo than real.
• Quincy, WA (Microsoft)
• The Dalles, Oregon (Google)
• Prineville, Oregon (Facebook, Apple)
• Hillsboro, Oregon (Cloudflare, others)
• Boardman, Oregon (AWS)
[1] https://dev.moe/wp-content/uploads/2022/05/image-14.png
[2] https://en.wikipedia.org/wiki/Arrest_and_indictment_of_Pavel...
(and a follow-up: https://istories.media/en/news/2025/06/10/telegram-responds-... )