Not everyone has a github account and can comment or vote there.
But, agree. Don't think any good will come from making votes public. Any pro/con should be measured against who it benefits. If it's mods or devs, there are always alternatives
If it's end-users, consider the edge-cases and the repercussions of malicious actors having access to those individual preferences.
Runs the margarita blender in the cockpit.
Times like this, I really miss George Carlin.
The thing that is most amazing about the immunity ruling is that it a) hands the executive a giant mallet with which to smash whatever it wants (as long as it's called 'official' aka 'national security') but for the few times that it may get challenged, reserves the right to decide whether it was official or not to the same gang that handed over the mallet.
That gives them the right to declare anything they don't like by a president they don't favor as 'non-official' and whatever a president they like does as 'cool.' And good luck challenging something when you can't even take a look at the 'evidence.'
It's an elaborate construct designed to divert water in exactly one direction and not another, at least for the lifetime of this Chief Justice.
It's not just cars. Anything with electronics (appliances, smarthome devices, healthcare, transportation) that is designed to last more than three years will hit a wall.
The host devices are designed to last 10-15 years, but the electronics will be out-of-date in 3-5 years.
The processor manufacturer will have moved on to new tech and will stop making spare parts. The firmware will only get updated if something really bad happens. Most likely, it'll get abandoned. And some time soon, the software toolchain and libraries will not be available anymore. Let's not think of the devs who will have moved on. Anyone want to make a career fixing up 10-yo software stack? Where's the profit in that for the manufacturer?
So as an end-user, you're stuck with devices that can not be updated and there's still at least 10-20 years of life left on them. Best of luck.
Solution: go analog. Pay extra if you have to. They'll last longer and the ROI and privacy can't be beat.
Many years ago, folks figured out how to crack firmware and find embedded keys. Since then, there have been many technological advances, like secure enclaves, private/public key workflows, attestation systems, etc. to avoid this exact thing.
Hopefully, the Rabbit folks spec'd a hardware TPM or secure-enclave as part of their design, otherwise no amount of firmware updating or key rotation will help.
There's a well-established industry of Android crackers and this sort of beating will keep happening until morale improves.
I was running between work and meeting friends for drinks last week. Lost track of time and it got past 10pm. On the way home, saw a Burger King drive-in. Haven't had fast food in years (we eat at home a lot). What the hell.
Two discoveries:
For that kind of money, you can do much better. Lesson learned.
Anyone tempted to write a custom database should ask if they're prepared to be in the database maintenance business.
Because that's where they're heading, for a really long time.
"Donald Trump would be on track to win a historic landslide in November — if so many US voters didn’t find him personally repugnant."
That if is doing a lot of heavy lifting.
Ugh. If you're going to go low, workshop the name-calling. Go with alliteration or rhyming. And nothing too fancy, like Destitute Don.
At least make it flow a bit, like Broke Donny.
Or go sing-songy, like: Donny Chapter 11, Don-o Busto, or Donny The Cheat.
But if you really want to get under his skin, you can't go wrong with: Dirt-Poor Donny.
Repeat 1000 times.
Got a ride in one coming back from a school event. The Mom driving it was so apologetic about having one. Musk is burning down a lot of goodwill with his customers.