laosb

Telegram's servers are far from "distributed worldwide": In fact, it currently has only 5 logical "data center"s, and while DC3 is still on, clues [0] seem to suggest DC3 doesn't actually carry user data at all now, and both DC2 and 4 are in Amsterdam, so essentially they just need to serve 3 locations.

Also, Telegram's protocol design only allows for connecting to user's home DC for any write interactions (except media, which in most cases still is home DC, or a "media DC" alongside the home DC). Bots are based on the same DC of the user, so almost all meaningful interactions will happen only on one DC for any specific bot.

[0] https://dev.moe/en/3025

Well it’s actually the same on iOS: Once you granted access by opening a folder via the picker, the app can save a bookmark and have access to it forever.

How plausible the deniability is when they discover you only have those two apps and both logged out due to inactivity, while they can see your storage usage is definitely larger than those two apps?

I would assume it’s because their QA doesn’t test against anything other than WebKit & Chromium browsers at all, so to avoid any potential problems, they decides it’s easier to just urge the user to use supported browsers. Yes, modern web apps should not have big problems on Firefox, but yes it’s also not officially supported.

Hello, I’m the author of App Privacy Insights, an app which parses and presents the iOS 15 App Privacy Report. This app is built with SwiftUI and Core Data, and uses iTunes API to query app information. The app privacy report provides a lot of useful raw data, and I planned to implement more features to really dig into this. Any suggestions are welcome!

Er forgot the link to doc: https://core.telegram.org/import-stickers

As a user since your beta on Airport: Congratulations for making it on App Store! Just to let you know that Telegram has client-side API (and SDK) for creating sticker packs - hope you can support it!

Big Sur 11.1 did fix a bug of M1 Macs not being able to reinitialize connections to external displays or wrongly detect the resolution of the integrated display. I no longer have external display issues on M1 MacBook Pro. Might be related?