Earlier quoted context omitted.
The meteorological dates for "summer" correspond to June 1 to August 31. That straddles 2 quarters and both halves of the year. What are you going to do if a product launch is in July (+- 1 month)? You can't really use Q3 or H2 because neither of them fully captures that 3 month period.
> The meteorological dates for "summer" correspond to June 1 to August 31 That is winter in the southern hemisphere. I'm amazed at the need to have to explain this to a grown adult: https://spaceplace.nasa.gov/seasons/en/
CrowdStrike will be liable for damages in France, based on the OVH precedent
281–285 of 285 posts
Re: CrowdStrike will be liable for damages in France, based on the OVH precedent
#282Earlier quoted context omitted.
I am not sure it's fair to include Canada in the same basket. We don't use freedom degrees, we know that numbers should start with the most significant digits and I believe liability waivers have no value here as well.
> numbers should start with the most significant digits Am curious: where does that not happen in the US? (And in parts of Canada they say 4-20-10 to mean 90 :-)
To us French this is a word like others, it's not like we are calculating in our heads. Belgians have "septante" which is more logical but they do not calculate either.
Re: CrowdStrike will be liable for damages in France, based on the OVH precedent
#283Earlier quoted context omitted.
Well, it'd be a lot easier if most US entities understood that M/d/yy(yy) format is rare, or that default to Frankenstein degrees is pretty much the same/awkward (even Microsoft reset their weather widget to F on regular basis). The root of issue, not understanding local laws/culture, is very similar - surrounded by a vast market/culture (US +Canada) dulls your senses for the rest of the globe.
I always prefer, default to, and advocate for yyyy-MM-dd format for dates to avoid confusion. Once you're used to them, no other format will do. Also, files with such names (backups, etc) will also be in a natural order.
I have to work with logs from computers and applications and this is driving me nuts. "What is the timezone ?" is the question everyone fears.
Re: CrowdStrike will be liable for damages in France, based on the OVH precedent
#284French here, and working for another french CSP. We lived the OVH incident live and saw the whole aftermath. OVH was held liable because of the data loss, not for the service interruption. Data loss is something irremediable, permanent, definitive. Some businesses were basically ruined from this incident because they had no more data to operate. To add insult to injury, they sold offsite backups in the datacenter lit…
IMHO it would send really wrong signals if this doesn't end up with CrowdStrike closing their doors... like if the largest outage in history was caused by you due to a config parser failing and it looks as far as I can tell that they didn't follow industry best practices when it comes to config/parsing handling and probably also didn't follow some best practices when it comes to kernel module programming then honestl…
If aws goes down in a region yeah it sucks but we fail over. If aws goes down ww then it's like well...sometimes that happens. If I've built critical infra like electric utilities, airports etc with swathing vulnerable points then that's the real problem.
Re: CrowdStrike will be liable for damages in France, based on the OVH precedent
#285Earlier quoted context omitted.
the full headline (at this time at least) is more nuanced than seen here in hn: CrowdStrike will be liable for damages in France, based on the OVH precedent.
Doesn’t really make it any less misleading. It is still just an opinion.