Well, lucky for you, it’s all camera based now.

This is some sovereign citizen mental gymnastics.

I don’t get what you mean.

The app is intended to remote start your vehicle when you’re out of range of the key fob. I’m not sure how you’d propose that function works without servers and infrastructure.

Most manufacturers are doing this.

Most people don’t seem to care since they understand there are ongoing server and infrastructure costs.

This is one of the downfalls of a distributed system. You basically need public votes. Without it, instances lack critical information about the validity of votes. You don’t have a centralized system with back door access to monitor and maintain things.

Thing is they needed to factor this j to the cost of selling the device.

It basically costs them nothing to ru the service for this device. If they failed to calculate that as part of the sale price, that’s not the consumers fault.

I went with it because I figured it had same peering defaults.

It does, which is really nice.

They are. It’s not incredibly common, but it’s not rare.

My coworker had his car stolen from his driveway. He believes it was a relay attack.

That being said, it’s super easy to mitigate by putting your keys in a metal bin.

But that’s not actually a thing. I start both of my newer vehicles before I’m buckled. No beeping until I actually put it in drive.

It rarely happens because I always buckle

I’ve built and seen many real world use cases for LLMs. The reality is the most valuable use cases are extremely mundane.

I’m guessing this is an issue because of the increased usage of the “frunk”.

Nearly every ICE can suffer the exact same issue.

Sometimes you can.

It’s common to use a Hall effect sensor for positioning. It gives off an analog value. You might be able adjust the signal threshold that you consider to be “open” or “closed” in software.

Further, this is probably something that you just don’t spend a bunch of time engineering. Pick a value that’s well with your tolerance range and move onto harder problems. When a problem comes up, you can fine turn the range.

Recalls aren’t uncommon. You just don’t hear about most because it’s not trendy.

One of my vehicles is at risk of catching fire. The other is at risk of its axle falling off.

These are major brands, within the past 5 years.

I mean, this can happen with any car that has a hinged hood (so nearly all cars)

I know you jest, but Samsung is a massive battery supplier.

These will be plain old dumb batteries

I’m not sure why you think this statement is so profound.

CrowdStrike is expected to have kernel level access to operate correctly. Kernel level exceptions cause these types of errors.

Windows handles exceptions just fine when code is run in user space.

This is how nearly all computers operate.

I think the person you’re trying to correct was making the same point as you.

They were simply trying to demonstrate that butter isn’t 100% fat.

Switched from Android to iPhone.

Everything just works in the Apple ecosystem. Android has an app for everything but none of them work well. They always require some sort of configurations, etc, etc. what really set me over was consistently missing calls because my phone just didn’t receive them.

Seriously, nothing in the Android ecosystem works well together. It all just sucks.

Your premise relies on two false pretenses:

1. That we have time to calculate how everything works. We don’t.

2. The system doing the calculations is affected by doing the calculations. This creates infinite recursion, which by definition means we can’t actually compute everything

If our universe exists within another universe, the outer universe could calculate and predict everything in our universe, but we cannot do it from within the confines of our own universe.

I guarantee you’ve become use to the slop in nearly all of the components.