search

captn3m0 / hello-cloudflare

A public letter to Cloudflare to fix their snoopy vendor
241 stars 13 forks source link

Cloudflare Pages #8

Closed JeffHochberg closed 2 years ago

JeffHochberg commented 2 years ago

Switch from GitHub Pages to Cloudflare Pages. Then you just configure Cloudflare Pages to connect to your GitHub Repositories.

Anytime you commit to your repositories that are connected to Cloudflare Pages, Pages will automatically kick off a build and your site will be updated within a couple of minutes or so.

ignoramous commented 2 years ago

The problem here is two fold:

  1. GitHub pages is where existing websites are at.
  2. Defaults matter. And the default with Cloudflare is Flexible SSL, which is atrociously misleading in cases like these when a Cloudflare peer (like Airtel) mucks with Cloudflare's customer traffic (albeit under government guidance). From this Cloudflare CTO's past interview on VPNs, it doesn't look like they care about it (government censorship) enough, though.

None of this is addressed with pages.dev. In fact, you'd want to not put more stuff on Cloudflare when GitHub Pages is plenty fast and vends free TLS/SSL certs.

captn3m0 commented 2 years ago

Discussing Cloudflare Pages is out of scope of this letter. The ground reality is that enough projects and users are using Cloudflare against GitHub Pages and we can't realistically get everyone off this combination (to any solution) to fix the problem for folks in India.

Enabling Strict SSL is the fastest and easiest fix for now, which is why that's the current recommendation.

captn3m0 commented 2 years ago

Added a third fix on switching to a different provider.

Thanks!