This is an archived community post.

This post is no longer open for new replies - but we'd still love to hear from you! Share your feedback with our team via our Feedback Form.

Need help getting started? Check out this article for step-by-step instructions on submitting feedback through the form.

suypposed-location when authorizing your log-in-location, is still not working / not good enough / mis-informative

Vurrath

 

The supposedly 'accurate'  confirm log-in location function, is still wildly off, the one i just noticed, is on the other side of the major city where i live... more than 7.5, if not 10Km away. more than 10 suburbs, easily.

 

why have something that supposedly identifies WHICH suburb, if it's always wrong?

 

and similarly, why have something that "might use" according to what i've been told, the location of your ISP, or a internet-hub.

 

my local ISP's tower, is no where near that far, so it could only be the local hub, IF, that's where it is.

 

you might as well not have it, and instead, for dynamic-allocation-IP, have just [ DYNAMIC IP ] , displayed, instead of a location  -  it would save time/unneccessary-processing / wait-time,.. and it wouldn't create mis-information anywhere.

 

??

 

just fix it, no more arguments!

1

Comments

0 comments