On Monday a user writes in a Matrix space, causing every member to receive a notification; old clients render spaces as regular rooms while new clients show confusing UI and permissions are often left unchecked. The author uses Element devtools to set admin rights and disable chat. On Tuesday a user reports an unexpected ban; a Draupnir query of the handle’s domain reveals a policy rule banning the domain because the homeserver allowed open registrations. Searching messages fails, so the author exports the chat as HTML and greps for the domain, finding seven hits and solving the issue in roughly 40 minutes.

On Wednesday a newcomer cannot see a suggested room until an admin joins it, exposing a sync visibility bug that affects multiple homeservers; removing and recreating the room or tombstoning does not help, while an admin’s presence makes the room reappear.

On Friday the same accidental space write repeats, permissions reset, creating a split‑brain where some homeservers receive updates and others do not, requiring another admin on a different homeserver to re‑apply the settings. On Saturday federation degrades due to DNS errors routing servers to wrong ports; after fixing the port issue, a desynced bot account is kicked and re‑invited to restore functionality. On Sunday a Mastodon boost highlights a happy user unfamiliar with spaces, contrasting with the author’s experience running a real community, while noting Matrix’s strengths.