Skip to content
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.

XMPP E2EE tracking #1838

Open
4 tasks
Mikaela opened this issue Apr 18, 2020 · 12 comments
Open
4 tasks

XMPP E2EE tracking #1838

Mikaela opened this issue Apr 18, 2020 · 12 comments
Labels
approved approved, waiting for a PR 💬 discussion ℹ️ help wanted XMPP Extensible Messaging and Presence Protocol

Comments

@Mikaela
Copy link
Contributor

Mikaela commented Apr 18, 2020

XMPP is under thread of delisting in https://github.com/privacytoolsIO/privacytools.io/pull/1836 as there is currently only one client known that has OMEMO enabled by default, Conversations.

I wish to relist it as soon as it comforms the criteria and I hope this issue can be used for tracking issues related to that.

From XMPP Compliance Suites 2020 / Future development there are a few interesting specifications linked:

@Mikaela Mikaela added ℹ️ help wanted 💬 discussion XMPP Extensible Messaging and Presence Protocol approved approved, waiting for a PR labels Apr 18, 2020
@Mikaela Mikaela self-assigned this Apr 18, 2020
@dngray
Copy link
Collaborator

dngray commented Apr 18, 2020

I've subscribed to this issue, because I am curious to see how it develops.

I think we that we can continue with https://github.com/privacytoolsIO/privacytools.io/pull/1836.

@jonaharagon
Copy link
Contributor

jonaharagon commented Apr 19, 2020

We're going to relist "Matrix" as "Riot" in #1836 because we realized we wanted to avoid recommending protocols (which is mostly helpful for administrators) and focus on recommending clients (which is more helpful for end-users, our target).

So we can rethink criteria a bit, and maybe that deserves its own issue, but what it boils down to is:

  1. The client needs to be secure and privacy-respecting (which I think Conversations is)
    • I think we should also agree now whether we only want OMEMO (this is my current assumption) or if OTR is acceptable.
  2. Users need to be able to communicate across platforms to avoid vendor lock-in.

The second point being where I think "XMPP" is currently failing, because Conversations is Android-only... I'm not against listing XMPP clients per-operating-system if we need to, but I'm not aware of any other decent clients, so what we're waiting for is...

  • Android: Conversations
  • iOS
    • Having used ChatSecure and Monal I feel incredibly uncomfortable with recommending either. Unless they have drastically changed in the past 6 months.
  • Linux: Dino?
    • Which may not be a good recommendation due to the lack of tagged releases multiple people have brought up, so I don't know if we want to consider it.
  • macOS
  • Windows

A web-client would also be neat but is perhaps wishful thinking. But I think when decent clients materialize for all of the above platforms we can probably list that set of clients as our general "XMPP" recommendation for RTC.

@Mikaela Mikaela removed their assignment Apr 19, 2020
@Mikaela
Copy link
Contributor Author

Mikaela commented Apr 19, 2020

https://conversejs.org/

@nitrohorse
Copy link
Contributor

For iOS clients, I believe Monal has the most active development with Siskin coming in 2nd and now ChatSecure in 3rd.

Having used ChatSecure and Monal I feel incredibly uncomfortable with recommending either. Unless they have drastically changed in the past 6 months.

No, I don't think either has drastically changed in terms of UX or UI.

@woj-tek
Copy link

woj-tek commented May 6, 2020

@jonaharagon there is SiskinIM for iOS (https://github.com/tigase/siskin-im/) and BeagleIM for macOS (https://github.com/tigase/beagle-im/)

@mdosch
Copy link

mdosch commented Oct 27, 2020

As others already mentioned: Siskin is the client I recommend to iOS people.
Also if you have objections to Dino you could recommend Gajim for Linux and Windows (I'm not sure about the state on Macs).

@GintokiHub
Copy link

I find gajim quite easy to use actually. It might seem a -littele-bit- imposing at first but it's really quite straightforward IMO.
What are others opinion on the client for windows?

@mdosch
Copy link

mdosch commented Oct 28, 2020 via email

@arendtio
Copy link

Just contributing my experience:

  • Conversations is superb. Quicksy (Conversations flavor + Account) might be worth mentioning, as it has the lowest entrance barrier.

  • iOS clients are a disaster. Currently, I have ChatSecure and Siskin installed, but neither works in a way that I would recommend it. ChatSecure seems to be the best but it has some serious issues (like asking to confirm valid SSL certificates when they get renewed).

  • For desktop usage I recommend Gajim. I tried Dino from time to time but always returned to Gajim so far.

All these clients support OMEMO afaik. I don't think that having OMEMO enabled by default should be relevant for listing XMPP clients. On the other hand, I would not recommend clients that only support OTR (used a few years before OMEMO became a thing and still remember those slow transfer speeds).

Haven't tried anything on MacOS yet, but I heard that Monal is a bad but still the best option.

@albjeremias
Copy link

why isn't conversations on privacytools.io ?!

@mdosch
Copy link

mdosch commented Sep 9, 2021

See above, because conversations is android only whereas riot is everywhere.

@Mikaela

This comment has been minimized.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved approved, waiting for a PR 💬 discussion ℹ️ help wanted XMPP Extensible Messaging and Presence Protocol
Projects
None yet
Development

No branches or pull requests

9 participants