Sure, but go to any English conservative Christian community and you'll see similar posts, but we don't get big fearmongering posts about that. We don't get big write-ups about /r/conservative posters celebrating the ICE murders and how their beliefs are incompatible with Western liberal democracy, even though they are exactly as incompatible. We're literally living with the consequences of those beliefs right now, while people are still writing hyperventilating posts about theoretical consequences of similar beliefs.

All I'm saying is, selective reporting is misinforming, especially when there's more pressing matters. People have a bias against Muslims and hold them to standards that our own religious groups don't even meet. I'm not arguing that they don't hold bad beliefs, they absolutely do. I'm saying we need to deal with the same beliefs that already exist at home before we start worrying about that. Or at the very least, start painting with a broader brush and include all of it, not just the easy to pick on groups.

But it's not misinformation to say that's what you say or that it concerns you if it is actually true.

I'll contest this. You can misinform people using only the truth. Information can be entirely true and still lead to you being misinformed without necessary context.

I don't doubt there are people celebrating murder in Arabic. My problem is that I see people celebrating murder in English every time I open Twitter, but nobody writes that article about English-speaking comments. Selective reporting can misinform people by providing a biased and limited set of information that is otherwise completely factual and true.

Everybody sitting here pretending otherwise leads me to believe that the point was to misinform, but this misinformation confirms many people's biases so they're fine with it.

You're not actually engaging with the point, but I suspect further messages wouldn't change that.

Really? We are setting consecutive year over year records for temperature, wildfires, storms, and fossil fuel usage. That's what "working" looks like to you?

What's your proposal, then?

Desktop Linux and Linux gaming largely exists on the back of hobbyists. DXVK was created by a hobbyist who wanted to play Nier Automata and just got officially hired by Valve later. Many of the projects that now make up Proton and SteamOS started the same way. Valve is effectively the only major corporation backing it, and they're going out of their way to elevate community-driven projects.

I would say there's solid benefits to breaking out your networking into at least 4 VLANs: IoT, guest, main, and infrastructure. IoT is obvious, these devices are security nightmares, but sometimes you have no alternative so you throw them into a network black hole. Guest for guests that you don't want touching your stuff but keep asking for wifi. Main is for everybody else, this is your "real" network. Infrastructure for servers and network equipment.

The reason you break infrastructure off into its own VLAN is that modern firewalls are stateful and you can allow the main VLAN to initiate connections to the infrastructure VLAN but not the other way around, so if your server or IoT stuff gets infected it can't become an attack vector for all your other devices. You allow Main to access Infrastructure, but not vise versa.

I take mine further and add two more VLANs, services and admin access. I split infrastructure (networking, proxmox hosts, etc) and services (proxmox VMs, NAS, etc) and then only allow admin access to the former, which is exclusive to my PC and phone. Some might call this excessive, but it helps me sleep a little better at night.

If genocide isn't that line for you, then what is?

The people who “stood up” to genocide allowed the ones who genocide MORE into power.

Is there any point at which you think we should draw the line in supporting our own party, even if the other party is still worse?

I'll go further and just say they shouldn't use Arch at all. The "stop being a gatekeeper, I shouldn't need the terminal" to "everything just suddenly broke itself after an update" pipeline is so real.

I straight up just think these tools that simplify the install process or package management shouldn't exist. The difficulty in Arch was never in the install processes. Anybody who can follow the instructions on a box of mac and cheese can eventually stumble through the process to install Arch and use pacman. The challenge was not digging your own grave post-install to the point that you need to wipe and start fresh, an experience basically every Arch user goes through at least once. The problem is that the further you abstract these tools and divest the user from hands-on experience, the less they understand about why it broke.

Basically, these tools don't make the hard parts easier, they make the easy parts easier in a way that leaves new users less equipped to understand the hard parts.

They have a zero tolerance policy and direct it at the small fish instead of the actual problem, which is governments using it to kill people, companies investing billions into speculation, and nobody stopping them or making them pay for copyright infringement.

What exactly would you like me, specifically, to do about that? I'm open to all suggestions.

It gets logged in the event viewer, yeah. That's how I discovered it, on account of the screens not waking up in time to show the actual bluescreen. The users were only reporting that their computers were deleting all their windows when waking up. From their perspective, all they saw was their computer taking a mildly longer time to wake up from deep sleep and then losing their entire session, but what it was actually doing was hard rebooting.

Headless is fine, the bug was specifically triggered when a computer woke up and detected a monitor exists, but the monitor took some unspecified amount of time too long to wake up. It was also fixed at some point, I'm not sure when, but it went on long enough that we swapped dozens of cables because it specifically only happened on the ones using DisplayPort, not HDMI.