Comment by emmelaich
8 years ago
Merely 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.
8 years ago
Merely 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.
But 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.
Without disagreeing, can you give me an example.
And it's just a speculation. Shrug.
One 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.
1 reply →