Store configuration to disk or elsewhere reliable / Matrix state resets keep altering configuration and banning benevolent users for "spam"

[Mikaela]

I have three times disabled basicfloodingprotection as it keeps triggering on redactions or other expected Matrix behaviour (#187), but the change gets reverted as Matrix cannot be trusted for things such as software configuration.

Thus I think the configuration should be stored on disk or something like software usually does.

Ref: matrix-org/synapse#8629

[Gnuxie]

This doesn't seem to be caused by state resets, since the list of enabled protections is loaded from account data. However this is still a Major usability issue.

[Mikaela]

And this happens again. Were there any ideas on what causes it, if not state resets?

---

#196 - is it possible that Draupnir isn't either writing or reading to/from account data? I think Draupnir4all was rebooted a couple of times yesterday or two days ago or so and I wonder if that is relevant to it happening again.

However it's a couple of hours since so-called flooder went to sleep so I don't know if that is relevant as the "state reset" seems to have happened long after the spam. I don't know if @MTRNord has some automatic that would trigger around this time to cause this.

My other idea was automatic message removal, but reacting configuration changes after message redaction would be stupid in my opinion and the timing doesn't match since I haven't booted computer (and thus Nheko) yet today, so I haven't removed any messages automatically either.

• Me at Draupnir room on Matrix in case any of this proves itself relevant.

[Gnuxie]

To be confirmed, but we suspect that under certain conditions where synapse starts and then later loses a connection to the database, it will return empty account data (or something else TBC) with a http OK response to Draupnir when requested. Meaning that we have no way to detect this failure mode, and Draupnir is then using the defaults for enabled protections.

[Gnuxie]

OK turns out there was a Synapse+Redis problem specific to draupnir.midnightthoughts.space CC @MTRNord will close on confirmation.

[MTRNord]

I am monitoring this but it seems to have been resolved after the redis was fixed. Closing :)