41–50 of 56 posts
The original visitor.js identified my city correctly; this only put me in the USA. Is there a free reliable precise geolocation service that can take as many hits as a script like this could throw at it?
Worked fine with me, here in Brazil.
The original visitor.js identified my city correctly; this only put me in the USA. Is there a free reliable precise geolocation service that can take as many hits as a script like this could throw at it?
Your best bet is html5 geolocation + modernizr.js + a shim. Browsers that support html5 geolocation will return highly accurate results while those that don't support it will fall back to calling the google maps api (ip to geo). https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-Brow...
Better off getting the free version of the MaxMind city database[1] and running it on a server somewhere.
Although I am probably an edge-case, I'm tethering from an iPhone on Rogers in Canada.
Visitor.js (the paid service) correctly positions me in Toronto, Canada though.
after reading visitorjs.com thread i asked myself WHY Question: who would pay 10 bucks a month for using a js file for 30K requests?
Earlier quoted context omitted.
In that case, this implementation really should have a different name. It's confusing to have two competing implementations share the same name, and it may be a trademark violation.
>" and it may be a trademark violation. " "visitor.js" isn't distinct in the field, particularly as it's descriptive and of a common form, I'd warrant it's not novel either. That doesn't mean that you wouldn't be sued for using it just that any sane TM office shouldn't allow it to be registered and that a sane IP judge should dismiss a case brought against it's use as passing off. The law isn't sane of course .... I…
The fork of OpenOffice.org was named LibreOffice, because it would be unfair to name a competing product with the same name. I'm glad the author of this library has decided to do the same.
location is either "null" or "err/google" for me all the time. Although I am probably an edge-case, I'm tethering from an iPhone on Rogers in Canada. Visitor.js (the paid service) correctly positions me in Toronto, Canada though.
Earlier quoted context omitted.
Your best bet is html5 geolocation + modernizr.js + a shim. Browsers that support html5 geolocation will return highly accurate results while those that don't support it will fall back to calling the google maps api (ip to geo). https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-Brow...
HTML5 Geolocation requires people to opt-in, which is pretty messy. Better off getting the free version of the MaxMind city database[1] and running it on a server somewhere. [1] http://www.maxmind.com/app/geolitecity
What are the ethical concerns about using this and storing the data? If I wanted to use this on my site, should I let visitors know, or is this data fair game to store? I rather not use the location data (or any of it) if there could be an issue.
You should always tell your users what data you gather and how you use it. If you only let the data stay in the browser and never send it to the server then tell them.
where's the server stuff? is google providing everything that the pay service did, but for free?
Google provides it as an extra for the JSAPI, no telling how long it will last, though.
Earlier quoted context omitted.
Your best bet is html5 geolocation + modernizr.js + a shim. Browsers that support html5 geolocation will return highly accurate results while those that don't support it will fall back to calling the google maps api (ip to geo). https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-Brow...
HTML5 Geolocation requires people to opt-in, which is pretty messy. Better off getting the free version of the MaxMind city database[1] and running it on a server somewhere. [1] http://www.maxmind.com/app/geolitecity