3 ms·

From the user perspective, Pidgin is pretty much unmaintained at this point, so it's like complaining that old software isn't modern. Also, ejabberd doesn't dis

From the user perspective, Pidgin is pretty much unmaintained at this point, so it's like complaining that old software isn't modern. Also, ejabberd doesn't disable OMEMO by default for quite a long time already.

arendtio 8y ago
Actually, they still do (or do again?). Here comes the relevant part from their example config [1]: force_node_config: ## Change from "whitelist" to "open" to enable OMEMO support ## See https://github.com/processone/ejabberd/issues/2425 "eu.siacs.conversations.axolotl.*": access_model: whitelist [1] https://github.com/processone/ejabberd/blob/master/ejabberd.yml.example#L223 https://github.com/processone/ejabberd/blob/master/ejabberd....
- seba_dos1 8y ago
  Oh, my bad - it was the default config in Debian package that got changed. I assumed it originated from upstream, but I was wrong and it's actually patched by Debian maintainer: http://deb.debian.org/debian/pool/main/e/ejabberd/ejabberd_18.12.1-2.debian.tar.xz http://deb.debian.org/debian/pool/main/e/ejabberd/ejabberd_1... (debian/patches/ejabberd.yml.example.diff)
com2kid 8y ago
And yet Pidgin is the go to client for people, especially on Windows. When I got a MacOS machine up and running, I installed Adium (top result still if you go around looking for a MacOS XMPP client), also a dead project. On Android, the top XMPP client does not support OMEMO and the new hotness XMPP client does not support OTP! I have a legacy client on Android and Pidgin half hacked together with random plugins on my Windows boxes and I forget what in the world MacOS is running because I have it turned off half the time because the more clients I have connected the more problems I have and holy crap this is why Slack is a great product. XMPP has had 20 years to solve these problems, and part of their problems of course is that the base protocol wasn't designed to solve these issues out of the box. But, from the end user's perspective, Telegram, Signal, What's App, Slack, Discord, and Teams, all "just work"!

arendtio 8y ago

Actually, they still do (or do again?). Here comes the relevant part from their example config [1]: force_node_config: ## Change from "whitelist" to "open" to enable OMEMO support ## See https://github.com/processone/ejabberd/issues/2425 "eu.siacs.conversations.axolotl.*": access_model: whitelist [1] https://github.com/processone/ejabberd/blob/master/ejabberd.yml.example#L223 https://github.com/processone/ejabberd/blob/master/ejabberd....

seba_dos1 8y ago
Oh, my bad - it was the default config in Debian package that got changed. I assumed it originated from upstream, but I was wrong and it's actually patched by Debian maintainer: http://deb.debian.org/debian/pool/main/e/ejabberd/ejabberd_18.12.1-2.debian.tar.xz http://deb.debian.org/debian/pool/main/e/ejabberd/ejabberd_1... (debian/patches/ejabberd.yml.example.diff)

com2kid 8y ago

And yet Pidgin is the go to client for people, especially on Windows. When I got a MacOS machine up and running, I installed Adium (top result still if you go around looking for a MacOS XMPP client), also a dead project. On Android, the top XMPP client does not support OMEMO and the new hotness XMPP client does not support OTP! I have a legacy client on Android and Pidgin half hacked together with random plugins on my Windows boxes and I forget what in the world MacOS is running because I have it turned off half the time because the more clients I have connected the more problems I have and holy crap this is why Slack is a great product. XMPP has had 20 years to solve these problems, and part of their problems of course is that the base protocol wasn't designed to solve these issues out of the box. But, from the end user's perspective, Telegram, Signal, What's App, Slack, Discord, and Teams, all "just work"!