Friday 8th April, 2011
Update: Timmy lived a brief but glorious life in mid-April 2011. Timmy is offline for now, but you can see his glorious life in timelapse-tastic video below.
One of the perks of being part of Go Free Range is the opportunity to play with fun ideas for the clients we work with, but also for ourselves. This week the whole company has taken a step back from direct client work to explore some of the ideas we’ve had pinned to the wall for the past couple of months, and the first output of that is Project Codename: Timmy Printface.
Here he is, hard at work this very minute: Here’s a video of little Timmy running in April 2011: Go to Timmy’s page, and that image will update automatically, showing you the messages that he’s receiving, live and direct. It’s better than most of what’s on TV, I’m fairly sure. You can play along by texting +447716354419.
I should mention that this is a hack built on top of a beta service that we are still developing, and so we’re very sorry if your message happens to fall down a crack. Sometimes it can take a couple of minutes for your SMS to actually reach the network.
If it doesn’t appear after some time, however, let us know when you sent it, what it contained and the last few digits of your phone number and we’ll try to trace what happened and use your feedback to improve the service.
Behind the scenes
In a nutshell, we’ve taken a simple message feed from the #blue API, and with a little bit of Ruby magic and some breadboards-and-wire fun, any messages that you send to Timmy are printed out pretty much immediately.
Where #blue knows who the person is, we can print their name along with the message; otherwise it’s just the number.
Here’s what it looks like from my desk:
However, frequently these projects are about taking what is current - tweets, blogs, and other digital artefacts - and bringing them into the physical world.
What I really like about Timmy is that this is taking two old, hacky technologies (SMS was invented in 1984 as a hack itself on top of the signalling pathways used to control telephony traffic) and gluing them together using something new.
It’s like getting your grandparents to FaceTime each other.
But let’s not lose our sense of perspective; it’s a fun demonstration of a new way of dealing with your own text messages, now possible via the #blue API that we’ve been building with O2 for the last year.
The #blue api takes these messages, which have previously been trapped in your phone like prehistoric insects in amber, and liberates them. Until you’ve done it (and unless you’re a bit of a geek), you probably can’t imagine the strange novelty of being able to run a
curl command and suddenly be able to
pipe your SMSes around on your normal computer.
It’s like the first time you realised you could program, making a computer do whatever you can imagine and then describe; suddenly things become possible.
While we have always tried to provide the best possible user experience via the front end of #blue, but we’ve also always felt strongly about the potential of the API. We’re excited to see what other hopefully-but-not-necessarily more practical applications that developers start building on top of it, to give everyone new and valuable ways to make use of the messaging services provided by telcos.
The API uses OAuth2 for authentication, and your messages are always private. You are always in control of which applications can be granted access to your messages, and this access can be revoked at any time.
Here is selection of our favourite texts so far - click to zoom in, see if you can see yours!
This was an impressive rickroll attempt:
We have even received some actual art:
Beautiful, particularly given the constraints.
Keep your texts coming; send ‘em to +447716354419, lines are now closed, but don’t forget - if you’re an O2 customer, you can sign up to #blue now to help give us some more momentum in our quest toward changing how these huge companies treat your data.
If we have seen far…
It would be remiss not to mention the giants on whose shoulders Timmy is happily perched.
The original idea of connecting a small printer to a stream of information - the “Microprinter” - comes from Tom Taylor, as indeed does the actual printer we’re using, which Tom has generously loaned. You can read about his original project from 2009 here.
The Ruby library we’re using to send commands to the printer was written by Roo Reynolds, and is available on Github here. In fact, there’s a little cloister of microprinter hackery, should you want to try something out yourself.
We went from the first moments of prodding the printer to what you see now in under a day, so hopefully this is a good example of the “Making Things Fast” idea that Leila Johnston has championed. See if you can spot a message from her new “Extreme Acts of Kindness” project in the selection. She was even kind enough to mention Timmy in her weeknotes. Thanks!