Innovation and privacy go hand in hand here at Mozilla. To continue developing features and products that resonate with our users, we’re adopting a new a
Buddy, I just want to type a search term and get results.
Telemetry can help them do better at providing that. Devs aren’t magical beings, they don’t know what’s working and what’s not unless someone tells them.
That’s like saying the window pane between me and the teller has to understand the conversation and dynamically modify the light between him and I. The window pane’s only job is to let light through. Keep it at that.
No, this analogy would make more sense if it was a matter of recording a large number of interactions between customers and tellers to ensure that the window isn’t interfering with their interactions. Is the window the right size? Can the customer and teller hear each other through it? Is that little hole at the bottom large enough to let through the things they need to physically exchange? If you deploy the windows and then never gather any telemetry you have no idea whether it’s working well or if it could be improved.
You’re describing telemetry to improve the overall performance of the window. That’s very different from what Mozilla: listening in to what is sent between the teller and I. They even gave an example of a trip to Spain and recording it as travel. That’s going way beyond the performance of a window. The teller is probably already doing that. The window operator has no business listening in on that discussion nor recording even a summary of details of the discussion.
In this case the content of the search is all that really matters for the quality of the search. What else would you suggest be recorded, the words-per-minute typing speed, the font size? If they want to improve the search system they need to know how it’s working, and that involves recording the searches.
It’s anonymized and you can opt out. Go ahead and opt out. There’ll still be enough telemetry for them to do their work.
Telemetry can help them do better at providing that. Devs aren’t magical beings, they don’t know what’s working and what’s not unless someone tells them.
That’s like saying the window pane between me and the teller has to understand the conversation and dynamically modify the light between him and I. The window pane’s only job is to let light through. Keep it at that.
Anti Commercial-AI license
No, this analogy would make more sense if it was a matter of recording a large number of interactions between customers and tellers to ensure that the window isn’t interfering with their interactions. Is the window the right size? Can the customer and teller hear each other through it? Is that little hole at the bottom large enough to let through the things they need to physically exchange? If you deploy the windows and then never gather any telemetry you have no idea whether it’s working well or if it could be improved.
You’re describing telemetry to improve the overall performance of the window. That’s very different from what Mozilla: listening in to what is sent between the teller and I. They even gave an example of a trip to Spain and recording it as travel. That’s going way beyond the performance of a window. The teller is probably already doing that. The window operator has no business listening in on that discussion nor recording even a summary of details of the discussion.
Anti Commercial-AI license
The analogy isn’t perfect, no analogy ever is.
In this case the content of the search is all that really matters for the quality of the search. What else would you suggest be recorded, the words-per-minute typing speed, the font size? If they want to improve the search system they need to know how it’s working, and that involves recording the searches.
It’s anonymized and you can opt out. Go ahead and opt out. There’ll still be enough telemetry for them to do their work.
Telemetry doesn’t need topic categorization. This is building a dataset for AI.