My RedLib instance is now Cloudflare-free aswell!

I have disabled Cloudflare’s proxy for the r4fo.com RedLib instance aswell.

A long time ago I disabled Cloudflare’s proxy on the majority of my clearnet instances. I did it for privacy reasons, because technically Cloudflare terminates TLS for proxied traffic, meaning they can take a look at the raw HTTP traffic and potentially log it.

I had decided to keep it enabled for the few very popular instances, to save bandwidth and filter out most junk traffic.

Several times I experimented with disabling it for RedLib, but my instance would get rate-limited and go down frequently because of the bots.

Today, I’ve finally gotten my self-hosted anti-bot solution to a point where I believe it is sufficient to handle the bots on its own.

Cloudflare’s proxy remains enabled on the clearnet Nitter instance because of increased risks with hosting it. If your threat model includes Cloudflare, I recommend you to use its Tor or I2P version.