A public letter to CloudFlare to fix their snoopy vendor
1–10 of 117 posts
Re: A public letter to CloudFlare to fix their snoopy vendor
#2Re: A public letter to CloudFlare to fix their snoopy vendor
#3what are the use-cases for cloudflare in front of GitHub pages?
GitHub Pages originally didn't support SSL on custom domains, so people would often put Cloudflare in front of it.
Now GHP does support SSL on custom domains, so Cloudflare is no longer needed, but obviously a lot of sites still exist with the original setup.
Re: A public letter to CloudFlare to fix their snoopy vendor
#4what are the use-cases for cloudflare in front of GitHub pages?
Re: A public letter to CloudFlare to fix their snoopy vendor
#5Re: A public letter to CloudFlare to fix their snoopy vendor
#6Re: A public letter to CloudFlare to fix their snoopy vendor
#7Re: A public letter to CloudFlare to fix their snoopy vendor
#8Re: A public letter to CloudFlare to fix their snoopy vendor
#9What if the site owners change their SSL settings to Full SSL though?
Re: A public letter to CloudFlare to fix their snoopy vendor
#10Please Cloudflare, I'm a paying customer and have some IPv6 only users that are very frustrated every time they see a Cloudflare challenge page. Your provider, HCaptcha still do not support IPv6. I have to use workarounds like an alternative domain without CF and this is very frustrating.
edit: I realize there are plenty users behind NAT64 gateways etc, that's the point: how many users out there have no IPv4 connectivity at all?