wk ... all due respect, but is it possible they felt YOU took the first swing today? More than one way to look at today's events. I assume because of your past interactions with the engineering team, you've built up some relationship. All of a sudden, they see you informing the world (and the top guy directly, Elon himself) that they didn't keep something very well hidden, instead of just telling them directly. I can't help but think that they might feel a bit burned by someone they thought was an ally. Just another way to look at it.
With all due respect to you and others on this as well, I just don't see it that way. I mean really, think about it. 24 hours ago I had something like 40 whole twitter followers, a dozen of which I know in person and have nothing to do with Tesla related stuff. I've tweeted random nonsense to @TeslaMotors and @elonmusk a bunch of times, never expecting a response, and all in good fun. I don't really do social media, besides TMC (if that counts).
Going through the update on my car last night at like 2AM or so I spotted the
P100D badge, among other things. The P100D had already been elsewhere in the firmware for *months* prior and I never even bothered to say a word, cryptically or not, publicly about it or any of the several dozen things, big and small, that Tesla includes in these production firmware versions that the public probably shouldn't see yet.... by
my own choice to do so, not because of any agreement or relationship with Tesla implied or otherwise.
I figured I'd have a little fun, and sort of provably time-stamp the fact that Tesla included something like the P100D in the firmware already... without actually saying so. I didn't think for a second that anyone besides myself would ever post the hash input, or bother to attempt to crack it, regardless of the short length message. Maybe that was up-at-3AM sleepiness, but thinking back I still am somewhat impressed that someone out of those ~28 people on my twitter made the effort, and so quickly. And what's done is done.
So, not to sound like a jackass, but I'm going to be very blunt and make one thing perfectly clear here. Understand that I'm under
ZERO obligation to keep
ANYTHING I find out about Tesla, the Model S, etc, through my efforts tinkering around with
my own car, private. The fact that
I DO keep a ton of this stuff completely to myself should be more than enough to vindicate me of any perception of events that suggest bad intentions on my part with the small thing I unintentionally let slip here. Especially on Tesla's side of this, since they certainly know full well what's in the firmware more than anyone and certainly know everything I know that I've NOT posted about.
And again, if people reading about a potential P100D being talked about by me were such a big deal, Tesla should have reached out to me and said so. "Hey man, not cool," with a brief conversation that probably would have ended with my apologies and subsequent tweeting/posting of something like, "Hah, gotcha! Early April fools!" to cover up my leak. This, or one of 100 different things could have been done or not done to just have made the whole thing a non-issue.
Instead, for some reason, Tesla decided to remotely access my car without permission and attempt to make changes that really have nothing to do with the situation whatsoever. I mean seriously, what does downgrading my P85D to 2.12.45 vs leaving it at 2.12.126 (with 2.13.77 staged to be installed in evening) gain them in this situation? I REALLY want to know what they think the answer to this one is, because from my perspective it gains them nothing whatsoever besides a) alerting me to the fact that this is the kind of tactic they're going to use, and b) p***ing me off. It does nothing to rectify the P100D leak situation whatsoever. I managed to catch them in the act and disable the VPN connection and the updater, however, but too late to keep 2.13.77 staged, so, I'll just have to keep my chargers at 80A for now I guess.
Anyway, regardless of what you all may think of me and my intentions, Tesla should have been better than remotely screwing with an owner's firmware for no real reason in this situation. Regardless of how they felt about what I've done, that was NOT the right thing to do on their part in response, and I'm not going to tolerate it.