17 Comments


  1. Worst thing about Gravatar is that you can’t delete the account once you have created it. I learned it the hard way.

    Reply

  2. This looks pretty cool. Wondering how it works exactly? Does it hotlink to Facebook’s avatar? Or does it actually save a copy of the file locally?

    Reply

    1. Henry, I am glad you liked it.
      To answer your question, no it doesn’t save a copy of the image locally. It uses the handle of Facebook/Googleplus account to fetch the profile picture hotlink with dynamic sizes.

      Reply

  3. This looks promising but am concern on the impa ct it will have on my blog

    Reply

    1. If your blog have author gravatar in it, then it will give your blog a sprint of freshness. :)

      Reply

  4. Minor problem with the Google+ avatar code: You’re making a request to the Google+ API to get the picture information, which is fine. But you’re using your own key to do it instead of having a site use it’s own key.

    This is an issue because normally these requests are limited to 10,000 API calls per day for the free versions of them. If a bunch of people use this plugin, you could rapidly run out of requests.

    Additionally, you’re using direct curl calls and not the wp_remote calls to make these requests, which means that this won’t work on sites without curl available to them.

    Additionally, you’re making this same API hit on every request to display said avatar, with no caching around it. This will exceed the limits fairly rapidly, the returned data should be cached for at least a day or two before making the same request again. You could use a transient for this, or usermeta would be appropriate in this instance.

    Just a few points. It’s relatively easy to make code in WordPress interact with external services APIs, it’s a lot trickier to make them scale as well.

    Reply

    1. Thank you so much Otto for scrutinizing my work. You totally make a lot of sense, I will start working on making the plugin better. Thanks again for the points :)

      Reply

    2. Those are fairly significant issues, Otto, and enough to encourage me to wait for Maruti’s next version. Thanks for pointing this out.

      Reply

      1. I totally agree with this, I am working on this and will update about the version which has all these fixed :)

        Reply

      2. Hi Tammi,

        I have made changes as per Otto’s suggestion and have taken off the curl call and replaced it with wp_remote_get and also have implemented a cache functionality to make the API calls every 48 hours and also have provided a clear cache button to get the immediate changes.

        Hope you would like to check the latest version which is 1.4.

        Thanks

        Reply

  5. Simply, one of the most wanted feature on my list! I always thought how nice it would be if we could pick from any social profile.
    Nice work Maruti.

    Reply

Leave a Reply