[Bug 57126] Provide a JavaScript API for geoip lookups

2014-04-14 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=57126

Derk-Jan Hartman hartman.w...@gmail.com changed:

   What|Removed |Added

 CC||hartman.w...@gmail.com

--- Comment #4 from Derk-Jan Hartman hartman.w...@gmail.com ---
This is also used by English Wikipedia Geonotices:

https://en.wikipedia.org/wiki/Wikipedia:Geonotice

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 57126] Provide a JavaScript API for geoip lookups

2014-01-24 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=57126

--- Comment #3 from Niklas Laxström niklas.laxst...@gmail.com ---
ULS uses the country information for language selection suggestions on the
frontend.

We use the information that is already loaded on WMF sites (except for third
parties where we add a call to retrieve that info), but it could potentially be
delayed until click, but it would add to the delay of showing the language
selector widget for the first time.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 57126] Provide a JavaScript API for geoip lookups

2013-12-12 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=57126

MZMcBride b...@mzmcbride.com changed:

   What|Removed |Added

 CC||federicol...@tiscali.it,
   ||niklas.laxst...@gmail.com

--- Comment #2 from MZMcBride b...@mzmcbride.com ---
(In reply to comment #1)
 b) Deprecate the bits.wikimedia.org/geoiplookup URL and rely solely on
 geoiplookup.wikimedia.org. As a reminder, the reason that we used a separate
 top-level domain is that IPv6 city databases are non-existent, so we have to
 force users to use IPv4 by using a separate domain; depending on (a), we
 might not need this anymore, but having a separate domain gives us more
 possibilities, so let's keep that.

Bug 55907 comment 2 and documentation ([[wikitech:geoiplookup]] 
[[m:geoiplookup]]) suggest that geoiplookup.wikimedia.org is deprecated in
favor of bits.wikimedia.org/geoiplookup.

If geoiplookup.wikimedia.org is going to be un-deprecated, we'll need to make
sure that developers are aware and that the relevant documentation is updated.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 57126] Provide a JavaScript API for geoip lookups

2013-11-16 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=57126

Sam Reed (reedy) s...@reedyboy.net changed:

   What|Removed |Added

   Priority|Unprioritized   |Normal
   Severity|normal  |enhancement

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 57126] Provide a JavaScript API for geoip lookups

2013-11-15 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=57126

--- Comment #1 from Faidon Liambotis fai...@wikimedia.org ---
Thanks Ori, I'm excited to see progress in this area.

From our (techops) side I have two requests for this common API:
a) Identify what exactly is it that we need from GeoIP; we currently provide
alot of information, including city, lat long as well as a netmask that we had
to hardcode to 24 (i.e. useless) due to performance issues with libgeoip (cf.
https://gerrit.wikimedia.org/r/#/c/34280/). I couldn't identify any code that
actually used anything but country from my cursory lookup.

b) Deprecate the bits.wikimedia.org/geoiplookup URL and rely solely on
geoiplookup.wikimedia.org. As a reminder, the reason that we used a separate
top-level domain is that IPv6 city databases are non-existent, so we have to
force users to use IPv4 by using a separate domain; depending on (a), we might
not need this anymore, but having a separate domain gives us more
possibilities, so let's keep that.

Additionally, note that depending on the use case, it might be possible to do
some GeoIP lookups on the Varnish layer but instead of serving JSON, tagging
regular requests to MediaWiki with a custom header that it can be then Vary-ed
on. It looks possible we e.g. might going to end up doing that for CentralAuth.

Finally -and this falls outside of ops- it might be helpful to look at
MaxMind's own Javascript API ( http://www.maxmind.com/en/javascript ) for ideas
on what could be implemented in ours from an API perspective.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l