| Hi, authors here (Again, as we already have had the pleasure a while ago). > The main problem with this article is that all the points apply equally to other services, but the article frames it such that it implies the problems are unique to XMPP. The article never states that these issues exclusively apply to XMPP. In our opinion, users should be aware of these downsides that might be obvious to technical people, but aren't obvious to others. And no, not all the points apply equally to other services. Even if this would be the case, then should we just withhold downsides of XMPP because these downsides might also apply to unrelated communication protocols? This article is about XMPP, not about something else. > Pretty much everything else listed is solved by verified end-to-end encryption, which is the primary solution to these problems regardless of any platform or protocol you use. No, as stated in the article, you can't solve most problems with XMPP by enforcing E2EE in XMPP. This article is about XMPP, not about unrelated communication protocols that might have similar problems. > Instead of focusing on helping educate people sensibly about these things, the article seems to be a lot of biased scaremongering. Ehm, no, again, this article lists verifiable downsides of XMPP. People should be aware of these downsides and decide on their own what they want to do. There is no need to call it "biased scaremongering." > Full disclosure Full disclosure: We aren't involved in any XMPP projects or any other projects related to instant messaging. No party paid for our article. |