34
cross platform chat alternative to facebook messenger?
(discuss.tchncs.de)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Dec 2023
34 points (100.0% liked)
Open Source
31375 readers
126 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
pidgin, gadjim, chatty, dino, kaiden, psi, psi+... some other ones
it isn't automatic from what I have found. vague "omemo"-related errors are popping up here and there.
what set up do you suggest where the experience is simple? it seems that there are a bunch of standards which servers and clients have varying support for. plus there is a plugin architecture for lot of them which extends or changes functionality, or it matters what version of libraries were used in compilation, and many other little details.
I believe that some people do have a seamless experience but ours hasn't been. If there is some sort of documentation describing exactly how to get going I would appreciate it.
Well you can try https://snikket.org which packages a Prosody server with suitable clients and it all should just work (tm). They also offer a hosted version.
On https://joinjabber.org you can also find recommended clients and servers that should work without problems.
But to be honest, none of the issues you describe are actually real in my experience. Yes you read them everywhere from badly informed online pundits, but if you use a modern xmpp client with a modern xmpp server it all just works without issues and e2ee keys are automatically exchanged on first message without any problem.
There are some vastly outdated clients like Pidgin that do cause issues, but it is a bit unfair to blame that on xmpp, when Pidgin has not updated their xmpp implementation for more than 10 years π
Do you have the impression that I have not actually had the problems I am describing? Like I just read online that other people had problems? Not the case. As I said after you assumed I "only tried Pidgin π€¦ββοΈ" I have tried lots clients.
Who is blaming anything on pidgin? you are the one who brought up pidgin.
The join jabber link is very nice and I didn't find it before. But I actually tried the 2 linux clients they recommend: dino and gajim. And between us, going from memory I think we have tried all but 1 of the recommended servers.
The impression I got from digging around in repos (which I don't really want to be doing just to get a messaging app tbh) is that the problems we had are legit open issues in some cases. But it is hard to diagnose because the client developers don't have knowledge/control of the end user's local environment or the server set up. And likewise the server admins don't know the internals of every single client. End users with problems are challenged to collect all the required information. Here is an example from gagim: Chat History Sync Issue (#11380)
I do not think it is fair to characterize that user as a "badly informed online pundit". They have a problem and it is basically too complicated to resolve with the available resources. There is probably some unknown contributing factor.
Snikket:
https://snikket.org/hosting/
They can host it for you.
As for Gajim, I have been using it for years and never had history sync issues. Maybe you expect to be able to sync old e2ee messages on new devices? That is impossible to do with OMEMO and actually an intended security feature.