It is a closed ecosystem, where - as a viewer - you have gated access and - as a publisher - require your viewers to consent to a third-partys rule. Accessibg ststus.github.com has only the terms of GitHub involved, not also Twitter/X/...

I think that eeally depends on regions. Where I am located, nobody will ever knock and everybody uses the door bell.

But the internet does, and it is 12% for gambling, against 15-25% for tourism (whichever source you believe).

[1] https://timesofmalta.com/article/the-15-billion-question-is-...

[2] https://www.emcs.com.mt/emcs-tourism-malta-economy/

I have a Volvo. Twice a year when DST changes, the schedule is afterwards one hour off. Been this for 3 years now.

I'm really happy I live in a country and company sizes where you could leave your wallet on your desk and nothing happens. Glad I don't need to secure my mug to my desk.

Even in the safest country I would never intentionally leave my wallet at my desk.

Can't count the times a "nuget restore" in our CI fails with 401, just to succeed on a 2nd attempt a few seconds later. Seems like the IP range is somehow flagged, so there's definetly a downside to it.

giving real relatable task like that is memory excercise, not any reasoning excercise. The training dataset have tens of thousands apps like that

And I could tell you the opposite about 1Password. About half of the time, the extension does not realize ond which domain it is and autofill is broken.

To each their own (bugs).

Fair point - I've had no issue with it but I certainly don't use it as much as I do Bitwarden.

That really sounds line the US is the only country in the world. Considering the world is bigger, I would call Spirit maybe regional, but not small. Ask some europeans, basically no one will know Spirit - as US people may not know e.g. Wizz.

And then, someone added IAM so you could actually restrict your credentials from deleting your database.

First mistake is to use root credentials anyway for Terraform/automated API.

Second mistake is to not have any kind of deletion protection enabled on criticsl resources.

Third mistake is to ignore the 3-2-1 rule for backups. Where is your logically decoupled backup you could restore?

I am really sorry for their losss, but I do have close to zero empathy if you do not even try to understand the products you're using and just blindly trust the provider with all your critical data without any form of assessment.