> I have to strongly agree with your last point - I also never understood the massive hard-on that the technical user-base has against useful telemetry.
I think it would be far less hostility if we as users got access to the information ourselves. E.g. I would think it would be very useful to see stats on which features I'm using in firefox, how often, which features I'm not using, how many tabs I have (compared to the average user) etc., and I would be much more happy to share that data with firefox if I can see it first.
> I think it would be far less hostility if we as users got access to the information ourselves.
Go to about:telemetry
There are several pages detailing all of that information, and you can also get all of that data as the JSON payload if you want to munge and display it yourself.
I didn't know this existed - thank you for sharing. I've shared telemetry on Firefox, but wasn't sure exactly what was being sent so this helps quite a bit more.
I don't think it lists 100% of them. For example, I think there might be one that forces a crash for debugging purposes? There are definitely some that are used for displaying errors and things (eg about:httpsonlyerror).
Windows is doing well in this regard in that 11 (and some earlier versions of 10) includes a 'View diagnostic data' button in settings that starts duplicating shipped-off telemetry to the local disk for inspection.
I think it would be far less hostility if we as users got access to the information ourselves. E.g. I would think it would be very useful to see stats on which features I'm using in firefox, how often, which features I'm not using, how many tabs I have (compared to the average user) etc., and I would be much more happy to share that data with firefox if I can see it first.