All I was saying was that the unique download ID is only used once, not every time you start Firefox. I wasn’t making any other claims as to what other analytics they use.
Having said that, Telemetry is important to making a good product. The developer needs to know about crashes and what causes them (to fix bugs), which features people are using the most and least (to know what to work on and what to potentially deprecate), etc. As long as it’s anonymous, I don’t see a problem in that?
Sure, but a lot of systems don’t actually store it. Even if they do, erasing the last octet (for IPv4) or the last 32 bits (for IPv6) is sufficient to de-identify it.
You can’t guarantee it is isn’t stored somewhere or checked by someone between you and Mozilla and used against you. Even your ISP can use Mozilla’s calling home against you.
OK, but what do you expect companies to do about this? There’s literally no way to browse the web without revealing your IP address. Are you saying that every single company online is collecting PII?
Even just checking for updates (which happens in the background with all modern software) would connect to Mozilla’s servers.
I except things to be kept on a reasonable level and that doesn’t include the amount of connections Firefox does, nor contacting a 3rd party analytics company.
What I also expect is to have simple toggles instead of having to spend half an hour going over advanced config, disable everything that can be disabled and still having it making connections to 3rd parties. Is it that hard to be transparent and make things right?
Telemetry is important to making a good product. The developer needs to know about crashes and what causes them
Telemetry is the new age bullshit excuse and alternative to proper in-house software testing and money cuts. Why hire testers and have public testing programs if you can just deploy to the end users, let it break and then collect logs. You’ll get tons of PII as a bonus :)
No amount of in-house testing is going to catch everything that can be experienced on a nearly-infinite amount of hardware/software configurations that are tested once a large userbase gets a hold of a product.
All I was saying was that the unique download ID is only used once, not every time you start Firefox. I wasn’t making any other claims as to what other analytics they use.
Having said that, Telemetry is important to making a good product. The developer needs to know about crashes and what causes them (to fix bugs), which features people are using the most and least (to know what to work on and what to potentially deprecate), etc. As long as it’s anonymous, I don’t see a problem in that?
deleted by creator
Sure, but a lot of systems don’t actually store it. Even if they do, erasing the last octet (for IPv4) or the last 32 bits (for IPv6) is sufficient to de-identify it.
You can’t guarantee it is isn’t stored somewhere or checked by someone between you and Mozilla and used against you. Even your ISP can use Mozilla’s calling home against you.
OK, but what do you expect companies to do about this? There’s literally no way to browse the web without revealing your IP address. Are you saying that every single company online is collecting PII?
Even just checking for updates (which happens in the background with all modern software) would connect to Mozilla’s servers.
I except things to be kept on a reasonable level and that doesn’t include the amount of connections Firefox does, nor contacting a 3rd party analytics company.
What I also expect is to have simple toggles instead of having to spend half an hour going over advanced config, disable everything that can be disabled and still having it making connections to 3rd parties. Is it that hard to be transparent and make things right?
deleted by creator
Telemetry is the new age bullshit excuse and alternative to proper in-house software testing and money cuts. Why hire testers and have public testing programs if you can just deploy to the end users, let it break and then collect logs. You’ll get tons of PII as a bonus :)
No amount of in-house testing is going to catch everything that can be experienced on a nearly-infinite amount of hardware/software configurations that are tested once a large userbase gets a hold of a product.
tell me you’re not a decent software developer without telling me you’re not a decent software developer