Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tesla Fleet Telemetry

github.com

Post reply on HN
Print view View original

61–70 of 136 posts

Re: Tesla Fleet Telemetry

#61

Post by chroma »

bouke wrote: post #18

Every time Tesla refers to the cars they sold to customers as their ‘fleet’, I get the feeling they don’t really recognise they are no longer the owner of those vehicles. Fleet as defined in Oxford Dictionary: “A number of vehicles or aircraft working together, or under the same ownership.” (edit: use actual Oxford definition)

It's in reference to a company owning a fleet of Teslas, not Tesla owning the fleet.[1] The point of this reference implementation is to make it easier for companies that own a bunch of Teslas to collect data about their cars.

1. https://www.tesla.com/fleet

Re: Tesla Fleet Telemetry

#62

Post by chroma »

awinter-py wrote: post #38

congratulations your motor vehicle is now dependent on kubernetes pov you are headed for a collision and something is wrong. you issue a describe command ... Type Reason Age ---- ------ ---- Normal Sync 100s (x3 over 100s) Is that an expected status for this component? The distance narrows ...

The Kubernetes implementation is on the server side, not the car. The only way to control the car is through Tesla's API,[1] and that doesn't let you do dangerous stuff like turn the wheel while someone is driving.

Even if you could overwrite the software on the car, you'd still have to contend with the physical controls available to the driver. The steering wheel is physically connected to a typical rack and pinion setup. The brake pedal is physically connected to hydraulic lines just like every other car on the road. And like most cars, the brakes are more powerful than the motor.

1. There's no official documentation but a big chunk of it has been reverse engineered: https://tesla-api.timdorr.com/vehicle/commands

Re: Tesla Fleet Telemetry

#63

Post by AgentK20 »

abledon wrote: post #53

I'm a kubernetes noob, in https://github.com/teslamotors/helm-charts/blob/main/charts/... why do they do `helm repo add teslamotors https://teslamotors.github.io/helm-charts/ ` instead of `helm repo add teslamotors https://github.com/teslamotors/helm-charts/ ` ? isn't the first one a webpage rather than a repo?

The github.io site that they include the link to is the actual repository that can be read by Helm, in particular by it polling the known "index.yaml" file at https://teslamotors.github.io/helm-charts/index.yaml. Something _could_ be done using Github's "/raw" endpoint, but generally speaking Github pages works better for this sort of purpose and also is built to be a CDN, meaning it has additional caching layers in front of it that make it more performant.

Re: Tesla Fleet Telemetry

#64

Post by dotBen »

leoh wrote: post #4

>At Tesla we believe that security and privacy are core tenets of any modern technology. Customers should be able to decide what data they share with third parties, how they share it, and when it can be shared. We've developed a decentralized framework: "Fleet Telemetry" that allows customers to create a secure and direct bridge from their Tesla devices to any provider they authorize. Complete non-sequitur. “We care…

Our Teslas sends an insane amount of data home, even down to event calls for rolling down the window or opening the car door. But you kind of know that going into it - ok not everyone does but anyone who is reasonable technical and most likely to care about privacy and understand the issues is aware. And it's technically in the small print which of course everyone reads fully when they buy the car. /s

They also record the road and the way you drive it using cameras in the vehicle you own and paid for, upload it using your home internet connection and improve their self driving model which will no doubt represents $billion's, maybe $ trillions of enterprise value over time.

A Tesla is not a normal 'dumb' car, and you accept that going into it. Allowing consumers to have fair access to that data in a safe manner that doesn't involve sharing usernames and passwords is actually the right and responsible action on Tesla's part.

Re: Tesla Fleet Telemetry

#65

Post by revel »

Is there an accompanying architecture diagram that goes with this?

I'm not sure which bits and pieces are included without poking through the code

Re: Tesla Fleet Telemetry

#66

Post by revel »

bouke wrote: post #18

Every time Tesla refers to the cars they sold to customers as their ‘fleet’, I get the feeling they don’t really recognise they are no longer the owner of those vehicles. Fleet as defined in Oxford Dictionary: “A number of vehicles or aircraft working together, or under the same ownership.” (edit: use actual Oxford definition)

this is standard industry parlance

Re: Tesla Fleet Telemetry

#67

Post by rkagerer »

cryptonector wrote: post #51
awinter-py wrote: post #38

congratulations your motor vehicle is now dependent on kubernetes pov you are headed for a collision and something is wrong. you issue a describe command ... Type Reason Age ---- ------ ---- Normal Sync 100s (x3 over 100s) Is that an expected status for this component? The distance narrows ...

F-16s have kubernetes on them now[0]. [0] https://thenewstack.io/how-the-u-s-air-force-deployed-kubern...

Good grief

Re: Tesla Fleet Telemetry

#68

Post by NotYourLawyer »

stetrain wrote: post #32
leoh wrote: post #4

>At Tesla we believe that security and privacy are core tenets of any modern technology. Customers should be able to decide what data they share with third parties, how they share it, and when it can be shared. We've developed a decentralized framework: "Fleet Telemetry" that allows customers to create a secure and direct bridge from their Tesla devices to any provider they authorize. Complete non-sequitur. “We care…

The current situation for third party apps (which do exist, plenty of them) is you either give them your Tesla account username/password (super bad) or an access token that you get by signing into your Tesla account, which is less bad but still gives the app the same access as your full Tesla account. So yes, by building a framework to allow users to authorize third party apps to receive limited telemetry data withou…

> give them your Tesla account username/password (super bad)

Only slightly related, but buying a Tesla they encourage you to use Plaid for payment. Which involves… giving your banking account username and password to a third party.

Extremely bad. I can’t believe anyone would do this.

Re: Tesla Fleet Telemetry

#69

Post by killjoywashere »

cryptonector wrote: post #50
jabbequbs wrote: post #35

Earlier quoted context omitted.

I have bad news for you. This exact topic has been discussed on my local radio station (in a medium sized city) and loads of callers described working at a photo lab where there was a drawer full of copies of "noteworthy" photos. I think it's apples and oranges though. With a photo lab the customer has deliberately handed over whatever images they want developed, whether the images are private or not. Tesla employees…

If an employee at a hotel planted secret cameras and... If an vacation rental landlord planted secret cameras and... Bad news all around.

You can go to jail for having a surveillance system in your own home: https://www.cbsnews.com/news/navy-doctor-guilty-of-making-se...

Re: Tesla Fleet Telemetry

#70

Post by _ea1k »

rondini wrote: post #24
_ea1k wrote: post #15

Earlier quoted context omitted.

That sounds like a subtle mischaracterization of the leak to me. The leak sounded more like, "the teams responsible for tagging data uploaded by Teslas had access to data uploaded by Teslas". The fact that they could share them amongst themselves is also not particularly surprising. While I understand the alarm, it was also completely unsurprising even based purely on the company's public statements about how they us…

If an employee at a photo lab was keeping and sharing copies of compromising pictures there would be huge outrage and rightfully so. Just because they have to handle personal data doesn't mean it's acceptable to share and laugh with your colleagues; it should be handled with the utmost respect for your users' privacy.

That's what I mean about a mischaracterization. There's no indication of long term retention, but rather of pointing and laughing.

Remember the olden days of photo labs at the mall that would run the pictures visibly in front of the window?

They don't do that any more, but the employees still point and laugh while they are in their possession. Right or wrong, it is human nature, when they all technically have access.

Post reply on HN