My main concernsvwith these types of posts are management and defaults.
If management isn't automous, then you'll get fragmentation which becomes a fingerprinting mechanism.
If the defaults are too harsh, then you deter adoption and encourage fragmentation of those that do adopt (as they'll muck about in the config and unbreak different things).
With low adoption, using this could potentially make you more identifiable (mirroring the concern of Do Not Track as of late) , [citation needed, on mobile].
I'll definitely spin up an instance of later today, but it looks like the defaults might cause a fair bit of breakage
If management isn't automous, then you'll get fragmentation which becomes a fingerprinting mechanism.
If the defaults are too harsh, then you deter adoption and encourage fragmentation of those that do adopt (as they'll muck about in the config and unbreak different things).
With low adoption, using this could potentially make you more identifiable (mirroring the concern of Do Not Track as of late) , [citation needed, on mobile].
I'll definitely spin up an instance of later today, but it looks like the defaults might cause a fair bit of breakage