I read here that #Matrix / #Element has a dark history of funding and developing by the (original) Israeli company #Amdocs. I don't know if this is still the case, but alarming it is.

https://lukesmith.xyz/articles/matrix-vs-xmpp

So maybe I need to move away from Matrix. But to where? I really tried to endorse #XMPP, but two important issues stopped me.

1. Fluent multi-device support. I don't need to explain this I think.

2. Always end-to-end encryption for DM's and (at least by default) group chats.

Because we are now living in the year 2025, are both issues now fully resolved?

@joenepraat
Actually I don't understand 1., using multi device since ages with xmpp.

But maybe I understand it if you mean in the context of 2.?

And no, "xmpp" will never always use e2ee or even by default.
XMPP isn't a company but an extensible standard and client developers can make their clients freely how they like and for use cases that are not only secret private messages.
XMPP powers Apple and Google push servers and Nintendo switch status messages, so it isn't a thing to demand e2ee in the protocol.
Sayng that:

There are clients that default to e2ee.

I have the feeling many in the xmpp community don't have such a strong need for e2ee everywhere always, because many host their small servers themselfs ( it it easy and cheap) . And then you might have a different threat model, and don't like the inconvinience of PFS encryption so much.
Ultimately e2ee is for hiding your message from the server.

@joenepraat
There is not one person you can demand implementing it. It is unlikely it will happen that all clients will enforce it.

Most clients give a very visible warning if you get an unencrypted message when you have omemo enabled.
And generelly they default to e2ee.
I doubt that more then that will happen.
I never know of course. Someone could write a client that doesn't display unencrypted messages, I certainly wouldn't use it.
In any case. It is every project individually that needs to be convinced.