2 ms·
> Of course this may not be practical for small utilities It's utterly undoable for utilities (small or not) even if you ignore the likely blowback à la W10 te
by masklinn 10y ago
> Of course this may not be practical for small utilities
It's utterly undoable for utilities (small or not) even if you ignore the likely blowback à la W10 telemetry.
- paol 10y agoLots of large applications have extensive telemetry without any significant blowback (as far as I'm aware). MS Office, Firefox, Chrome, ... It's not undoable for utilities either, just the effort/benefit ratio probably doesn't justify it.
- masklinn 10y ago> Lots of large applications have extensive telemetry without any significant blowback (as far as I'm aware). MS Office, Firefox, Chrome, ... Not sure about the others, but AFAIK Firefox telemetry is only enabled (or at least sent to Mozilla) on pre-release channels. > It's not undoable for utilities either It's undoable in the sense that you'll be bundling more telemetry code than there is actual utility code, and downstream is going to remove it as soon as it lands.
- vertex-four 10y agoFirefox Health Report is on and shared with Mozilla by default on release builds - it prompts you about it on first run. There's additional telemetry in pre-release builds.