The good thing is that matrix can be bridged to Signal[1], to allow for a smoother transition period. This is also true with Whatsapp[2], but against their ter

The good thing is that matrix can be bridged to Signal[1], to allow for a smoother transition period. This is also true with Whatsapp[2], but against their terms of service, so you risk getting banned, and built on reverse-engineering, plus you need an android VM of some sort. I've been personally moving my family to Signal, since that provides the best UX and easier transition from Whatsapp. Once I'm comfortable enough with it, we'll likely transition to matrix. What Matrix is missing is in my view: - Client with simple UI, polished UX, and not just a smoking pot of features: FluffyChat[3] is mostly there. - Server of which I can guarantee the uptime. Dendrite should lower the resource usage for a ~5-100 accounts server, and decentralised identities[4] would allow falling back to another server (such as a friend's). We're mostly there, so I'm starting to prepare the switch, starting with my more technical friends, by setting a bridge up. Hopefully we can finally break that dependency on phone numbers (ideally, domain names as well with [4]) and move on to bey-based IDs. [1] https://github.com/tulir/mautrix-signal https://github.com/tulir/mautrix-signal [1] Older bridge, unmaintained: https://github.com/matrix-hacks/matrix-puppet-signal https://github.com/matrix-hacks/matrix-puppet-signal [2]https://matrix.org/docs/guides/whatsapp-bridging-mautrix-whatsapp https://matrix.org/docs/guides/whatsapp-bridging-mautrix-wha... [3] https://web.fluffychat.im/en/ https://web.fluffychat.im/en/ [4] https://github.com/matrix-org/matrix-doc/blob/neilalexander/identities/proposals/2787-portable-identities.md https://github.com/matrix-org/matrix-doc/blob/neilalexander/...