85
Giving Up on Element & Matrix.org
(xn--gckvb8fzb.com)
This is a most excellent place for technology news and articles.
We really need to stop abandoning existing foss projects and thinking a whole new thing needs to be invented. Free and open-source software is not a product, it doesn't abide by the same rules and relationships that proprietary tech does.
It's more organic. It's also a commons that we can continue to draw on, and reshape. If I recall correctly, there were something like three different vector graphic editors from the same codebase before Inkscape managed to be the one that gained traction.
Matrix isn't perfect, but abandoning it just to reinvent it all over again just because some people really need a thing that works like Discord, even though Discord is absolute hot garbage; is just going to re-create all the same problems. Matrix today is better than it was two years ago. And Matrix in a year will be better from now.
I agree. We should all abandon Matrix and implement any missing features into IRC or maybe XMPP
What I don't like about Matrix is that it's most visible homeserver and client implementations feel like they are being developed as a product by New Vector Ltd., not a community project.
How so?
New Vector forked the matrix foundation owned projects for synapse, dendrite, and element, and pulled all their devs, changing the license and bringing them under closer control. The foundation repos are now archived, and only the new vector owned ones are being actively developed. They sell an enterprise license for their element server suite that, at least according to their copy, seems more performant, and also offers admin tools that the free version lacks.
If you want to run a public instance that allows registration, you pretty much need some kind of external admin tool for moderation.
It's of course still better than pretty much all proprietary options, but also quite some room for improvement.
I agree with you, my main issue with Matrix is that it is a pain to self-host at the moment.
Isn't everything a pain to selfhost?
Honestly, setting up things using Docker Compose is generally a question of copying and pasting and editing the file locations.
The moment you need SSL and/or a reverse proxy it becomes a bit more complex, but once you set up a reverse proxy once you can generally expand that to your other applications.
Something like a Synology nas makes it very easy and to some extend even the Truenas apps are kinda easy.