Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CrowdStrike will be liable for damages in France, based on the OVH precedent

thehftguy.com

Post reply on HN
Print view View original

271–280 of 285 posts

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#271

Post by account42 »

HappySweeney wrote: post #241
627467 wrote: post #207

Earlier quoted context omitted.

I understand that CS doesn't draw much sympathies even before this happened - from myself included - and it is easy to pin point systemic issues to a single failure point and make it liable and financially responsible for all downstream failures. But this only creates excuses for all other responsible players in this systemic issue - or society at large. Just to pick 1 example: I keep reading comments on how profound…

I read that healthcare was mollified by a facility whereby they could choose when and which updates to allow, which CS intentionally bypassed with this latest update. This was during the chaotic day-of though, so possibly false.

There can always be lingering bugs that trigger at a certain time on all systems or for certain input data so the only way to have redundancy is to have actually heterogenous systems.

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#272

Post by account42 »

tracker1 wrote: post #234
xxs wrote: post #33

Earlier 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.

RFC 3339 / ISO 8601 FTW!

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#273

Post by account42 »

raverbashing wrote: post #144
xxs wrote: post #33

Earlier 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.

> f most US entities understood that M/d/yy(yy) format is rare The worse offender on this I suspect it's Apple. Where half of their localization stuff doesn't work or works in a weird way

It even affects open source projects like KDE: https://bugs.kde.org/show_bug.cgi?id=340982

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#274

Post by account42 »

dustincoates wrote: post #93
cmrdporcupine wrote: post #63

Earlier quoted context omitted.

> surrounded by a vast market/culture (US +Canada) US companies don't think about Canada as anything but an afterthought, and struggle with the same issues here that you just mentioned. Canada is metric, uses different spellings (closer to UK English.. colour, not color [Chrome just marked my spelling as wrong despite me having Canadian English as my setting]) and is officially bilingual with localization laws requir…

> And navigation on Android / Google Maps can't pronounce French names for streets/places while driving around in bilingual places in Canada. Honestly, I think this is the right approach, and I'm speaking as a bilingual French/English speaker. Google Maps doesn't know that you are bilingual. So it has two choices: pronounce words the "right" (i.e., native) way, or pronounce them the "English" way. If someone who is u…

There are plenty of English place names with surprising pronounciation too. I don't think out software should encourage us to stay ignorant of the proper pronounciation - it's not like the map software is the only place wehre you are ever going to encounter spoken place names.

> If someone who is unused to hearing the native pronunciation, their understanding is going to be impeded

Circular reasoning. If common software used the right pronounciation more people would be used to it.

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#275

Post by account42 »

xxs wrote: post #185
dustincoates wrote: post #93

Earlier quoted context omitted.

> And navigation on Android / Google Maps can't pronounce French names for streets/places while driving around in bilingual places in Canada. Honestly, I think this is the right approach, and I'm speaking as a bilingual French/English speaker. Google Maps doesn't know that you are bilingual. So it has two choices: pronounce words the "right" (i.e., native) way, or pronounce them the "English" way. If someone who is u…

>Google Maps doesn't know that you are bilingual. But it does know, e.g. "Accept-Language" header. Of course, google resent that part and travelling across Europe results in having a different language every day.

Google outright ignores Accept-Language: en-US and randomly resets your cookies to use the local language based on your IP. They've been hiding the link to change back to English more and more too and have started to show local language search results above english ones (e.g. for Wikipedia) even with the interface set to English. I have nothing but the worst wishes for those responsible.

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#276

Post by account42 »

ralgozino wrote: post #109
RandomThoughts3 wrote: post #49

Earlier quoted context omitted.

Special mention of the expression “the west” which Americans like to use to mean the USA and some amorphous blob I don’t really want to think about but I’m going to pretend is exactly the same as the USA.

Somehow related, expressions like "next summer", "starting this spring" and such on public global announcements make absolutely nonsense if you are in the southern hemisphere (like a big percentage of the global population)

"a big percentage" being only 13%.

I think this one is understandable.

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#277

Post by account42 »

JumpCrisscross wrote: post #126
classified wrote: post #39

Earlier quoted context omitted.

It's not unusual in the US to assume the US are the only planet in the universe.

> not unusual in the US to assume the US are the only planet in the universe This is true for every large culture.

Not really.

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#278

Post by sam_goody »

tuetuopay wrote: post #138

French 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…

As I understand it, anyone with bitlocker irretrievably lost all their data.

Logic dictates that the more critical the data - the more likely it is gone. An informal anecdotal survey says that alot of users use bitlocker - which means a lot of data loss.

EDIT: I see that in many cases one can recover Bitlocker encrypted drives. I wonder how much real data loss there is.

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#279

Post by xxs »

account42 wrote: post #275
xxs wrote: post #185

Earlier quoted context omitted.

>Google Maps doesn't know that you are bilingual. But it does know, e.g. "Accept-Language" header. Of course, google resent that part and travelling across Europe results in having a different language every day.

Google outright ignores Accept-Language: en-US and randomly resets your cookies to use the local language based on your IP. They've been hiding the link to change back to English more and more too and have started to show local language search results above english ones (e.g. for Wikipedia) even with the interface set to English. I have nothing but the worst wishes for those responsible.

adding a param "hl=en" (your language) in the URI query is what it takes, it has been this way for around two decades (iirc)

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#280

Post by 627467 »

adrianN wrote: post #263
627467 wrote: post #207

Earlier quoted context omitted.

I understand that CS doesn't draw much sympathies even before this happened - from myself included - and it is easy to pin point systemic issues to a single failure point and make it liable and financially responsible for all downstream failures. But this only creates excuses for all other responsible players in this systemic issue - or society at large. Just to pick 1 example: I keep reading comments on how profound…

In the end it's a matter of cost. Having two independent supply chains for anything as complex as healthcare infrastructure is essentially unaffordable.

Can't help but think that from this perspective buying a solution from a vendor is less about solving a problem and more about buying a blame-insurance in case something comes crashing down.
Post reply on HN