✧✦Catherine✦✧grebedoc had its highest share yet of serving garbage requests yesterday (a wave peaking at 150 req/sec)
these waves are getting bigger and bigger which is somewhat concerning. it's nowhere near the hardware capacity yet but i'm hitting some software bottlenecks that i've never thought would be relevant
Daphne Preston-Kendal@whitequark How do you define/measure garbage requests vs non-garbage?
@dpk with these waves it's pretty easy because they send Host: requests whose A/AAAA records don't point to grebedoc and never did (it's something like every domain from the Cloudflare 1M list, last time we investigated it)
requests that have no business being ever sent to grebedoc
some others try to brute-force wp-admin paths and such
Hugo Mills@whitequark @dpk It's jaw-dropping quite how awful some of this stuff is. Things that will never (to within probability of epsilon) work. I just don't know if it's ignorance (with unlimited resources) or malice (with unlimited malice). Either way, it engenders great anger.