this post was submitted on 21 Jun 2023
288 points (100.0% liked)
Technology
37801 readers
245 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
How is matrix a performance nightmare? been running a matrix server for years with almost no issues. I guess the only exception was the few times I ran out of hdd space, but that's it.
What's an official standard? Matrix is a protocol just like xmpp and the specs are public, just like with xmpp.
It's literally as easy as running a docker container and editing a yaml file, at least for synapse.
It is very well known that Synapse is a ressource hog. Heck, you can't even enable presence because it would kill your server ressources. Why do you think almost all instances have it disabled? Cmpared to an XMPP server ressource usage, Snypase is a nightmare to host. I also hosted a public server for a long time.
XMPP standards: https://wikiless.ftw.lol/wiki/XMPP https://xmpp.org/extensions/ https://xmpp.org/about/technology-overview/
just like xmmp is, difference is, matrix snypse uses like 20x the amount of ressources. Just try to host a public server for more than 100 people and you will know.
There is a reason why people make stuff like Conduit or the matrix team works on Dendrite as a new server.