How to Block Some of the Bots
nochan.net - 43 poäng - 30 kommentarer - 9092 sekunder sedan
Kommentarer (12)
- CqtGLRGcukpy - 2171 sekunder sedanIf you are unable to read this, there is an archived copy at https://archive.ph/d3236
- fxtentacle - 7207 sekunder sedanI like the idea of adding a fake cpanel subdomain for 169.254.169.254 so that script kiddies will start port-scanning their own hosting provider, which will likely get them flagged/banned.
- binaryturtle - 7950 sekunder sedan410 and a "Sec-Fetch-Mode:" string in the response body. I guess it thinks I'm a bot? Thanks!
Nothing to read, nothing to see, I move along. (Yikes, the modern web sucks!)
- genodethrowaway - 1615 sekunder sedanand all valid traffic too, judging by these HN comments (and my own attempts to connect).
- fatty_patty89 - 836 sekunder sedanwhat's up with those response headers? "adult" ...
"ai" ...
response length 68
- FabCH - 1470 sekunder sedanThe post content is great. I personally hate the way Cloudfare has been the „default answer“ for the bot problem because Cloudfare has become the most successful MITM attack in history. We need content like this to keep the internet alive.
The added explanations by the author in this comment thread are hilarious. You sir are a good writer.
- RobotToaster - 2512 sekunder sedanBlocks firefox's built in VPN.
- ajsnigrutin - 4760 sekunder sedanThere's a special place in hell for people who block curl and wget, especially on sites with downloadable files (eg source code tgz's, media, etc.), basically anything i might need to wget on a server.
- iririririr - 5934 sekunder sedanmost (all?) of those will 100% block valid traffic too
- Capricorn2481 - 4263 sekunder sedanAm I the only one that exclusively gets attacks with spoofed user agents and rotating TLS signatures? I feel like every post I see about not needing a CDN has tips that could be overcome in under an hour of scripting.
- gorkemyildirim - 1058 sekunder sedan[dead]
- receptopalak - 2920 sekunder sedan[flagged]
Nördnytt! 🤓