3 ms·

Hi, We made it so that you don't have to stop using Gravatar, but can expand to include other services. Probably the biggest win, though, is that you can also

• drivebyacct2 14y ago
  I guess I am still confused. I don't mean to belittle what you're doing, I just don't understand the value it adds for me. I suppose maybe your gems or prebuilt packages make it more transparent, but at the end of the day, my code still has to know whether to load avatars.io/{facebook,twitter,gravatar} etc, thus there isn't really a significant layer of abstraction? (Like I said, really just trying to wrap my head around it here)
  • gregarious 14y ago
    I think if your app is based solely on email addresses now, Gravatar will serve you well. When we started building this service, a lot of people wanted a simple way to handle their own avatars - that is letting users upload their own photos and not send them to Gravatar to do that. That's likely the biggest win for everyone. Also, a lot of apps are using more than email now so our goal is to offer that as an option. Being able to simple ask someone which avatar they want to use and storing that, as opposed to just an email gives the users more options - and we'll keep track as they change their avatars. Not sure that clarifies it much, but that's a big part of how we built this particular solution.
    • timjahn 14y ago
      "I think if your app is based solely on email addresses now, Gravatar will serve you well." Not necessarily. We're using emails as the identifier for matchist.com but based on some initial research (you can easily determine if an email has a Gravatar image associated with it), not everybody has a Gravatar.