Neowin has a brief warning that Mozilla plans to collect anonymized user data. The given reason is to better understand how people use Firefox. Perhaps the most alarming aspect of this plan is that it is opt-out rather than opt-in. This is very far from the early days of Firefox when it had previously touted privacy as one of its main advantages.
As stated in the Google Groups announcement thread, they intend to use RAPPOR:
RAPPOR is a novel privacy technology that allows inferring statistics about populations while preserving the privacy of individual users.
This repository contains simulation and analysis code in Python and R.
[...] Publications
- RAPPOR: Randomized Aggregatable Privacy-Preserving Ordinal Response
- Building a RAPPOR with the Unknown: Privacy-Preserving Learning of Associations and Data Dictionaries
Links
[Update @ 20170824_152224 UTC: fixed bad link to Google Groups thread.]
(Score: 0) by Anonymous Coward on Thursday August 24 2017, @09:05PM (2 children)
From what I'd read a while back google started including binary objects in the chromium source repo that are normally built in.
I am not sure how it acts on non-x86/arm platforms, or if it even builds on them ATM, but those stories concerned me enough to stop using it as my tertiary browser (I didn't like it much to begin with. FF still does what I need most of the time, Seamonkey if not, and then a pool of less customizable browsers in between.)
(Score: 1) by toddestan on Friday August 25 2017, @02:45AM
One of the problems with Chromium is that there are no official builds, so what is and is not in it all depends on who did the build. I'd trust the builds in the official repositories for Debian or Ubuntu to not include anything they didn't have the source for, but some of the other builds? Who knows. Or you could just build it yourself, though my understanding is that the build environment is rather complicated and you need a pretty decent computer if you want it to get done in any kind of reasonable time.
(Score: 1) by xhedit on Friday August 25 2017, @02:48AM
Ungoogled chromium fixes that issue.