Tablesaw Tablesawsen is a user on mastodon.social. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

Chrome's private browsing is broken

This defeats the purpose of Incognito. If any website is able to tell you're browsing in private mode, then the browser is leaking data that shows it's not private

@cypnk The same can be said of ad blocking. When a "deactivate your ad blocker" screen comes up it should be treated as a high-priority bug in the blocker.

@mattskala @cypnk Not a high priority. Adblockers are always detectable, and their primary function is not to be undetectable (unlike the virus/AV game.)

@varx @cypnk Being detectable interferes with their primary function, and it's not obvious to me why it would be necessary. The bits on the wire could be the same regardless of whether all of them end up displayed on the screen.

@mattskala @cypnk They have to be detectable because they interfere with the functioning of the page; they change what scripts are loaded, and it's trivial to discover that.

You can play a cat-and-mouse game and even go so far as to modify the site's Javascript to bypass the bits that notice the adblocker, but at that point you're deep into diminishing-returns territory.

@varx @cypnk We may place different values on the returns involved. As far as I'm concerned the pop-up that starts with "We noticed..." is a *big problem*, worth a lot of effort to prevent, and that effort is central to what I expect from my ad blocker.

Tablesaw Tablesawsen @Tablesaw

@mattskala @varx @cypnk The site necessarily needs to know whether the ads it wants to run are actually running, otherwise it could be held accountable for fraud.

@Tablesaw @varx @cypnk That's the site's problem. I am under no obligation to help.