News for hackers. Stuff that matters.
Re:Changing Our Approach to Anti-Tracking by Drdrdrq on Thursday August 30, 2018 @03:20PM (#17879862)
One word: uMatrix. NoScript lacks control on per-site basis, but is still ok.
Re:Changing Our Approach to Anti-Tracking by paulryanrogers on Thursday August 30, 2018 @03:37PM (#17880010)
IIRC, Noscript had per-domain JS controls before Umatrix existed.
Re:Changing Our Approach to Anti-Tracking by squarefoot on Thursday August 30, 2018 @03:58PM (#17880185)
But lacked fine grained control, at least the last time I used it. With uMatrix I can tell the browser to disable something (cookies/script/frames/media etc.) here but keep it enabled else/everywhere and the other way around. It gives the finest possible control but of course requires some time to whitelist the good stuff on new pages. A minor annoyance compared to the control it offers.
Re:Changing Our Approach to Anti-Tracking by matheusmoreira on Friday August 31, 2018 @10:30AM (#17885859)
I wish it allowed for even finer control, though. What if it could prevent one specific function from running? Or replace tracking functions with no-op ones? Or hook into HTTP APIs in order to let you audit, modify or interrupt communications?
Re:Changing Our Approach to Anti-Tracking by Drdrdrq on Saturday September 01, 2018 @12:42AM (#17890250)
I guess you could use GreaseMonkey for that, though I can't imagine how you could keep track of everything. Might be useful for smallish modifications though.
Re:Changing Our Approach to Anti-Tracking by staticassertion on Thursday August 30, 2018 @07:58PM (#17881869)
Yeah, noscript is pretty powerful.

The biggest difference between the two, in my experience, is UX. uMatrix is the best UX for a content blocker I've ever seen - very intuitive and simple.