Hacker News new | ask | show | jobs
by problems 3409 days ago
You might check out Conversations too (https://conversations.im/), it's a federated XMPP (with some really clever extensions) based approach that uses the signal protocol.
3 comments

Yes it is:

https://github.com/WhisperSystems/Signal-Server

It's sure become fashionable to hate on Signal/OWS. The price of actually successfully bringing good encryption mainstream?

Edit: The comment I replied to originally included a question on whether Signals server is even open source.

Signal is not mainstream. And you can't verify that Whatsapp/Allo have implemented the whisper protocol the way they claim to. We are being asked to "just trust them".
I have had success with getting lots of people on it. And the key selling point that it is no more difficult than WhatsApp makes that possible.

And that "no more" is really important. "Just slightly more" won't do. Especially not if it's "slightly more to someone who frequents HN". Because that's likely already prohibitive to most.

Take a person that just barely knows how to operate the play store. I can instruct that person over phone how to start chatting with me securely in a minute or two:

Go to the play store, download signal, open signal, I'm already there in your contact list. Write me a message. Done.

That's an amazing achievement. The much maligned fact that phone numbers are used as identifiers is key to that experience, too, because my phone number already is on that persons phone.

And yeah, I can't verify Whatsapp, but I still trust that Moxie et.al. have checked their implementation. Still that's why I push people to switch to Signal rather than stay on WhatsApp. Doubly so as WhatsApp belongs to Facebook now (I loved their original 1 Dollar a year business model, and if they still had that I would trust them a lot more).

Even with doubts about Facebook, it almost certainly is a massive win that WhatsApp implemented this. It makes WhatsApp immune to being subpoenaed for conversations, and thus they have a clear motive to implement it properly, too.

Signal is mainstream enough to have been used by the Clinton campaign in 2016 for internal communication. That's pretty mainstream.
A presidential candidate (and team) of one of the more powerfull countries in the world using Signal is not "mainstream". It's "due diligence".
> The comment I replied to originally included a question on whether Signals server is even open source.

Sorry about that, I had looked it up just a second after I posted and then removed that line.

> hate on Signal/OWS

I don't mean to hate on them, just their stance on getting away from Google, using F-Droid, federating their service and many other things has been more than a bit of a mess or disappointment. I'm glad they finally made a step in the right direction and I hope this will continue.

The thing is, they gave good reasons on all these points. It's certainly valid to disagree with the trade offs, but people don't acknowledge that there are trade offs at all.

As I said in another reply, I can get a completely non-technical user to start using Signal with me in a minute, and have them have an experience that is as accessible as WhatsApp. That's simply not true for any of the other options I'm aware of (and it relates directly to most of the points you raise, with the notable exception of F-Droid. There I also find their reasoning weakest).

You can host a server, but you can't talk with people on the official Signal server or any other Signal server, as far as I am aware. This is not federated, just allowing of other isolated centralized clusters.
The Signal server software has federation support. It's not enabled (anymore) on the official server but anyone could set up a server and federate with other federation enabled Signal servers.
I really like XMPP and use it with conversations.im every day. I even have my own XMPP server for friends and family, but it feels as if only very few developers spend time on modern clients. XMPP with its extensions is pretty mature and works great (if properly implemented). Sadly there very few up to date clients. Conversations.im seems to be the exception here. It is very stable, mature and energy efficient, but still lacking audio and video support.

I wish there would be more devs building modern clients for XMPP instead of building the 100th communication system.

I use it, but feel like XMPP is dated and complicated. All the extensions and whatnot are awkward to get setup and you can't make assumptions about how well they're implemented or built on the server you're on or communicating with. I intend to move to matrix/riot when it gets more stable. Things like video are second class citizens on XMPP too and the desktop apps are painful in my experience.
I definitely wouldn't suggest it for video, but I've never had an interest in video conferencing in general. Extensions are pretty straight forward in my experience - either your server supports them or it doesn't, but most of the time they only impact client-to-server in this case rather than server-to-server.