Earlier quoted context omitted.
Why? No, seriously; why? I don't get this mentality at all. Let's ignore the exact implementation here for a moment, and assume that Firefox is somehow magically doing this data collection in such a way that it is guaranteed the data collected cannot be traced back to you as an individual. (E.g. "sufficiently anonymous".) What problem do you have with that, specifically? How does this harm you in any way?
It’s a question of consent. Imagine I came to your house, and photocopied all your documents. Don’t worry, I blanked out the name, so it’s completely anonymous, and everything is where it used to be. Would you be okay with that? I certainly wouldn’t. Making this opt-in or opt-out is a question of consent, and choosing opt-out shows that you don’t give a flying fuck about me, and only want your own benefit.
Studying how Firefox can collect additional data in a privacy-preserving way
421–430 of 450 posts
Re: Studying how Firefox can collect additional data in a privacy-preserving way
#422I can do a quick summary of what's being proposed and why. I work in the JS team at Mozilla and deal directly with the problems caused by insufficient data. Please note that I'm speaking for myself here, and not on behalf of Mozilla as a whole. Tracking down regressions, crashes, and perf issues without good telemetry about how often it's happening and in what context. Issues that might have otherwise taken a few day…
> Tracking down regressions, crashes, and perf issues without good telemetry about how often it's happening and in what context. If that's what you're aiming at. Collect the data but keep it local. Install some sort of responsiveness/"problem" monitoring. Ask the user to send data relevant to the problem if a problem occurs. IMHO there is no need to systematically collect user data for that. Or get the data from a ra…
That sounds way more reasonable to me.
Re: Studying how Firefox can collect additional data in a privacy-preserving way
#423Earlier quoted context omitted.
The problem with differential privacy is I have to trust the person aggregating the data to actually do it.
Do you? Excuse my ignorance, but I thought there was a way to locally mangle the data before submitting. Is that not what apple is doing?
I don't know, is it? How would I check, if I consider apple an untrusted actor?
Re: Studying how Firefox can collect additional data in a privacy-preserving way
#424Earlier quoted context omitted.
The point is not whether this method is "sufficiently anonymous", the point is: I don't want my browser to collect any kind of data.
Why? No, seriously; why? I don't get this mentality at all. Let's ignore the exact implementation here for a moment, and assume that Firefox is somehow magically doing this data collection in such a way that it is guaranteed the data collected cannot be traced back to you as an individual. (E.g. "sufficiently anonymous".) What problem do you have with that, specifically? How does this harm you in any way?
I'm ok with testing things and sending feedback, but when I switch to a production environment, I just want my tools to behave like my tools, not the testing farm for somebody else.
Why should I prove to you that it would harm me? I just do not want it, it should be enough.
Re: Studying how Firefox can collect additional data in a privacy-preserving way
#425I tried to be unbiased in the submission title and it's probably late enough that this will be buried, but here are some my thoughts: > They don't plan on collecting URLs, just (eTLD+1). This is true as of right now, but can change at any time in the future. From the post: > What we plan to do now is run an opt-out SHIELD study [6] to validate our implementation of RAPPOR. This study will collect the value for users’…
Re: Studying how Firefox can collect additional data in a privacy-preserving way
#426The single largest advantage of Firefox over other browsers is that despite all odds and occasional missteps they managed to respect users' desire for complete privacy. For Firefox we want to better understand how people use our product to improve their experience. Sure thing. But the fact that they are unhappy that some (many?) people are opting-out from the data collection is merely a sign that they don't want to u…
I'm not really sure what your concern is here. Let's assume for a moment that Firefox's implementation of differential privacy in this scenario is completely correct, and that as a result it's completely impossible (even in an information-theoretic sense) to learn anything about any individual user using this data; only about many users in aggregate. In this scenario, how exactly would Firefox's actions here compromi…
You must be kidding me.
Re: Studying how Firefox can collect additional data in a privacy-preserving way
#427I tried to be unbiased in the submission title and it's probably late enough that this will be buried, but here are some my thoughts: > They don't plan on collecting URLs, just (eTLD+1). This is true as of right now, but can change at any time in the future. From the post: > What we plan to do now is run an opt-out SHIELD study [6] to validate our implementation of RAPPOR. This study will collect the value for users’…
Comment threads are a useful way of organizing the discussion, why did you choose to not use it?
My reasoning is that people might search for my comment (I sometimes do when others post), but by the time I wrote the it the first comment page was full and it ended up on the second one.
Re: Studying how Firefox can collect additional data in a privacy-preserving way
#428Earlier quoted context omitted.
Why would FireFox be on a dead spiral for not tracking it's users? If they want browsing data, then can use their own.
(Disclaimer: I work for Mozilla) The problem with our own browsing data--by which I'm assuming you mean the browsing habits of our ~1000 employees--is that it's wildly non-representative of the broader population. For instance, people here routinely have browser sessions with 10, 100, or even 1000+ tabs. These numbers also indicate that the browser is an application you start, and then you just leave up for a while,…
I value the expertise at Mozilla. Could you point to a browser that might fit me?
Re: Studying how Firefox can collect additional data in a privacy-preserving way
#429Earlier quoted context omitted.
Most likely Brave, Edge, Opera or Vivaldi. I haven't really dug into if they do telemetry but some quick google searches tells me that at least Vivaldi does not. Brave is also a browser all about privacy so it would be weird if they do spy on their users. But you are correct, if Firefox falls as the last bastion in the web browser world to protect users privacy there is little choice left of really nice browsers. If…
Brave sounded interesting until I saw this at the bottom of the landing page: "Brave makes money by taking 5% of any donations and -- after it is fully implemented -- a small cut of advertising that is placed. Brave even shares some revenue with you -- at least as much as we receive." Then there's this: https://brave.com/about-ad-replacement/ If they are planning to inject ads into the browser and somehow pay their u…
But I much rather just continue to use Firefox.
Re: Studying how Firefox can collect additional data in a privacy-preserving way
#430The real issue here is with ethos and perspective. I use Firefox because the ethos of the company and its employees, and their general "take" on issues like this allows (or has allowed) me a general sense of trust in them.
Even the very existence of this discussion erodes that trust. This says to me "the people making this browser don't understand the importance of consent, and have a vastly different perspective on the value of privacy to mine".
If your developers need more data from Telemetry, get consent and collect more data. Establish trust in users in what you do with that data.