cac.ophony.org

“Everyone is reading short-form text. Literature has not made that jump.” This is a key line from a recent NYT article “Serving Literature by the Tweet” which concerns a new literary magazine Electric Literature. The name of the magazine startled me at first, as I’m a big believer in the old fashioned way of reading literature precisely as a long-form text printed on a page where I can make notes in the margins. The editors of this new magazine, Andy Hunter and Scott Lindenbaum, make their texts available in multiple mediums: print, Kindle, e-book, iPhone, Twitter, and even audio books. They publish such well-known authors as Michael Cunningham, Colson Whitehead, Lydia Davis, Jim Shepard.

As I continued reading the article, I realized, despite my initial reservations, how promising this project really is. For instance, the authors are asked to select a line from their work to be animated and posted on YouTube. This is a new and very creative form of literary expression that allows for imaginative possibilities and, as Michael Cunningham pointed out, “maintain[s] the integrity of the written word and extend[s] its range.”

I was reminded of a few students in our in-class workshops in the past few weeks whose eyes were constantly on their iPhones. The same happens on the subway, in gym classes, etc. As much as I’m reluctant to accept the pervasive presence of the electronic world, I must admit that it can indeed create what Rick Moody has called “new envelopes for [literature’s] message.”

As an editor for the Radical History Review, I spend a lot of time counting characters (text characters that is).  Duke University Press, the publisher of the journal, allows a fixed number of journal pages per volume.  Short of typesetting an article, the most accurate way for RHR editors to estimate the length of a given article or entire issue is to count characters (yes, spaces count, and so do footnotes).  Occasionally we have a space crunch toward the end of a volume and the pressure is on.  If there is a huge overage, the game is political, determining which authors might be willing to postpone publication of their piece to a later issue.  If it is a smaller amount, authors and editors are forced to tighten the text or remove/shrink images.  It doesn’t take long before the cutting war becomes a word-by-word battle where every character counts (and the hefty penalty fee assessed by the publisher for overage looms large).  When we begin constructing an issue, the 600,000+ character space seems vast,  but as it comes down to the wire claustrophobia sets in.

Unlike a Twitterer bending to duck a 140-character limit, the journal author/editor can go only so far with creative solutions since the text must adhere to the Chicago Manual of Style and Merriam-Webster Dictionary.  Although the dictionary is growing it doesn’t allow for the creative abbreviations being pioneered by twitterati.  It usually means following Strunk and White’s advice: “Omit useless words.”  Not surprisingly, the intense editing done under the character-limit gun tends to yield excellent results.

As we help our students discover the value that comes along with the frustrations of editing, I think that space constraints can play a valuable role.  When a student shortens a text or tweet, they are employing some of the same skills necessary for communication efficiency in other contexts.

New technologies are not the first to put a price tag on characters.  An Op-Ed in the New York Times over the summer pointed to some humorous abbreviations invented by penny-pinching telegraph senders facing 15-character and 10-word limits.  I am intrigued by the expressions that the editors of the “The Anglo-American Telegraphic Code” (1891) deemed worthy of inclusion.  Some of them are not phrases I see often these days (“can you recommend to me a good female cook,” abbreviated “CRISP”); others are (“taxation is oppressive”, “ORGANISM” for short).

Here is an excerpt, including some other abbreviations you may choose to use in your next tweet:

ABANDONEE Abandoned in a sinking condition
ABETTING Everything depends on the ability with which it is (they are) handled.
ABUSAGE His (their) absence is rather mysterious.
ACESCET Has met with a trifling accident.

I see that this post is already at 2775 characters, so I best stop here.

Following the conversation via Twitter. Photo by Alan Levine.

If you attended the Symposium on May 1, you no doubt saw that Twitter played a major part in the event: as a topic of conversation (as in Gardner Campbell’s session), as a means of broadcasting what was happening over the course of the day, and as a way to connect with others out there in in the Interwebs interested in what we were talking about.

Our friends in media services wheeled over a beautiful 46″ flat panel display, which we used with Twitter Camp to display all tweets tagged #blsci as they came in. By the end of the evening portion of the event, there were almost 300 tweets on the Symposium from attendees as well as a few other folks chiming in or sharing our tweets with their networks. (See Boone Gorges’ great post on the use of Twitter as a backchannel at the Symposium for more on the impact of microblogging on the day’s conversations.)

Naturally, we wanted a record of all this and started looking into ways in which to pull all #blsci tweets and save them for posterity. Unfortunately, there was no one good option. The native Twitter search was ok, but only returned a few tweets at a time. Twazzup was very nice but only returned about 100 tweets. Hashtags.org returned even fewer results grouped according to no clear logic at all. (These sites are fine for following tweets live, but not so much for archiving old ones.) A Twitter contact in Texas suggested a Python script (scary) that didn’t quite work right either.

Then, our good friends Lucas Thurston and Zach Davis of Cast Iron Coding, the genius code-poet developers of our Video Oral Communication Assessment Tool (VOCAT), came up with a solution: a simple PHP script they called Tweetripper that dumped all the tweets we needed to a text file. When we ran it, Tweetripper, which came with simple but thorough instructions, gave us something that looks like this (these are just a few of the day’s tweets in reverse chronological order):


#blsci Elbow suggests we should learn the skill of ignoring audiences during speaking/writing. Says @jeffjarvis closed eyes during talk.
TiffanyPR
Fri, 01 May 2009 17:56:08 +0000

Elbow: first audience when writing must be yourself. #blsci
lwaltzer
Fri, 01 May 2009 17:50:59 +0000

A Twitterati gallery has emerged at the rear of the audience at #blsci. This might be related to the need for outlets.
boonebgorges
Fri, 01 May 2009 17:48:05 +0000

Afternoon speaker, Peter Elbow, is taking the stage. Author of "Writing With Power: Techniques for Mastering the Writing Process."; #blsci
TiffanyPR
Fri, 01 May 2009 17:48:01 +0000

Wish I was at #blsci!
katemo
Fri, 01 May 2009 17:36:52 +0000

Fantastically stimulating conversation at Baruch Communication Symposium #blsci. Boring academics? Nay. They are the Twittelligentsia!
alberrios
Fri, 01 May 2009 17:10:04 +0000


Perfect. Just what we were looking for: a way of creating a record of all the furious tweeting from a remarkably stimulating and memorable event.

Zach and Lucas wrote this script absolutely pro bono, in the interest of others out there like us interested in a way to archive tweets. They created something the community wanted and shared it, enabling others to tweak it and adapt it and develop it further. That is the spirit of open-source right there. So, in that spirit, here is the Tweetripper script for those not afraid of a command line interface. Use it well. If you modify it, let us know.