@kkarhan@infosec.space@LibreKitsune I still consider this a hostile act and a blatant violation of their previous #settlement that forced them into #publishing said #IPv4 #ranges...
- In fact had they not actively worked against that previously and it only raised my attention when I saw errors re: said ranges.
I'm considering to build a #workaround on #GitHub to just use a #cookie and some #compute to do it, but if I had cash to spare I'd sue them into removing #ClownFlare and allowing me to scrape the list directly...
- I'm very close to just sending them an #invoice for the personnel hours wasted on that bs and billing them regularly for the expense of manually checking the difference between those (@ minimum of 60:15 billable minutes)...
Otherwise I do expect regulators to actually go after #OpenAI and force them to undo the #Cloudflare-based #Enshittification, since it's neither feasible nor reasonable to claim "#DDoS-#Protection" for a 48 Bytes (!!!) file...
- Every #WAF / #WebApplicationFirewall I know would not get triggered even if I were to query it once per hour (which I now do just to annoy them or rather ClownFlare!...