Live data from Hacker News

Firefox 59 to strip path information from referrer values for 3rd parties

blog.mozilla.org

91–100 of 236 posts

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#91

Earlier quoted context omitted.

There are some news websites that blocks private browsing[1]. Private browsing is a method of bypass the paywall, so they they make a private-browsing-wall. 1: https://imgur.com/a/gXEtl

What is the current mechanism for them to know that you are in private browsing mode?

probably checking whether the DNT header is set to 1, or whether a known tracking domain is blocked (firefox has tracking protection by default in private browsing).

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#92
post #47

If Mozilla genuinely prioritized its users' interest it would block ads and tracking networks, which are the major way people's private information is leaked and also a primary vector for hacking. And yet for some mysterious reason Firefox hasn't broken ranks with Google by incorporating ad blocking. Even though its an obvious major feature and Firefox is losing marketshare every year. We know why Google won't priori…

If Firefox disabled ads by default, a large number of sites would likely block Firefox or set up angry messages telling the user to switch browsers. Yes, you could bypass that, but most people wouldn't bother. Add in the logistical issues, and the fact that some of the things blocked are beneficial, then I see no reason to expect the conspiracy you suspect.

If a major service blocks Firefox users it could lead to a massive boycott. Users could rally around Mozilla if it stopped selling out their interests.

More people use ad-blockers than Firefox has users. The best way to attract more users is to make the best possible browser. That means incorporating ad-blocking as users have loudly demanded for a decade.

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#95
This one of the reasons I tend to flip completely whenever I see healthcare providers and their suppliers run google analytics tags inside their logged in areas (yes, this really happens). Besides the questionable value of having such tracking inside the logged in areas (it's healthcare, they are not going to worry about their conversion rates) such information should simply never leave the premises. Better still if they didn't do this in private mode but always. Private mode is still associated with doing something sneaky, rather than that it should be the default.

Happy to see FF do the right thing here and I'm really curious if Google will follow suit. Microsoft and Apple have an opportunity here to show they care about end user privacy than Google.

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#96
post #90

As someone that digs in this data for a living, personally strongly believe this should be on by default for all browsing. The example they give is an insanely bad design for healthcare.gov and I would absolutely not want to find that type of data in my analytics telemetry. It is very useful to know where your traffic is coming from, but that’s usually viewed at a higher level than the querystring params being shown.…

Yes it's great from a marketer's point of view. From a consumer's point of view, I don't want you to know where I came from. I don't really care if it's useful to you. It's the difference between pleasing marketers vs pleasing users. Firefox chose wisely

Honestly, I don't think path information is all that useful for marketers.

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#97
post #22

Earlier quoted context omitted.

Well, probably I would be fine if they would remove the referrer completely (if it has a different domain than the current site, otherwise they might notice the tampering). After all the referrer is useful for the site owner, not for the browser user.

Some websites rely (at least in part for verification) on referrer for the authentication process, I can imagine that causing some headaches for people.

Frankly: that's their problem. If your business model revolves around client side security then you have other problems.

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#98
post #30

For those confused as to why half the comments have "misspelled" referrer, here's an interesting bit of history: The misspelling of referrer originated in the original proposal by computer scientist Phillip Hallam-Baker to incorporate the field into the HTTP specification. The misspelling was set in stone by the time of its incorporation into the Request for Comments standards document RFC 1945; document co-author Ro…

Always wondered. Thanks!

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#99
post #65

As someone that digs in this data for a living, personally strongly believe this should be on by default for all browsing. The example they give is an insanely bad design for healthcare.gov and I would absolutely not want to find that type of data in my analytics telemetry. It is very useful to know where your traffic is coming from, but that’s usually viewed at a higher level than the querystring params being shown.…

As a user I don't want you to know that information. I wish there was a way to click on links with the referer field removed entirely from the request(maybe via context menu)

If you're using Firefox, open 'about:config' and set 'network.http.sendRefererHeader' to 0.

http://kb.mozillazine.org/Network.http.sendRefererHeader

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#100

As someone that digs in this data for a living, personally strongly believe this should be on by default for all browsing. The example they give is an insanely bad design for healthcare.gov and I would absolutely not want to find that type of data in my analytics telemetry. It is very useful to know where your traffic is coming from, but that’s usually viewed at a higher level than the querystring params being shown.…

> As someone that digs in this data for a living, personally strongly believe this should be on by default for all browsing.

Yeah, but it may surprise you to know that your opinion isn't shared by the people who own the computers in question, or the private data you're digging in.

Your personal strong belief is, in this case, utterly irrelevant.

Post reply on HN