Telegram Beta
32.8K subscribers
1.24K photos
209 videos
1.37K files
1.22K links
Much Telegram, much wow.

👥 @tgbetachat
📎 @tgfiles
📢 @katalogtelegram
🐦 twitter.com/TelegramBeta
Logo by @thedzko
Download Telegram
🔂 Telegram Desktop 1.1.23 stable

1️⃣ See the message author photo and name while searching specific chat messages.
2️⃣ Fix "Send To" menu action on Windows.
3️⃣ Update faved sticker / saved GIF remove button.
4️⃣ Update emoji / sticker icons.
5️⃣ Fix command line parsing.

2017-09-06 #tdesktop #stable
🔥 Features Highlight on Challegram for Android

1️⃣ Chat previews without mark as read.
2️⃣ Blacklist and unban users in channels.
3️⃣ Calculate cache usage of chats list and sort by file size.
4️⃣ Auto Night-Mode: Activates when turning lights off.

http://telegra.ph/challegram-09-07

2017-09-07 @challegram
Telegram Beta 4.3.1 (10855) 20170907 @tgbeta.apk
16.5 MB
Telegram #Beta 4.3.1 (1085) for #Android 4.1+
MD5:_36104f40ea0052d05b33ff3e9bd50895
🔂 Telegram on Play Store updated to v4.3.1 (1085)

2017-09-07 #android #stable
😏 We need unlimited members for group.
Telegram Beta 4.3.1 (10875) 20170909 @tgbeta.apk
16.5 MB
Telegram #Beta 4.3.1 (1087) for #Android 4.1+
MD5:_cce07dba3b75bcbbea28bb7c9c2581e0
🆕 fix when share default theme
Telegram_macOS_3.2.1.104303_beta.zip
21.5 MB
Telegram 3.2.1.104303 #beta for #macOS 10.11+
MD5:_4b3e122317d76e1ace53f47610f2ebd3
👥 @macswift
Telegram_macOS_3.2.1.104303_stable.zip
18.7 MB
Telegram 3.2.1.104303 #stable for #macOS 10.11+
MD5:_3515196c894ecab2c37f46a6c0b53df0
https://macos.telegram.org
🔂 Telegram 3.2.1.104303 for macOS 10.11+

• Scrolling position is preserved when you leave a chat and come back later.
• Fixed a bug with the app loosing connection in background mode.
• Fixed a bug with the app crashing during Telegram calls.
• Bug fixes and improvements.

2017-09-09 #macOS #stable
🐛 Views count in @telegraph bot is reset to zero. #bug
🎉 Supergroups now can have max 20,000 members!
Telegram Beta 4.3.1 (10885) 20170911 @tgbeta.apk
16.4 MB
Telegram #Beta 4.3.1 (1088) for #Android 4.1+
MD5:_9ec6be442dfa57dd67cbadd60433ff71
Telegram iOS 5.0 (133) alpha 20170912.ipa
47.2 MB
Telegram 5.0 (133) Swift #alpha for #iOS 8.0+
MD5:_de4086af08ff303ee8d98cc1a2ef5cf5
ℹ️ t.me/tgbeta/1262
👥 @tgiostests
Telegram Beta 4.3.1 (10895) 20170912 @tgbeta.apk
16.4 MB
Telegram #Beta 4.3.1 (1089) for #Android 4.1+
MD5:_de11da098408a6b3b95c84d06ba93e38
Forwarded from Pavel Durov
On the September 13th Connection Issues

Yesterday Telegram experienced something extraordinary. At 17:45 UTC there was an immense spike in user activity on Telegram that exceeded our peak load by 5 times.

Telegram is different from most other internet services in that we use a distributed server infrastructure, so peak loads cannot make the whole of Telegram go down. However, if one of the Telegram clusters is severely affected, a part of our users can experience difficulties sending and receiving messages.

This is exactly what happened yesterday. Due to the spike, one of the Telegram server clusters went down in part and approximately 15% of the users who were online at the time experienced connection issues from 17:45 to 18:10. The issues were partially fixed at 18:10, but about 11% of online users could still face slow or no performance until 19:00 when the problem was permanently fixed.

The regions that were most affected are Germany, Iraq and the CIS – most notably, Uzbekistan, Russia, Ukraine, Kazakhstan and Belarus. We briefly commented on the situation via Twitter, but I’d like to tell more extensively about it here.

1. First of all, we are extremely sorry for the inconvenience this has caused. The cluster that went down hasn’t had any issues for a few years now, so I can imagine the shock of the users affected by yesterday’s downtime. We understand that you use Telegram constantly for work and leisure, and that we must be online 100% of the time. We take yesterday’s issues very seriously.

2. Secondly, to make sure this doesn’t happen again, we identified the cause of the problem and have eliminated the bottlenecks in our infrastructure that caused the downtime. We think that x5 peak load spikes won’t be a problem any longer. We've also set up a plan to be able to cope with x20 load spikes (however unlikely the x20 scenario may seem) before the end of 2017.

While unfortunately no one can completely rule out the chance of another downtime some time in the future (there’s always a slight probability of some unexpected Black Swan event), I can assure you that we at Telegram are working hard at taking this chance to the lowest in the industry.

We strive to be the winner in every aspect including availability. So far the Telegram uptime stats look good compared to other major communication services – also because Telegram can never go down entirely around the world. But we are not satisfied with just that, and our work continues.

Thanks for your attention, and sorry again to anyone who was affected.