Then don’t buy tesla, or force legislation about introducing such feature.
But make yourself a favor and don’t play Russian roulette with something that you can not understandbecause there are not data available.
And for final tip, if you really cares about that then enforce the fsf (fsf.org)
It is not comparable, not even by far.
Assuming your are not a psycho, to safely drive a car is orders of magnitude (in plural) easier than modifying the Sw in a safe and deterministic way.
It is not only that bad people exists, it is about that making a small mistake can kill you
First, second and third most important point is : Tesla needs to allow the connection to an alternative server.
The fourth should be access to the api and data that are exchanged.
You shouldn’t mess with the FW of your own car even for some innocent feature like this one, you don’t know/understand the interactions that may happen between different Sw components and the hw layer, you can not provide a similar of level of testing, including some worst case scenarios, that can make your car unsafe during some problems or unforeseen conditions. And perhaps also, the car could loose its license for driving…
If tesla allows that, then we can start speaking about it. But last time I check on that was not possible
Not good, you are going to lose a lot of stuff, from personal relations, connections to your wife and even your health.
I hope (really) your are not in a compromised financial situation and this is really temporary. If so, it is OK but you need to have a plan to reduce the hours in the foresable future.
If this is not the situation, then learn how to disconnect from the work in the spare time and spent quality time when possible, also do cardio. It helps. A lot.
When you are young you can really chew everything it is throwed at you, but it is not true anymore when you are past the 40s.
Take care of yourself, nobody else is going to do it.
Some clarifications :
The 3 2 1 rule applies only for the data. Not the backup, in my case I have the real/live data, then a daily snapshot in the same volume /pool and a external off-site backup
For the databases you got misleading information, you can copy the files as they are BUT you need to be sure that the database is not running (you could copy the data and n the middle of a transaction leading to some future problems) AND when you restore it, you need to restore to the exact same database version.
Using the export functionality you ensure that the data is not corrupted (the database ensure the correctness of the data) and the possibility to restore to another database version.
My suggestion, use borgbackup or any other backup system with de duplication, stop the docker to ensure no corruptions and save everything. Having a downtime of a minute every day is usually not a deal breaker for home users
Because the modification of that computer is order of magnitudes more difficult than a mechanical modification of a moving part. The humanity / regular human is able to understand much better the interactions of the mechanical parts that usually are always local and well defined.
This does not exist in the Sw, FW and digital hw, the interactions are not local and are millions timesmore complex to understand and properly modify.
It would be an utterly irresponsability to modify (blindly) the Sw of an xray machine that could make it unsafe and ultimately it could kill humans, and it is the same concept with the car. It is irresponsable to make a modification that can make the system unsafe.
For the rest? Regulations, free software foundation and good selfhosting Cheers