I recently switched back to plain GitHub Pages DNS – see comment in #109. Something must have gone wrong in the process and now I cannot activate GitHub's own HTTPS functionality. (DNS is already switched over and published a long time ago)

I’m not really sure what the progress bar is supposed to indicate. Also some of the projects which are at 100% have what I would argue is limited support for OMEMO. I therefor propose to replace it with a feature check box table that indicates various levels of support. (Sub) features that are historically milestones in the OMEMO development process include

• 1:1 chats
• trust management
• multi user chats
• the aesgcm uri scheme for HTTP upload

Am I XMPP yet?

I just wanna propose an idea without pushing anyone to do, as I know it is lots of work. I just had this in mind.

So, we now have a webbased server comparision by Daniel Gultsch and Rishi Raj: https://compliance.conversations.im/

And with your website we have a tracker for OMEMO compabiltity. However, a good xmpp client is not only based on OMEMO support. There are lots of other XEPs and features, which a client should support, nearby modern design. So, a website like the Compliance Tester and omemo.top would be an awesome thing for new users to make the right decision and see whats choices they have.

Kind regards

it's said to work somehow:
https://github.com/gkdr/lurch#does-it-work-in-finch

what are the criteria for the progress states? i guess the implementation status should be set to at least "testing: yes".

https://tigase.tech/issues/7511

Sent in via E-Mail: https://uwpx.org/

Someone wants to help adding it to our list?

It seems to support OMEMO via Plugin but it isn't really stable es far as I can see

https://adium.im/

Hi,

if you search for this Website or get it as search result, it looks like this:

For people like 'us' might be obvious what the ?OTR:.... means - for other, maybe normal users, this might looks like something awkward and/or they mistrust the website. I think we should erase this. Furthermore, the website issues OMEMO and not OTR anymore (even so, OTR is part of OMEMO).

What do you think?

Cheers

Hello, I offer bounty for OMEMO support for Psi+, but not on bountysource. Please add that to the list.
psi-im/plugins#10 (comment)
psi-plus/main#673 (comment)

OMEMO conversejs/converse.js#497 was implemented in https://github.com/conversejs/converse.js/releases/tag/v4.0.0

I don't know how to properly put it on the list, so creating issue instead.

There is another OMEMO plugin for Pidgin, libpurple-omemo-plugin. Judging by description, it seems to be less stable than lurch, but probably will be improved too.
Also, it seems like at least lurch works in Finch too, not sure about libpurple-omemo-plugin.

Pidgin is categorized fully complete, but I don't think it really is. The ticket still actually has the "new" status.

The OMEMO support is achieved by building and installing a third-party plugin that is labelled as "highly experimental" according to the readme. And to achieve the multi-device capability, an important selling point of OMEMO, you need to build and install another third-party plugin for Carbons. Even then the multi-device capability isn't quite complete, since there is no Message Archive Management available for Pidgin at all.

Feature: Free your JS using LibreJS standards.
How: https://www.gnu.org/software/librejs/

What do you think?

It is listed as Jitsi. I think it refers to older Jitsi desktop client? Then maybe it should be named as "Jitsi Desktop (Legacy)". With os_support: [Linux,macOS,Windows]. Link should point to https://desktop.jitsi.org/ I can do a PR. Just wanted to discuss this first.

Because Jitsi is more as an organization now. They have Jitsi Meet as a product, which can be listed separately.

While the current design is super awesome, we think we need something more polished here :)
Please feel free to send your thoughts (a.k.a Wireframes and/or Pull Requests).

The following requirements should be met:

• Use Jekyll Theming
• Responsive Design
• Keep all current info
• Make it beautiful ( this includes keeping the clownfish OMEMO logo)

Hey there,

I have just finished a first version, apparently working, of an Xtra for Adium, https://github.com/shtrom/Lurch4Adium.

From my rudimentary tests, it works as it should, so I guess this should address the Adium case.

I think there is way more info than we can cover at the moment (see #38). So – having a small section per client (maybe even with installation help / packaging status) below the table would be really nice.

Please add the messenger Coy.im, who declined to implement OMEMO (with flimsy excuses, IMHO), and instead want to implement a new OTR.

Maybe you need a new status "rejected" or so.

coyim/coyim#233

Hi,

unfortunately we should treat clients who hasn't received any activity for 1-2 years as dead

💀

E.g. Pidgin, Jitisi (Chat Client), Candy....

This would prevent people from going for dead client

There is a listing for Chatty (Purism OS). I think it is now called Librem Chat. Also OS would be PureOS, as Purism is a company. What do you think? We can still leave a link to the blog post that calls is Chatty as a historic link.

Hi,

what about listing this fork of Conversations?

https://github.com/kriztan/Pix-Art-Messenger/releases
https://jabber.pix-art.de/

Unfortunately, it is only available in German at the moment. But this could be mentioned, or?

Cheers

Hei, SailfishOS is nice, but the native xmpp client has no omemo encryption.
Can you please add it to your list?

Converse does not support OMEMO for group chats:
conversejs/converse.js#497 (comment)

This PR is wrong:
#121

In addition to the client support of omemo, a list of implementing libraries would be useful for those who want to add support for a particular client (using one of said libraries). Useful attributes to track would be:

• links to website and source code
• programming language
• actively developed? (esp. w.r.t. security issues)

may omemo.top be a place for that too?

The client sections of #40 are missing a simple "Go back to top / table" 🏠 style button to quickly scroll up to the table.

Preferably in the white space between the dimmed sections:

PRISM break is a list of free open source alternatives to proprietary software. Its not an XMPP client and therefore it is not able to do OMEMO encryption.

Is it possible to have the list sorted first by "done" and then by "work in progress", because it would be nice to see the finished ones first.

Or maybe include a date of publication/latest update and sort by that? Then we could attribute conversations to being the first one :)

I would do the work it if you think it's a good idea.

ChatSecure doesn't support OMEMO in MUC: ChatSecure/ChatSecure-iOS#580 and has issues with OMEMO file transfer (it is not working): ChatSecure/ChatSecure-iOS#810

Hi,

I was wondering if it could make sense to sort all the "OMEMO not supported" tagged clients to the end of the list?

What do you think?

Cheers

Not sure why and if this is only temporary, but the site fails to load the Tablesort module.

Seems like they have some progress on OMEMO:
https://github.com/miranda-ng/miranda-ng/commits/master/protocols/JabberG/src/jabber_omemo.cpp

the "tracking issue" icon link areas overlap well into the icons of the preceeding clients.
clicking the linked "tracking issue" icon may lead you to the page for the client listed below if you hit near the lower end of the icon.

The list seems to be completely unsorted. Sort it by any obvious or intuitive criteria like:

• alphabet
• ticket status
• …

I'm having high hopes on Monal, with ChatSecure giving my iOS friends quite a lot of headaches with notifications for omemo messages.
That said, the Monal Testflight betas don't have omemo implemented yet, so I find the 80% graph on omemo.top kind of misleading.

Thunderbird has a libpurple chatclient. I am not sure how to use libpurple plugins there, but i opened an issue at the lurch repo as well.

It appears as though it has appropriate OMEMO support. I am not a technical user, but it would appear that this is out of date.

Hi, would it be possible to show in your table an entry for distribution packaging? like "available in..." with debian, fedora, centos and arch (aur)?

for debian/ubuntu there is no packaging with lurch for example :)

kandru is a conversations fork and probably supports omemo or will do so soon.

Some issues referenced by omemo.top to track omemo progress of clients are closed while progressbar is not 100%
ex: dino/dino#36
ex: ChatSecure/ChatSecure-iOS#376

What has to be done about this? Reference other issues? Implement #122?

(btw: https://en.wikipedia.org/wiki/Comparison_of_instant_messaging_clients#XMPP-related_features claims omemo support of chatsecure)

http://omemo.top/ does not redirect to https://omemo.top/
I think you just have to enable a checkbox like described here

I think the list is for the clients, not for the services. Am i wrong? Because one would also list some other services providing XMPP web chat. I don't see an option to download, install or embedd Xabber Web as Converse.js or Candy. I think it should be removed.

Vacuum-IM is a C++/Qt XMPP-client. Currently in transition from Qt4 to Qt5.
OMEMO support issue

Thanks.

I'm a little bit confused, why the list "Client Progress" is containing some libraries (Slixmpp, SleekXMPP).
I think those should be listed in a separate "Library Progress" list instead.

Some apps are highly unlikely to get OMEMO support anytime soon (see for example redsolution/xabber-android#540).

It would be nice to have a visual indicator that tells the user that OMEMO is not going to be implemented at all. This would prevent devs from getting spammed from user requests for that feature.

While there are several closed issues about the list to be sorted (#21, #38), the list still is not sorted. Please sort it. Thanks.

Since sorting might not be that easy in liquid, https://stackoverflow.com/questions/8991995/using-liquid-to-sort-posts-alphabetically might be of help.

http://profanity.im seems to be abandoned

current website is
https://profanity-im.github.io/

(edit: i tried doing a pull request myself but didn't quite work out, still have to figure out git...)

Hi,

would be great to use the OS information from the yml file to aslo show the supported operating system for the client.

Cheers

Currently when OMEMO support is still in progress it shows a bookmark icon. The hover text says "Client is working on OMEMO support". First, client itself can't work on something. This is done by people, developers, so semantically this is not right, in my opinion. This is even more confusing to not native English speakers (as i understood from a recent chat on Spark support forum). They read this like "Client is working with OMEMO support". They don't get the nuance of "on". They see "Client is working" and the quickly conclude, that it should work. So, i would suggest changing that to something like "Developers working to support OMEMO". Yeah, this still can be confusing, but maybe a bit more clear and correct. Maybe something like "No support for OMEMO yet" would be even more clear. Maybe also changing the icon to some tools or construction sign ("under construction") also makes sense.

https://github.com/dino/dino
Fresh gtk3 client, yet seems to be already supporting OMEMO: dino/dino@d5ea517 At least they are working on it.