Jen, EnbymilfApr 15, 2024

come chat with us online, your options are:

- unencrypted faang client
- other unencrypted faang client
- other other unencrypted faang client
- encrypted faang client that is likely backdoored
- $20 profile microtransactions and constantly changing UX
- client with optional encryption and requires a phone number
- encrypted by default client that also requires a phone number
- 35 year old protocol lacking a lot of QOL features that people still use for some reason
- 25 year old protocol that nobody can agree on which extensions to use
- "unable to decrypt message"

Show threadKevin Karhan Apr 15, 2024

@Jenetrix well, #XMPP just works...

Try @monocles / #MonoclesChat and @gajim / #Gajim.

They just work and do proper #E2EE!

Otherwise consider #IRC for bublic chats and #SelfHosted #Zulip for organization chats...

Show threadash Apr 16, 2024
@kkarhan @Jenetrix @monocles @gajim both of those protocols are in fact in this list :p
also, my experience with XMPP (including Gajim) was incredibly flaky and the inability to reliably keep any history across a pool of changing devices was what ultimately made me quit using it tbh
Show threadnullenvk
@darkphoenix @Jenetrix @gajim @monocles @kkarhan that must've been a misconfigured server tbh.
I had problems with cross-device history synchronization on tchncs.de and some other instance, but once I switched to an instance ran by a friend, the experience suddenly got 10x better (and ofc, cross-device history synchronization started working even on OMEMO-encrypted MUCs)
XMPP

Open source deployments with love! Find your home at tchncs.de

tchncs.de
Apr 16, 2024 at 6:04pmWeb
Show threadash Apr 16, 2024
@[email protected] @Jenetrix @gajim @monocles @kkarhan I'll have you know I misconfigured that server myself tyvm
but more seriously, it seems like there's no solid way across platforms to get old history to a brand new device joining the pool. And, sorry, but that's a hard non-negotiable requirement for me.