

It’s worth noting that this is a new line of ThinkPad, there’s a bunch of existing lines that will all keep the classic look. Though I feel like the name X9 isn’t great, but whatever.
It’s worth noting that this is a new line of ThinkPad, there’s a bunch of existing lines that will all keep the classic look. Though I feel like the name X9 isn’t great, but whatever.
A DE has little to do with this, it’s a driver, it gets loaded when you plug in a compatible device, there’s no interaction. This should have been disabled 2 years ago when the gaping security holes were found, and actually Greg had attempted to have it disabled in 2022 but it kept getting pushed back.
The issue isn’t just a simple oversight. Git includes the file name as part of the tree and commit hash. The hash has security implications. There’s really no way to make the hash support case insensitivity without opening up a multitude of holes there. So there will always be a mismatch, and you can’t just fix it without changing how git works from the ground up.
We did it, reddit NYPD!
Oh yeah, it was Tuesday yesterday.
Podman not because of security but because of quadlets (systemd integration). Makes setting up and managing container services a breeze.
So much more. It’s not even in the same ballpark.
Information for Internet Archive.
MBFC: Left-Center
That’s just embarrassing.
You should probably use a double slash in that non-equality sign as a single slash will be seen as an escape character by some parsers and then not rendered. In my client it just shows two equal signs, i.e. the opposite of what you wanted to convey.
What’s up with the abuse of the word open lately. I had a look at that project to see how they were doing the conversion, but I couldn’t find it. But I found this:
Short answer, yes! OpenScanCloud (OSC) is and will stay closed source…
Your data will be transferred through Dropbox and stored/processed on my local servers. I will use those image sets and resulting 3d models for further research, but none of your data will be published without your explicit consent!
I feel like I’d rather use Autodesk at that point. At least I know what I’m dealing with right out of the gate.
But check that it has all the features you need because it lags behind gitea in some aspects (like ci).
I mean I learned it in a few days and found it very intuitive as well. Far more intuitive than I found fusion when I tried that years later. Inventor and onshape also feel more pleasant to use.
The issue seems to be that the fusion interface is very non-standard when compared to other cad suites, so people that get used to it first find everything else unintuitive.
I remember watching golden boy on there, it was great.
Podman quadlets have been a blessing. They basically let you manage containers as if they were simple services. You just plop a container unit file in /etc/containers/systemd/
, daemon-reload and presto, you’ve got a service that other containers or services can depend on.
I’ve been in love with the concept of ansible since I discovered it almost a decade ago, but I still hate how verbose it is, and how cumbersome the yaml based DSL is. You can have a role that basically does the job of 3 lines of bash and it’ll need 3 yaml files in 4 directories.
About 3 years ago I wrote a big ansible playbook that would fully configure my home server, desktop and laptop from a minimal arch install. Then I used said playbook for my laptop and server.
I just got a new laptop and went to look at the playbook but realised it probably needs to be updated in a few places. I got feelings of dread thinking about reading all that yaml and updating it.
So instead I’m just gonna rewrite everything in simple python with a few helper functions. The few roles I rewrote are already so much cleaner and shorter. Should be way faster and more user friendly and maintainable.
I’ll keep ansible for actual deployments.
Someone found a way to weaponise bikeshedding.
All public companies are, it’s just what Boeing makes things that fall out of the sky if they mess up, so it’s more obvious.
Just have NAS A send a rocket with the data to NAS B.
By having the stupid idea of existing next to Russia (or a similar country).
As they point out at the end, this wasn’t about the old control panel, but the new settings panel. It’s all brand new code.