41–50 of 142 posts
The very first sentence irks me: "[…] for the only standardized chat protocol [XMPP]" Haven't they heard about IRC (RFCs 1459, 2810–2813)?
screen + ssh + irssi (+ bitlbee, if you need xmpp) > any web based solution. Why? Because I can see it on my phone and on my laptop, and it's as lightweight and simple as a `ssh -t irssi.myDomain.foo screen -DD -R` and I'm all caught up. This is, ofc, my $0.02. Stuck in the old way of doing things, I guess. Still pretty cool, particularly the deploy on DO.
Earlier quoted context omitted.
> The client code comes from the server, so you need to trust it anyway. Sure, but we have TLS for that. E2E is still needed to cover everything else (e.g., I trust the server now , but I don't want to have plain-text logs on it in case the feds seize it).
OTR also breaks Message Archive Management (MAM) and Carbons - the two features making multi-client operation any useful, and highlighted in the article. And with MAM, there actually are plain-text logs of your conversations on the server. The call is still open on end-to-end encryption over XMPP when multiple devices (or more than two parties) are involved.
Is there any chat system out there with end-to-end crypto and reasonable support for multiple devices?
Is there a good mobile client to use with a xmpp serveR?
Is there a good mobile client to use with a xmpp serveR?
Besides of the ones referenced in the article, there is also ChatSecure [0] for Android and iOS (with a strong focus on security) and Xabber [1] and yaxim [2] for Android (I am the maintainer of yaxim). [0] https://chatsecure.org/ [1] http://www.xabber.org/ [2] https://yaxim.org/
I've been working with XMPP and a number of XMPP daemons. A couple years later I'm not a fan.
The UI feels like a 1 to 1 copy of the Slack client, or is Slacks UI so common now copying it is just using the Chat-UI standard?