Will it still support OTR (E2EE not dependent on the protocol in use) for all the protocols it implements? Meaning whether or not a platform has pseudo E2EE, will Pidgin 3.0+ eventually support using it's own E2EE especially if cranky old farts like me do not and will never trust server managed pseudo E2EE? Bonus if pre-shared secrets and keys can be shared out of band.<p>Hypothetical Use Case: A bunch of agents and I want to use a XMPP platform hosted by the cartel to raid the cartel and even if they suspect we are agents and even if they backdoor eJabber's own E2EE it would be literally impossible for them to decode the messages as we shared our OTR keys ahead of time on a private LAN or a USB or a stack of QR codes or some punch cards or ribbon tape strapped to carrier pidgins and have our own E2EE on top of their pseudo E2EE.<p>Dictionary: I created the term pseudo E2EE for any of the big centralized platforms that claim to use E2EE and use some client encryption magical incantations from code maintained by said platform. This is not real E2EE regardless of what magical explanation anyone gives.
We’re live on Flathub Beta now!! Flathub Beta means it won’t show up on the site, but it’ll show up in GNOME Software and other app stores after you add the Flathub Beta remote. You can find instructions on how to do so here <a href="https://discourse.imfreedom.org/t/pidgin-3-on-flathub-beta/230" rel="nofollow">https://discourse.imfreedom.org/t/pidgin-3-on-flathub-beta/2...</a>
Just an update that we missed some bugs that were affecting new users so we've released 2.90.1 which fixes them. The linked posted has been updated with this information as well.