[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 johnjamesjacoby):

 Replying to [comment:7 modemlooper]:
 > Why even use Gravatar? Most people dislike it.
 Because it comes baked into !WordPress, we get a huge avatar distribution
 network for free, and it serves billions of images every month.

 Per a Skype chat, I think this is an educational issue about keeping the
 default Gravatar publicly accessible for 1.7. Later on, we can store the
 URL to the user's Gravatar in usermeta, and perform whatever logic we need
 in a BP_Avatar class. It's a complicated enough piece of code that it
 deserves its own architecture.

 Since !BuddyPress doesn't load avatars without some kind of
 user/group/blog information available to it, we should have already
 queried that object, cached it's results, and have nothing to lose by
 keeping an avatar URL in meta.

 Let's move this to future release for now, and revisit it later?

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