Seems to be conceptually similar to Android’s intents: an application registers itself to handle a particular action, avoiding the O(m.n) development effort of hooking everything up to everything else.

‘The solution we've used is to build a presenter for each model, solely responsible for building the json.’

A walkthrough using RABL.

‘This stuff is a big deal. If a user doesn’t want some superficial Kanye West app to read and download all of her private direct messages, she should be able to expressly restrict that. The same goes for apps tweeting from her account.’

‘BadAPI allows you to simulate misbehaving APIs. This is useful if your site relies on the availability of service X, and you want to ensure that any downtime experienced by that service has minimal impact on your own application.’

‘Grit gives you object oriented read/write access to Git repositories via Ruby. The main goals are stability and performance.’ Used by GitHub.

Someone in the audience at Ruby Manor mentioned this. It’s a library to simplify handling web services.

I’m pretty sure that no-one understands exactly what REST means except Fielding himself, and he can’t explain it to others adequately.

It can do QR codes!

Looks genuinely useful: give it a resource URL, and it will tell you how to embed it into your page.

YouTube API interface. Might be useful for my video jukebox idea.

A lightweight web service protocol.

Ruby interface to Google Spreadsheet.

Online Cocoa reference.

Presentation on BBC programmes, unique identifiers, and URLs.