209
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 06 Jun 2024
209 points (96.9% liked)
Open Source
29787 readers
44 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
What I mean by closer is code-wise. On the backend, WhatsApp literally uses XMPP. The big difference is that WhatsApp also has a few proprietary plugins, and a singular client that uses these and hides away the fact that it's all XMPP.
That’s why it’s less janky & doesn’t take minutes to join a room unlike Matrix. WhatsApp to the XTENSIBLE part of XMPP & extended it in a proprietary direction, but at least you have the option to easily do so with XML.
I don’t know what Matrix is giving users other than the eventual consistency model of chat, but most users don’t need the entire chat history of everything—you could argue it is an anti-feature that makes self-hosting too expensive in comparison & also leads to chat overuse/abuse ala Slack/Telegram/Discord where folks treat it as a forum that you can barely search when you have an account while being authenticated & where messages/topics get easily lost. For instance, you can replace an ’announcements room’ with a Atom feed.