I suspect the bandwidth and storage costs are considerably higher than your average instance as well.

Was it explained? There was a comment that Klingons don't like to talk about it but no explanation I remember.

My personal head canon was something went wrong during the DISCO timeline and somehow the process that gave us Tyler ends up infecting the rest of the Klingons who spend the next 50 or so years as swarthy humans before eventually being restored by scientists to the TNG/TOS films ridges we all know and love.

When it comes to export controls and sanctioned entities it doesn't really matter what Red Hat would like to do - they have to comply with the law in the jurisdictions they work in. Even if it was purely a community project individual contributors face a similar liability if based in those jurisdictions.

When it comes to sanction lists there is a fair amount of commonalty between the US and Europe. This is really something to complain to government about.

If you have ever read the "thought" process on some of the reasoning models you can catch them going into loops of circular reasoning just slowly burning tokens. I'm not even sure this isn't by design.

What ever happend to the classic "reticulating splines"?

Because OpenVPN is fiddly to set up and modern Wireguard setups seem to scale well enough.

In my first interview they put me in a room with a PC with Borland C and a copy of K&R and a sheet with a simple problem to solve and some extra enhancements if I had time. They said they would be back in half an hour and left me to it. That I passed fine.

Some twenty-ish years later I was asked to write a C function to reverse a string on a white board and I failed because I'd misformatted the for loop. I don't think it was because I've become a worse C coder in the intervening years.

When I'm actually coding I'm sat with my editor configured Just So with completion, compilation and unit tests at my finger tips. My favourite coding music blasting my speakers and a handy browser window for looking up anything in unsure of. This is my most productive setting and expecting the same performance in a stressful interview setting is foolish in my opinion.

Working through problems on a white board can work well but you are looking for the problem solving approach, not an encyclopedic knowledge of regex syntax. Those same problems get immeasurably harder when explained over a phone call.

My personal preference when evaluating candidates ability to code is reading their actual production code, the break down of commits, the commit messages and the sort of unit tests they add with a feature. The interview is more focused on their soft skills, what about the work excites them and what they are looking to get out of the role.

The kernel on GitHub is just a mirror - the primary source is on kernel.org

I just want to buy home automation gadgets that don't need a bloody cloud account to work.

I think car automation peaked at adaptive cruise control. It's a simple tractable problem that's generally well confined and improves the drivers ability to concentrate on other road risks.

Don't be too hard on Collin. Looking back on the threads it's fairly clear he's been the victim of a social engineering attack on an overworked maintainer. People were pressuring him to hand over maintainership while expressing disappointment at the slow pace of development. The off-list contact by Jia must have seemed like a helpful enthusiastic solution to a burnt out developer.

It's looking more like a long game to compromise an upstream.