I just wanted to say that I have the same questions, and it's a relief to see it posted by someone with more courage. I'm too ignorant to contribute to the discussion though. I don't know how a government or private entity could pressure a FOSS project in this way, unless that pressure was put on the project's git platform. At which point the repo just moves elsewhere.
QuillanFae
I would prefer to use a standardised, client–agnostic messaging protocol than anything that requires a specific app.
I stopped using WhatsApp because using a Meta product makes me feel icky. I use Telegram and Matrix to contact drug dealers. My work requires a combination of Google Chat, Teams and Slack. Some of my friends like to stick to Discord.
What would be really great is if we could all decide on one protocol for sending end–to–end encrypted text and media over HTTPS to a globally unique ID and have everyone use whatever client they like. Like SMTP but more streamlined and secure. Google, Apple, Samsung etc can ship devices with a default client, but allow users to install another one that they like more.
But OEMs don't like things to be open. Apple has iMessage, Google has RCS, and Samsung probably does some bullshit I'm not aware of since committing to the Pixel life. So I will probably always have a folder with 15 different messaging apps.
💙