The “Brick through a widow” bug has been an active exploit since the Model T.

Enabling the PIN mitigates this issue entirely. Can’t drive it away if you don’t know the PIN, even if you have the physical key, fob, or phone.

This ad is literally the perfect opposite of their famous Think different ad:

We have an actual gigantic, unfeeling machine, literally crushing an effigy of the sum total of human creativity, only to proudly declare that everyone now needs to do all those things in the same, apple-approved way.

And the real irony is that’s the actual message they’re trying to get across.

Lemmy’s bigger than ever, and that’s a direct consequence of reddit’s enshittification, so there’s that at least.

It doesn’t pay well, but “park ranger” is exactly that.

Fuck. That’s exactly it.

nothing, it’s an open standard now: SAE J3400

Once more, I’m literally not injecting an opinion here or arguing for or against anyone’s point. All the articles here talked about counts of individual accidents with zero context about sample size, something that is absolutely crucial to establishing exactly what you’re talking about, rates. You can shit all over that, and then pretend you didn’t, but Im only pointing out that the math doesn’t work unless that context is there.

(I find it funny that the article you just posted is literally an ad for a traffic accident lawyer: here’s the study the ad is citing. The ad did some creative interpretation on those numbers, ignoring things like DUI’s for example: https://www.lendingtree.com/insurance/brand-incidents-study/#:~:text=Tesla drivers have the highest accident rate compared with all,over 20.00 per 1%2C000 drivers.)

No one’s talking about rates. The article itself, all the articles linked in these comments are talking about counts. Numbers of incidents. I’m not justifying anything because I’m not injecting my opinion here. I’m only pointing out that without context, counts don’t give you enough information to draw a conclusion, that’s just math. You can’t even derive a rate without that context!

The NHSTA hasn’t issued rules for these things either.

the U.S. gov has issued general guidelines for the technology/industry here:

https://www.transportation.gov/av/4

They have an article on it discussing levels of automation here:

https://www.nhtsa.gov/vehicle-safety/automated-vehicles-safety

By all definitions layed out in that article:

BlueCruise, Super Cruise, Mercedes’ thing is a lvl3 system ( you must be alert to reengage when the conditions for their operation no longer apply )

Tesla’s FSD is a lvl 3 system (the system will warn you when you must reengage for any reason)

Waymo and Cruise are a lvl 4 system (geolocked)

Lvl 5 systems don’t exist.

What we don’t have is any kind of federal laws:

https://www.ncsl.org/transportation/autonomous-vehicles

Separated into two sections – voluntary guidance and technical assistance to states – the new guidance focuses on SAE international levels of automation 3-5, clarifies that entities do not need to wait to test or deploy their ADS, revises design elements from the safety self-assessment, aligns federal guidance with the latest developments and terminology, and clarifies the role of federal and state governments.

The guidance reinforces the voluntary nature of the guidelines and does not come with a compliance requirement or enforcement mechanism.

(emphasis mine)

The U.S. has operated on a “states are laboratories for laws” principal since its founding. The current situation is in line with that principle.

These are not my opinions, these are all facts.

I’m saying larger sample size == larger numbers.

Tesla announced 300 million miles on FSD v12 in just the last month.

https://www.notateslaapp.com/news/2001/tesla-on-fsd-close-to-license-deal-with-major-automaker-announces-miles-driven-on-fsd-v12

Geographically, that’s all over the U.S, not just in hyper specific metro areas or stretches of road.

The sample size is orders of magnitude bigger than everyone else, by almost every metric.

If you include the most basic autopilot, Tesla surpassed 1 billion miles in 2018.

These are not opinions, just facts. Take them into account when you decide to interpret the opinion of others.

No one else has the same capability in as wide a geographic range. Waymo, Cruise, Blue Cruise, Mercedes, etc are all geolocked to certain areas or certain stretches of road.

Talk of the Tik Tok ban predates the attack that triggered the current iteration of violence in Israel/Gaza.

The only way this makes sense is as a punitive measure against foreign landlords, where the tenant (as the tax payer) gets some measure of ownership over the property, which doesn’t seem to be the case.

Yeah, most infotainment systems hide their memory leaks behind the fact that when you turn the car off, you reset the computer. Not so in an always on EV.

Honestly that’s the best possible name for it.

Tabs are a dark pattern confirmed.

The war is over, long live spaces.

At worst, they might cancel the subscriptions. I imagine trying to give the money back (get the charges reversed) is the labor intensive part.

A repo dedicated to non-unit-test tests would be the best way to go. No need to pollute your main code repo with orders of magnitude more code and junk than the actual application.

That said, from what I understand of the exploit, it could have been avoided by having packaging and testing run in different environments (I could be wrong here, I’ve only given the explanation a cursory look). The tests modified the code that got released. Tests rightly shouldn’t be constrained by other demands (like specific versions of libraries that may be shared between the test and build steps, for example), and the deploy/build step shouldn’t have to work around whatever side effects the tests might create. Containers are easy to spin up.

Keeping them separate helps. Sure, you could do folders on the same repo, but test repos are usually huge compared to code repos (in my experience) and it’s nicer to work with a repo that keeps its focus tight.

It’s comically dumb to assume all tests are equal and should absolutely live in the same repo as the code they test, when writing tests that function multiple codebases is trivial, necessary, and ubiquitous.