vnkr

That looks like a lot of work.

Cloudflare is a tool. Website owners use this tool to solve the challenges they face. You are shouting at a wrench.

Depending on the mode you choose there can be an interactive element

Not on purpose.

https://www.cloudflarestatus.com/incidents/jgv6r0czdddt

Cloudflare does not protect that website. It’s not behind Cloudflare.

Correct. And also customer needs, UI technologies, the way people use apps and services change. So it's all right for apps to change as well.

If you don't want your software to change, don't update it. The way Thunderbird looks and the messages list is a large part of it is horrendous and is a deal breaker for me, for example.

Yes, but FF on iOS sucks precisely for the reason stated in the article.

I don't use FF on desktop partly because I don't use it on mobile and so can't sync open tabs, bookmarks, etc.

Cloudflare's status page is one of the very few services of Cloudflare that are hosted elsewhere precisely for the reason it needs to be available if something isn't working.

That's what is suggested in the blogpost as one of future prevention plans.

It's very difficult if not impossible to create a staging environment that would well enough replicate production at this scale. What bog posts suggest as a remediation in the process: "There are several opportunities in our automation suite that would mitigate some or all of the impact seen from this event. Primarily, we will be concentrating on automation improvements that enforce an improved stagger policy for rollouts of network configuration and provide an automated “commit-confirm” rollback. The former enhancement would have significantly lessened the overall impact, and the latter would have greatly reduced the Time-to-Resolve during the incident."

The isolation itself happens by way of prepending the URL in the original link with a Remote Browser endpoint.

In order to do that Area 1 has to either be your MX or integrated with your email provider via API AFAIK

You don’t, even the free plan has 3 included.

HTML can often be server rendered dynamic and is unsafe to cache by default.

By “this” do you mean the fact that “we do not block or challenge Firefox by default”?

Customers can create firewall rules to challenge requests using any type of request metadata. User agent is one of the filters, that can be used in manual Firewall fields.