Just like the old proverb. "The best time to plant a tree is 20 years ago. The second best time is today."

I agree. But first, open it up to able-bodied women of age to serve too.

Absolutely *this*. I love the tinkering and granularity of my Gentoo system, all of which requires setting shit up through terminal. Doesn't mean I don't appreciate the convenience of a GUI for most things. And if Linux is ever truly going to break through into being a daily-driver for the average Joe, shit like familiar and easy-to-parse GUIs are going to be a requirement. it does NOT remove the ability to fall back to (or even lead with) shells and CLIs.

Unicomp sells a "New model M" keyboard using the old buckling spring switches, and comes in either USB or PS/2. it feels fantastic to use.
https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.pckeyboard.com%2Fpag...

As it should. Look up Israel's use of Lavender AI, a tool they used to profile and target suspected Hamas members for drone strikes. There was almost no human oversight, and the "acceptable losses" included entire households of civilians per target.

Username checks out

It should be "Half-life 2 *Episode* 3," not "Half-Life 3".

And what category do we portage users fall into? :)

Cite the law you are speaking of, please.

What do you *mean* "SOP won't help"?
Having an established method by which a Verizon employee is supposed to interact with law-enforcement won't help? So you expect all Verizon employees should just wing it when someone says they're a cop?

Well, what needs to happen here first, is we need to dig deeper into if they have an SOP for this. I would be very surprised if such a large telecom *didn't* have an SOP in place.
Deeper than that, we need to see what the Verizon employee who answered the phone did. Did they use their tools and KB articles to try and find out what they should do? Did they panic and just go with it for fear of reprisal from the (alleged) police? If the employee DIDN'T do the right thing, how well had Verizon trained them, or vetted them before hiring?
In the end, it's clear that *someone* fucked up, but without digging deep into that rabbit-hole, we don't know if it was an individual, several individuals, or Verizon as a whole.

Same. Ublock Origin on Firefox for Linux, no ads, no messages, no delays. But I'm ALSO using adGuard DNS servers as well.

I agree on that, but I think that's the whole crux of what they were getting at... They were asking if it would even be *possible* to reinstall them once valve has deprecated support, since TFS mentions valve will be removing 32-bit only mac games from their compatibility list. If that is the case, it *absolutely* is something that you can't reinstall.

However, I use Linux as my daily driver, including playing games on steam, so I can put my experience here.

I use valve's official steam client for my OS. No workarounds, no VMs, nothing containerized. For those who don't know, the steam store marks OSes that games are compatible with by an icon next to the games price. Windows has their icon, Mac has theirs, and Linux titles have a steam icon next to them. As a Linux user, I can purchase windows-only games from the store using the Linux client with no issues.

Now, here's where things get a little bit sticky; If a game has confirmed Linux support out-of-the-box by the devs, steam will simply allow you to install it and run it. If it lacks that confirmation, steam has an option to "enable support for other titles" in the settings. This will let steam try to use it's built-in compatibility tools to try and run the windows game. For me, it has almost always worked perfectly, with very minimal tinkering. Most games that have issues either use their own launcher with ancient code (ffxiv), or have very finicky anti-cheat that is either too old or outright refuses to allow the compatibility tools to work (destiny 2).

So steam already has the infrastructure all there to buy/install games from unsupported OSes already there (in Linux). The question should be "Is valve going to extend that option to the mac client?". Not any compatibility bits to make the 32-bit work, mind you, simply the option to just"allow the 32-bit users to try and figure it out".
    The most reasonable option here, imo, is that even though valve is removing the 32-bit only mac games from the "mac compatible" list, they should still allow mac users to *attempt* to install and run them. Hell, make separate Mac flags even: List the old games as Mac-32 only, and leave the rest as Mac/Mac-64.
This would save the folks running their old hardware some headache, and also warn anyone on a 64-bit mac that a 32-bit only game won't work for them. It also has the least maintenance burden from valve, aside from outright being completely hands-off and just letting them go dark.

This is sort of a precedent for this sort of thing. Linux is slowly moving towards 64-bit as well; Hell, steam is the ONLY thing on my system that needs 32-bit support.
When windows finally gives up 32-bit support (and that is ABSOLUTELY a *when*, not an *if*), then it will be the same discussion all over again.

Right up there with Germany burning "biofuel" (wood pellets) for credits.

Another issue is supply/demand. You cannot feasibly just "spin down" a reactor for a little bit if you are overproducing. Sure, battery banks and the like can help buffer that, but the issue is still there when that buffer fills up.