-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reenable gravatar fallback #148
Comments
Will look at that one and send PR. |
I've enabled gravatar support in hroncok@57040d5 But this code overwrites it
Is there a way to know if this has failed and is serving default pic? Cause I don't think so :( So this might only be possible to use once pyDNS thing is solved? |
See here under "default url for missing images" - http://wiki.libravatar.org/api/ We could:
The trick we never quite got working was to "triple fallback", direct users to libravatar.. if the image isn't there, have libravatar send them to gravatar... if the image isn't there, have gravatar send them to https://badges.fedoraproject.org/static/img/badger_avatar.png |
FWIW, pyDNS finally got branched for el6, so python-pylibravatar is making its way through epel-test. https://apps.fedoraproject.org/packages/python-pylibravatar/overview/ |
Change Stable karma to 1 and let me check it in virtual machine with CentOS :) |
--enablerepo=epel-test ? 💃 |
Yes, if you can do this on a machine, where this runs. :) |
It used to be that we would first check libravatar for an image, if that failed we'd fallback to gravatar, and if that failed we'd fall back to the fedora logo.
One week before flock, I broke that (commented it out) because I realised that using OpenID as the key for libravatar was way better than using [email protected] as the key.
That gravatar fallback code should probably be re-added. We'll have to still use http://USERNAME.id.fedoraproject.org for libravatar and [email protected] for gravatar. Tricky, not impossible.
The text was updated successfully, but these errors were encountered: