Very true. But GDPR is pure annoyance. I wish they would 100X consequences of offenders and quit wasting development time on the worthless permission prompts.
Is it? I'm the marketing manager of a European app publishers with around 5 millions active monthly users (and many times more if we account for the SDK that we license to other developers). We operates cloud services as part of our offering too. We find it very easy to comply with GDPR.
As for me, I'm very glad as the end users to be protected by GDPR. I've had my data deleted or unpublished about a dozen times since the law has been enacted. And all the people around me are far more careful with how they share their data (and mine! e.g switching to Signal vs Facebook Messenger, or ProtonMail vs Gmail...).
Permission prompts are the wrong way to approach a generally good feature. It would be much more useful if you could configure the permissions you want to give once and for all in your client (browser), and there would be a standard to communicate that transparently to the server.
I keep making the same settings over and over again with different websites. That should not be necessary.
Having browser-wide permissions is actually allowed for if the constent string is stored in the consensu.org cookie. But website owners choose to use their own cookies.
Meh, I want notifications on for whatsapp but I definitely don't want them on news sites. This is the wrong way to go about this IMO. Just a default, should definitely be overridable.
