I'm a pretty big fan of crusader kings and I think 3 is a fantastic fantastic sequel, only missing some of the depth from all the DLC of 2, especially with the more fantastic/myth stuff, which isn't even a huge draw- I am really curious what makes you want 2 remastered instead of just playing 3?

I've used alacritty for ages, its lack of ui is appealing on a tiling wm and it is as performant as i need it to be

specifically he had to absolutely bomb a stand up routine. I forget if Ally wrote it for him or if they just made him write bad jokes but it was NOT as good as Grant's usual writing

You prefer gcp to aws? I've only worked with public cloud a little bit but AWS has felt far ahead of its competition.

Clunky, but featureful.

You're never too old to start learning that stuff.

For networking, there's a ton of resources on selfhosting and homelabbing, and big communities here on lemmy and elsewhere. It can be as expensive a hobby as you want, you can stretch an old laptop pretty far, get really cheap stuff from the cloud, or build a data closet in your house/apartment.

If you wanted to learn more about software, Rust has a ton of high quality official documentation available and would be really valuable knowledge for a career.

For the raw hardware tinkering getting the $30 essentials set from ifixit will get you into 90% of consumer devices, and even as a professional I'm usually watching a 5 minute youtube video before dissassembling anything, and that's really all you need.

Money would trickle down if workers ensured that key markets like housing and healthcare were competitive, and not systems that take whatever wage increase they can get.

is my read of it

I ran savages for over a year before burning out, all on Linux, never banned. YMMV

I've been diagramming/documenting my network at work using draw.io, it is a little clunky but it works well for me, has good features and preloaded art for different types of devices.

I usually haven't, but I installed Clam about a month ago on my desktop, ran a full and complete scan, then left it running scheduled scans. Hasn't found anything, and I get a lot of software from outside of my package manager, and use wine for a lot of it, so I'd say my risk/exposure is higher than most.

I think it's fine to go without AV on a linux desktop, but I like the peace of mind. There will definitely be more things targeting linux sytems as/if more market share is acquired, but in terms of security it's more important that you harden the system than run an AV.

Hot news, linux is incredibly compatible with printers. CUPS is very well designed. With relatively little technical knowledge you could probably plug a raspberry pi into virtually any old printer and get it running with the Pi as a print server sharing it with the network.

aka i don't either and i need help at my new job 🥲

A virtual local area network, or vlan, is a logically defined subset of a computer network that are used to control, from an administrator/system level, which computers are 'connected' to others. There can be an unbroken, physical connection between two devices, but they won't be able to communicate because network hardware is stepping in and segregating the network.

This is good because it can increase security- rather than having your sensitive information on your company network with a password, which can be cracked or stolen, being the only thing controlling access to it, with a vlan you can limit access to even attempt to use a password to only the parts of your network that actually require it. It also controls traffic and congestion on the network, because some data is 'broadcast', effectively addressed "to whom it may concern,". A vlan places a wall around parts of the network that keeps these broadcasts inside, i.e. splits broadcast domains. Ordinarily, this would require different hardware and physical design, which can increase cost and complexity.

But on the other hand, the physical network structure encouraged by this design is very flat, with all devices physically connected to each other. It is only inside configuration on the network hardware that things are broken up and divided, which means if whoever set it up didn't document it, you are required to not only figure out where all the cables go, but also how the network systems are controlling the data. It's also another "thing" that can break. If there were physical segmentation, you could follow a cable and see where its gone wrong, and if something were plugged into the wrong port, it would be plugged into the wrong device entirely, and you would just move the connection to the correct device. With a vlan, you'll have a switch with dozens of ports, each having its own independent configuration defined on a table, which means it can be plugged into the correct device, but the wrong individual port out of dozens. The configuration could also become corrupt, or be broken by an accidental change or hardware failure, and you would now need to rebuild the table, going through each individual port and configuring which vlan was supposed to be on it.