For a project I’m working on, I’ve been looking at a lot of web service authentication/verification APIs lately. I thought folks might be interested in the results. Here are the methods available for a variety of web services/applications online, with links to their appropriate docs:
There are lots of “conversation platforms” out there, and more arriving daily. FriendFeed, Twitter, Facebook, Google Reader (now that it has commenting functionality); you name it. These systems are all great for getting your content out there and exposing more people to it, but the problem (in my opinion) is that it becomes really hard to follow the conversations on all of these different platforms. They all generally act as either a kind of content aggregation platform (e.g. FriendFeed/Google Reader), or as a unique content creation/delivery system, which is heavily used to redistribute existing content (e.g. Twitter). With all this aggregating going on, why not do the same thing in reverse? Mashable has just started doing something along these lines and that prompted me to finally publish this draft post.