by kuba-orlik on 4/23/23, 7:59 AM with 92 comments
by kotaKat on 4/23/23, 12:25 PM
Checking to see if that statement is secure.
refreshes
Checking to see if that statement is secure.
refreshes
Checking to see if that statement is secure.
by harry8 on 4/23/23, 11:55 AM
by jacquesm on 4/23/23, 12:32 PM
by codegeek on 4/23/23, 2:49 PM
Btw, if you haven't tried, give Cloudflare pages a shot if you are looking for a no nonsense static website tool. Combine it with Cloudflare workers, you can add dynamic features as needed. I don't work for them but just a happy customer.
by TekMol on 4/23/23, 11:00 AM
If so, how do you manage consent?
I tried to build a simple modal that asks the user if they agree to ads+cookies, with a link to a privacy policy which explains that I use Adsense and a link to their privacy policy. And only loaded Adsense if the user agreeed. But Google never accepted that. They never gave an explanation why.
by snowstormsun on 4/23/23, 2:48 PM
by donohoe on 4/23/23, 1:07 PM
The issue with this and all consent mangers is always ads.
It is impossible to know all the potential ad vendors, ad tech, and what other devices ads will load in advance.
Googled consent framework, the IAB framework, etc, all fail to address this.
by evntdrvn on 4/23/23, 1:58 PM
by jacooper on 4/23/23, 4:07 PM
My rule of thumb is just never to use them as a proxy, CDN through R2, static pages etc are okay. Unfortunately Zaraz requires your website to be behind CF proxy.
> And if you've ever clicked something other than Approve you'll have noticed that the list of choices about which services should or should not be allowed to use cookies can be very, very long.
There should be a reject all button, right?
by time4tea on 4/23/23, 5:15 PM
It's only because sites are jam-packed with spyware that all these horrendous popups are everywhere.
If you need a complex consent manager, it's a signal that you're doing the wrong thing.
Ads are not strictly necessary, nor visitor tracking, btw.
by JCWasmx86 on 4/23/23, 2:48 PM
by syndacks on 4/23/23, 2:55 PM
by skrebbel on 4/23/23, 1:42 PM
by sylware on 4/23/23, 11:16 AM
by mhils on 4/23/23, 5:10 PM
If Cloudflare is serious about privacy here, they should at least respect GPC and not provide customers with an option to disable it.
by PoignardAzur on 4/23/23, 10:35 AM
No consumer is going to say "oh, now that you've provided me such a streamlined tracking consent experience, I'll give you consent to track me across sites to show me personalized ads". They'll just click the "reject all" option you're legally compelled to give them.
Also, the example includes a consent option for anonimized pageview counts data, which under GDPR you don't need consent for.
An approach that would really respect user would be to store traffic analytics anonymously (in a way that resists trivial de-anonimization, so with binning and stuff), and throw away the rest. There, no consent popup needed.
by hammyhavoc on 4/23/23, 4:04 PM
by blibble on 4/23/23, 1:45 PM
and the US is not considered to have adequate data protection laws under the GDPR