“groovy mother...”

Through the medium of OAuth and APIs, safely links your FourSquare checkins to your FireEagle account.

Now if only there was anything that actually *used* FireEagle’s data. (Beyond the little box on the right hand side of my blog frontpage)

This is good: The underlying goodness of OpenID, used in a way which completely hides itself from the user.

Google announce alpha OAuth support, a day after Yahoo announce they’ll be rolling it out. Giving your password to an untrusted site just became even dumber. “This is our first step towards OAuth enabling all
Google Data APIs.”

Simon Willison knocks out a quick prototype showing Wikipedia articles related to your current location, a masterpiece of mashuppery.

Pretty much inevitable — An app that asked for your GMail username & password was harvesting them. One point to the “Why we need OAuth” party.

The OAuth spec is finalized. Let the mashing-up commence!

Simple test OAuth server which has a predefined list of keys and tokens, so you can test your client implementations against it. Handy.

Blaine at Twitter has implemented OAuth authentication, the first (I believe) live implementation on the web. I hope to have this rolled into Twadget in the next week or two, so I can stop asking for usernames and passwords.

Excellent summary of what “OAuth” is, who’s behind it, and why you should pay attention to it if you build webapps.