this post was submitted on 18 Nov 2025
409 points (92.3% liked)
memes
18070 readers
1708 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The funny thing is that the Lemmy nodes are synchronized with each other, and to calculate the real address of any Federation node, it is enough to raise a node, write a comment in the interested node, and then reply to yourself from that node. Done. Real IP in you node logs. However, everyone continues to use Cloudflare... This will only protect you from technically illiterate people.
The point of cloudflare isn't just to hide your real IP. It's the caching, bot scrape protection, etc.
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.
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.
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