Bouncers are an option, but the need to use that sort of extra services will make non-technical users turn away.
132 karma · joined December 4, 2023
Bouncers are an option, but the need to use that sort of extra services will make non-technical users turn away.
I think there is a some sort of catch-22 going on. Matrix Foundation can't fund the replacement of Synapse with a better-designed server, because hosting matrix.org consumes all the money. And it consumes so much money because it runs Synapse, which uses computing resources in a very inefficient manner.
And the Foundation might have a some sort of conflict-of-interest, since it is closely interwoven with the New Vector company, which business case is being able to make Synapse work despite its flaws.
I wonder why such thing wasn't done 15...20 years ago. Now it seems to be too little too late, with Matrix more or less having been taken the place of IRC.
Hell, I was told I was a some sort of bad person for being unhappy with room joins taking hours or even days.
After exhausting all other options, they have improved their software a lot (it's still not perfect, but definitely usable), but their poor attitude has soured their reputation, and made it really difficult to be enthusiastic about Matrix.
I haven't encountered any of that kind of abuse in Matrix after it has been implemented. It partially nullifies the point of the room decentralization, though.
Some of the biggest public rooms like "Matrix HQ" are almost unusably slow, though, since they have tens of thousands zombie users.
Matrix performance feels now more or less adequate for all realistic use cases, as long as long-term idle users are pruned out every now and then from public rooms.
https://discuss.privacyguides.net/t/so-can-pfs-be-enabled-in...
According to this, it by default implements it for batches of 100 messages or something. And for slow-paced messaging, it is quite a lot. No idea why, maybe doing it somehow else would make the already bad performance even worse.
That is still a failure (to spam check), even if it is not a failure to deliver the messages altogether.
It may also end up being a vulnerability. For example, the attackers might do a some sort of flood attack on the policy server, and then get the abuse through.
The Matrix HQ room may work every now and then, but it certainly doesn't work well at all.
> Policy Servers are not a kludge, and they do not work by “routing all messages through a central server, and after then, passed onto the distributed database”. They are the opposite, as the linked blog post tries to spell out.
> DAG distribution works as normal; messages flow full mesh between servers as always without centralisation. The optional policy server simply provides a /check endpoint which the servers in a given room can use to filter messages for abuse before they pass them to clients. That’s it.
Distinction without difference. In any case, the single-point-of-failure server is needed to process all the messages and give the go/no go instruction to the larger network.
Policy Servers are not all that optional, since without them, the public rooms will be full of CSAM/gore material, and that is completely unacceptable.
They store all the messages in a some sort of distributed append-only graph database, which theoretically makes it a bit more fault-tolerant and censorship-resistant, but which does not work very well in real-world use cases. In addition to performance issues, it makes it very hard to filter out all sorts of abuse on public channels before it reaches the clients. In a rather bizarre turn of events, they implemented a kludge solution (1) in which all the messages are routed through a central server, and after then, passed on to the distributed database.
1) https://matrix.org/blog/2025/04/introducing-policy-servers/
However, the solution seems to introduce a single point of failure to the rooms, at least partially defeating the purpose of the (very resource-intensive) model of distributed rooms, giving us the worst of the both worlds.
Companies make billions? Good. It's time to tax them and use the money for the benefit of everyone.
GrapheneOS dev account seems to disagree about the scalability issue being limited to very large instances. Due to the way how Matrix works, even activity on other servers can generate events at your server, particularly when you have joined busy channels.
Not a software engineer, but a server software that collapses at only 100 events per second on modern hardware sounds pretty bad to me.
Not only they are admitting that it is an exercise in futility to set up a medium-to-large Matrix deployment using an open source software stack.
100 000 people is not "nation-scale". It is small town scale. I am wondering if they intend Matrix ever to become truly mainstream instead of being confined to internal use of government organizations.
And it only gets worse from there: https://element.io/blog/synapse-pro-slashes-costs-for-runnin...
Synapse Pro was released only about a month ago. All these years they have been selling their solution to large organizations, despite it being hopelessly inadequate what it comes to scalability.
Will this finally be enough, or will it end up so that even more features are going to be available only on the proprietary version?
Outright denying people's bad experience with Matrix has also been a sad part in Matrix marketing for so long. Unfortunately, I don't have experience with Element X, since my provider doesn't support it yet, so I can't confirm or deny that testimonial, but my exceptations are not high.
> It might be worth considering that whining about Matrix is misdirected anger - it may be better off pointed at the proprietary centralised surveillance capitalism alternatives rather than us…
It's not either or. People are frustrated on the other hand because of the annoying proprietary platforms, but also because there are currently no alternatives to them that one could whole-heartedly recommend as a replacement.
I already use use Matrix for many public chat rooms, but it still needs some work before I can recommend it to other people.