In my opinion, anyone who puts this sort of stuff in front of their blog is overly paranoid (unless they are some sort of high-profile victim, like Brian Krebs). Just avoid reading their blog.
In my opinion, anyone who puts this sort of stuff in front of their blog is overly paranoid (unless they are some sort of high-profile victim, like Brian Krebs). Just avoid reading their blog.
https://en.wikipedia.org/wiki/Defense_in_depth_(computing)
Really, the longer a website is online, the more it attracts bots. Spam bots, brute-force login attempting bots, information gathering bots, vulnerability testing bots, and many more. This isn't even counting targeted attacks.
I've seen many small websites recieve much more bot traffic than user traffic. Sometimes to a crippling level.
My point is, it's not paranoia if they really are after you - even if it's a mindless mass of bots.
Like all security though, sometimes you affect legitimate users. This is why it's great to have multiple ways they can provide feedback.
This was mitigated by implementing a few layers of a decent caching strategy, as well as some db improvements, and moving search queries to a separate database server (mongodb, then elasticsearch) altogether.
In the end, there are lot of things you can do to help mitigate these things... It really just depends on what you are trying to accomplish with a given site.
The only reason Cloudflare captchas exist is because of utterly incompetent engineers, nothing else. You can stop attacks without breaking the internet for people without US residential IPs.
I would much rather than Cloudflare added a header when in "under attack" mode, and delivered cached responses to get requests.