chat

> Why would you invent something new when you could use a protocol that already exists and already has a vast ecosystem of libraries and users? Unfortunately that's exactly what Matrix did, and people keep repeating the same mistake. Just this week, i was seeing a new federated IM protocol whose main selling point is "not XMPP/Matrix": https://github.com/tinode/chat If only these Matrix/Tinode people spent their energy on making a decent XMPP client, Discord would not even be born. Alas, my interpretation is it's a hard-sell to investors to make a client for an existing network and these devs want to put bread on their tables.

It doesn't have to be p2p. It just needs to be sufficiently decentralized, like email. If a company provides software but not a service then it's not liable under the new ruling. You can also run it outside of US jurisdiction. For example, use something like https://github.com/tinode/chat to set your own chat service. Sure, they may try to go after a myriad of individual operators but it's a completely different story that forcing half a dozen US companies to drop e2e encryption.

Well, then there is even more open sourced alternative than Mattermost: https://github.com/tinode/chat

You might want to consider tinode/chat (https://github.com/tinode/chat)