Description

100pxls transforms a stream of live twitter posts into a wall of tiny 10x10 pixel images. The image shown is determined by common words in the post.
If you'd like to be in control of the image you can use the drawing area to convert an image into a tweet, and then use the button to post it.
Any standard Twitter search can be used to find images on the wall.

N.B. This app requires an HTML5 compliant browser (i.e.not IE!) such as Chrome/Firefox

Winner: HTML5 Runner-Up

Ratings Closed

Comments

Leave One!

Related Tags

Winner, HTML5, Chrome, Firefox, Safari

Your rating has been saved. To change your rating, just select a new rating and it will saved.


Comments (8)

Avatar

Chris Price

Wednesday, January 20, 2010 2:43 PM

Just a quick heads up about a couple of small bugs in the app to (hopefully!) save anyone getting frustrated - 1. Tweets containing the words "Moon" and "Acid" can show up slightly corrupted. Therefore it's probably wise to avoid posting any messages containing those words as they could end up being slightly corrupted (there's a 50% chance). If you change the order of the colours in your palette then it should be possible to still draw the same image but without either of those words. This is because I blundered when creating the underlying word list and included the words "Moon" and "Acid" twice. There should be a one to one mapping from a word to a 5 pixel pattern. However, due to the duplicate words there are two sets of two patterns that during encoding will map to the same word. During decoding, this 2->1 mapping will cause both patterns to be decoded as the same thing. 2. Search terms containing spaces will not return any results. Unfortunately there's no getting around this one. The problem occurs because of a difference in how the Twitter API encodes spaces in the query in the returned JSON and the DOM method encodeURIComponent. When the search JSON response is received, the code quickly checks to see if it contains results for the current search term (to prevent stale results due to out of order responses). The encodeURIComponent method converts spaces to %20, unfortunately the Twitter API is using + to represent spaces. The upshot is that the results are being received by the browser but are being ignored because the app thinks they're stale...doh! Anyway enough bugs, get drawing!

Avatar

Ryan Corradini

Thursday, January 21, 2010 9:58 AM

Nicely done, sir. I hadn't expected the Twit-encoding to use real words, even if together they amount to nonsense. A fun toy, in any event.

Avatar

Chris Price

Thursday, January 21, 2010 10:14 AM

Thanks! The reasoning behind the real words was to add an extra challenge of trying to come up with a proper sentence that's also a funky picture. If you fancy trying it, there are a few tricks to know about. The decoding is completely case insensitive and ignores all punctuation apart from exclamation marks. Each exclamation mark causes the previous word to be repeated (in a run length encoding type of way).

Avatar

Bruno Molloy

Wednesday, February 10, 2010 7:37 AM

Fantastic work Chris - very clever!

Avatar

Bruno Molloy

Wednesday, February 10, 2010 12:18 PM

Fantastic work Chris - very clever!

Avatar

Ueli

Tuesday, February 16, 2010 6:3 AM

Congratulations for the well deserved prize, Chris!

Avatar

Sean Gerety

Tuesday, February 16, 2010 4:42 PM

Congratulations. Great concept.

Avatar

Trey Smith

Friday, December 31, 2010 10:38 PM

You got a good page. Keep it up.

Comments are Closed