News for hackers. Stuff that matters.
Re:Defeating Cookie Banners by zauguin on Tuesday July 06, 2021 @09:07PM (#27756253)
Wouldn't less annoying Cookie Banners lead to significantly less data?

Or maybe asked differently: Is people giving actual informed consent to tracking actually a thing? I mean for most people I know, the reaction to such banners is one of:

  - opting out
  - trying to opt out but being tricked by misleading design to press a "opt in" button
  - trying to out out but failing and then "opting in" out of desperation
  - people who encountered the previous situations before and "opt in" since they don't have the time/patience to work through the opt out dialogues and decide that tracking is "the lesser evil"
  - Not understanding what this is about and just clicking anything to make it disappear
I can't remember anyone who ever really wanted to agree to such stuff. Of course I haven't done any reliable research on this and it might just be my sampling bias, but I would expect any system which really gives people a choice to get very little positive responses. (On the other hand people are also trained to accept things like ToS without thinking at the end of the user journey, so maybe it works out fine...)

Don't get me wrong, I really like the idea and hope that it will be successful. I just don't see users agreeing to this.

Re:Defeating Cookie Banners by mmarq on Wednesday July 07, 2021 @07:46AM (#27759967)
We should go back to a world where users are paid to test a product, rather than expecting everybody to accept being tracked and to participate to experiments.
Re:Defeating Cookie Banners by mavhc on Wednesday July 07, 2021 @04:29AM (#27758742)
I press the button most likely to get rid of the thing in my way as fast as possible
Re:Defeating Cookie Banners by tremon on Wednesday July 07, 2021 @05:33AM (#27759162)
So basically, you're rewarding dark patterns. I get where you're coming from, but I'd rather people-in-the-know use CSS rules or other hacks to work around this.

Basically, anything but enabling treacherous design.

Re:Defeating Cookie Banners by mavhc on Wednesday July 07, 2021 @09:32AM (#27760909)
well, I have ubo enabled too, so I remove overlays and blurs sometimes, my point is I don't care, I'm visiting the site once ever most likely, I just want to read the page and leave
Re:Defeating Cookie Banners by Sephr on Wednesday July 07, 2021 @03:25AM (#27758353)
I completely get where you're coming from. I'd personally never consent to tracking either without adequate incentives.

This new consent manager makes it easier for site owners to offer incentives to consent (e.g. share your user journey for 5% off at checkout).

Note: 'Selling your privacy' (and likely incentivizing consent) may not be legal under some regimes, so nuance should be applied to any novel implementations using our consent manager. We have a privacy legal regime detection API which helps enable varying UI & behavior based on user-applicable legal regimes.

Re:Defeating Cookie Banners by Y_Y on Wednesday July 07, 2021 @03:34AM (#27758405)
How do you check what the applicable legal regime is?

(Please don't say IP geolocation.)

Re:Defeating Cookie Banners by Sephr on Wednesday July 07, 2021 @03:57AM (#27758539)
Currently we use your browser's language and time zone settings to derive applicable legal regimes such as GDPR, CPRA, and LGPD.

This method even supports the nuance of detecting a EU-likely user vacationing in California, affording them both CPRA and GDPR protections. You can try out this API by typing `await airgap.getRegimes()` in your browser console on this blog post.

This method won't scale forever as more states and countries enact new privacy laws so we do plan on eventually falling back to IP geolocation as well.

Re:Defeating Cookie Banners by TeMPOraL on Wednesday July 07, 2021 @05:09AM (#27759011)
For those of us less fluent in modern JS, the console command should be:

  await airgap.getRegimes()
to unwrap the promise and display the regime set directly in the output :).

Also, I can confirm it correctly identifies the regime applicable to me (GDPR).

EDIT: I played a bit more with your blog post, after disabling my Adblock and tracking protection features in Firefox. It seems you're dogfooding your system here and now; I don't see any analytics calls happening beyond the scripts being loaded, and I also see a bunch of requests being trapped by airgap (I found it by doing airgap.export("foo") in the console). Nice work!

(So, what kind of analytics are you getting from this blogpost without asking? ;))