| >Telemetry is not a vote From the developer point of view, this is incorrect, the developers are using it to decide which features to prioritize. If you are aware that it's happening and you leave it on, then I don't see what the problem is. Resource and bandwidth usage should be very minimal, if it's not then I would urge you to actually measure it and report bugs. It should be possible to compress it so that it doesn't eat up your bandwidth. Remember that it also takes bandwidth and CPU to post on Hacker News, so you will have to compare it to that to have any kind of meaningful data. My point is, it if lacks the data from those users, it would make sense to start sending them that data. It doesn't make sense to me to complain about them having incorrect data on you when you intentionally don't send them the right data and then threaten to jump ship because of what seems to be your own actions. I personally also disable telemetry but I know full well that I'm opting out of an important system for them so I don't expect to get attention in return for doing that. If you wanted to help, I think they would very much welcome attempts to fix the telemetry and make it more bandwidth-respecting and privacy-respecting, rather than finding ways to just throw it out. >You can of course make a zero telemetry browser, relying 100% on your own research and what the users volunteer to tell you directly. And those most passionate about it with tell you the most, a wonderful positive feedback loop. In my experience, this is an unreliable way to make products, the type of user who is passionate and volunteers this information is not the average user. You will end up with a very niche product that way, and the cost would be very high since you would be expecting the same quality of features but for a smaller number of users. If you're interested to do this I would suggest you to fork Firefox and attempt to get funding, and try that out just to see how much work it actually is compared to how little those users are actually willing to pay. Take a look at Waterfox if you want to see an example of how this would be done. |
Most people are not aware of telemetry. Most of those that are, disable it. So you end up getting what you call 'votes' from the people who are not aware they are 'voting'. That is not voting (for which a person need to be consciously doing it) but rather extraction of information.
Imagine in an election, the votes of those who didn't explicitly vote get automatically extracted and cast based on a biased algorithm produced by the government. If you do not like the idea of that, you should not like the idea of opt-out telemetry. What you want is opt-in telemetry (aka. voting).
> Resource and bandwidth usage should be very minimal
I fully agree, that is the other reason zero telemetry is a way to go and should be default. You can not beat that.
> In my experience, this is an unreliable way to make products
Not sure what your experience is but I already built one company like that and I am doing another one right now (incidentally a web browser) based on this same principle which is called user-centric product development. Btw. Mozilla practiced that too ~15 years ago (the "golden age" of Firefox, reference here https://news.ycombinator.com/item?id=28493855).