Honestly, not even mad. Sucks for the victims, but we need hackers poking holes in kernel anticheats. Show the game companies that kernel anticheat is a waste of effort and maybe this horrific plague of gaming will die off.

If Bungie is behind it I have zero interest without even knowing what it is. Destiny 2 was an OK game, but its god awful anticheat bans Linux users. That is a sure-fire way to make me pretend your game doesn't exist. Client side anticheat is a plague. Do it properly on the server side.

Until any competing store releases a Linux client, I can't really argue against Steam. They are a gatekeeper and almost a monopoly, but they're also the most benevolent and pro-consumer gatekeeper that we have in the PC gaming distribution space. As long as all the competition continue to be Windows-only and, in some cases, actively work against Linux users, I don't want Valve's digital fiefdom to fall.

I've been experimenting with both of these and recently wrote up a guide for installing FEX on postmarketOS (as I am testing it on my phone and tablet) but the steps should work for Pi as well.

https://wiki.postmarketos.org/wiki/Steam

I also just made a video tutorial/demo on YouTube. I ran Half Life 2 and Tomb Raider (2013). I'm not sure how capable the Pi 4 GPU is in comparison to the Adreno GPUs I tested.

https://youtube.com/watch?v=EuOX2L_yNqI

Box86/64 and FEX can both run Steam on ARM. Lighter games should be playable on RPi4 and 5.

APIs can be complex too. Look at how much stuff the Win32 API provides from all the kernel calls, defined data structures/types, libraries, etc. I would venture a guess that if you documented the Win32 API including all the needed system libraries to make something like Wine, it would also be 850 pages long. The fact remains that a documented prototype for a software implementation is free to reimplement but a documented prototype for a hardware implementation requires a license. This makes no sense from a fairness perspective. I'm fine with ARM not giving away their fully developed IP cores which are actual implementations of the ARM instruction set, but locking third parties from making their own compatible designs without a license is horribly anticompetitive. I wish standards organizations still had power. Letting corporations own de-facto "standards" is awful for everyone.

In the mobile Linux scene, Qualcomm chips are some of the best supported ones. I don't love everything Qualcomm does, but the Snapdragon 845 makes for a great Linux phone and has open source drivers for most of the stack (little thanks to Qualcomm themselves).

RISC V is just an open standard set of instructions and their encodings. It is not expected nor required for implementations of RISC V to be open sourced, but if they do make a RISC V chip they don't have to pay anyone to have that privilege and the chip will be compatible with other RISC V chips because it is an open and standardized instruction set. That's the point. Qualcomm pays ARM to make their own chip designs that implement the ARM instruction set, they aren't paying for off the shelf ARM designs like most ARM chip companies do.

Hopefully Qualcomm takes the hint and takes this opportunity to develop a high performance RISC V core. Don't just give the extortionists more money, break free and use an open standard. Instruction sets shouldn't even require licensing to begin with if APIs aren't copyrightable. Why is it OK to make your own implentation of any software API (see Oracle vs. Google on the Java API, Wine implementing the Windows API, etc) but not OK to do the same thing with an instruction set (which is just a hardware API). Why is writing an ARM or x86 emulator fine but not making your own chip? Why are FPGA emulator systems legal if instruction sets are protected? It makes no sense.

The other acceptable outcome here is a Qualcomm vs. ARM lawsuit that sets a precedence that instruction sets are not protected. If they want to copyright their own cores and sell the core design fine, but Qualcomm is making their own in house designs here.

It's just a matter of flashing the CorsairLightingProtocol firmware (instructions on the project's GitHub page) and then soldering the data pin of your LED strip to the appropriate Arduino pin. You can provide 5V power to the LEDs from a Molex or SATA power cable which allows as much power as your PSU can handle. You can draw 5V from the Arduino directly to run the LEDs but I would only run 30 LEDs or fewer with this power source. If you want more LEDs then connect them straight to your PSU.

Corsair Lighting Node is another good option. The real Corsair one works well but if you're willing to DIY you can use CorsairLightingProtocol on an Arduino Pro Micro and have 2 channels of ARGB with direct mode support for like $6, and you can use multiple. I have one in my case for case lighting as I used up my motherboard headers on fans and I used this as the controller for my OpenRGB desk fan project as well.

Except the one platform that actually matters, Linux. My girlfriend got me into this game and it's the only game I have to keep a Windows installation around for. It doesn't run on the Steam Deck, so it's the only multiplayer game I play where I would even contemplate having to play it on Switch. I hate Epic Games.

The name Unity just needs to be avoided. I get the well intentioned meaning behind the word, but it has been the name of three major controversial/disastrous products in semi-recent history - Ubuntu Unity Desktop, Assassin's Creed: Unity, and the Unity Engine.

Leave it on, but turn off the monitor. I have it set up as a GitLab runner for some projects and also want to be able to SSH/SFTP in to access files, run updates, etc.

If it doesn't have an official control app then we most likely cannot add it. Usually button-controlled RGB means that the device just uses the USB cable for power, not data, so there is no control protocol we can send to the device to control it. We use the official applications to reverse engineer the control commands.

I'm guessing the packet we send for this device is either supposed to contain the custom mouse settings or puts it into a mode where it overrides not just the RGB but the other settings as well. I'm not personally familiar with this mouse or the controller it uses so I'm not really sure. Did you have your buttons customized from their defaults in iCue or another program that remaps the buttons?

Mozilla sold out a long time ago, they are nothing like they used to be. Everyone should be ditching Firefox for forks if possible. Yes, Firefox is still miles ahead of anything Chromium-based but we can't trust Mozilla to not screw over their users anymore (and it's been apparent for YEARS...Pocket, "Sponsored" shortcuts and links, Mozilla VPN popup ads, this behavior is hardly new). What can we trust? Firefox forks with the bullshit stripped out, mostly. I've been using LibreWolf for several years on my Linux, Windows, and MacOS systems now. I originally switched because of the Mozilla VPN popups but at the time, complaining about those popups was met with a bunch of Mozilla apologists going "it's not that bad" "they're a big company and they need their precious monies"...no. That was ADVERTISING front and center, and it was in Firefox years ago. So was Pocket. So was having Amazon links auto-filled on the new tab shortcuts. Go to something that isn't run by money. Go to a community-maintained and sanitized fork.

I've been pretty happy overall with my Arc A770. For the price, it performs well, and driver issues are mostly a thing of the past. My only complaint is that the anv Mesa driver doesn't implement VK_NV_device_generated_commands which appears to be a requirement for some D3D12 games on Linux (Starfield being the one I had issues with). Luckily, it looks like there is a new non-NVIDIA specific extension to solve that and an open MR in the Mesa GitLab to add it to anv.

I recently printed the Fractal Design North Pi case which turned out quite nicely.

If you read the article, it is indeed full Linux because the 4004 is running a MIPS emulator that provides the necessary memory management features. Pretty much all of the "run Linux on some old chip incapable of running Linux" projects achieve it via emulating a more featured architecture that Linux supports, not by somehow compiling Linux to natively run on a 4 bit, MMU-less architecture.