<IdleBot_aeb66fa0>
pie___: maybe we should train by disabling telemetry (Firefox build recognises Nixpkgs build as development channel and force-enables telemetry)
<IdleBot_aeb66fa0>
pie___: No idea if disabling TRR will oblige us to debrand again
pie___ has quit [Quit: Leaving]
<andi->
I have the same concerns.. unless it is a compile-time switch? Would that get around agreement with mozilla? I also hesitate to switch to dns over tols when cloudflare or whoever runs the resolvers..
<IdleBot_aeb66fa0>
andi-: I think switching off telemetry would be in line with saying we rebuild release versions, actually. Compile-time-removing TRR would probably be a violation even if it is a provided switch. Changing the default… hard question.
<andi->
IdleBot_aeb66fa0: I didn't mean removing just changing the default.. but it's all guessing anyway?!
<ivan>
if we lived in TRR world and reverted to ISP-DNS world people would write very concerned blog posts too
<ekleog>
stupid idea: wrap firefox in a helper that pre-fills $HOME/.mozilla/firefox/*/prefs.js
<ekleog>
now, the hard part is actually figuring out the right *, and doing this in a way that doesn't erase the user's choice if they have changed from the nixpkgs default
<ekleog>
(mostly the “don't erase users' conscious choice” part, though, as it could then be applied to all profiles)
<samueldr>
could it be safe to assume unset means default?
<ekleog>
I'd think so, but not sure
<samueldr>
the issue though is how do we detect a user choice vs. a distro choice?