There is most likely an overlap on what you can get from the OBD port, but generally speaking the API will provide more high level info e.g driving status, mileage, live location - and the OBD port will provide more low level data e.g. detailed battery stats from the BMS, energy usage, etc.
Rookeh
joined 1 year ago
Highlight where in the above post I am defending anything.
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.
That also means we can still use the expansion cards for the Framework in any other device that also has a USB-C port. Need an SD card reader or a 2.5Gb LAN adapter? Not a problem, I'll just grab one from my laptop.
Didn't he become a Commodore, not an Admiral?
Por qué no los dos?
Solution: don't read that shitrag. It was always a waste of paper, now it is a waste of bandwidth as well.
Not exactly crazy but just mysterious...this was at a software company I worked at many years ago. It was one of the developers in the team adjacent to ours who I worked with occasionally - nice enough person, really friendly and helpful, everyone seemed to get on with them really well and generally seemed like a pretty competent developer. Nothing to suggest any kind of gross misconduct was happening.
Anyway, we all went off to get lunch one day and came back to an email that this person no longer worked at the company, effective immediately. Never saw them again.
No idea what went down - but the culture at that place actually became pretty toxic after a while, which led to a few people (including me) quitting - so maybe they dodged a bullet.
Nah, the SWAT would have to arrest themselves.
I've tried Copilot and to be honest, most of the time it's a coin toss, even for short snippets. In one scenario it might try to autocomplete a unit test I'm writing and get it pretty much spot on, but it's also equally likely to spit out complete garbage that won't even compile, never mind being semantically correct.
To have any chance of producing decent output, even for quite simple tasks, you will need to give an LLM an extremely specific prompt, detailing the precise behaviour you want and what the code should do in each scenario, including failure cases (hmm...there used to be a term for this...)
Even then, there are no guarantees it won't just spit out hallucinated nonsense. And for larger, enterprise scale applications? Forget it.
My daily driver is a pure EV, but while I was on holiday a few months ago I was driving a Yaris Hybrid as a rental (which to my understanding is basically a Prius drivetrain in a Yaris body).
Fuck me it was terrible. Every time I applied even mild acceleration it sounded like the valves were going to eject out of the engine, meanwhile it had about as much get up and go as a sedated elephant. 0-60 in four to six business days. On ramps were an interesting experience.
The only saving grace was that we only used about a third of a tank of gas during our week long trip.
I'll stick with pure electric thanks. No complicated drivetrain with multiple systems to go wrong, no compromised performance, enough range to get me everywhere I need to go, and good enough charging infrastructure (at least in my country) to make longer journeys trivial.
Not at all.
Lemmy is overwhelmingly militantly anti-Tesla, which is understandable considering who owns it, but it does mean that users tend to interpret any neutral or factual statements (basically anything that is not outright criticism) as having a pro-Tesla bias.
In this case, all I am stating is the fact that this specific change currently only affects corporate users. That could of course change in the future.
There is a rich history of cloud based data providers pulling the rug from under users with no warning. Look at what happened to Nest users when Google took over.