Database model for privacy modes

[staltz]

No description provided.

[cryptix]

A bit meta but I'm having trouble making up my mind about this: I'm contested between have a separate config file that needs to be set before starting the server and putting it on a single row config table that can be changed from the web UI.

I see being able to change from the frontend both as problem and feature here. Like, the HTTPS hostname is something we probably need before we could even show a first-use setup wizard.

Also only being able to change it through the UI might also turn into a problem.

[cryptix]

We at least need to be careful not to mix deployment configuration with room configuration.

If we advise for restoring from backup by just saving the roomdb, changing the hostname of your room might turn into a problem.

[staltz]

Hmm, I understand some of the problems you described, like the backup issue, but what's the connection between a privacy mode and the HTTPS hostname? Ideally it would be best that the privacy mode can be changed after deployment.

Or is the problem the choice of the default privacy mode?