https://news.ycombinator.com/item?id=50167754

Sadly, probably still the best Cloudflare blog written in the last nine months.

https://nginx.org/en/docs/http/ngx_http_upstream_module.html...

We had the same thing happen with any email with 2f anywhere in the message body on Google workspace

The "2F" URL decodes to slash / and a third party registered our 2f.com (probably for nefarious purposes)

That kicked on the automatic filtering on messages that had URL encoded links and started blocking them.

Eventually, we had to register 2fgoogle.com ourselves to escalate the issue.

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

I'm not sure I would call it even close to battle hardened.

They are still many lurking footguns and bugs.

Try running it with > 250k tables. Falls down hard.

Error logic around etcd/topo server is very shaky, edge cases can wedge cells/clusters into broken state.

Heck, you could even display a warning or the top directories consuming space upon login.

Not a great take - this is a operations problem, not a design problem.

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.

For complex multi-member clusters Maria/MySQL are quite far ahead.

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.