I have a paper out this month in the American Archivist with my friend and former UT Austin colleague Tim Arnold. The paper centers on best practices for collecting and preserving a collection of tweets, and looks specifically at a collection culled during the protests in Tahrir Square in early 2011. We dig into the difficulties of scoping search terms and users (in the context of the Egyptian Revolution of 2011 and more generally), the constraints of the Twitter API, and how to contextualize the harvesting of thousands of tweets through that API.
Many thanks to the original researchers for collecting the data and to the American Archivist for their interest in the paper.
Preserving the Voices of Revolution: Examining the Creation and Preservation of a Subject-Centered Collection of Tweets from the Eighteen Days in Egypt (SAA) (CU Scholar)
Jon Ippolito, from an interview with Trevor Owens at The Signal:
Two files with different passages of 1s and 0s automatically have different checksums but may still offer the same experience; for example, two copies of a digitized film may differ by a few frames but look identical to the human eye. The point of digitizing a Stanley Kubrick film isn’t to create a new mathematical artifact with its own unchanging properties, but to capture for future generations the experience us old timers had of watching his cinematic genius in celluloid. As a custodian of culture, my job isn’t to ensure my DVD of A Clockwork Orange is faithful to some technician’s choices when digitizing the film; it’s to ensure it’s faithful to Kubrick’s choices as a filmmaker.
As in nearly all storage-based solutions, fixity does little to help capture context. We can run checksums on the Riverside “King Lear” till the cows come home, and it still won’t tell us that boys played women’s parts, or that Elizabethan actors spoke with rounded vowels that sound more like a contemporary American accent than the King’s English, or how each generation of performers has drawn on the previous for inspiration. Even on a manuscript level, a checksum will only validate one of many variations of a text that was in reality constantly mutating and evolving.
In my own preoccupation with disk imaging, generating checksums and storing them on servers, I forget that at best this is the very beginning of preservation; not an incontestable “ground truth” of the artifact.
I just finished reading Anna Anthropy’s ZZT, from the Boss Fight Books series. While I have a few issues with the book, I was really happy with her work and felt that it struck a great balance between personal narrative and game history.
On the latter, I’m especially happy that the author has taken pains to convey the culture surrounding the ZZT game and its creation tools. There are two reasons for this which tie well into game preservation.
First, it’s a prime example of discussing games and game development outside the context of entertainment. I previously linked to Jaroslav Švelch’s article in Game Studies, “Say it with a Computer Game”. Anna Anthropy’s book demonstrates how a game (in this case ZZT and the games made from its toolkit) facilitated groups, rivalries, skill demonstrations, personal expression, cultural commentary, and so on.
It’s also a great example of looking beyond gameplay as the final result of game preservation. I recently attended the Born Digital and Cultural Heritage conference in Melbourne, put on by the Play It Again group there. In his keynote Henry Lowood emphasized looking to end products of the preservation process beyond playing the game, such as recordings of play, narratives of play, the cultural materials surrounding the game, etc. ZZT preserves some of the experience of play, and of being enmeshed in that culture, through a wonderful preservation technology that goes criminally under-emphasized: writing.
(As a further example, if you download Stanford’s DOOM collection you’ll have the shareware copy of the game, but along with that you’ll find a wealth of artifacts surrounding the game: .WAD collections, web pages and fan sites, articles, reviews, forum user threads, and the like (and I will add, many copies of beta and alpha versions of the seminal shooter, which I have argued before ought to be a key priority for game archives). It’s an excellent resource and any researcher would want to move through this collection as a way to understand the game and some of its critical context.)
Noam Schieber at The New Republic:
Like too many other computer prodigies of his generation, Aaron Swartz was used long before he was invented. He hadn’t lived long enough to know that not every mistake he made would reverberate for all time or haunt him until the end of his days. In this, he was not so different from any other teenager who sweats the pop quiz he failed or the fender he banged up. What distinguished Swartz was that, from a young age, he was handed a fantastically powerful set of tools—“you can do magic,” he would exhort his fellow programmers—and told it was his destiny to create a more free and just society.
For Swartz and his fellow computer prodigies, this was a deeply isolating existence.
I find Schieber’s article from last year a welcome addition to much of the coverage of Swartz’s life and career.
From Persuasive Games by Ian Bogost:
Previously, I have argued that videogames represent in the gap between procedural representation and individual subjectivity. The disparity between the simulation and the player’s understanding of the source system it models creates a crisis in the player; I named this crisis simulation fever, a madness through which an interrogation of the rules that drive both systems begins. The vertigo of this fever — one gets simsick as he might get seasick — motivates criticism.
Procedural rhetoric also produces simulation fever. It motivates a player to address the logic of a situation in general, and the point at which it breaks and gives way to a new situation in particular.
Roberto Simanowski interviewing David Golumbia:
I have begun some work in which I try to disambiguate the “technical” definitions of “hacker” from its actual deployment in social discourse, and my tentative conclusion is that “hacker” means something like “identified with and desirous of power, and eager to see oneself and have others see oneself as possessing more power than others do.” That isn’t what I see as a welcome political formation.
Interview at Dichtung Digitalt