Well you can see reports of people drag stripping teslas, and comparing speeds at 100 vs 90 vs 50% charge. Whatever the reason, you do slow down.

For a top speed run, cornering ability is next to useless. You need grip to put down the power and be stable at speed, the corners taken for top speed runs are fairly wide. The bigger issue here is for how long can a BEV sustain max power output - it can deplete its battery in 2 minutes. EVs also can only produce top power whilst battery is at top voltage, since draining it drops voltage, max power drops with charge levels. The tyre grip itself is fine, the issue is tyre durability - they can usually last less than 20 minutes at top speed.

It is an impressive feat of engineering to get to a vmax record in a BEV.

That may not be a perfect answer. One issue with fire suppression systems and spinning rust drives is that the pressure change etc. from the system can also ‘suppress’ the glass platters in drives as well.

I've been self-hosting my email for over 10 years now (I'm going to link a bunch of my old comments on old email HN threads). I have fallen back to using Amazon's SES to send because all of Digital Ocean's IP blocks suddenly got marked as bad and I don't have enough volume to improve a new IP reputation - https://news.ycombinator.com/item?id=39891262, https://news.ycombinator.com/item?id=38471262

I use Gmail as a free spam harvester to train my own spam filter - https://news.ycombinator.com/item?id=38843288.

But as others here have suggested greylisting is extremely helpful in this space as legitimate servers should always retry. Well only my power company is the exception and they will fall back to sending paper bills, but even Gmail falls foul for them. It's also one big reason I'm not worried about up to a week downtime. But I have two email servers, a receiving and a storage server, the receiving is cattle and I car re-deploy in minutes if needed. - https://news.ycombinator.com/item?id=38512732

On greylisting I would say using https://github.com/stevejenkins/postwhite (even if it's very old and not actively maintained) has proven very important for the annoying 2FA emails, I strongly contend that email isn't suitable for this use case but that's another conversation)

Because you can? It looks like a great project for getting started with nontrivial FPGA design.

Programming-wise I'd say full FPGA is less useful than QMK. Doing a direct 1:1 mapping from key inputs to USB HID report isn't too bad to do in an FPGA, but dynamic behavior like macros, layers, leader keys, mod tap, auto shift, and so on are significantly easier to implement in a regular programming language. If you want flexibility you're basically forced to have your FPGA run a soft core, so at that point why not go for a regular MCU?

In theory you could make an argument for lower latency, but that doesn't really apply when you're limited by USB 2's 1000Hz polling rate while some off-the-shelf MCU-based keyboards use USB 3 for 8000Hz polling.

IIRC, many TPMS systems run as CAN over IP, basically giving unsecured network access to a car if it thinks it's talking to a TPMS. Granted that some/most these sensors typically have to be "paired" with a car using a scantool (sometimes), but IIRC, some are self-pairing creating a vulnerability where the legit sensor could be replaced with a hostile one. Also the possibilities of spoofing, sniffing, and/or packet injection seem real too.

For our build servers for devs we utilize roughly this setup as a ram disk. It's amazing. Build times are lighting fast (compared to HDD/SSD)

The fact that this is even brought up as a solution really speaks to how bad Windows is.

https://www.microsoft.com/en-us/evalcenter/evaluate-windows-...

> after you install Windows 11 IoT Enterprise LTSC Evaluation, you won't be able to use the recovery partition on your PC to go back to your previous version of Windows.

Yikes.

let's all agree sending incremental data to something that settings were changed, without any error, is a bug