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.

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.

Yep, you can download their "Desktop Editors"

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.

Maybe apps will finally feel free to bundle LAME instead of forcing you to download it externally!

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

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

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.

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.

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.

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.

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?