My understanding is risk is low on this one as we already have a prepared and tested vaccine, and we have a known medicative treatment.

So it’d suck if it spreads but we at least have the tools to fight it on hand.

All headlines for “X” need to just be soecufucally replaced with “Elon Musk”

At this point the two are synonymous.

We need to start phrasing it as:

“Elon musk’s platform…” now.

Lasse is the original maintainer of XZ, they have been placed back in their position as sole maintainer.

“Jia Tan” was the person who slipped the backdoor into XZ and is now banned.

Lasse has already fixed abd removed the backdoor.

XZ itself is critical software everyone uses (its one of the main compression/decompression programs used on linux)

but the best way to avoid getting them is still to just avoiding stupid shit.

This is fine and dandy on a personal pc, but in a work environment you are now being actively targeted by malicious actors if your company is a good target.

Constantly.

So once you are in that zone you do need some fast acting reactive tools that keep watch for viruses.

Nowadays it’s less of an issue with docker and whatnot.

Just set the image to refresh every night at midnight and if they tried to make manual changes it’ll just revert back to its original state at midnight.

Customers don’t really get direct access to deployed code now, it’s buried under like 4 layers of abstraction on most CDNs now.

Simply deploying to azure already smears multiple layers of access control and RBAC overtop that it’s hard enough for me, the dev, to answer the question if “what is actually deployed atm?”, let alone for the customer to get in their and meddle.

For casual users I typically recommend using Cinnamon Desktop, it’s the most Windows-esque UI and will be the easiest for them to pick up and use.

I roll with Cinnamon on Ubuntu and it’s been extremely painless, very simple to get stuff do and shit just works.

I feel like this is more “how we feel we get perceived by others” moreso.

I try and perceive all the members of my team as, well, my team. I heavily appreciate everyone busting their assess off and contributions.

However, there are folks on each layer that do actually treat others like this and I think we can all agree those people suuuuck.

In Canada the Cert and the Degree are separate.

You typically through getting your degree also become certified, but the key is while your degree lasts forever, the Cert has to be maintained and renewed.

Cert has a lifetime and expires and you have to keep it up to date.

In Alberta for example the regulatory authority is APEGA: https://alis.alberta.ca/occinfo/certifications-in-alberta/engineer/

I think even technically the license is also a separate piece of paperwork.

Degree: you completed school at some point

Cert: up to date on current practices, must be maintained, requires the degree

License: you are legally allowed to practice in the province/country and have registered. Requires degree+cert

What if they are actually a software engineer, with a cert? >_>;

I have worked with actual cert’d engineers on web projects, lol

This by a long shot, I agree.

What CLI tools do you find have install problems on Powershell?

Everything I’ve used can be installed “headless”, often using winget now.

But powershell just sucks and windows file system is cumbersome, so limux is still better.

So far any use case I’ve solved with just SSH.

What specifically do you need to rdp in for?

Man you’d think the US would’ve learned its lesson last time a small power hungry country kept trying to oppress and take over other neighboring regions, allowing its fascism to grow until it became more than just a localized threat…

Why does this mistake keep repeating? It’s almost like the US likes going to war… oh. Hm.

Last week, Ukraine said it was able to attack Russian soldiers after they attempted to shoot down a Ukrainian flag that was attached to helium balloons and flew into occupied territory.

Fish in a barrel I see.

My understanding is “immutable” is a bit of a misnomer and avoids the “point” of using these distros.

“Layered Distros” is a better terminology, where you can imagine the OS as multiple layers, and you can swap 1 layer out for another without modifying the others and still have a functional operational machine.

Now some of those layers have to be immutable ones at runtime for this concept to work, so thats where that part of the name comes from, but thats an implicit result from the actual point/use case of these distros, not the selling point.

So you can swap versions/releases of your OS very cleanly at boot, without modifying userland, and it will continue to function just the same. This lets you do stuff at the admin level like broadly releases a version update merely by having users just reboot their machines, and next time they boot up their machine will now be running on the new OS layer, with their local “user” layer being unchanged.