@GrahamcOfBorg test matrix-synapse

I don't really like the idea of having servers phoning home and relying on those central 3pid servers by default.
We should perhaps list those values as examples instead of default ones, if we don't mind not matching the upstream default configuration.

Thank you! Merged, as it is an improvement over current status.

@pacien I kind of agree with you that I don't want my server phoning home either, but I think currently nixpkgs mostly errs on the side of sticking close to upstream default configuration, as embodied by nginx's recommended*Settings for instance.

Now, if you open an RFC to change this state of affairs for a defined number of cases (said RFC should, I think, say when it's acceptable to diverge from upstream defaults -- insecurity, telemetry, lack of privacy, default config improvements, etc…), I'll likely support you in this endeavor :)

@Ekleog thanks! 🍻

@pacien without identity servers, you can't register e-mail addresses, even if they're just for password reset links, so in case we decide to deviate from the default, we should pair that with defaulting to host our own identity server. Probably mxisd, not sure how much sense it makes to self-host sydent if it doesn't federate.

While I agree with you in general, I think there is stuff with more impact, especially integration managers, which are used much more often, a gateway to self-host bots and bridges, and are a centralized service as well. As soon as we have a module for dimensions, we can start to think about deviating from the default integrations service to a self-hosted one.