RED RIDING HOOD

RED RIDING HOOD is a combinatory, interactive fiction piece collectively written in twine. Our game references and draws inspiration from Colossal Cave Adventure and ZORK. Traversing more thoroughly or multiple times is rewarded with more text and multiple story endings. The narrative and structure were heavily influenced by the process of Jake and I collectively writing the work. It has game like structure and is traversed spatially like a piece of interactive fiction, while having a hyperlink structure by benefit of being made in twine.

Depending on what items the reader finds throughout the game, different parts of the story will be revealed. If you remember to bring your RED RIDING HOOD, text about your character feeling secure and warm will appear throughout the game. But if you forget your hood, whiny, shuddering text will appear throughout the cave system, and there is only one way to escape the caves. The piece is different depending on what items the reader chooses to pick up before entering the forest, and what items the traverser finds throughout the caves. The amount of choices the traverser has when encountering the goblin and Grandma increases with the number of items they find in the caves. The combinatory nature of the piece being linked to the items found while traversing rewards the reader for exploring more thoroughly. It is possible to forget your RED RIDING HOOD, pick up the hatchet and cucumber, smash the golden eggs, escape with the help of the wolf, and only have the options to offer Grandma the cucumber or tell her about the caves at the end of the game. It’s not possible to reach the end with all the items, so it is not possible to reveal all the endings of the game with just one traversal.

The piece heavily references the games ZORK and Colossal Cave Adventure. We sought to incorporate or reference aspects of interactive fiction games, such as traversing the piece spatially and problems for the interactor to solve to reach the end of the piece. Once in the cave system, the piece is traversed using a compass in the lower right corner of the page. Our game was created in twine and is a web of hyperlinks, but the cave system can be viewed as a grid like map in the twine editing interface. The caves are numbered and linked to each other, with alternate link names corresponding to where the cave is in relation to the cave the link is in. These links are arranged into a compass shape using css grid. The problem solving in this game is much simpler than the puzzles in ZORK or CCA. The traverser can use the items they’ve found when they are made available to solve problems as links within the passage text. I chose to use a hyperlink structure rather than an inventory system because it was easier for both Jake and I to make changes to the story this way, and because there would be text in the passage based on the items in the traversers inventory anyways, so it would be simplest for the link to be in the passage.

We reference ZORK and CCA in the narrative and aesthetic of our piece as well. The font and color are reminiscent of the games, but our piece has major differences in appearance from ZORK and CCA as well. There are hyperlinks within the passage text, descriptions of the cold shudder, and the caverns are navigated using a compass with links labelled as the cardinal directions rather than navigating using a text parser. The narrative and descriptions of unsuccessful moves are snarky and sometimes nonsensical, like CCA or ZORK. There are choices the player can make in the beginning of the game or while in the caverns that result in failure, as well as choices that leave the game unwinnable. It is impossible to escape the caverns without the hatchet if you forget your hood.

Our work is a piece of collective writing even though Jake and I were the only contributors, because the way we wrote the piece led to an unsuspected structure and storyline that we would not have created independently. We wrote the piece without the end in mind, though we had a common goal. The beginning of the game, before entering the forest, was written together as an in-class exercise. Beginning the project that far in advance of the due date allowed us to exchange the project back and forth many times. We added a manageable amount each time without the pressure of needing to complete a large portion, and the final version is the eleventh version of the file. We discussed the general direction of the work and occasional details, but for the most part did not know what to expect each time we opened the file. We created twists and problems for the other writer to solve that created a story and structure neither of us would have made on our own. Jake created the treasures and expected me to create a trophy case or have Grandma send RED RIDING HOOD back into the caves to retrieve the treasures, but instead I introduced the goblin to the story and created multiple ways to escape the cave system using different treasures and items. An arbitrary decision during the collective writing process made our piece multilinear, a choice either of us might not have made had we written the piece by ourselves.

The collective writing process mixed with creating aspects of interactive fiction was difficult and rewarding, because as we created puzzles for the traverser to solve, we created problems for our partner to find a solution for in the writing. The game flows from a hyperlink structure, to a spatial structure, and back to hyperlinks, and has multiple endings. RED RIDING HOOD grew into a game that neither Jake or I could have expected when we first began it.

Kinetic and Interactive Poetry


The first pieced I looked at was “Cruising” by Ingrid Ankerson and Megan Sapnar. It was a really cool and interesting way to tell the story. As you move the mouse side to side, it goes through a slideshow type strip a the bottom. When you pull the mouse up or down it will either zoom in or zoom out of the story. Although it was a really cool idea, I’m not sure I exactly liked it. It was pretty hard to control, at least for me, and the constant moving and zooming in and out actually made me feel a little nauseous. It is possible iI was just doing it wrong though. The second one I looked at was “The Dreamlife of Letters” by Brian Kim Stefans. If I’m being honest, I didn’t really understand this one either. I’ve never been a huge fan of poetry, especially poetry that is made to be confusing on purpose. I do understand the importance of poetry and interactive poetry, it’s just not really anything I think I will ever be interested in. I did try really hard on this assignment to find one of them that I did like. I went through each one but either I couldn’t figure out how I was supposed to do them, or they didn’t really make sense to me.

*EDIT* I’ve just now realized that I never got past the introduction part of “The Dreamlife of Letters”. I’m not sure how I didn’t get past it before, since I looked at it for a good 5-10 minutes. Now that I’ve explored this piece deeper, I actually really enjoyed it. I love how it flows through without anyone having to interact with it at all. Out of all of them, I think this one ended up being my favorite piece to explore through.

Like I said before, I understand that they are an important piece of history in literature, and interactive poetry is very important in electronic literature. But this is a type of electronic literature that really challenged me. I did like that there were some in video form such as “Rain on the Sea” that I found myself understanding a little more. It goes by really fast, complete with music to match the speed of the switching letters and numbers on the screen.

Gorge Taroko Gorge: Combinatory Poetry in Motion

 

While taking DTC 101, I learned about Electronic Literature. I was fascinated by the medium because I am a writer. Combinatory Poetics is style of writing that I have never heard of. While reading the text I found that it was part of the early avant-garde/ abstract art movement which I have never been a fan of. With that said, I do fine that Poems that I read to be exciting. The poem Taroko Gorge is about nature. It appears the poet admires nature. While reading the poem, the images of trees and rocks I seen while hiking last year came to mind. The poem Gorge is about the human body. It was as if the poet was a practicing coroner that was studying the human body; Da Vinci’s Vitruvian Man came to mind.

 

I not familiar with source code. To be honest, I did not understand what the heck I was looking at. I can only assume that it was generated through an algorithm. While reading the poems I kind of felt like I was the scrolling text at the beginning of Star Wars. The way to poems are presented allows the readers to be part of the action. If a few lines were missed by the reader the first time, the reader would have to read it again to fully understand the meaning of the poem. It’s kind of like watching a movie again and seeing something you missed the first time. I would like to try my hand at writing this kind of poetry.

Taroko Gorge

“Taroko Gorge” by Nick Monfort is an example of a poem generated by a computer, or combinatory poetics, as outlined in the Electronic Literature Organization’s list of existing electronic literature practices as part of their definition of E-lit. It fulfills John Cayley’s short definition of E-lit as it is “writing in networked and programmable media” and is primarily an example of writing in a programmable media. It also a good example of Stephanie Strickland’s definition of E-lit, which she says

“relies on code for its creation, preservation, and display: there is no way to experience a work of e-literature unless a computer is running it –reading it and perhaps also generating it,”

“Taroko Gorge” could not be read and would not exist without a computer generating it.
“Taroko Gorge” was originally created in Python and then recreated in Javascript so it could be viewed in a browser. The poem is created by first announcing in the program a series of lists of words, which are then returned randomly in an order determined by the type of list they are in and displayed in phrases that create a poem. “Taroko Gorge” is what N. Katherine Hayles would call “born digital” and each iteration of the poem is unique. Every instance of the webpage will return a different poem than the last. The piece is not only “not easily produced or consumed in print literary contexts” as Scott Rettberg describes in the reading, but it is impossible to produce or consume as print. One iteration of the poem could be printed and distributed as print, but the intention of the piece would be lost.
The piece is a straight forward example of combinatory poetics. Scott Rettberg describes combinatory poetics as programs that “access and present data… and then through algorithmic processes, modify or substitute the data.” “Taroko Gorge” uses Javascript create lists of data, words in the poem, and select and present them randomly to form a poem. This is a similar process to the recipe for a Dadaist poem Tristan Tzara describes, cutting words out of a newspaper and gluing them down randomly as you draw them from a mixed bag. Combinatory poetics uses computer programming languages to create Dadaist poems instantly.

Combinatory Poetics and Taroko Gorge

While examining a few different versions of the Taroko Gorge works, I noticed that many shared the same source code or framework. Nick Monfort’s original Python program was used for each of the works that I examined. Some versions, such as Camel Tail by Sonny Rae, modified the code enough that it looks like a completely different program. Sonny used blocks of text as opposed to individual words, as they were inspired by and using lyrics written by the band Metallica as opposed to individual words. The disclaimer that usually precedes the code about the original author is missing, and the names of the variables have been changed. The end result is similar enough as to be included in the list of versions of Taroko Gorge, and it looks similar when it runs, but it is different enough as to make one look closer at the code to find the common threads.

The meaning of each of the works would, I assume, vary from author to author. Each author uses similar framework but different content to generate combinatory poetry that speaks to them. Rettberg described Taroko Gorge as “ambient” (47) then went on to hack the source code, replacing Monfort’s verbs and adjectives with his own. He chose language he described as “frenetic” (48) which changed the entire feel of the work from one evoking peaceful Taiwanese scenery to an urban metropolis bristling with energy. To this end, the effect of combinatory processes on the reader are many-fold and widely variable. The uncertainty of what’s coming next can be exciting or unsettling depending on the reader. What is exciting, though, is how people and computers are working together and using one another (intentionally or not) to create these new, electronic forms of poetry that are contrived and organic at the same time.

var blog = ‘words, writing, response, questions’

 

Farinsky Blog Post 1: Combinatory Writing

Combinatory texts such as Taroko Gorge by Nick Monfort are similar in code construction to Mad Libs stories. There are defined variables which randomly propagate words from defined arrays in an established, looping sequence once the program executes. The structure, color, font, and text size are all dictated within the opening lines of code below the header. The code also includes lines modifying the names on the far right column.

The text is both meaningless, and meaningful to the right mindset. From a pure programming perspective this is simply a program executing lines of code as planed by the programmer. However, human nature often finds creativity and meaning in places apparently devoid of such on the surface. Depending on the iteration of the code the lines within the program sound mysterious and elevated in a manner expected from prose or other poetry.

There is certainly a strong argument for the original Taroko Gorge to be included as digital literature because of it’s unique output, code structure, and clear evolution from similar programs in the genre. It is harder for me to personally agree that the other struck-through versions are also “literature” because in any other setting the high levels of similarity would be considered plagiarism.

One of the modern miracles of computer science is the strong push for open-source projects- projects that allow others to see, use, and modify existing lines of code for a separate project often with the only requirement being a credit to the original creator. Momentous amounts of work have benefited from pooling the collective knowledge base this collaboration of creators has communally built. However, is simply changing the words within a defined variable array really unique work? Does adding an image, changing the color scheme, or the time between publishing lines make the hypothetical edition different enough to be considered a unique work from the original? Is the copying only adding noise or adding to the genre of digital literature?

Even if one only considers the original work worthy of the title: “literature”, does it make the copy-cats not worth archiving? Digital literature is unique that it is constantly evolving in a very traceable way. With the rise of the internet, and corresponding platforms, directed for creative literature historians have the opportunity to catalog very distinct steps in the creation, or ignoring of, genre conventions. We can look at a network of similar programs and see exactly how the source codes are the same or divergent. This gives rise to the question of how can we tell what is significant though which is an entirely new dilemma considering in print the origins of “traditional” literature are very limited due to time or disasters.

The idea of word substitution in print or online is not something new- but creators such as Nick Monfort clearly deserve credit for creating a program which emulates human poetics in a more, and more human sounding manner.

Combinatory Poetics Blog

Combinatory poetics is a form of writing that I’ve come across before but I never knew the name of. The foundation upon which it was built has a colorful cast, ranging from the seemingly paradoxical Dada group with the cut up technique, the surrealist with automatism, the Fluxus artists, etc. all helped shape combinatory writing.

Taroko Gorge serves as a representation of combinatory poetics. Taroko Gorge is a poetry generator created by Nick Montfort, as Retterberg explains in Electronic Literature, “It is a relatively simple script that produces an endlessly scrolling poem, cascading ceaselessly in the web browser until the reader closes the window in which it manifests.” (Retterberg 47)

Looking at the code, in the script section of Fred and George, by Flourish Klink, in the script section there are nouns, verbs, and adjectives. Now words aren’t completely chosen at random, there is a structure as shown in the actual poem. In the main sections of the poem, it starts with a noun, then it follows up with a verb, and then another noun. Now the words that are actually selected within the set variables are mostly random.

The picture below shows an example of certain parameters set within the poem generated to give a sense of coherence and structure.

These similar parameters can be seen the other variations as well, like in “The Dark Side of the Wall” by Bob Bonsall. The main difference lies in the fact that rather than the variables contain single words, Bonsall’s put entire sentences and questions within them. Outside of that main difference, the code is virtually the same as the other variations.

There is a basic meaning that can be taken from these poems, like for example “Fred and George” is incredibly sexual and this was intentional on the part of Flourish Klink. There are wizards and wands involved, I think it goes without saying that Flourish Klink really likes Harry Potter.

There is one point in the book that I believe is worth discussing as it relates to combinatory poetics within the digital sphere. On page 43, Rettberg discusses how combinatory work isn’t made to produce the greatest pieces of writing, but rather as a way to represent a “range of possibilites in interesting ways”.

“If a generative system only operates to demonstrate a concept while producing texts that can only be appreciated as output of a computer program but not as compelling language, in my view it fails as a work of electronic literature.” (Rettberg 43)”

When I looked at the various examples of Taroko Gorge I never viewed any of the poems as compelling in any way, I simply viewed them as demonstrations of a concept. Now maybe I’m simply blind to the beauty of combinatory poetics through the use of story and poetry generators but I don’t take any real meaning in the actual text. I certainly appreciate the technology, as it is incredibly impressive, but outside of that, theres nothing.

When I listen to a song like “Smells Like Teen Spirit” by Nirvana it isn’t just the words and the music alone that are compelling, it is the fact that the Kurt Cobain actually experienced those emotions. With each note and lyric you can feel the passion and emotion behind it all. When you’re a teenager or even an adult, you can relate with those emotions and connect with not just the song, but the artist behind it.

Lets say that a song generator creates a song that is just as powerful if not better than “Smells Like Teen Spirit.” Even if it was an objectively better song, I would still like “Smells Like Teen Spirit” more, and I would view the product created by the generator as a lesser product. I say this because a generator does not know what it is like to experience emotion, it doesn’t know what it is like to struggle, it doesn’t understand the frustrations of being a teenager and how that affects someone. Anything that it creates rings hollow because it can’t actually experience anything it describes.

Sources:

Electronic Literature by Scott Rettberg

“Taroko Gorge” by Nick Montfort

“Fred and George” by Flourish Klink

“The Dark Side of the Wall” by Bob Bonsall

 

 

A look at digital combinatory poetics

 

Taroko Gorge was not something I was familiar with before taking a look at the pages for this week. So before I began sifting through the many different works, I made a Google search. In looking at Taroko Gorge, it is quite picturesque and looks like the type of place one puts on a bucket list. After viewing these photos I was expecting all of the poems to be poetic takes describing the scenery of the Gorge.

The original page is a never-ending repeat of phrases. Mixed together they make a random poem about the Gorge. In the code, the author gives everyone the freedom to manipulate and make their own work from his, as long as they give credit. He uses javascript and creates a function that will randomly pick words from an array, and sort them in a way that the poem will still be understandable.

To the side of the original is a multitude of links, showing what others have done with the code. Looking through them these are the ones I found most interesting.

Brendan Howell took the original code as an inspiration to make Designer Gulch. Not only a digital work, but also physical art piece that sits in the Berliner Technische Kunsthochschule. There two dueling computers sit side by side spitting out content. They are programmed to string together “industry jargon” to create the verses. This is the one I found with the most coherent outcome.

Then there was Gorge by J.R. Carpenter, who’s generated poem I would describe as an anatomical feast. It’s quite odd and sometimes offputting with the results, but it does keep the attention of the viewer.

Overall, I liked taking a look at this different form of making poetry.

Taroko Gorge and Combinatory Poetics


For the assignment this week, we were tasked with reading multiple variations of the poem “Taroko Gorge”. First, I took a look at some of the poems, and I noticed that they all had a very similar structure going on with them. After looking into the source code, I determined that it looked like each variation was different because of different key words that were replaced by each author of the poem. I noticed pretty early on into the reading this week of “Electronic Literature” by Scott Rettberg, that kinetic poetry was mentioned as a genre of Electronic Literature. After looking a little more into kinetic poetry, I discovered that it was essentially a form of combinatory poetics. It takes random words out of a piece of text, and they will all be floating around each other. Eventually the words will be drawn towards each other, forming different phrases.

Although the poem has seemingly infinite different versions that could be created through just changing the key words, the part thats most interesting to me is that no matter what words you change in it, the basic structure of the poem will always stay the same. Such as the first sentence of the poem will always be “*Key Word* *Key word*s the *Key Word*”. I also noticed while looking at the poems, that it doesn’t let you scroll back up to view a certain part of the poem, like it’s forcing you to live in the moment of the poem and focus on what’s appearing in front of you while it infinitely continues on. Since the poem is also randomized, once something disappears it’s very unlikely you’ll see it again even through replaying the same poem.

“Taroko Gorge” is very similar to a dadaist poem, which are created from other types of literature, but when cut into pieces and mixed up, they create something different than originally intended. The difference is, you can reread a dadaist poem as much as you like and take as much time as you like with it, which isn’t true with “Taroko Gorge” poems. Hit refresh and even with the same words, everything will be completely different again. As a reader this makes every line feel even more important, since you’ll never be able to read it again. On page 23 of Electronic Literature, Rettburg shares a quote from Manovich that perfectly sums up Taroko Gorge and Combinatory Poetics,

“a new media object is not something fixed once and for all, but something that can exist in different, potentially infinite versions”(23, Electronic Literature)

Sources:

Electronic Literature by Scott Rettberg

Taroko Gorge: https://nickm.com/taroko_gorge/

Taroko Gorge and Combinatory Poetry

The concepts and ideas behind combinatory writing provide insight as to how poetry can be manipulated and enhanced through technology. Nick Montfort developed his poetry generator Taroko Gorge in the programming language Python, later converting the project to HTML, CSS and Javascript which not only made his work both easily accessible for web users, but also simple to hack and manipulate for other poets to engage with poetry through this medium. The open-source characteristics of Taroko Gorge allows for anybody to express their ideas through the medium of front-end web technologies and to expand the possibilities of what poetry can be by co-creating with the computer itself.

While analyzing some of the notable renditions of Taroko Gorge, it can be noticed that an infinite amount of ideas can be expressed through the generator by making simple adjustments to the source code. John Pat McNamara’s rendition, Take Ogre incorporates a background image on the webpage as a personal artistic decision to provide context for his work. The image of a desk and the impeding darkness of the night help articulate that he created his remix while isolated on Archill Sound, Ireland. Chuck Rybak’s remix, Tacoma Grunge explores themes of the Seattle Grunge scene while maintaining a minimalist aesthetic.

Each remix of Taroko Gorge is created by manipulating the keywords that lie within the Javascript variables, where the use of arrays organize the text. Due to the structure of the code that Montfort created, all of the numerous renditions of Taroko Gorge follow the same poetic structure, creating a sort of communal feel between each rendition.

While the work of Montfort certainly creates new possibilities for poetry and literature, it also has roots in the traditional ideas of  Surrealism. As stated by Rettberg:

“Surrealist writers and artists were just as likely to write together, and to freely mix image and text, as they were to write alone or in one medium” (Rettberg 25).

Combinatory writing and the work of Mantfort is not only a new and exciting form of literature, but is also a homage to traditional forms of art and poetry.

 

 

 

 

Taroko Gorge

As with all works of Electronic Literature, these variations or versions of Nick Montfort’s “Taroko Gorge” are born digital. Through the use of javascript, each version including the original implement if/else conditionals, variables and arrays with a variety of words to alternate the contents of the poem as lines appear.

Given Montfort’s note within the code granting permission for the copying, modification and redistribution of the software, as well as the number of other known E-Lit authors including Talan Memmott, Scott Rettberg, and Judy Malloy, among others, brings one to draw the conclusion that perhaps this also played into a sort of collaboration among the Electronic Literature community or an experiment of sorts.

Each text provides a different meaning based on not only the subject or focus of the version, but also the words that appear as they appear, creating an almost individualized experience that changes each and every time it is read. It is poetry so the meaning is up to individual interpretation. For instance, J.R. Carpenter’s “Whisper Wire” follows a similar pattern to Montfort’s “Taroko Gorge” but instead focuses on electricity and sound and how noise travels.

Andrew Plotkin’s “Argot Ogre, OK!” takes one of the other remixed versions and shows simultaneously the work’s process along the right side of the browser while also showing the actions the background code is taking with the conditionals along the left side.

As Plotkin phrases it, the process he implements is,

Combining the word-lists of any two poems;

Mutating the stanza schema.

In this version of the work, he shows the effect of the conditionals in numerous ways but places more emphasis on what lays beneath. As if exposing the skeleton instead of looking at the surface of a person’s skin.

 

Sources:
https://nickm.com/taroko_gorge/
https://nickm.com/taroko_gorge/whisper_wire/
https://nickm.com/taroko_gorge/along_the_briny_beach/
https://nickm.com/taroko_gorge/argot_ogre_ok/