Live data from Hacker News

Firefox to Block All 3rd Party Trackers by Default

twitter.com

181–190 of 190 posts

Re: Firefox to Block All 3rd Party Trackers by Default

#181
post #30

Earlier quoted context omitted.

"breaking the web by default" It's not breaking the web, it's breaking part of the web's grasp on users. Is the web for people or is it there to use people? "Ad blocking will start being a problem" I live in the days where both all ads and all bullshit responses to my adblocker ("don't block my ads!!") are blocked; it's a breeze of fresh air. Sometimes a site tries to get around it and I block it permanently.

What do you use to block the requests to disable your ad blocker?

uBlock Origin comes with anti-adblock lists; they're just disabled by default. I also use element picker mode.

Element picker mode is right at the edge of my patience, so I usually give up if it doesn't work. If I still really want something from the site I view source.

Re: Firefox to Block All 3rd Party Trackers by Default

#182

Earlier quoted context omitted.

I partly agree with you: they should be an earned privilege that I agree to turn on for some websites, not something turned on by default. because there are some genuine use cases, such as single sign-on, that they're actually useful for.

Eh, single-sign-on is easily fixed for most applications; just forward the entire window to the SSO provider, so the cookies are first-party, then forward back once they're logged in.

I wish it was that simple.

If you can bounce through an SSO provider to set a first-party cookie, you can bounce through an ad tracker. Even with a heuristic that requires action on the interstitial, how do you distinguish between redirects to services like Google that support social login and ad tracking?

Separating SSO and ad tracking is nontrivial and may result in collateral damage.

Re: Firefox to Block All 3rd Party Trackers by Default

#183

How do you prevent Iframes from communicating their cookies to the parent window? Using window.postMessage? Disable all cookies for iframes? That seems like it would break the internet.

If you're the parent, you can use the `sandbox` attribute on the frame. If you're the child, you can use the `frame-ancestors` CSP directive.

"If you're the parent, you can use the `sandbox` attribute on the frame. If you're the child, you can use the `frame-ancestors` CSP directive."

... Yea but that requires the parent frame not to want the tracking to take place right? Why would they put the iframe in sandbox mode if they were trying to track their users?

Re: Firefox to Block All 3rd Party Trackers by Default

#184

Earlier quoted context omitted.

Browser fingerprinting? How do you defeat that? If people want to track... they will track.

Throw away your browser and renounce all web technologies made after November of 1995.

Disable Javascript!

Re: Firefox to Block All 3rd Party Trackers by Default

#185

Earlier quoted context omitted.

Throw away your browser and renounce all web technologies made after November of 1995.

Disable Javascript!

I remember when people used to believe Progressive Enhancement meant works without JS... no longer.

Re: Firefox to Block All 3rd Party Trackers by Default

#187

Earlier quoted context omitted.

> Also, why a limit of 8 colors and 12 icons? Why not an arbitrary number of colors and user definable icons? This commonly called the paradox of choice. Satisfaction is often higher when choosing from a limited set of good options than choosing from a large set of options with varying quality. (YMMV, it is also used as an excuse for being inflexible, or for forcing bad options on users a.l.a. a false dilemma, and to…

It's pretty crap in practice. Which of those icons am I to choose for HN? Dog? Fork and knife? Apple? Sunglasses? Briefcase? Gift? I chose 'Dollars' as the closest fit due to the association between the tech industry and greed, but really shouldn't there be at least one tech-themed icon? Of the 12, two are food themed, two or three are shopping related, etc. The icon set is redundant with poor conceptual coverage. Ok…

I just pretend that’s not a feature and use the circle with a single color for everything.

Re: Firefox to Block All 3rd Party Trackers by Default

#188

Earlier quoted context omitted.

https://panopticlick.eff.org/ reports that 1 in 1.67 browsers send the DNT header, so the best option fingerprinting-wise might be to leave it on, at least information-wise. Of course, that ratio will likely change when Safari drops support for DNT entirely. See discussion here https://news.ycombinator.com/item?id=19101156

They send the header, but with which value? I probably didn't express myself well enough, I want my browser to send the "DNT not configured" value.

Sorry, I left that part out. My browser sends DNT=1, and I get 1/1.67, which should mean that 1/1.67 browsers send DNT=1. This means that the total share of browsers that send the DNT header at all is at least 1/1.67, but probably higher.

Re: Firefox to Block All 3rd Party Trackers by Default

#189
post #97
post #95

Earlier quoted context omitted.

To add with that the parent comment said, I do as well, in two ways: - IE prompts me if I want to block cookies on a website, so unless I trust it, I block by default. - I have an extension on Firefox that is "Cookie Autodelete", so I visit a site and unless I whitelist it, all cookies will be deleted when I leave. I wondering if you are not seeing blocked cookie because of the second one. I'm not blocking it, but as…

Right. I have Firefox configured to delete all cookies when I close it. And it only accepts 3rd-party cookies from sites that I've already visited during a session.

Cookie Autodelete is a step over that, it will automatically delete cookies from a site after you close the tab.

Re: Firefox to Block All 3rd Party Trackers by Default

#190
post #15

Companies have begun switching tracking tech to first-party cookies (where possible) since Apple's introduction of "Intelligent Tracking Protection," so Mozilla's similar move probably won't have that much of an impact either. Apple has responded with ITP 2.1, though, limiting _all_ (persistent) cookie lifetime to 7 days, although these could probably be accurately re-issued/kept alive in my opinion: https://webkit.o…

Why do you believe that first party cookies will be able to be re-issued/kept alive? It seems unclear if a visit within 7 days can refresh that timer
Post reply on HN