Still, it was implemented miserably. The solution is worse than the problem. Why does WordPress get to hijack Gravatar credentials? And the error message it gave was completely useless...The first one didn't even mention wordpress...it just said you had to log in. To what?! Someone must have realized that was a miserable message because it got changed to include WordPress. But many of us were left wondering why we had to log into wordpress when the email address we were using had no affiliation with any wordpress accounts. Perhaps an error message including a link to where you needed to log in with at little note: Don't have a WordPress account? Enter your Gravatar credentials. Why not put one of those tiny little icons for a gravatar log in?
Many blogs have a moderation policy for first time posts, so using an alternate address with no gravatar wasn't an option either.
Really really bad implementation. You folks have access to a huge user community--you couldn't ask folks for feed back? If you didn't want any input, the least you could have done was warn blog owners that you were going to do something drastic. For over 24 hours, numerous blogging communities were completely in the dark, guessing at what the problem could be. What a waste of time.
So much like FaceBook lately--implement something that messes up users and then claim you thought you were doing a good thing.