It’s either woefully incomplete or behind a paywall so someone in the company has access to be you can’t figure out who and eventually just give up.

I’ve seen it a few times in passing and always assumed it was like, a tech demo or proof of concept.

I’ve had bad tinkering break my system before, but never had an update break it irreversibly. The closest would actually be on Silverblue itself, when an update to the kernel was using different signing keys that cause the system not to boot. Fortunately it was simple, I selected the previous deployment and I was in (on a non versioned OS I would have selected the previous kernel which most are configured to retain the last few). A quick Google revealed Ublue had a whole kerfuffle and after verifying it was legit, I enrolled the new certs into my MOK.

Although one time on Arch I had installed an experimental version of Gnome from one of their repos, and was pleasantly surprised when that version finally released and I removed the experiment repo and did an update absolutely nothing at all broke. Nothing.

This consternation is definitely common. It’s hard to apply skills to something with no long term impact of benefit. I’ve improved my skills by finding stuff I can help on in the communities I participate in.

It’s natural to be overwhelmed, so deciding on a project does scope what you can learn, but a hard part is architecting the foundation of that project.

Introducing new features to an existing project is a great way to get your feet wet - it has multiple benefits, for one of you do take a position as a developer in the future, you likely won’t be architecting anything initially, primarily improving on existing projects. So participating in OSS projects is a similar mechanism to that - you have to learn their codebase to a degree, you have to learn their style and requirements, etc.

Even if you don’t ultimately contribute, it’s still a learning experience.

LUKS, or anything that relies on the server encrypting, is highly vulnerable (see [email protected]’s response).

Your best bet would be encrypting client side before it arrives on the server using a solution like rclone, restic, borg, etc.

That’s what I thought at first, but the person who wrote the article is named Simon, and based on the context given in the article I’m assuming that was a test unit he had on his desk, but the planned implementation is in bathrooms.

Considering it only detects if someone in the bathroom is vaping and not who, disciplinary action just isn’t really possible with your typical school restroom.

Yup. Toyota Yaris '15 stock. Lowest trim they offer.

My car is a 2015 and didn’t come with a cruise control lol :(.

To be fair, I can drive at and maintain a consistent speed without it, though I didn’t have to often thanks to stop and go traffic 🎉.

Programming and self hosting the results when I was ~14 is what led me to a tech background. No university, but I’ve been working professionally in both IT and software for over a decade and self hosting even longer.

The article that user links is referring to GrapheneOS (and other OSS software) as not being “free software” - and they (GNU) delves into it more here.

Basically, GNU is saying software shouldn’t claim to be free and open source if they contain non free binaries / other non-free blobs.

The nuances between FOSS and OSS can be confusing. GrapheneOS is not claiming to be FOSS.

The new gamer’s nexus review outlines some pretty specific prerequisites that AMD sent to fix performance on Windows, and AMD didn’t communicate those until they’d had the review units for days.

Bookmarking Arkane. I’m a huge fan of Fedora Atomic but miss AUR.

Going by their comment history, Germany.

I mean, that’s how it should be. Just like getting drivers license requires you to demonstrate you can drive safely, so should a firearms license.

Due to the nature if those charts, they’re usually web based, not desktop native, and will probably have to be self hosted, even just locally. For example, Redmine supports Gantt charts and can be spun up fairly easily from its Docker image.

I’ve been told they’re a projection put in the sky by God to test our faith lol.

The command modifies the firewall to allow all incoming traffic on the docker0 network interface (which is created by Docker). It’s basically a bypass.

You can configure Docker to not try and manage it’s own rules, here is some discussion on the topic: https://github.com/moby/moby/issues/22054#issuecomment-2241481323

Or just skip it entirely, I use the Consent-O-Matic extension which has a surprising amount of features.

The post is describing the scripts to disable telemetry, OneDrive, ads, etc.