Live data from Hacker News

Open-source tests of web browser privacy

privacytests.org

11–20 of 34 posts

Re: Open-source tests of web browser privacy

#11

This reminds me so much of the ACID tests[1] from the late 90's, early 2000s. I wonder if it will have a similar effect, i.e. to drive people away from Chrome in the same way it eventually drove people away from IE. [1] https://en.wikipedia.org/wiki/Acid1

I don't think the Acid tests had anything to do with Chrome's rise. That thing was pushed and promoted in ways that reminded everyone with half a brain (and knowledge) of malware. As difficult to remove, too.

Re: Open-source tests of web browser privacy

#12
post #7

This is under the assumption that each browser is being used with the default settings, firefox can do much better with customizable settings.

> This is under the assumption that each browser is being used with the default settings

That is the only valid assumption. The absolute vast majority of users will use any and all software under default settings.

Re: Open-source tests of web browser privacy

#14
post #4

Firefox with these settings from Librewolf looks very much equivalent: https://gitlab.com/librewolf-community/settings/-/blob/maste...

I would disagree. Most of the fingerprinting protection is enabled by the user.js, of which LibreWolf inherits the efforts made by arkenfox[1][2]. Many of the most significant preferences themselves made it into Firefox by the Tor uplift project[3].

[1] https://github.com/arkenfox/user.js

[2] https://librewolf.net/license-disclaimers

[3] https://wiki.mozilla.org/Security/Tor_Uplift

Re: Open-source tests of web browser privacy

#15
These really need context or better explanations.

For instance I clicked on the Blob line and the code looks to fetch and URL with a Blob encoded and fetches it again? There is so little context to say what is really wrong... or if there is anything really wrong.

I looked up Blobs myself and read through the specs on MDN and I just dont see a problem.

Re: Open-source tests of web browser privacy

#16
post #8

To me, it seemed that if a browser had passed every test, the user might not be able to use many web sites. Perhaps the current status is a conscious decision by developers to keep users from hating their browser. Security vs usability.

If enough users used a privacy friendly browser web devs would be forced to make their sites compatible or they would lose traffic.

Re: Open-source tests of web browser privacy

#17

These really need context or better explanations. For instance I clicked on the Blob line and the code looks to fetch and URL with a Blob encoded and fetches it again? There is so little context to say what is really wrong... or if there is anything really wrong. I looked up Blobs myself and read through the specs on MDN and I just dont see a problem.

Thank you for the feedback -- I agree more context and explanation is needed for each of these tests.

In the Blob case: the test code is storing a unique string in a Blob URL under one website (first party), and then attempting to read back that string under a second, different website. (See "result, different first party".) If the string is accessible under a different first party, then it is possible to use a Blob URL to track a user between two different websites.

Re: Open-source tests of web browser privacy

#18

More useful would be showing what can be enabled (if it's not on by default), how useful it actually is (not every checkmark is created equally heh), and what can be added (especially on the tracking side) by simply installing μblock origin (which everyone would/should do in every browser anyway).

Agreed -- in the future I'm hoping to have a page showing results with browsers with various privacy-helpful extensions installed.

Re: Open-source tests of web browser privacy

#20
post #4

Firefox with these settings from Librewolf looks very much equivalent: https://gitlab.com/librewolf-community/settings/-/blob/maste...

Where would I put this file on my Firefox install ?

The file's first line points to a README with details.

(On my machine it's under "C:\Program Files\Mozilla Firefox\distribution".)

Post reply on HN