[wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results

Making WordPress.org noreply at wordpress.org
Mon May 15 22:28:42 UTC 2017

#2823: Improve IP Geolocation Results
 Reporter:  iandunn  |       Owner:  iandunn
     Type:  defect   |      Status:  accepted
 Priority:  normal   |   Milestone:
Component:  API      |  Resolution:
 Keywords:           |

Comment (by barry):

 Replying to [comment:18 iandunn]:
 > To clarify, are you thinking we'd remove the IP from the client's
 request and just use `REMOTE_ADDR` on the API side, or would the client
 still be able to specify an arbitrary IP?

 Clients can specify an arbitrary IP.  I was initially concerned about the
 privacy implications of the clients connecting directly to the .org API
 which would provide their full IP and not the truncated version that the
 current proxy approach uses.  I thought this would be the only place that
 a .org site sends the client IP to WordPress.org (as opposed to the server
 IP which is sent in many places).  However, I then remembered that we use
 the W.org CDN for serving emoji in core, so I am not sure if it's a huge

 I'm ok with any approach that satisfies the "business requirements" of
 this widget and doesn't violate the EULA for the data source(s) we use.
 The rest of the stuff like performance and scaling we can figure out
 pretty easily.

Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:19>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list