3 ms·
Forget all the stories about GAFAM implementations, network effects or complexity. It's 2022, XMPP is 23 years old, and I still can't use it as a primary solut
by tupolef 4y ago
Forget all the stories about GAFAM implementations, network effects or complexity.
It's 2022, XMPP is 23 years old, and I still can't use it as a primary solution for my community. There is no client/server environment available that meets the most demanded purposes and runs on all common devices.
In 5 years I have tried to set up an infrastructure 3 times to have a look, I always come back to Matrix (just because I have more hope that it will turn out better in the future).
XMPP is ready to do too many things, that's a good point, but the most common practices that everyone finds on centralized solutions are not implemented on all platforms, clients, and servers.
The server documentation doesn't give any advice on which clients to use, and the clients doesn't advise which server to use. Everyone has their head in the sand.
It's been at least 15 years since it's easy to set up an email infrastructure by yourself, that everyone can use on all their devices.