3 ms·

But even just inputting destination addresses has its problems. What happens when an Uber-like app freaks out and spams the self-driving algos with a hundred de

But even just inputting destination addresses has its problems. What happens when an Uber-like app freaks out and spams the self-driving algos with a hundred destinations a second? Or screws up the location and sends a passenger a dozen miles from their intended destination? Or where the Tesla algos find a route it's been given to be undriveable and just turn back? Sure, you and I would rightly hold the modder accountable, but that's because we understand how this stuff works. Everybody else will see "Tesla cars" not working right, and that's a huge headache and liability for Tesla. We don't know exactly how "black box" their system is, and how easily it can be made immune to spurious (or even malicious!) inputs, while also leaving it open to third-party apps. I would guess it's just a risk that they don't want to take. And I don't think they'll ever ban people from going to places - as long as you use approved Tesla tools to request that destination.

deleted 10y ago
[deleted]
csallen 10y ago
> But even just inputting destination addresses has its problems. What happens when an Uber-like app freaks out and spams the self-driving algos with a hundred destinations a second? If Tesla's APIs can't handle input spam, that's on them. That's a very predictable and easily-solved problem. The entire point of an API is to expose a limited surface area so that you can easily interoperate while maintaining control and responsibility. > Or screws up the location and sends a passenger a dozen miles from their intended destination? Or where the Tesla algos find a route it's been given to be undriveable and just turn back? Sure, you and I would rightly hold the modder accountable, but that's because we understand how this stuff works. Everybody else will see "Tesla cars" not working right, and that's a huge headache and liability for Tesla. If Uber sends your car to the wrong location, then that's that. No big deal. People go to the wrong locations themselves all the time. I don't see how this is an Uber-specific problem, and I don't buy the argument that people are smart enough to hook their Tesla up to Uber but too stupid to understand who's at fault when the car correctly navigates itself to an incorrect location. > And I don't think they'll ever ban people from going to places - as long as you use approved Tesla tools to request that destination. There is no "approved Tesla tool" to connect to Uber. What happens if they modify their "approved Tesla tools" so they won't auto-drive you to a Burger King?
- snrplfth 10y ago
  > If Tesla's APIs can't handle input spam, that's on them. That's a very predictable and easily-solved problem. The entire point of an API is to expose a limited surface area so that you can easily interoperate while maintaining control and responsibility. Sure, it's on them, and it appears they've solved that problem by cutting out other apps entirely. Certainly I'd prefer it if they would let people experiment with their product, but I can see why they wouldn't want them to, considering that it's a rapidly evolving, high-stakes product. > If Uber sends your car to the wrong location, then that's that. No big deal. People go to the wrong locations themselves all the time. I don't see how this is an Uber-specific problem, and I don't buy the argument that people are smart enough to hook their Tesla up to Uber but too stupid to understand who's at fault when the car correctly navigates itself to an incorrect location. It's not "Uber-specific", it's just an example of the sort of thing that could happen if a third-party app makes errors. Reasonable people will understand that it's the app at fault, but most people will just see the headline: "Panicked partiers trapped as Tesla self-driving car goes on a robot joyride!" > There is no "approved Tesla tool" to connect to Uber. What happens if they modify their "approved Tesla tools" so they won't auto-drive you to a Burger King? Tesla disallowing third-party apps and self-driving-for-revenue outside Tesla Network doesn't make a difference to whether they could do such a thing. But you can see that they have sensible reasons to not want these things (software concerns, commercial insurance, public/regulator perception) and there's no real reason that they would block you from going to particular destinations. Internet Explorer could block you from using anything but Bing, but they don't. That would be ridiculous.
  - csallen 10y ago
    Allowing self-driving-for-revenue via the Tesla Network but not via Uber is absolutely no different than Internet Explorer allowing Bing but blocking Google.
    - snrplfth 10y ago
      No, because you can still get to all destinations, but you can't use it for certain tasks. Tesla has understandable reasons why they don't want self-driving capability used on alternate revenue-generating networks. You may disagree with them, but it doesn't mean that these reasons would ever lead them to block off physical locations.

deleted 10y ago

[deleted]

csallen 10y ago

> But even just inputting destination addresses has its problems. What happens when an Uber-like app freaks out and spams the self-driving algos with a hundred destinations a second? If Tesla's APIs can't handle input spam, that's on them. That's a very predictable and easily-solved problem. The entire point of an API is to expose a limited surface area so that you can easily interoperate while maintaining control and responsibility. > Or screws up the location and sends a passenger a dozen miles from their intended destination? Or where the Tesla algos find a route it's been given to be undriveable and just turn back? Sure, you and I would rightly hold the modder accountable, but that's because we understand how this stuff works. Everybody else will see "Tesla cars" not working right, and that's a huge headache and liability for Tesla. If Uber sends your car to the wrong location, then that's that. No big deal. People go to the wrong locations themselves all the time. I don't see how this is an Uber-specific problem, and I don't buy the argument that people are smart enough to hook their Tesla up to Uber but too stupid to understand who's at fault when the car correctly navigates itself to an incorrect location. > And I don't think they'll ever ban people from going to places - as long as you use approved Tesla tools to request that destination. There is no "approved Tesla tool" to connect to Uber. What happens if they modify their "approved Tesla tools" so they won't auto-drive you to a Burger King?

snrplfth 10y ago
> If Tesla's APIs can't handle input spam, that's on them. That's a very predictable and easily-solved problem. The entire point of an API is to expose a limited surface area so that you can easily interoperate while maintaining control and responsibility. Sure, it's on them, and it appears they've solved that problem by cutting out other apps entirely. Certainly I'd prefer it if they would let people experiment with their product, but I can see why they wouldn't want them to, considering that it's a rapidly evolving, high-stakes product. > If Uber sends your car to the wrong location, then that's that. No big deal. People go to the wrong locations themselves all the time. I don't see how this is an Uber-specific problem, and I don't buy the argument that people are smart enough to hook their Tesla up to Uber but too stupid to understand who's at fault when the car correctly navigates itself to an incorrect location. It's not "Uber-specific", it's just an example of the sort of thing that could happen if a third-party app makes errors. Reasonable people will understand that it's the app at fault, but most people will just see the headline: "Panicked partiers trapped as Tesla self-driving car goes on a robot joyride!" > There is no "approved Tesla tool" to connect to Uber. What happens if they modify their "approved Tesla tools" so they won't auto-drive you to a Burger King? Tesla disallowing third-party apps and self-driving-for-revenue outside Tesla Network doesn't make a difference to whether they could do such a thing. But you can see that they have sensible reasons to not want these things (software concerns, commercial insurance, public/regulator perception) and there's no real reason that they would block you from going to particular destinations. Internet Explorer could block you from using anything but Bing, but they don't. That would be ridiculous.
- csallen 10y ago
  Allowing self-driving-for-revenue via the Tesla Network but not via Uber is absolutely no different than Internet Explorer allowing Bing but blocking Google.
  - snrplfth 10y ago
    No, because you can still get to all destinations, but you can't use it for certain tasks. Tesla has understandable reasons why they don't want self-driving capability used on alternate revenue-generating networks. You may disagree with them, but it doesn't mean that these reasons would ever lead them to block off physical locations.