Why then do they make the most annoying, user-hostile dark pattern cookie banners they can come up with? No, website operators hate that they have to either stop spamming thousands of tracker scripts or put up a banner.
replyThey found out that they can offload blame on the EU instead and so have chosen to make the web as annoying as possible.
Yeah, that's more the point; in discussions with clients I very often get asked how far we can go without any consent. Most companies want all the privacy ignoring stuff and they don't want to tell their users about it.
replyRealistically you won't be caught analyzing server-side logs of things the client is doing anyway, even if you don't follow GDPR rules with those logs. But they want Google Analytics, right?
replyMost of them don’t care and just integrate whatever is the most common cookie banner widget because their legal team asked them to
replyThe solution to that one is pretty simple, simply don't collect information you don't need, and you can avoid the banner altogether! Github manages to not have banners, it's not because of magic.
replyThere is no obligation to put a banner of you don't sell your users' data to third parties. The law is very clear that your don't need it for period technical cookies, so it's really always and every time solely about tracking and advertisement money.
replyYou do need it for analytics though, or any other non-essential purpose.
replyYou could probably argue self-hosted, privacy-preserving analytics is a "legitimate business purpose" so doesn't need consent. AFAIK it's because you're sending user data to Google that you normally need consent for GA.