![[Discussion] What would it take to selfhost some of the backend that Tesla's connect to?](https://lemmy.ca/pictrs/image/58e8ff1a-930a-4e1e-8c7c-da3bcc7dc88b.jpeg){kind=link}
I saw this article earlier:
Tesla ‘going bankrupt’ is endpoint of protests, says local organizer
In the spirit of right to repair, self-hosting, giving a second life to old devices, and limiting data collection by car companies:
- What are some considerations?
- Are there any projects worth keeping an eye on?
An example that came to mind was Valetudo, which is a cloud replacement for vacuum robots enabling local-only operation. Some robot vacuums are easy to install this on, and others require more invasive modifications.
What I’ve found so far:
I’m talking ‘I disabled the awareness requirement of autopilot’ or ‘I fucked with the object detection and here goes my beta test yolo’ or ‘I added a button to disable all the lights so I can covertly street race’ or…
Imagine thinking Tesla has all-that-much in place to prevent those things in a stock configuration. Full-stop, any self-driving is one of the first features anyone trying to disconnect their cars from Tesla servers would lose outright.
Ehh doubt, but I don’t have a tesla to verify. If I can sever the connection to the home base, I can fuck with it however I want, and their kill switch is useless. Maybe they implemented the kill switch in the modem or something, but again I can’t test. I highly doubt that when you’re road-tripping in bumfuck nowhere the ap disables itself…
Anybody want to give me $40k? We can be besties.
And? People can already do this with most cars.
There’s a difference between ‘physical work required’ and ‘plug in this dongle and run the exe’ though