[_nalply]

I've learnt my lesson.

In future I will dismiss cookie consent buttons by deleting it's DOM node from the inspector.

[_nalply]

Addendum: Google logged me out of some services and I had to re-login with 2FA. It seems that Google is doing something about this, but what exactly?

[EADGBE]

Sounds like an "oh shit" "self-destruct" button just to cover their asses while they figure it out.

[_nalply]

Nope I think it's more some AI stuff who has triggered.

[defen]

Happened to me too

[eganist]

This would be a nice adblock list.

[kuschku]

Considering cookie consent buttons will be gone in two weeks, I don't think that's gonna be of much value.

EDIT: Please research the GDPR and new ePrivacy regulation before you vote.

[technion]

I won't vote either way, but I will say that regardless of what GDPR may mean, "you need a cookie warning" will be accepted web dev mantra for years, and the things they build in that time will be around longer still.

[kuschku]

The "you need a cookie warning" is yhe reason why the GDPR is actually so strict, though.

The goal was to let users opt out of tracking in the hope that the industry would self-regulate.

Now that it hasn't, GDPR is coming down hard.

Web devs really manage to fuck everything up.

[icebraining]

I bet you they'll still be around in a decade :)

[kuschku]

They may be, but they'll be useless then. They're not considered consent anymore under the new regulations.

[icebraining]

Being useless is just one more reason to adblock them.

[epanchin]

another neat method for closing them;

https://news.ycombinator.com/item?id=16575304

[ghba66]

This one works well for me: https://github.com/r4vi/block-the-eu-cookie-shit-list

[me_bx]

Fanboy's cookiemonster list seems to be updated more frequently: https://github.com/ryanbr/fanboy-adblock/blob/master/fanboy-...