maengooen

I did a bit of research and came to a similar "they will pay for themselves" so I got a higher end (afaik) device called a Mighty. It is fantastic, still going strong years later. Heats up quickly, smooth pulls from it, battery life has gone down a little but still plenty to not be deskbound.

This is what the nice command is for

Am I the only one who crashes every other cutscene and every 30 minutes of gameplay?

just want to add, I personally thought heavensward was just alright, stormbringer was a step backwards, but Holy Hell Shadowbringers and Endwalker stand out as some of the best gaming experiences I've ever had.

Find a group and play with them, having a 4 man party through the whole game is what kept me going. The free trial lets you touch the first extreme trials which are some pretty good content in my opinion.

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

In my experience aur packages are solid as long as they are maintained, but experience far more maintenance churn. I've used things for months and then they stop getting updates, and then when they stop working you'll often have an easier time looking at the AUR comments and finding a fix than going to the github or whatever.

I definitely prefer main repos where possible, even if it forces me to choose different packages. I would like to use vmware, but virtualbox has a package in normal repos so I use it instead.

I wouldn't use AUR without a wrapper for it- I use yay but there's many alternatives and yay may not be the best, it's just what I settled into.

It's going to be a lot more work (based on my experience) to keep things working the more aur stuff you use.

Granted I also find that even main repos break than I'd like them to. Notably had issues with lmms and some library needing to be downgraded to keep working. But if you really want stability without personal effort, arch isn't the correct choice in the first place.

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.

i3 counts, right? I have always been a keyboard oriented user and a big part of what drove me from Windows is them breaking or changing the hotkeys I used regularly. To me it is the perfect "you have control, this is your device, it works and looks how you want." wm

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.