Earlier quoted context omitted.
But how many of them come from the rendering engine?
For example, NoScript disables webfonts because parsing font files (which is among the jobs of the rendering engine) is done in decades-old, convoluted C code.
Ask HN: Firefox vs. Chrome security
71–73 of 73 posts
Re: Ask HN: Firefox vs. Chrome security
#72Earlier quoted context omitted.
Firefox does NOT do any this, as far as I know. What is the source of this FUD? A public discussion was started to get to know how people felt about privacy conserving telemetry collection that would be opt out by default. There was massive negative feedback (duh). The feature did not ship in 57. https://medium.com/georg-fritzsche/data-preference-changes-i... "instead we always collect LESS data on Firefox release."
> The feature did not ship in 57. But CliqZ did ship for some German users, randomly chosen. Which tracks your entire browsing history, and sends it to a company that’s most known for its tracking products. After this, Firefox deserves to be treated as just as much spyware as Chrome.
Re: Ask HN: Firefox vs. Chrome security
#73Earlier quoted context omitted.
> The feature did not ship in 57. But CliqZ did ship for some German users, randomly chosen. Which tracks your entire browsing history, and sends it to a company that’s most known for its tracking products. After this, Firefox deserves to be treated as just as much spyware as Chrome.
This is simply not true. They do not send the user browser history. Most data is processed on the client side https://gist.github.com/solso/423a1104a9e3c1e3b8d7c9ca14e885...
That's so much of an improvement for a browser which people only use because they want absolute privacy.