cloudflare

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-08-28

Final complete day: 2026-08-28. Attention was 1.3% — this entity appeared in 34 of 2,594 analyzed posts/comments in the seven days ending that day (44 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-08-28 18:21 UTCComment

   You have 9 hours to move to cloudflare :)

2. 2026-08-28 15:19 UTCComment

   I would use a combination of Cloudflare with a rule to filter out the bots. I'd also use a ratelimiter to block the IPs sending too many requests as an additional line of defense.

3. 2026-08-28 13:12 UTCPost

   Won a bot battle. - We support a client site with ~20,000 pages. It has an SSR search page that uses the url querystring to execute the search/sort/filter. We have of course disallowed bots on that page because the 20k pages are meaningful and should be scraped/indexed, but the billions of possible query combinations on a search page are not. Most of the bots just ignore the robots rule and this results in waves of traffic hammering every possible query combination on the search page. These waves are 10x-50x the human traffic. Rather than let the bill autoscale along with the server cluster, I wrote a little bash script that crons 1/m: - Hits DO's metrics endpoint to check the CPU usage on the VPSs/DBs - Each minute any of the CPUs stays above a given threshold, bump Cloudflare's security level, eventually ending in "under attack" + "bot fight" - When the cpu drops below the threshold for a given amount of time, start backing off until we're back to normal operation. Works a treat. It's nothing particularly flashy or sophisticated, but it was satisfying to think through an under-engineered solution to a problem that a lot of people end up just chucking money/clusters at. Edit: more info for context: We do have pretty aggressive WAF rules especially on the search page, but we've been seeing an increasing amount of bot traffic get past CF's "known bots". Rate-limiting has been minimally effective too because the bots that get through are cycling through 100s of IPs in a given scrape.

4. 2026-08-28 06:45 UTCComment

   one angle nobody mentioned: personal projects outlive your willingness to pay for them. i had a paid host lapse once and the site plus every subdomain just went dark. moved the static parts to cloudflare pages (free tier, custom domain, no card required) and now the parts that cant "expire" are the parts that dont bill. so my rule: frontend on a free static host forever, backend on something that scales to zero, and dns at cloudflare so you can repoint pieces in one click when you inevitably move the backend. and +1 to the billing alert advice above, that one sounds earned

5. 2026-08-27 20:17 UTCComment

   For frontend, cheap VPS or Cloudflare pages works very well. For backend / hybrid Next setups, Google Cloud Run is very straightforward and you only get charged based on usage