Sometime in the near future, when these things are running around killing us, I will remember this code is buried somewhere deep in their AI Core. As it's standing over me, about to deliver the killing blow, I will hit the play button on my phone, (cued up the uptown funk song earlier just in case). As the death-bot starts to uncontrollably moonwalk, I will slip away to survive another day in this hell on earth, delivered to us by Bostondyne Systems.

This is all fine, why not. IMHO Formula 1 is basically approaching this from the other shore most of the time.

Racing cars used to be about adrenalin, taming a beast, surviving unlikely odds and so on, an adventure for gentlemen.

In the last 40 years it has become a competition in pushing buttons, mostly.

If racing cars can have ABS, automatic gearboxes, power steering and all, why not an electric motor?

I still think it is sad and I am glad I saw F1 in the 70s.

For best effect, click the CC button for the auto-generated machine translation.

It's hilariously terribad.

I actually used an old Intellimouse Explorer 2.0 from 2003 today -- it's in my laptop bag for those times when the trackpad just doesn't cut it.

Still works pretty well. The button hardware switches are a bit old and some of them produce signals that are too noisy for the signal bounce processing chips to filter out. So, the wheel button registers a single click as a double basically 100% of the time (PITA when using it to open new tabs in a browser), and the "forward" button does the same 50% of the time (much less frequently an issue). Not half bad for 15 year old hardware, really.

After these phased out of popularity, I switched loyalties to Logitech and then more recently Razer. But the hand feel of the chassis (which will be the exact same for this reboot version) of the Explorer was really quite excellent. Might have to look for one!

I like that they worked in some of the elements of the original pip-boy into this one. The vacuum tubes and red buttons are a nice touch.

The sound effect right before makes me think the guy watching on CCTV has a button that drops dogs. First of all, that's a silly security system. And misused in this case.

I assume you are using vs6 and if so go to the top header bar and scroll over your name. The drop down menu should reveal a fix embed code button.

Sorry, last message was ambiguous - you need the key fob to be in close proximity to both unlock, and to press the start button.
From the video, the thief driving the car takes his box inside the car as well, which would mimic the key in order to start it as well.

I'm surprised that these things put out a strong enough signal to get out of the house. Maybe build a case for the fob that cuts off the signal unless you hit a button and exposes enough of it for the signal to get out?

The key is only needed to unlock the door and press the "start" button inside. At least with Honda (not sure of others), the car will only start beeping when the key gets out of range, it won't turn off or anything (probably for safety reasons).
Also with Honda, you have to press your foot on the brake in order for the start button to work. I have seen other makes where this is not required.

I would assume that if these thieves have the tech to create the relay boxes, they also have to the tech to reprogram replacement keys for the stolen vehicle (otherwise how will they sell it on? unless it's just parted out)

"I've always wondered myself about keyless tech safety for this exact reason. How can the signal not just be copied and replayed?"

Well, I can't say for certain, but if I was designing it, the signal wouldn't be the same every time. Basically, you would have an algorithm that generates a signal (essentially a large number encoded as a binary stream) based on a seed and the current time.

The seed is unique to the car and the key.

So when you press the button, the key does something like

entryCode = SomeComplexAlgorithm(seed, time())

so the car would do something like

entryRequest = GetSignal()
checkedRequest = SomeComplexAlgorithm(sameSeedAsKey, time())
if (checkedRequest == entryRequest) Unlock()

That's obviously a vast oversimplification (not sure how they'd get around the time sync), but you get the idea.

What surprises me here is not that the car starts, but that it doesn't cut out once it gets out of range of the key. Even a strong relay would only have a short range (1-2km at most?).

And for those of you who many not have taken it all the way, notarobot means "click on the Spin button until you discover something fun!"

Those can be blocked by adding the following filters to your ad blocker (i.e. uBlock):

youtube.com##.ytp-ce-covering-overlay
youtube.com##.ytp-ce-element-shadow
youtube.com##.ytp-ce-covering-image
youtube.com##.ytp-ce-expanding-image
youtube.com##.ytp-ce-element.ytp-ce-video.ytp-ce-element-show
youtube.com##.ytp-ce-element.ytp-ce-channel.ytp-ce-channel-this
youtube.com##.ytp-cards-teaser
youtube.com##.ytp-ce-element
youtube.com##.ytp-cards-button
youtube.com##.iv-click-target

Well I drive trucks and make this type of "button-hook" turn a lot. First of all if it were a car he would leave his trailer less than 4 feet from the curb in back so a car can't sneak by. They teach you this in truck school. He had his signal on and I drive through a college housing area all the time and make a turn like this with young people on my right a lot. She probably should have stopped and let him turn, him being in busy traffic he has to turn with the flow of traffic which might be slower than a bicycle. That said, of course he has to monitor the cyclist (I also ride bicycles in the big city) and stop immediately if she didn't yield or time his approach so she goes ahead of him. So ya, from truck driving school to my next work day (tomorrow) the driver is ALWAYS at fault if he hits anything on his right turning no matter who has the right a way. Sad case