I remember this day because I worked in a company that made software for train networks.
It did briefly made the news but not for long due to the terror attacks and also there wasn’t any passenger on this train, it was a train testing.
In fact the story is even more tragic when you know that the day before, they also were too fast in the same turn and in the records you hear something like « few, that was close, better take care next time ».
However, for sure this crash should have never happened but it only happened because they were testing the limits of both the train and the track.
It’s literally like a test pilot crashing an airplane while testing all the limits : it should never happen but they are still there for it not to happen in commercial flights.
> However, for sure this crash should have never happened but it only happened because they were testing the limits of both the train and the track.
No. It happened because they were under-prepared and disorganized, and thereby didn't respect the speed restrictions for the segment of track they were on.
They crashed entering a 175 km/h segment at 265 km/h, which is well above the 10% overspeed they were theoretically testing that day.
That's not macos fault in this case, it's just that Logitech mouses (MX Master at least) doesn't act well at all without driver. Like, for scrolling, it's like the mouse is sending raw smooth scrolling each time you just touch the wheel and without the driver that presumably fake it on the computer side, there is no synchronisation between your actual scroll and the steps you physically feel in the wheel.
I work in a company where I have two okta accounts (because hey, why not) on two .okta.com subdomains.
Bitwarden _randomly_ messes up the two subdomains and most of the times (but not always, which seems strange actually), it fills the form with the wrong password. I don’t know why. I know that there is an option to make it stricter on domain matching but you can’t configure it on per item basis, only for the whole vault.
Every browser-based bitwarden client I have used have the option to choose the autofill option on single items as well as the global default. Find the login item, click edit, scroll to autofill options, where each URI is listed with a gear icon next to it. Click the gear and select the appropriate match type.
For the absolute majority of use cases, "host" should be the default, but i have found uses for both "base domain" and "regular expression" in some special cases.
Normal browser extension Bitwarden Ctrl-Shift-L autofill defaults to the most recently used entry when there are multiple matches, afaik.
You can indeed configure it on a per-item basis. The vault-wide setting you found is just the default for ones that don’t have an override set. Click on the domain/url matching setting in the individual credential and you can change it to exact host match.
Yep. Unless you have really good eyes, XFCE is unusable on a 4K screen. On the same screen, KDE at 150-175% is glorious at providing both more real estate than 1920x1080 while being crispy.
It did briefly made the news but not for long due to the terror attacks and also there wasn’t any passenger on this train, it was a train testing.
In fact the story is even more tragic when you know that the day before, they also were too fast in the same turn and in the records you hear something like « few, that was close, better take care next time ».
However, for sure this crash should have never happened but it only happened because they were testing the limits of both the train and the track.
It’s literally like a test pilot crashing an airplane while testing all the limits : it should never happen but they are still there for it not to happen in commercial flights.
reply