@SupportGrapheneOS_667 @GrapheneOS same here as in my previous comment. This just states the default problem and is also outdated since MTProto 2.0, Kuketz references problems of 1.0, which were real. While I don't like bad defaults, this ultimately is a design choice. The malicious part is calling it private by default. But: That's just bad faith marketing. Microsoft also says their shit is secure. Nothing different.

Anybody got something _recent_ about MTProto 2.0?