""

slick use of dividing the page to give code examples in context

"It’s simple to make requests to Rdio’s REST API. It’s built on widely used standards and conventions so there are libraries for most common web development platforms. All method calls are made as POST requests to http://api.rdio.com/1/. Arguments are sent as application/x-www-form-urlencoded, just like when a browser submits a form. The name of the method is passed as the ‘method’ argument. [Emphasis mine.]
What’s wrong with this? Well, the first bolded point is immediately contradicted by the ones that follow. Specifically, this cannot be a REST API, because it uses only one URL and one HTTP method. Two of the key features of HTTP-based REST are that

It’s object-oriented, where objects are identified by URLs. Each request’s URL identifies what object it operates on.
The methods to invoke on the objects are primarily indicated by the request’s method (GET, PUT, POST, DELETE). In fact this is why Tim Berners-Lee used the word “method” in the HTTP protocol in the first place."

"diagram was featured in Dan Brown's (excellent) book Communicating Design (Chapter 6, on page 159.)"

"One of the last things I did before leaving Plaxo was to implement PubSubHubbub (PuSH) subscriber support, so that any blogs which ping a PuSH hub will show up almost instantly in pulse after being published. It’s easy to do (you don’t even need a library!), and it significantly improves the user experience while simultaneously reducing server load on your site and the sites whose feeds you’re crawling. At the time, I couldn’t find any good tutorials for how to implement PuSH subscriber support (add a comment if you know of any), so here’s how I did it. (Note: depending on your needs, you might find it useful instead to use a third-party service like Gnip to do this.)"

"A plugin template for making plugin development as easy and simple as possible. Only 4 steps to make a simple plugin, by editing 2 files (PluginDefinition.h and PluginDefinition.cpp) : 1. Define your plugin name in "PluginDefinition.h" 2. Define your plugin commands number in "PluginDefinition.h" 3. Customize plugin commands names and associated function name (and the other stuff) in "PluginDefinition.cpp". 4. Define the associated functions."

"Here is a 2-legged OAuth Javascript function that makes it easy to get YQL results into your Javascript application."

nice howto for beginners, demystifies the OAuth process with code examples.

asynchronous library to monitor changes. next level ahk programming.

a pipe that will take all feeds listed in an OPML file, aggregate all of the items therein, and return the results.