Because, unless you’re driving a forklift, the point of a vehicle’s rotation is in line with the rear wheels, meaning you can take turns at a much more acute angle when reversing than going forwards. Which makes backing into spaces much easier.

Notice that most of the half-assed parking jobs you see are generally people who have driven forward and left the car parked at a diagonal half out of the space, because getting the vehicle lined up in that situation is more difficult.

Well, I’m currently writing a service and frontend, both in C# (Blazor for the UI), and using docker-compose to build and deploy them to a Raspberry Pi running Linux. So not only cross-platform, but cross-architecture as well.

This is not a new thing either. Since .NET Core was released almost 10 years ago, it has supported cross platform development.

2017: covfefe

2025: cvefefe

Right now none of the native clients support SSO. It is a frequently requested feature but, unfortunately, it doesn’t look like it will be implemented any time soon. As with many OSS projects it is probably a case of “you want it, you build it” - but nobody has actually stepped up.

For web access, stick it behind a reverse proxy and use something like Authentik/Authelia/SSO provider of your choice to secure it.

For full access including native clients, set up a VPN.

Oh fuck me, HOW in like 25 years did I not get that pun?!

We refer to it as kew-bee-cuttle

Something to note: Tesla has two vehicle APIs, the Fleet API for commercial accounts and the Owner API for individuals. This change currently only impacts the Fleet API.

If you are an individual owner who accesses your vehicle data from the Owner API (usually via a self hosted tool like TeslaMate), this does not affect you. Yet.