3 ms·

Lyft doesn't create fake rides. Source: work there.

by vecter 5y ago

okareaman 5y ago
Do you understand how your ride scheduling software works? I can be even more specific: I was travelling south on 280 near Daly City sometime in the fall of 2019. I got a pickup in what turned out to be a cemetary. I refused to go into the dark cemetery figuring it was a mistake. The ride was cancelled then a message came up suggesting I stay and wait there because there was high demand in that neighborhood. Look it up. You keep logs don't you? Edit: It was a pickup at the Golden Gate National Cemetery around 10 PM. I have an alt email in my profile. Contact me if you need more information.
- vecter 5y ago
  We keep logs of course, but we have strict privacy guidelines that prevent me or any employees from looking at random rides of users. We have annual training that reminds us of such (and for good reason--imagine how creepy it would be if Lyft employees could look at the ride histories for any users). We match drivers with riders based on some algorithms and heuristics that try to optimize for some metrics which I won't go into for obvious reasons. In order to match a driver with a rider, there must be a real ride request from a real user account. It's that simple. What you claim simply does not exist, and would be so blatantly unethical that someone even suggesting such a thing would raise a ton of eyebrows immediately and might get them fired, and persisting to push such an idea would almost certainly get them fired. You reference an "AI" in your other comments. That's not how AIs work. It is not a Skynet-level artificial intelligence that decides what the policy is, but rather an optimization problem that is solved with certain constraints. There is no system on Earth with anywhere near the level of agency and intelligence that you're implying it would have to have in order to be able to modify the source code of a system to create the concept of fake users and riders.
  - okareaman 5y ago
    Well I was a driver not a rider and I didn't pick anyone up. You should be able to look at what drivers are doing it seems. It's a mystery to me how I got a pickup in a cemetery late at night. Someone ordered it. The ride was cancelled shortly after I got there. Seems fishy to me that I got a message suggesting I wait in that neighborhood because of high demand right after the ride was cancelled. I've written software for a lot of years, and there's times when it does something unexpected. Consider this a bug report then.
    - vecter 5y ago
      There's no bug that could possibly cause that behavior. Someone requested a ride and then cancelled it. Maybe they requested both an Uber and a Lyft and went with the one that was going to pick them up faster. Or they just changed their minds and cancelled the ride for some other reason. Also, we value driver privacy as much as rider privacy, so the same privacy guidelines apply there. The only way to get someone to look at a specific event is to file a support ticket and have the support agent go through our system. Any other method of access is basically forbidden.

Lyft doesn't create fake rides. Source: work there.

by vecter 5y ago

Lyft doesn't create fake rides. Source: work there.

Do you understand how your ride scheduling software works? I can be even more specific: I was travelling south on 280 near Daly City sometime in the fall of 2019. I got a pickup in what turned out to be a cemetary. I refused to go into the dark cemetery figuring it was a mistake. The ride was cancelled then a message came up suggesting I stay and wait there because there was high demand in that neighborhood. Look it up. You keep logs don't you? Edit: It was a pickup at the Golden Gate National Cemetery around 10 PM. I have an alt email in my profile. Contact me if you need more information.

vecter 5y ago
We keep logs of course, but we have strict privacy guidelines that prevent me or any employees from looking at random rides of users. We have annual training that reminds us of such (and for good reason--imagine how creepy it would be if Lyft employees could look at the ride histories for any users). We match drivers with riders based on some algorithms and heuristics that try to optimize for some metrics which I won't go into for obvious reasons. In order to match a driver with a rider, there must be a real ride request from a real user account. It's that simple. What you claim simply does not exist, and would be so blatantly unethical that someone even suggesting such a thing would raise a ton of eyebrows immediately and might get them fired, and persisting to push such an idea would almost certainly get them fired. You reference an "AI" in your other comments. That's not how AIs work. It is not a Skynet-level artificial intelligence that decides what the policy is, but rather an optimization problem that is solved with certain constraints. There is no system on Earth with anywhere near the level of agency and intelligence that you're implying it would have to have in order to be able to modify the source code of a system to create the concept of fake users and riders.
- okareaman 5y ago
  Well I was a driver not a rider and I didn't pick anyone up. You should be able to look at what drivers are doing it seems. It's a mystery to me how I got a pickup in a cemetery late at night. Someone ordered it. The ride was cancelled shortly after I got there. Seems fishy to me that I got a message suggesting I wait in that neighborhood because of high demand right after the ride was cancelled. I've written software for a lot of years, and there's times when it does something unexpected. Consider this a bug report then.
  - vecter 5y ago
    There's no bug that could possibly cause that behavior. Someone requested a ride and then cancelled it. Maybe they requested both an Uber and a Lyft and went with the one that was going to pick them up faster. Or they just changed their minds and cancelled the ride for some other reason. Also, we value driver privacy as much as rider privacy, so the same privacy guidelines apply there. The only way to get someone to look at a specific event is to file a support ticket and have the support agent go through our system. Any other method of access is basically forbidden.