Klout Klock - Using Netduino to display your Klout
Klout is a fairly new (to me anyway) service that measures your social interactions, reach, etc to calculate your Klout Score. The higher your score, the more clout your believed to have. I've even heard reports that for social related job interviews, Klout Scores are being asked for...
Being geeks, wouldn't it be cool if we could build a piece of hardware that reaches out to Klout web services, gets our score and then displays it? Maybe using Netdunio?
Curiously, it turns out that the Klout team has come up with a set of metrics to do just that. If you have a Twitter, Facebook or LinkedIn account, you should try to link them to Klout to understand how this works: in a nutshell, Klout applies a set of algorithms, similar to Google’s page ranking algorithm, to your interactions and relationships within social networks and comes up with a synthetic score on a scale of 1 to 100, representing your overall influence a.k.a your “Klout Score”. A “Klout Score” is itself broken down into multiple data points, described in details here.
Klout’s metrics are interesting from a self-development standpoint because they can be used as a feedback loop: with them, you can evaluate within days or hours the effect of your communications, measuring what works vs. what doesn’t and learn to focus a message in the areas where it will resonate with a target audience. This is a valuable tool for individual bloggers and businesses alike.
Building a Klout Klock
Klout exposes a web service enabling developers to build mash-up applications around its metrics and all that is required to play is an API key which is easily obtained when registering an application. My application is the “Klout Klock” device and before getting into the details of building it, you can see it how it works in this video:
To get around the limited RAM in the Netduino Plus, the project shows off using an SD card as virtual memory...
Using an SD card as Virtual Memory
The Netduino Plus, in addition to its Ethernet connector, features a handy micro SD card reader for storage which I turned into virtual memory to get around the RAM constraints.
The virtual memory concept is straight forward: instead of reading and writing to/from a RAM buffer matching the size of the AdaFruit TFT display, all reading and writing operations happen against a file whose size matches the size of the display. In this case, that file is exactly 40960 bytes, the size required to hold a 128*160*16 bit/pixel image.
To actually refresh the screen with the image contained in virtual memory, the physical display is updated in ‘segments’, reading the data for each segment into a small RAM buffer, then blasting its content over SPI to the display. For each segment update, a display address window is positioned to cover the proper range of pixels.
The trade-off here is speed since file I/Os are orders of magnitude slower than operations in RAM but speed is not the main concern in this scenario. In addition, the more memory segments are used to chop up a virtual memory block, the slower it gets.
Finally some code...
For folks interested and actively participating in social networks, for fun or for profit, Klout has valuable insights to offer. As Klout integrates their services with more and more social networks, the relevance and accuracy of their metrics is bound to improve as well. Given their overlap, focus and methods, I would not be surprised if Google acquired Klout one of these days.
Here’s a few more links you might find interesting:
- Getting started with the .Net Micro Framework, hardware and, oh, robots...
- Six Places Where I buy Netduino and other Electronics Bits
- A Gentle Introduction to Netduino
- Netduino is opening up to an wider audience with the .Net Micro Framework v4.2 release
- Netduino is RAD
- netduino Helpers
This conversation has been locked by the site admins. No new comments can be made.