These annoying messages are a bad attempt to follow a bad law. But to just block these messages in the browser seems like a bad approach. The point is to get in

These annoying messages are a bad attempt to follow a bad law. But to just block these messages in the browser seems like a bad approach. The point is to get informed consent to write+read cookies from the user. One could argue that the act of installing a plug-in for this purpose = implicitly consenting to accepting any and all cookies, but that seems like a weak inference. Given the law, it would be better to be able to pre-emptively, explicitly blanket-consent to all cookies, or specific types of cookies (e.g. analytics tracking, or saving user settings) in one's browser (or at first, before it's standardised, with a plugin). Of course, this solution would require web developers to follow certain standards in implementing their cookie-consent-getting method. (It would have been even worse if they tried to legislate this from the outset.)