Pavatar is a specification as opposed to a service like Gravatar, but the objective is the same – one consistent avatar.
Since it’s a developing specification I felt the need to add my two cents, here’s what I posted in their forum:
First of all, I’d like to submit my vote to stick with term “avatar” rather than pavatar (or gravatar or favatar or whatever). So in my humble and naive opinion it should be:
Furthermore, I think it would be cool if the Pavatar spec supported Gravatar! Since Pavatar is a spec and Gravatar is a service the two should be complimentary.
It’s already possible since Gravatar generates a consistent URL for your avatar you could always use that in the X-avatar header or link href attribute.
But I would take it one step further: the URL could be mailto:… and then the consumer would need to convert that to a Gravatar URL (their algorithm is published, it’s an MD5 sum).
One could even take this another step further, and add base and method attributes to link that would identify the base of the URL and the hash method to convert a mailto: href. Although in the HTTP headers we would then need X-avatar-url, x-avatar-base, and X-avatar-method.
For example, for Gravatar you’d have something like:
I hope you don’t mind my jumping in like this, I sure hope Pavatars work out ‘cuz I’m in favour of anything that consolidates my profiles.
Hopefully this all leads to something soon!