I have my picture on Gravatar and i would like to have this option. We all have our pictures on gravatar. why not use it and make it easier to set up pictures on jd. I can work on this feature, but before i do, i wanted to know others opinion on this one.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
This would definitely be a good feature to have. For users to come straight onto the site with their picture there and ready to go would really make things simple!
Found This: https://github.com/mdeering/gravatar_image_tag
Problem is getting it to work with local images as well. Any ideas?
As an additional option for a profile image, this would surely be useful.
But considering that the profile picture has to federate to other pods and also keeping in mind the current work on the new profiles, it would be best if you discuss architectural aspects of this feature directly with the team, so that you don't do any work that you'd have to re-do for changes that might happen in the near future.
Also, the other feature request (#1166) regarding gravatar was most certainly closed because of our Feature Request Guidelines
Just noting that I see this more as a nogo as it would either cause confusion why the picture isn't set on other pods or the email address would need to federate onto other pods which is not a good idea IMO.
@liamnic It's actually pretty easy to setup Gravatar. So much so that i doubt you need for Gem for that :). @Raven24 I will perhaps discuss this with the team on the Mailing List and on irc.
@MrZYX Could you guys please tell me what exactly do you mean when you say different pods ?
A pod is what we call an production setup, a server running Diaspora. The profile is federated to these other pods, the user records aren't, so no pod but the one the user signed up at knows the email of a user (which is a good thing).
So basically you'd need to find a way to display the profile picture on say both joindiaspora.com and diasp.org. Say the user signed up on joindiaspora.com that is the only pod with the email address. So you'd need to find a way to display that picture on say diasp.org (or any other pod for that matter) WITHOUT sending the username to the other pod's. I agree with @MrZYX that thats the biggest downfall of gravatar.
Well, the profile picture path is saved in the database as a complete URL, so that's the place, where you could put the Gravatar image URL. But I don't know if that URL is also communicated to other pods or if it is generated according to the origin of the image and what not... You're going to have to do some digging there.
The email address wouldn't need to be federated, just the Gravatar URL (or at the very least, an MD5 hash of the lowercased email address, since the Gravatar URL is based on that).
@ktkaushik Gravatars are simple when you're not dealing with issues like federation, no need for a gem, check out Michael Hartl's Rails Tutorial for an example of an extremely simple gravatar_for view helper. 😁
@Raven24 I don't know a lot about how federation works, but considering that we can use our Facebook or Twitter photo as an avatar I'd assume the URL is being federated to other pods. If that's the case, supporting Gravatar shouldn't be much more difficult than supporting Facebook and Twitter.
@MrZYX I get it what you mean by a Pod. If the email is not going on to diasp.org, then there has to be some other unique identification for a user.
@stevenh512 I have used Gravatar in an earlier project of mine. We can always create a helper which would use Gravatar api. Also, the api would anyway send a photo and nothing else. :)
@Raven24 I think that the idea of storing the Gravatar URL should work.
@liamnic i think that is going ot be a little difficult.
For anyone else who is wondering what kind of URL then here is an example.
Gravatar api would return you the image object based on the email address.
We can store this object or hit the URL every time while reloading the page by a helper method.
Has there been any progress towards this issue? I am asking because I am developing a WordPress integration with Diaspora called Diasposter and I'm wondering how best to deal with user avatars now. WordPress uses Gravatar out of the box, so if Diaspora did, too, it would cut down on the amount of code I need to write for the integration. I do understand that Gravatar is centralized and that this is a potential problem. At the moment I am just saving the avatar image URL reported by the pod in the WordPress database along with the content of the object I am integrating with. This will work but will also mean that if a user later changes their avatar picture, the metadata of all the objects they created (like comments) will have to be updated if the new avatar is to be used.