4 ms·
The first couple I looked at were requests to Uber and Fitbit...
by tlrobinson 10y ago
The first couple I looked at were requests to Uber and Fitbit...
- emmelaich 10y agoOne of my Uber rides two weeks ago went completely nuts. Both my and my drivers app screwed up at the same time and I was never picked up and then seconds later the app claimed I reached my destination. You have to wonder whether something like this is implicated.
- SteveNuts 10y agoProbably not. If someone knew about this exploit they're not going to be messing with people's Uber rides for lulz.
- emmelaich 10y agoI wasn't implying intention.
- Twirrim 10y agoThat's one phenomenal leap of logic there. Why would you think that?
- emmelaich 10y agoMerely that both my and the drivers app screwed up at the same time, and have a good chance of hitting the same Uber end-point. Apps that consume APIs would be more sensitive to unexpected junk than browsers.
- deleted 10y ago[deleted]
- fletchowns 10y agoBut there are so many other much more likely reasons why something like that would have happened, it is quite a leap to think that it is somehow related to this issue.
- emmelaich 10y agoWithout disagreeing, can you give me an example. And it's just a speculation. Shrug.
- wapz 10y agoOne simple explanation could be the road was between very large concrete buildings or the area has some sort of GPS interference (there is one place in Tokyo that jumps my GPS and probably others' by about 300m to the same location every time). Another simple explanation is the software has a bug on when it thinks you arrive in some extremely bizarre scenario (hence you both had it happen simultaneously). I don't know how it works in the back so this is all speculation of course.
- emmelaich 10y agoYep, but I'd already taken an Uber ride from the exact same place the day before. And everything went smoothly.