The problem fixed itself when backend servers were reachable again.

I don't know what the design decision is here, but in a sane browser, there should be 0% reliance on "backend servers" in order for it to be usable.

I assume it's just out-of-control polling. The fix is probably to add a stepping timeout on errors. Not ideal, but not a very egregious oversight given that a browser will nearly always be used in an environment that's at least internet-connected.

Lack of internet connectivity should be a basic scenario any browser should have a plan for.

"- The Mail app comes with an "Upgrade to Office 365" button always visible."

By right-clicking on the button you can hide it completely.

Thank god Brave has field trials disabled by default [1], among many other Google "services" [2].

[1] https://github.com/brave/brave-browser/issues/4283 [2] https://github.com/brave/brave-browser/wiki/Deviations-from-...

That is ridiculous. Does anyone know if that's the case with GCP / Azure too?

From what I know is that you can peer the Lightsail (AWS-managed) VPC with your normal, default EC2 VPC via the Lightsail console. Then you launch EC2 instances in the default VPC for the transfer

Fun fact is, that Netflix only hosts their website on AWS, the video stream is delivered from their very own CDN which is completely self-engineered by them and multiple magnitudes cheaper than AWS: https://openconnect.netflix.com/

Interesting, I like the fact that "Replicated objects can be owned by the same AWS account as the original copy or by different accounts, to protect from accidental deletion." is something they thought of.

That's really a pity (I am from Europe and would love to participate too!)

In this talk, part of "The Future of Programmable Money" series, Andreas discusses digital gentrification and corporatisation, how this relates to the "blockchain not Bitcoin" phenomenon, and why we should maintain interesting communities both offline and online.