[wp-meta] [Making WordPress.org] #613: JSON output/endpoint(s) for profiles.wordpress.org

Making WordPress.org noreply at wordpress.org
Thu Sep 18 20:45:20 UTC 2014

#613: JSON output/endpoint(s) for profiles.wordpress.org
  Reporter:  stephdau     |      Owner:
      Type:  enhancement  |     Status:  new
  Priority:  normal       |  Component:  Profiles
Resolution:               |   Keywords:  needs-patch

Comment (by nacin):

 Replying to [comment:3 stephdau]:
 > Works for me. Thanks for the feedback!
 > Also: MD5 hash of email: I just had a duh moment... Let's just make that
 field their Gravatar URL (currently displayed on front end), which will
 contains said hash (and be a grav :) ).

 There's a wrinkle here, technically — http://www.gravatar.com versus
 https://secure.gravatar.com. You could pick one based on whether the
 request (which presumably would support JSONP and also have Access-
 Control-Allow-Origin: *, for the purposes of JS use) is over SSL or not.
 Also note that "subdomain" could be www, 0, 1, etc. Core actually does
 toggle between 0 and 1, but that's likely not necessary here. Barry's
 preference is 0 over www. (Also note, sharding should not be used for SSL
 requests as the handshake is slower.)

 I just dealt with this for the plugins info endpoint but it should be a
 little easier as here you're not also trying to determine whether the
 admin is over SSL (not just the request).

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

More information about the wp-meta mailing list