[buddypress-trac] [BuddyPress] #4571: Changes in Gravatar APIs result in failed fallback on default avatars

[buddypress-trac at lists.automattic.com]

#4571: Changes in Gravatar APIs result in failed fallback on default avatars
--------------------------+--------------------
 Reporter:  boonebgorges  |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  1.6.2
Component:  Core          |     Version:
 Severity:  major         |  Resolution:
 Keywords:                |
--------------------------+--------------------

Comment (by DJPaul):

 I've seen this in a dev environment using a mapped hostname, and today I
 found a report on the bporg forums. This obviously has backpat concerns
 but I'm not sure if we can do anything.
 http://buddypress.org/community/groups/miscellaneous/forum/topic/what-
 is-i0-wp-com/

 Another idea which I'm pretty sure we've discussed before: set a usermeta
 flag for users who have uploaded a "BP avatar" to avoid the gravatar.com
 lookup. Seems simpler than making a ton of HEADER requests to gravatar
 just to see if it would return a valid response or not. I'm not fond of
 this approach anyway -- a slow internet connection from the server to
 gravatar could impact page load times.

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/4571#comment:1>
BuddyPress <http://buddypress.org/>
BuddyPress