Western manufacturing tends to be much more automation heavy. Chinese manufactures don’t bother with buying a $100k machine that can make a car part when they can just hire 10 guys at $10k/yr to make that same part with a $50 drill press and some hand files.

It’s not that it all strictly balances out, but if we actually gave a shit we could potentially be cost competitive for a lot of price brackets, especially given the costs to move whole ass cars across the Pacific.

Bear in mind these sub $10k Chinese EVs are not something US consumers would really be interested in buying, they are basically tiny car shaped golf carts with extremely minimalist feature sets. Think ‘no audio system at’ all type interiors.

Or not subsidize oil and gas to the tune of ~$20 billion/yr and corn at $2.2 billion/yr and redirect that towards EVs.

Intrinsically/semantically no but the expectation is that the texts are encrypted at rest and the keys are password and/or tpm+biometric protected. That’s just how this works at this point. Also that’s the government standard for literally everything from handheld devices to satellites (yes, actually).

At this point one of the most likely threat vectors is someone just taking your shit. Things like border crossings, rubber stamped search warrants, cops raid your house because your roommate pissed them off, protests, needing to go home from work near a protest, on and on.

RF analysis is kinda difficult, you’d need to take the car out into the middle of nowhere and have access to fairly good equipment. A tinySA would maybe work if you’re very patient but data transmissions are generally very bursty so it may be difficult to nail down where it’s coming from in a sane amount of time.

One option would be to try to figure out if there are any FCC filings for your car. All filings will have pictures of whatever module is being used and what antenna systems it uses which may give you a good idea of where it is and what it looks like. There should be an FCC ID mentioned somewhere at the beginning or end of the cars manual. Googling that should bring up some stuff.

Fuck HDMI. The committee makes doing custom hardware near impossible unless you’re a mega corp

The lower layers all already at least moderately well encrypted, what they’re doing here is trying to pull the unencrypted device ID necessary to establish a connection. It’s not really what you’re sending (though traffic frequency analysis may be included) and more about just figuring out where a particular phone is so they can physically track the user.

I hate that it needs to be said but love that they said it so plainly

There might be a few layers to this one. Drones are becoming a central part of strategic production and the US doesn’t really have many competitive companies manufacturing small ones at volume.

They need to force the domestic market to build up local expertise and manufacturing capacity in the event that small drones are the direction warfare ends up going more broadly.

The us defense apparatus is still on the fence about this given that their volume of use in Ukraine could be more of an aberration due to the respective industrial bases and static nature of the war. That said the numbers are insane enough that they warrant some action just in case.

The unspoken part is that unless Gabe has a very strong plan involving some sort of employee co-op, when he retires or dies the company will likely get sold by the estate to private capital which is 100x worse than being a public company.

Installed it in k3s and then pulled up the Android app but all it does is say every single file is a duplicate and overload my notifications tray while not uploading anything

Judging from how many voters are in the US, it’s basically a totalitarian dictatorship or die.

That like of reasoning is kinda broken. We need people to take responsibility before things go too far. Google engineers can get jobs anywhere, they don’t need to be doing this shit if they don’t want to.

As a SWE you have responsibility for what you do. “Golden handcuffs” isn’t a cover to help wage wars against users. If it becomes an undesirable posting, they’ll either have to pay more or worse engineers will end up working on it.

Recommendation: report the pop-up as a bug with the provided link. Just act confused and claim to not be using an ad blocker. Muddy the waters and make life hell for their devs.

Yeah, that’s the issue ultimately. The ESP32 chips are nice and easy to use but still pale in comparison to getting things working on a pi for the average developer without embedded experience. These devs may not even know they exist to be completely honest.

I’m not intimately familiar with the BCM2711 but I believe it’s a reasonable, albeit somewhat overpowered, processor for the application. It can be put into a variety of low power states and probably pulled out of sleep by various events like the GSM chip sending packets or accelerometer motion (frequently the peripheral chips have dedicated “wakeup” pins that you can wire to interrupts). It’s not the most cost effective option by far, there are sub $5 microcontrollers with multiple cores for handling communications and real time motor control concurrently but you’d need to hire someone like me for a few months @$200/hr to write the low level drivers and design the boards. The rpi lets random web-only devs fumble their way through hardware development using whatever GitHub Python libraries they can find. If you only need a hundred scooters it makes more sense to just yolo it and buy up the remaining supply of rpis to start your grift.