|
|
|
|
|
by spwa4
61 days ago
|
|
The problem with these efforts is always the same: organizations make their own messenger, and the fact that these organizations then have control over their own messenger ... means their employees won't use it. And that's ignoring that you can bet your firstborn they cut corners developing these messengers, so they're not pleasant to use to boot. In 2026 you still hear complaints of government employees that they only have 200 mb of mailbox space ... sigh People "don't trust" in the very abstract sense, Mark Zuckerberg. But in a very real sense they don't trust their manager at all, and they know their own manager can see their messages on the "sovereign" messenger. Zuckerberg wants to sell them stuff they don't want on occasion. Their manager ... well they're cheating their manager. Oh and it doesn't even buy extra security: the platform owners can spy directly through hardware backdoors, they can "update" any app on the phone, and they have the root keys to the secure element, and so it isn't secure to them. And if you look under the covers ... the backend is on AWS? No? Must be on Azure then. So annoying lots of people, reducing functionality, for no actual security. Sure sounds like EU governments are behind this ... |
|
For private discussions, you do that on your private device, with a private messenger.
I would say that the digital sovereignty is more about "Entity X doesn't want the US to have access to all of their internal communications". Typically a non-US company or a non-US government should care about that.