To be clear, I definitely agree that this is a bad idea.

However, one of the hardest things about making autonomous cars work is avoiding traffic and pedestrians. If air traffic control can be managed such that these avoid other aircraft (and things like buildings and cell towers, obviously) I could actually see this as easier to get the software working.

Unfortunately, I think you're unlikely to find anything besides the ones made by the big companies: Google, Apple, Samsung, and Garmin are the ones I know. They each have agreements with the banks and credit card companies to handle the secure exchange of data required for the touch payment system. In fact, there are still some issues resulting from a lack of cooperation (such as Citi Bank not working with Garmin Pay because they can't be bothered to set up the relationship). I imagine an open source software would be unable to get the banks to pay attention to them to establish a partnership, or would otherwise be declined because the financial institutions wouldn't trust them.

KMS requires phoning back to MS periodically to keep the license activated. It's still "permanent" because there's no limit on duration (as of now at least).

HWID activation registers a hardware ID in MS servers to permanently license it. That means no renewal, just forever activation that survives reinstalls.

DOCSIS (AKA internet service over coaxial cable) deals in some number of bonded channels, meaning portions of the total available bandwidth on the wire. They asymmetrically allocate channels to download speeds to overcome the limitations of the older copper wire technology. 100Mbps symmetrical is beyond what most of their existing "Broadband" infrastructure can support in rural and underserved areas, so they complained about it being unreasonable. 100Mbps symmetrical is certainly possible over DOCSIS, but speeds are only as fast as the weakest link... And there are a helluva lot of weak links outside of high population density areas.

This is the real blow. Truly the end of an era.

Creating a driver requires a deep understanding of some pretty low-level pieces of Linux. If you're new to Linux, you should probably start with some "new to Linux" tutorials and get an understanding of some basic command line usage. Work your way up to being able to follow a guide on compiling the Linux kernel (without any of your own modifications). After that, you can seek out guides on creating a driver.

As a second note, fingerprint drivers are categorically difficult to work with, so this would really be jumping in on the deepest of deep ends. You can do it! But it will take a LOT of self-education.

Fix is to address a critical CVE:

Specific handling of an attacker-controlled VP8 media stream could lead to a heap buffer overflow in the content process. We are aware of this issue being exploited in other products in the wild.

Microsoft’s blog adds caveats, such as that Excel avoids the conversion by saving the data as text, which means the data may not work for calculations later. There’s also a known issue where you can’t disable the conversions when running macros.

Bookmarking this. I have such high hopes for this! I recently went searching for my new git GUI, looking for something free, cross-platform, and simple. Basically what I found is the only one I like is GitKraken, which is not free (I have private projects, which GitKraken paywalls).

If this ends up anything like how these screenshots look, this will be my new client! Do you have a Patreon or other donation mechanism?

Permanent zero-cost activation that survives reinstalls

Yep, you can download their "Desktop Editors"

It is 100% the support. Corporations pay big money to have experts on call to fix things fast when they break, and there's basically no other player for that kind of model in the Linux space.

100% in the same boat. WSL and VSCode is basically a requirement for me, and codium can't do the WSL linking.

My strategy too. I have a piece of paper with my bitwarden credentials (password and OTP code) and a list of important items like bank accounts, utilities on autopay, etc.

I review it with my spouse every year and update anything out of date.

Now that you have a working setup, make a backup. Then, experiment with either starting over and only doing a few of the steps OR experiment with removing some of those parameters. Find your minimum set of working parameters this way, then you can look them up to find out more about what each parameter does that you discovered to be essential.

I can for sure tell you that passing the render device is required for hardware transcoding, but I'm not sure what else is required. The iommu and vfio parameters are related to passing the entire gpu device into a container, but I don't know anything about Proxmox so I can't comment on whether that would be required for your situation.

I really wish the WSL extension wasn't locked behind VS Code. My workflow is heavily reliant on it which locks me into the proprietary IDE.

My recollection is that Fail2Ban has some default settings, but is mostly reactionary in terms of blacklisting things that it observes trying to get in. Crowdsec behaves in a similar vein but, as the name implies, includes a lot of crowdsourced rules and preventative measures.

Arch on my home server, Zorin on my laptop

Just want to shout out to reviewbrah for giving us this absolute gem of a phrase

The commit added Ukrainian translations to the install instructions. Most were vanilla, but at the end of the file they added some statements with things like "Oh no, this is inappropriate for your sensitive religion". I'm not quoting exactly here, for obvious reasons.