sneaky

I did something similar. Everybody is different so maybe not the best option for you, but who knows.

I have a single mini PC that handles my stack of virtual machines hosting various things. For the main OS I went with Fedora KDE. I chose something with a GUI for two reasons, the primary being that sometimes.. Maybe not as often as you get more familiar, but sometimes there is an easier way to accomplish something in the GUI than in the CLI. Things like system settings. You can save a lot of time looking up commands and syntax by flipping a switch in the settings application.

Second and most important reason for the GUI, I watch TV on this thing. Which I would not recommend if you are hosting anything that can't handle a little downtime. Once in a while a web browser may hang, bluetooth could fail, and you end up having to restart. Nothing I host is critical to anybody so this isn't a big deal to me. I also find a little inner peace knowing that I am interacting with the main system controlling these hosts on a daily basis. If it does get compromised in some way this makes it just a little more likely I will notice quickly.

So that's the hardware system and I'm running Libvirt as the hypervisor. It's pretty bare bones, but easy to use and gets the job done. Hardest step to me was generating SSH certificates/keys. Not that it was hard moreso just new to me. Libvirt will not allow you to connect remotely with plain text. So regardless of your threat model this is a required step if you want remote access to the hypervisor remotely.

If you make it that far you can start really getting into the weeds with networking. I'm not going to go into the topology of my network, but I will say if you are hosting anything public you should do as much as possible to isolate that from your home network. You can create a VM to act as a firewall/router for other VMs.

Teamspeak is self-hostable and has streaming.

Sometimes people ask others instead of googling things because it offers an opportunity to socialize. We all know google is an option. I get what you're saying, but it's sad to see this described as a burden.

Dude runs a tech youtube channel and acts like he knows everything about computers. But for some reason when he uses Linux we're supposed to treat him like grandma with her first ever laptop? Don't trust this guy on anything he puts videos out about. He's not tech savvy, dude is an actor. Found it really funny he encountered two issues with running PopOS but didn't bother explaining why or how he fixed either of them. If I had to guess, I'd say he called a crew member off camera.

Not typically what you'd think of when somebody says "mom's computer," but this is exactly what happens when my GPU overheats. Monitors stay on with black screen and no response from keyboard input.

This happens to me once in a while with Fedora KDE. Usually right after a kernel update and I can resolve by going back to the previous kernel for a few days. Always guessed it was the AMD GPU driver.

I came here to say this also. First bad update and then both would be broken and pretty stressful for your friend...

Pile in if I'm wrong, but I dual boot win11 and linux it works fine. The only condition is it has to be separate physical disk. I wasn't able to use the same hard drive with just partitions had to be completely different drives.

I tried, but could never find anything that would work as a VOIP subsititute. So now I have a pixel that does everyrhing except phone calls. Getting close to just giving up and slamming a sim in it because at least it's a little better than stock android.

I was over here thinking what if somebody didn't even know that was what she was doing or that they were supposed to say thank you. Now that poor person will be left wondering what even happened because her resolution (picking it up and putting it back) provides no opportunity to learn.

'Murica

Did you try dual boot with one drive? Windows will fuck that up.

In this specific instance, it sounds like education on how to safely communicate and interact with ICE, or at least best available practices, was shared to people who may not have otherwise gotten any info at all. That seems like something to me.