this post was submitted on 07 Sep 2025
252 points (98.5% liked)
Privacy
41550 readers
1134 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Because people keep pushing for them to completely leave a platform.
Instead try to get them to dual-use platforms.
One of the big problems nowadays is proprietary protocols. Back in the day, you could have a single client that could talk to different networks. Today you have to run a bunch of separate apps, and what's worse is that a lot of them are built with stuff like Electron that's resource hungry.
Even the FOSS apps don't all get along.
Conversations is great for XMPP, and it can act as a UnifiedPush pusher, but AFAICT it doesn't support other protocols and it doesn't act as a UnifiedPush subscriber.
So running 2 chat protocols, one being the well-support app Conversations on the well-supported protocol XMPP, means 2 push setups and 2 apps. Bleh.
I would like to see an architecture where the expensive app side of things is separated from the protocol. But that's all speculative, I haven't put work hours into it. Basically, if I have an idea for P2P chat, why do I need to re-invent emojis and channels and shit like that? I only want to iterate on transport. And if I have a better idea for channels, why would I have to re-invent the transport like XMPP and Matrix?
(The reason is that cutting those two apart is hard - But I will continue to wonder.)
Oh yeah the whole thing is a mess. It kind of blows my mind that we still don't have a single common protocol that at least the open source world agrees on. Like there is a more or less fixed set of things chat apps need to do, we should be able to agree on something akin to ActivityPub here as a base.
This is the way. I this case they get to "feel" those other options themselves, and even if you are the one that put that seed in their head, they are the ones making that final decision based on their own needs, capabilities and preferences.