Hey guys!
A year or so ago I tried hosting a federated matrix and synapse server. While at the beginning it seemed nice, the moment I tried to join a large room it died completely for 10-20 minutes while blasting my DNS server with 10K+ requests. Sometimes at the end it wouldn’t join, while filling the logs with errors. It really didn’t seem like a good user-experience. Ironically, one of the groups I tried to join was the support group, but I failed, because it was too big.
I am wondering if it has improved since, or it’s pretty much the same.
At the same time, I’m also wondering if there’s a good, fast self-hosted alternative, that kinda just works.
I just say you seem extremely uninformed for somebody who want to run a federation outpost, i.e. from the FAQ: https://matrix.org/docs/older/faq/
Why is the state_groups_state table so large? What is it storing? Room state takes up a lot of space! To be specific, regular snapshots are taken of room states, so you can rapidly find out the state for historical events.
Why is it so important to record this, and to know the past room state including full member list?
It’s needed to enable access control and state resolution, for example the homeserver needs to be able to decide:
“who can see this message at that point in time?” “what was the state of the room was when this message was received, and so is it allowed to be received?” Synapse stores these snapshots approximately every 100 messages, with deltas in between.
Well, I can’t recall every minute detail I’ve delt with a year ago. I shared my past experience and asked if it would be more or less the same.