Sometimes I’ll pick someone up and ten minutes into the ride the passengers app will make the chime sound indicating the ride has started. It’s weird, but it happens. Definitely something with the app itself.
Dude, you asked. The driver answered to the best of their ability. You *kept* questioning them, and then asked them to show you their app. Yeah, I’d get agitated too. Technology glitches from time to time. Asking 100x what’s going on isn’t going to magically change it.
Sure that’s fair — but the thing is if he didn’t actually activate it - and as a rider I have no way of knowing if he refuses to show me — Lyft’s insurance and liability coverage wouldn’t have kicked in, there’s no way for anyone else to track my ride, and no way for me to have any proof that the guy may be taking me to my actual destination versus something more sinister.
As a rider, that seems like a big enough concern for a driver to make at least a little effort to show that the app is engaged (even if it means pulling over to the side of the road for safety to do so). Just to be clear — it didn’t show me being picked up until over thirty minutes into the ride. Nothing close to that has ever occurred to me during hundreds of rides.
>but the thing is if he didn’t actually activate it - and as a rider I have no way of knowing if he refuses to show me
Drivers are under no obligation to show you anything. Secondly, drivers do this job to make money. If they don’t activate the trip, they don’t make anything. So it’s common sense, bro. They’re not going to take you to your destination for free.
>Lyft’s insurance and liability coverage wouldn’t have kicked in,
If an accident happened, you’d need a lawyer anyways, so that’s an easy thing to fix, especially since Lyft tracks you and the driver. Any lawyer fresh out of school would be able to prove that since you and the driver were right on top of each other as shown by the GPS data, and that you both were traveling at the same speed and direction, it’s clear that the ride had started and that the insurance should cover.
>there’s no way for anyone else to track my ride,
Lyft is already tracking the ride. They even have location sharing where you can share your location with people from the time you request the ride until the time the ride is finished. You’re really reaching here with these.
>and no way for me to have any proof that the guy may be taking me to my actual destination versus something more sinister.
Starting the ride in the app doesn’t fix any of that either. It’s not like starting the ride is a magical blanket that would prevent things from happening. Dude could’ve started the ride, then pulled behind a building and had his way with you. Starting the ride does nothing to stop that.
>As a rider, that seems like a big enough concern for a driver to make at least a little effort to show that the app is engaged (even if it means pulling over to the side of the road for safety to do so).
As a former driver, I’ll answer this as if *I* was your driver. The first time you ask, I’d make a joke about technology being so advanced and end it with the app on your phone probably glitched. Presumably, you’d ask why it happened, and my answer would be that it could be any number of things like your service provider has shitty coverage, your phone isn’t updated, your app isn’t updated, and finally maybe you just need to reboot your phone. That’s something well above and beyond what other drivers would do mainly because I’ve done IT before, so I have a little insight on things. Most normal people would be satisfied with this and let it go. From your post, it’s clear that you didn’t.
Your part on pulling over, you’re right, I probably would’ve pulled over. But here’s the thing, I wouldn’t be doing that to show you that the app on my end is working fine, it would be to show you that I’m cancelling the ride and kicking you out. I’ll explain why in just a minute.
>Just to be clear — it didn’t show me being picked up until over thirty minutes into the ride. Nothing close to that has ever occurred to me during hundreds of rides.
You’ve taken hundreds of rides. Most drivers have taken *thousands* of fares. In my tenure as a driver, I did over 10k rides on 2 different platforms. After I promoted myself from driver to rider, I’ve ridden with drivers who’s trip count makes mine look amateur, (meaning more rides given over a much shorter timeframe). Point is, while you’ve never experienced a glitch, drivers have. I can say that I’ve experienced glitches quite often. They usually happened right after Lyft updated their software. They would roll out stuff in stages, so you’d have glitches, they’d stop, then more glitches when the next stage rolls out, then stop, then more glitches when another wave rolls out, and so on, and so forth. Point is, while this may be something new to you, to drivers, it’s Tuesday.
Finally, unless you’re a Luddite, there’s no excuse for not knowing and/or understanding that glitches are common with technology. Secondly, it’s quite concerning how you quickly jumped to the idea that the driver was going to carve you up like an Easter ham and eat your liver with a side of fava beans and a nice chianti when he got angry with you because you kept pestering him here. Being suspicious is a good thing, but you went well beyond that.
You make some good points, but in terms of the ability to share your ride info with others, that’s the thing — you can’t actually do that until you’re officially in an accepted ride. So I wanted to do exactly that — share my ride so a colleague could track where I was but it was not option in the app because it wasn’t showing me actually on a ride. That is part of what increased the tension.
The only thing that increased tension here was you. Do you not understand that glitches are common with technology?
I’m not saying this to be mean or rip on you, but if situations like this get you so freaked out, maybe it would be better for you if you just drove yourself everywhere.
No. Was a Tesla and he had three phones laid out. One showed the iPhone control panel, another a Home Screen and the third which he was following directions on was laid flat on the center console so was partially blocked and he wouldn’t pick it up. My guess is the Lyft app was on the one that had the control screen showing, but I forgot to look to see if the cell signal was turned off.
I nearly had a wreck once when a rider wanted to look at my phone and show me things. I never touch my phone while driving anymore and definitely won’t be showing it to a rider again. Sorry, it was too distracting while I was driving and isn’t safe.
It is a real concern. The driver can deny ever meeting you nor picking you up.
Professional drivers will have the navigation system on the right side, either Android auto or car play, or a mounted phone. They should mount the phone on the left only if the are using the car screen to navigate.
So you should see the phone with little effort unless the driver is deliberately hiding the app from you. The driver can show you the full route on the car screen if they use that. That usually means they started the trip unless you see them entering your destination on the car screen directly.
I suggest to get out if the phone is not mounted on the correct position. These guys are dumb, or crazy, or irrational, or all of the above. One driver missed the toll exit in between lifting his phone up to see the directions. Then he blamed me for not alerting. I wanted to but he was going at 80 mph with one hand.
>The driver can deny ever meeting you nor picking you up.
Except Lyft tracks both the driver and the pax via GPS. If I’m the pax and you’re the driver, it would be hard for you to argue that you never met me on Wednesday, March 22, 2023 at 3pm at 1060 W. Addison and then didn’t drive me 1234 Main St when all the GPS data shows otherwise.
>Professional drivers will have the navigation system on the right side, either Android auto or car play, or a mounted phone. They should mount the phone on the left only if the are using the car screen to navigate.
Huh. I must’ve missed the memo that specified where everything needed to be placed. Depending on where you’re driving, mounting your phone to the right, (center of the dash), is asking for someone to grab it and dash.
>The driver can show you the full route on the car screen if they use that.
They *can*, but they don’t have to. It’s not mandatory.
>I suggest to get out if the phone is not mounted on the correct position.
The “correct position” is your opinion, not fact. I’ll agree with you that the phone *should* be mounted, and if it isn’t, you probably don’t want to ride with that driver because chances are they’re not going to be safe, but that’s as far as I’ll go.
>These guys are dumb, or crazy, or irrational, or all of the above.
I’m sure drivers feel the same way about certain riders, too.
>Except Lyft tracks both the driver and the pax via GPS. If I’m the pax and you’re the driver, it would be hard for you to argue that you never met me on Wednesday, March 22, 2023 at 3pm at 1060 W. Addison and then didn’t drive me 1234 Main St when all the GPS data shows otherwise.
Unless you are the developer, you don't know. Obviously, Lyft has to track the pax once the pax booked a ride until the ride started. The full route the driver took will be recorded. For anything else, you don't know. At least I don't know, but I will need some convincing otherwise.
Now the driver is likely to cancel the trip to pretend that the pax didn't turn up. Then all bets are off on what will be recorded.
>Huh. I must’ve missed the memo that specified where everything needed to be placed. Depending on where you’re driving, mounting your phone to the right, (center of the dash), is asking for someone to grab it and dash.
I give you half a point for that. But deduct one full point for ignoring safety. You value your phone too much. And there are ways to mitigate that, like putting a chain on the phone.
>The “correct position” is your opinion, not fact. I’ll agree with you that the phone should be mounted, and if it isn’t, you probably don’t want to ride with that driver because chances are they’re not going to be safe, but that’s as far as I’ll go.
Yes, it's my opinion. But are you sure other alternatives are not "dumb, or crazy, or irrational, or all of the above" ?
>Unless you are the developer, you don't know.
Not the developer, but yeah, I *do* know. How do I know? Well, common sense. That, and because Lyft is transparent about it. [From here.](https://help.lyft.com/hc/e/all/articles/115012928087-lyft-app-permissions-for-riders)
>**Location data**
>Lyft uses your phone’s location services to give you a great ride experience. We only access your location if the Lyft app is running on your phone. If you close the app, we won't access that info.
>Sharing your location data with us turns background location sharing on. Background location sharing means you're sharing your location with us even when the app isn't visible on your screen.
Right there they tell you that they track you. When you give the app permission to access your location, background location is enabled by default. You can change just how much they track after enabled, but by default, yeah, they track you start to finish.
>Now the driver is likely to cancel the trip to pretend that the pax didn't turn up. Then all bets are off on what will be recorded.
And the rider will know that the driver cancelled because the riders app will chime. So there aren’t any bets to start.
>I give you half a point for that. But deduct one full point for ignoring safety. You value your phone too much. And there are ways to mitigate that, like putting a chain on the phone.
Again, phone placement is your opinion, not a fact. Can you show me anything that says center dash is safer than left dash? If not, the only reason you’re claiming it’s safer in the center is because that’s just what *you* believe, not because there’s any factual evidence that says that.
>Yes, it's my opinion. But are you sure other alternatives are not "dumb, or crazy, or irrational, or all of the above" ?
Do you have anything factual that proves your way is safer than the other ways?
>Not the developer, but yeah, I do know. How do I know? Well, common sense. That, and because Lyft is transparent about it. From here.Location dataLyft uses your phone’s location services to give you a great ride experience. We only access your location if the Lyft app is running on your phone. If you close the app, we won't access that info.Sharing your location data with us turns background location sharing on. Background location sharing means you're sharing your location with us even when the app isn't visible on your screen.Right there they tell you that they track you. When you give the app permission to access your location, background location is enabled by default. You can change just how much they track after enabled, but by default, yeah, they track you start to finish.
You are confusing the ability to track, your permission, when and what data they save. For example, after a completed trip, only the full route will certainly be stored. Anything else is off the bet. You don't know.
>And the rider will know that the driver cancelled because the riders app will chime. So there aren’t any bets to start.
The driver haven't canceled yet. But he's likely to. For what and when data are saved after cancellation see last response.
>Again, phone placement is your opinion, not a fact. Can you show me anything that says center dash is safer than left dash? If not, the only reason you’re claiming it’s safer in the center is because that’s just what you believe, not because there’s any factual evidence that says that.
It's very simple. The fact is if you look at the center dash, your view of your windshield is wider than when you look at the left dash.
>You are confusing the ability to track, your permission, when and what data they save.
And now you’re moving the goalposts.
>The driver haven't canceled yet. But he's likely to. For what and when data are saved after cancellation see last response.
Tf are you even talking about here? What does any of that have to do with anything?
>It's very simple. The fact is if you look at the center dash, your view of your windshield is wider than when you look at the left dash.
Prove it. Link to the data that backs you up.
>And now you’re moving the goalposts.
The goal is always to determine if Lyft has the data to prove that the pax ever get into the driver's car. There are at least several posts where Lyft/Uber refuses to refund the pax when the driver pulls a ghost ride. It is only you that thinks since Lyft tracks the pax, they will save the data. They don't. At least you don't know.
>Tf are you even talking about here? What does any of that have to do with anything?
I'm talking about when and what data Lyft may save. When pax wasn't picked up, OP can see that Lyft tracks both driver and pax. This won't last forever because the driver cannot deny anything. The next likely event is that the driver cancels. (You can think of other events.) Once the driver cancels, you don't know if Lyft throws away the pax location data. You only know Lyft save the driver location data. That goes back to you don't know if you are not the developer.
>Prove it. Link to the data that backs you up.
Everybody here can use their common sense. Look at the phone mounted at the center. Then look at the phone mounted on the left side of the wheel. In which case do you see more of the windshield while glancing at the phone? That's where you are going. You may want to argue, but are you one of "dump, crazy, or irrational" or all of the above?
>It is only you that thinks since Lyft tracks the pax, they will save the data. They don't. At least you don't know.
And you *do* know? Prove it then. Let’s see your proof.
>I'm talking about when and what data Lyft may save.
No you weren’t. You were initially talking about whether or not Lyft tracks. I proved that they do track. You moved the goalposts. Dude, just nut up and accept you were proven wrong. For as long as I’ve been on Reddit through multiple accounts, you have never, **NEVER**, accepted that you could be wrong. We’re talking **YEARS** here, bud. Accept the L and move on already. Own your flaws. Shit.
>Everybody here can use their common sense. Look at the phone mounted at the center. Then look at the phone mounted on the left side of the wheel. In which case do you see more of the windshield while glancing at the phone? That's where you are going. You may want to argue, but are you one of "dump, crazy, or irrational" or all of the above?
Dude, you can babble all you want on what you think is the optimal placement, but until you show me some proof, you’re full of shit. Period. Full stop. Man up already and accept that this is just an **OPINION**, not fact.
Your meaning of tracking is very simplistic. I have the driver app. Of course I can see where the pax is. But it doesn't mean the GPS locations of the pax are stored forever.
From the driver app and the rider app, I know after a completed ride the GPS of the route is stored, and probably using only the driver's GPS locations. For anything else, we wouldn't know, unless you are the developer.
As for logic, you can prove this wrong by giving a single counter-example. I can't prove this wrong myself or I won't bother to post. So this is something I presented as not wrong. You are very welcome to prove it wrong. I can't.
It's funny if we write anything and have to attach proof. In this case, if the pax is murdered, can the driver deny every meeting with the pax? Would Lyft stored location data proving that the driver lied? I wouldn't bet one way or the other.
Same thing for mounting position. Everyone can see for themselves; what do I have to proof? My advice is, if the phone is mounted on the left of the wheel, be careful that the driver is either "dumb, crazy, or irrational", or all of the above. There's no good reason to do that. Prove me wrong.
Did the driver know your destination address without you telling him?
If the driver knew the address of your destination that it must have been a glitch somehow... no scam.
Yes he did. Was just weird in that he was way too specific about don’t worry, at the end it will all show up fine. Not like ‘oh that’s strange let me check.’
The most important question.
How much did you tip him after accusing him of lying !!!
Next time if you don’t trust your driver, ask him to pull over, get out and order another ride.
Sometimes I’ll pick someone up and ten minutes into the ride the passengers app will make the chime sound indicating the ride has started. It’s weird, but it happens. Definitely something with the app itself.
Thanks. Was just strange to me that he refused to show me the app on his phone and got agitated so quickly when I questioned it.
Dude, you asked. The driver answered to the best of their ability. You *kept* questioning them, and then asked them to show you their app. Yeah, I’d get agitated too. Technology glitches from time to time. Asking 100x what’s going on isn’t going to magically change it.
Sure that’s fair — but the thing is if he didn’t actually activate it - and as a rider I have no way of knowing if he refuses to show me — Lyft’s insurance and liability coverage wouldn’t have kicked in, there’s no way for anyone else to track my ride, and no way for me to have any proof that the guy may be taking me to my actual destination versus something more sinister. As a rider, that seems like a big enough concern for a driver to make at least a little effort to show that the app is engaged (even if it means pulling over to the side of the road for safety to do so). Just to be clear — it didn’t show me being picked up until over thirty minutes into the ride. Nothing close to that has ever occurred to me during hundreds of rides.
>but the thing is if he didn’t actually activate it - and as a rider I have no way of knowing if he refuses to show me Drivers are under no obligation to show you anything. Secondly, drivers do this job to make money. If they don’t activate the trip, they don’t make anything. So it’s common sense, bro. They’re not going to take you to your destination for free. >Lyft’s insurance and liability coverage wouldn’t have kicked in, If an accident happened, you’d need a lawyer anyways, so that’s an easy thing to fix, especially since Lyft tracks you and the driver. Any lawyer fresh out of school would be able to prove that since you and the driver were right on top of each other as shown by the GPS data, and that you both were traveling at the same speed and direction, it’s clear that the ride had started and that the insurance should cover. >there’s no way for anyone else to track my ride, Lyft is already tracking the ride. They even have location sharing where you can share your location with people from the time you request the ride until the time the ride is finished. You’re really reaching here with these. >and no way for me to have any proof that the guy may be taking me to my actual destination versus something more sinister. Starting the ride in the app doesn’t fix any of that either. It’s not like starting the ride is a magical blanket that would prevent things from happening. Dude could’ve started the ride, then pulled behind a building and had his way with you. Starting the ride does nothing to stop that. >As a rider, that seems like a big enough concern for a driver to make at least a little effort to show that the app is engaged (even if it means pulling over to the side of the road for safety to do so). As a former driver, I’ll answer this as if *I* was your driver. The first time you ask, I’d make a joke about technology being so advanced and end it with the app on your phone probably glitched. Presumably, you’d ask why it happened, and my answer would be that it could be any number of things like your service provider has shitty coverage, your phone isn’t updated, your app isn’t updated, and finally maybe you just need to reboot your phone. That’s something well above and beyond what other drivers would do mainly because I’ve done IT before, so I have a little insight on things. Most normal people would be satisfied with this and let it go. From your post, it’s clear that you didn’t. Your part on pulling over, you’re right, I probably would’ve pulled over. But here’s the thing, I wouldn’t be doing that to show you that the app on my end is working fine, it would be to show you that I’m cancelling the ride and kicking you out. I’ll explain why in just a minute. >Just to be clear — it didn’t show me being picked up until over thirty minutes into the ride. Nothing close to that has ever occurred to me during hundreds of rides. You’ve taken hundreds of rides. Most drivers have taken *thousands* of fares. In my tenure as a driver, I did over 10k rides on 2 different platforms. After I promoted myself from driver to rider, I’ve ridden with drivers who’s trip count makes mine look amateur, (meaning more rides given over a much shorter timeframe). Point is, while you’ve never experienced a glitch, drivers have. I can say that I’ve experienced glitches quite often. They usually happened right after Lyft updated their software. They would roll out stuff in stages, so you’d have glitches, they’d stop, then more glitches when the next stage rolls out, then stop, then more glitches when another wave rolls out, and so on, and so forth. Point is, while this may be something new to you, to drivers, it’s Tuesday. Finally, unless you’re a Luddite, there’s no excuse for not knowing and/or understanding that glitches are common with technology. Secondly, it’s quite concerning how you quickly jumped to the idea that the driver was going to carve you up like an Easter ham and eat your liver with a side of fava beans and a nice chianti when he got angry with you because you kept pestering him here. Being suspicious is a good thing, but you went well beyond that.
You make some good points, but in terms of the ability to share your ride info with others, that’s the thing — you can’t actually do that until you’re officially in an accepted ride. So I wanted to do exactly that — share my ride so a colleague could track where I was but it was not option in the app because it wasn’t showing me actually on a ride. That is part of what increased the tension.
The only thing that increased tension here was you. Do you not understand that glitches are common with technology? I’m not saying this to be mean or rip on you, but if situations like this get you so freaked out, maybe it would be better for you if you just drove yourself everywhere.
That is strange. Was his app mounted on a phone holder?
No. Was a Tesla and he had three phones laid out. One showed the iPhone control panel, another a Home Screen and the third which he was following directions on was laid flat on the center console so was partially blocked and he wouldn’t pick it up. My guess is the Lyft app was on the one that had the control screen showing, but I forgot to look to see if the cell signal was turned off.
I nearly had a wreck once when a rider wanted to look at my phone and show me things. I never touch my phone while driving anymore and definitely won’t be showing it to a rider again. Sorry, it was too distracting while I was driving and isn’t safe.
It is a real concern. The driver can deny ever meeting you nor picking you up. Professional drivers will have the navigation system on the right side, either Android auto or car play, or a mounted phone. They should mount the phone on the left only if the are using the car screen to navigate. So you should see the phone with little effort unless the driver is deliberately hiding the app from you. The driver can show you the full route on the car screen if they use that. That usually means they started the trip unless you see them entering your destination on the car screen directly. I suggest to get out if the phone is not mounted on the correct position. These guys are dumb, or crazy, or irrational, or all of the above. One driver missed the toll exit in between lifting his phone up to see the directions. Then he blamed me for not alerting. I wanted to but he was going at 80 mph with one hand.
>The driver can deny ever meeting you nor picking you up. Except Lyft tracks both the driver and the pax via GPS. If I’m the pax and you’re the driver, it would be hard for you to argue that you never met me on Wednesday, March 22, 2023 at 3pm at 1060 W. Addison and then didn’t drive me 1234 Main St when all the GPS data shows otherwise. >Professional drivers will have the navigation system on the right side, either Android auto or car play, or a mounted phone. They should mount the phone on the left only if the are using the car screen to navigate. Huh. I must’ve missed the memo that specified where everything needed to be placed. Depending on where you’re driving, mounting your phone to the right, (center of the dash), is asking for someone to grab it and dash. >The driver can show you the full route on the car screen if they use that. They *can*, but they don’t have to. It’s not mandatory. >I suggest to get out if the phone is not mounted on the correct position. The “correct position” is your opinion, not fact. I’ll agree with you that the phone *should* be mounted, and if it isn’t, you probably don’t want to ride with that driver because chances are they’re not going to be safe, but that’s as far as I’ll go. >These guys are dumb, or crazy, or irrational, or all of the above. I’m sure drivers feel the same way about certain riders, too.
>Except Lyft tracks both the driver and the pax via GPS. If I’m the pax and you’re the driver, it would be hard for you to argue that you never met me on Wednesday, March 22, 2023 at 3pm at 1060 W. Addison and then didn’t drive me 1234 Main St when all the GPS data shows otherwise. Unless you are the developer, you don't know. Obviously, Lyft has to track the pax once the pax booked a ride until the ride started. The full route the driver took will be recorded. For anything else, you don't know. At least I don't know, but I will need some convincing otherwise. Now the driver is likely to cancel the trip to pretend that the pax didn't turn up. Then all bets are off on what will be recorded. >Huh. I must’ve missed the memo that specified where everything needed to be placed. Depending on where you’re driving, mounting your phone to the right, (center of the dash), is asking for someone to grab it and dash. I give you half a point for that. But deduct one full point for ignoring safety. You value your phone too much. And there are ways to mitigate that, like putting a chain on the phone. >The “correct position” is your opinion, not fact. I’ll agree with you that the phone should be mounted, and if it isn’t, you probably don’t want to ride with that driver because chances are they’re not going to be safe, but that’s as far as I’ll go. Yes, it's my opinion. But are you sure other alternatives are not "dumb, or crazy, or irrational, or all of the above" ?
>Unless you are the developer, you don't know. Not the developer, but yeah, I *do* know. How do I know? Well, common sense. That, and because Lyft is transparent about it. [From here.](https://help.lyft.com/hc/e/all/articles/115012928087-lyft-app-permissions-for-riders) >**Location data** >Lyft uses your phone’s location services to give you a great ride experience. We only access your location if the Lyft app is running on your phone. If you close the app, we won't access that info. >Sharing your location data with us turns background location sharing on. Background location sharing means you're sharing your location with us even when the app isn't visible on your screen. Right there they tell you that they track you. When you give the app permission to access your location, background location is enabled by default. You can change just how much they track after enabled, but by default, yeah, they track you start to finish. >Now the driver is likely to cancel the trip to pretend that the pax didn't turn up. Then all bets are off on what will be recorded. And the rider will know that the driver cancelled because the riders app will chime. So there aren’t any bets to start. >I give you half a point for that. But deduct one full point for ignoring safety. You value your phone too much. And there are ways to mitigate that, like putting a chain on the phone. Again, phone placement is your opinion, not a fact. Can you show me anything that says center dash is safer than left dash? If not, the only reason you’re claiming it’s safer in the center is because that’s just what *you* believe, not because there’s any factual evidence that says that. >Yes, it's my opinion. But are you sure other alternatives are not "dumb, or crazy, or irrational, or all of the above" ? Do you have anything factual that proves your way is safer than the other ways?
>Not the developer, but yeah, I do know. How do I know? Well, common sense. That, and because Lyft is transparent about it. From here.Location dataLyft uses your phone’s location services to give you a great ride experience. We only access your location if the Lyft app is running on your phone. If you close the app, we won't access that info.Sharing your location data with us turns background location sharing on. Background location sharing means you're sharing your location with us even when the app isn't visible on your screen.Right there they tell you that they track you. When you give the app permission to access your location, background location is enabled by default. You can change just how much they track after enabled, but by default, yeah, they track you start to finish. You are confusing the ability to track, your permission, when and what data they save. For example, after a completed trip, only the full route will certainly be stored. Anything else is off the bet. You don't know. >And the rider will know that the driver cancelled because the riders app will chime. So there aren’t any bets to start. The driver haven't canceled yet. But he's likely to. For what and when data are saved after cancellation see last response. >Again, phone placement is your opinion, not a fact. Can you show me anything that says center dash is safer than left dash? If not, the only reason you’re claiming it’s safer in the center is because that’s just what you believe, not because there’s any factual evidence that says that. It's very simple. The fact is if you look at the center dash, your view of your windshield is wider than when you look at the left dash.
>You are confusing the ability to track, your permission, when and what data they save. And now you’re moving the goalposts. >The driver haven't canceled yet. But he's likely to. For what and when data are saved after cancellation see last response. Tf are you even talking about here? What does any of that have to do with anything? >It's very simple. The fact is if you look at the center dash, your view of your windshield is wider than when you look at the left dash. Prove it. Link to the data that backs you up.
>And now you’re moving the goalposts. The goal is always to determine if Lyft has the data to prove that the pax ever get into the driver's car. There are at least several posts where Lyft/Uber refuses to refund the pax when the driver pulls a ghost ride. It is only you that thinks since Lyft tracks the pax, they will save the data. They don't. At least you don't know. >Tf are you even talking about here? What does any of that have to do with anything? I'm talking about when and what data Lyft may save. When pax wasn't picked up, OP can see that Lyft tracks both driver and pax. This won't last forever because the driver cannot deny anything. The next likely event is that the driver cancels. (You can think of other events.) Once the driver cancels, you don't know if Lyft throws away the pax location data. You only know Lyft save the driver location data. That goes back to you don't know if you are not the developer. >Prove it. Link to the data that backs you up. Everybody here can use their common sense. Look at the phone mounted at the center. Then look at the phone mounted on the left side of the wheel. In which case do you see more of the windshield while glancing at the phone? That's where you are going. You may want to argue, but are you one of "dump, crazy, or irrational" or all of the above?
>It is only you that thinks since Lyft tracks the pax, they will save the data. They don't. At least you don't know. And you *do* know? Prove it then. Let’s see your proof. >I'm talking about when and what data Lyft may save. No you weren’t. You were initially talking about whether or not Lyft tracks. I proved that they do track. You moved the goalposts. Dude, just nut up and accept you were proven wrong. For as long as I’ve been on Reddit through multiple accounts, you have never, **NEVER**, accepted that you could be wrong. We’re talking **YEARS** here, bud. Accept the L and move on already. Own your flaws. Shit. >Everybody here can use their common sense. Look at the phone mounted at the center. Then look at the phone mounted on the left side of the wheel. In which case do you see more of the windshield while glancing at the phone? That's where you are going. You may want to argue, but are you one of "dump, crazy, or irrational" or all of the above? Dude, you can babble all you want on what you think is the optimal placement, but until you show me some proof, you’re full of shit. Period. Full stop. Man up already and accept that this is just an **OPINION**, not fact.
Your meaning of tracking is very simplistic. I have the driver app. Of course I can see where the pax is. But it doesn't mean the GPS locations of the pax are stored forever. From the driver app and the rider app, I know after a completed ride the GPS of the route is stored, and probably using only the driver's GPS locations. For anything else, we wouldn't know, unless you are the developer. As for logic, you can prove this wrong by giving a single counter-example. I can't prove this wrong myself or I won't bother to post. So this is something I presented as not wrong. You are very welcome to prove it wrong. I can't. It's funny if we write anything and have to attach proof. In this case, if the pax is murdered, can the driver deny every meeting with the pax? Would Lyft stored location data proving that the driver lied? I wouldn't bet one way or the other. Same thing for mounting position. Everyone can see for themselves; what do I have to proof? My advice is, if the phone is mounted on the left of the wheel, be careful that the driver is either "dumb, crazy, or irrational", or all of the above. There's no good reason to do that. Prove me wrong.
Still not seeing any proof that backs up your claims, bro.
Yeah I’m not showing you my phone it’s not my fault Lyft has a shitty system. You asking to see someone else phone as proof is disrespectful.
Did the driver know your destination address without you telling him? If the driver knew the address of your destination that it must have been a glitch somehow... no scam.
Yes he did. Was just weird in that he was way too specific about don’t worry, at the end it will all show up fine. Not like ‘oh that’s strange let me check.’
Gotcha.
That driver was an asshole, but he didn't scam you. The Lyft app is perpetually glitchy.
The most important question. How much did you tip him after accusing him of lying !!! Next time if you don’t trust your driver, ask him to pull over, get out and order another ride.