[vsl]

See GDPR side effect of annoying banners everywhere even if I don't give a damn about my website visits information being processed, for how unintended consequences played out and made the web worse for everyone.

For DMA specifically, see Apple withholding Screen Mirroring (a feature I would enjoy tremendously) from EU for fear (IMHO quite reasonable) that the vaguely written DMA could be interpreted as requiring them to open mirroring to 3rd parties.

It's been just a few months and already DMA impacted my enjoyment of my devices, no?

[Moldoteck]

the only problem with gdpr is that it didn't push far enough. If your browser provides a header with accept/reject all, a banner should not be shown. Also, GDPR does have many other interesting things, including being able to download/delete your data

[xandrius]

Just for your info, the banners are absolutely not required and they are the band aid solution of websites who don't give a crap about their users.

If you also don't care about yourself, it's worse for you but many others now have the chance to deny providers of their scummy way to make money off unwitting users.

[shagie]

Here is the home page of the European Union https://european-union.europa.eu/index_en

There is a banner.

The European Commission on data protection https://commission.europa.eu/law/law-topic/data-protection_e...

There is a banner.

The press release for the current enforcement against Apple https://ec.europa.eu/commission/presscorner/detail/en/ip_24_...

There is a banner.

> the banners are absolutely not required and they are the band aid solution of websites who don't give a crap about their users.

If this is true, it says a lot about the organization running those websites.

[alt227]

Parent is right, banners are not required by GDPR. These websites do not reflect the people in the organisations they represent, they are made by developers like the rest of us who are following the crowd like sheep.

[shagie]

From https://european-union.europa.eu/cookies_en

    3. Analytics cookies

    We use these purely for internal research on how we can improve the service we provide for all our users.

    The cookies simply assess how you interact with our website – as an anonymous user (they data gathered does not identify you personally).

    Also, this data is not shared with any third parties or used for any other purpose. The anonymised statistics could be shared with contractors working on communication projects under contractual agreement with the European Commission.

    However, you are free to refuse these types of cookies – either via the cookie banner you will see on the first page you visit or at Europa Analytics.

That appears to be things covered by the GDPR and that they need some way to inform you that you can reject them ... and that's done with a banner that allows you to reject those cookies.

Given that analytics is used, and that has cookies that track information, they're required to have that notification somehow. That page doesn't appear to be a "developers following the crowd like sheep" but rather "the requirements of the law are followed to the spirit and letter and the easiest and most accessible way to provide that functionality is with a banner."

[alt227]

I agree with your points, but with this...

>the easiest and most accessible way to provide that functionality is with a banner.

I read that as 'the laziest way'.

[p_l]

Well, one option is to automatically trigger "reject all" option if you see "Do Not Track" header or equivalent.

[shagie]

Designing the website in a way that works with browsers that meet the requirements of https://digital-strategy.ec.europa.eu/en/policies/digital-in... and https://commission.europa.eu/resources-partners/europa-web-g...

The banner works for its requirements with GDPR and meets the requirements for accessibility.

Surely, one cannot expect that companies trying to save costs will go through great lengths to implement something that they don't know if it will work or not or if they'll get sued in the EU if they implement a different solution when the EU themselves implement it this way.

If there is a better way of doing it that doesn't lead to lawsuits, the EU's website should be the first ones to implement and demonstrate an easier and more accessible way to comply with the GPDR.

As it is, the websites of europa.eu are setting the standard for companies to follow when they want to make sure that they don't get sued for failure to comply with the GPDR for website notifications and accessibility within the EU.

[hindsightbias]

It's interesting the views in the threads of "screw your parents if they can't figure out how to protect themselves w/o iOS/AppStore" to "we must think of the children and protect them from cookies"