And all this is done with a single entry in hosts after receiving the real address. After all, knowing the real address, the bot doesn’t have to go through cloudflare. The only good argument is caching, and it can be implemented independently. I find it strange to give all the traffic, including authorization, to cloudflare decrypt for the sake of caching.
The point of cloudflare isn’t just to hide your real IP. It’s the caching, bot scrape protection, etc.
And all this is done with a single entry in hosts after receiving the real address. After all, knowing the real address, the bot doesn’t have to go through cloudflare. The only good argument is caching, and it can be implemented independently. I find it strange to give all the traffic, including authorization, to cloudflare decrypt for the sake of caching.
You can simply configure your server to reject non-cloudflare traffic, as you’re supposed to if you’re doing it properly.
deleted by creator
and I don’t understand why you think CloudFlare keeps your traffic so secret. After all, if you don’t pay for the service, you’re the product.
Heh. You can just put a header that nginx routes to. For example:
curl -H “Host: lemmy.ml” https://1.1.1.1/
P.S. The address is not real. It’s just an example.
Yeah I realized that and deleted the comment before you replied
And an ai slop trainer blocker, which is a fucking godsend.
Yeah. I’m going to figure out another solution but this is a big one.
If you are technically capable, Anubis is an option.
Yeah that’s what I’m looking at for my instance.