Safari on IOS still has a ton lingering HTTP/3 / QUIC bugs.
I think it is to the point that if your user base doesn't warrant it, (i.e. you are targeting well connected devices with minimal latency/packetloss) it's not even worth turning HTTP/3 on
Meanwhile, it’s going on two weeks that a large volumetric amplification attack has been coming from CF itself against systems I manage.
Ironically, their abuse report does validate the domain being used to route traffic is a registered customer domain. But the abuse report and even Slack pings have yet to affect the traffic. It’s incredibly frustrating because you’d expect a company like Cloudflare, which positions itself as a defender against DDoS and similar threats, to take action much more quickly when they’re part of the problem.
I want to know that you care enough to have done a modicum of research on your new potential employer. And in turn, that you can give a short answer on why you might want to spend 40 some hours a week with us.
If you can't do that, (and it really just is all about the money) then that's just a precursor to a disaster or new future burn out.
Sadly, probably still the best Cloudflare blog written in the last nine months.