Listen to This Week in Ontario Edublogs on voicEd Radio

Follow me on Twitter

What’s in a Tweet?

If you have been following the news, I’m sure that you’ve been at least mildly interested in the story coming from the Bronx Zoo about a missing cobra. WPIX has the story on their website. Someone with a great sense of humour has created a Twitter account for the snake. You can "follow" the snake at @BronxZoosCobra. The tweets coming from this account are hilarious.

So funny, in fact, that I sent out a Twitter message indicating that this account was one of the best follows on Twitter right now.

He/She has one of the great avatars and a really good sense of humour. Even if you decide not to be one of the thousands who are following the account, at least click this link and see what the snake has been saying. At least one person read my Twitter message and replied.

In other news, I was in the Google Chrome store today and noticed a "new to me" Twitter client called Streamie. One of Streamie’s claims to fame, other than running in the Chrome browser is that it updates in real time, very much like the Twitter plugin that I use with Seesmic Desktop or from the web through the Twitter website.

In fact, the first time I read the message from @jaxbeachteach, it was through Streamie. It didn’t look like the above; it looked like this.

Interesting.

You’ll notice that the layout of the message and colouring is completely different but the content is exactly the same.

I’ve always maintained that all students should take at least one course in Computer Science. There are the nay-sayers who feel that it’s not necessary. "Programming is all gobbly-gook. What’s important is being an end user and using the stuff" Really? You need to read or ponder Douglas Rushkoff’s book "Program or Be Programmed". An excerpt from the book appears here.

Back to Streamie.

Another claim to fame of Streamie is that you can configure it to see the JSON code behind a Twitter message. All that you have to do is enable it in the configuration and double click to see it. For the message above, here’s the code.

Students of Computer Science would be able to read and decipher a great deal of the above code. They would be able to understand what’s in a message. They would understand how threads are built. They would know how images are attached to messages. They would understand the twitpocalypse and how Twitter had to scramble for indexing of messages because of its own popularity. They would get a deeper understanding of how privacy and geo-locating issues are transferred in a seemingly innocuous message.

The best of Computer Science students could pull the content apart and write the code that would give a custom look to a Twitter message. Some of the very best could actually write their own Twitter client!

Those that don’t understand could point out that one is blue and the other is green. <tongue in cheek>

There really is a deeper understanding to what is happening in the device that you’re reading from at the moment. Now, not everyone who studies Computer Science is going to write the next great Twitter client. But, I would maintain that they do have a deeper understanding of what’s happening in their digital world. Do we want students to be happy with being programmed? Do we want them to grow up not being able to articulate what they’re trying to achieve or to explain when something goes wrong? I don’t think so.

Even something as simple as a Twitter message about a cobra on the loose does reveal that there’s more going on with your computer and behind the scenes than what would appear on the surface. It does make sense that we have the skills to be able to pull back the covers and have a sense of what’s happening inside.