Poetic Infrastructures

updated 11:08:22 - June 29, 2020

Poetic Infrastructures

Our group, “Poetic Infrastructures” is tasked—and uniquely suited—to produce conference-wide documentation and poetic invention over (and covering) the course of the event.

How to


You can edit this note, and go back to the general Publishing Sphere note.

For more information about this pad, click here

Information about our group

information brainstorming

(please edit the information about you!)

The group is composed by:

Danny Francois Craig Nick Danielle

Topic proposal

brainstorming topic poetry poster

Feel free to edit this note.

Brief Note

Hey all, this is Michael – I am writing to test out this platform and to begin to build something in this document. I realize it’s slightly obscure at the moment how this pad will come to be useful during Publishing Sphere – I believe this will be come clearer in the coming days as we begin to roll out some of the sites, info, and programming for the gathering.

Danny and I will be meeting tomorrow (Thursday, the 2nd of May) to discuss the publishing apparatus we have been discussing, and will begin to introduce it to the group as something to work off, develop in new directions, or to create publication systems concurrent to this one. Once we have this initial formulation mapped out, I’ll let him introduce it to you all to begin to discuss and edit.

Shortly, I’ll post some info that I think is relevant to the gathering more generally, and then some additional information about you all so that you might begin to become more aware of the other members of the group. I’m truly looking forward to witnessing how you might all begin to work with one another.

More soonest~

intro infrastructure poetry Michael

Three coordinated projects proposal

1. A Conference Participant Map & Annotation Extraction Poster (title tbd)

In advance of the conference, I’d like to develop a “map” of the participants, ie a foldable poster with images, short info, and a selected citation from all participants. Instead of a guide to a series of rooms for panels, this is a map that locates grouped individuals. Alongside each individual is a blank space, which can be used by all participants during the conference for notes, information exchanges, doodles, idles thoughts, and so forth. We can use these maps to extract these writings to aid in gathering materials for a conference reader during the event (see part 3 below).

Timeline: For this project, in advance, we’ll need to design the poster and select excerpts for participants. The conference team has already collated information on all participants, so this should be a quick task.

2. A Human-Located Publishing Sphere Reading Series (title tbd)

Given the possibility of the Conference Map Extraction Poster, I thought it would be marvelous for our group to host a schedule of readings that are “located” at specific individuals. For example, “On Friday at 3:00pm Craig Dworkin will be reading at Michael Nardone.” We can post the announcements of these readings alongside the image/sector of the individual who is “hosting” that reading (with their permission, of course). Yes?!

Timeline: For this project, we’d just need to coordinate on who would like to read, and “at whom” they would like to give their reading. We’ll build this into the poster design. Again, should be minimal in terms of preparation—perhaps the readings could be new material crafted for the occasion? Entirely up to you!

3. A Conference Reader (title tbd)

This is the primary object we’ve been tasked with generating. And there are many ways we could go about collecting, editing, designing, and publishing this reader. I’m thinking of a shared cloud-based folder hierarchy to gather texts, handwritten notes, poems, images, performance documentation, and anything else you all might like. Throughout the conference, our job will be to meet together to develop this publication—in all regards: design, organization, concept, etc—and to comingle with the rest of the participants to extract (and colaboratively generate!) materials for the reader. I’m hoping you might see how the Map/Annotation/Extraction Poster could work as one primary vehicle for this process. I’d also like to arrive with a bevy of hand-held scanning tools and capture devices. With a shared cloud-based folder system (likely Google Drive)—we can make a database of all materials publically accessible to conference-goers (and beyond?). Finally, all this will be toward the production of a polished print-on-demand book publication that encapsulates a few intensive days of collaboration and conversation.

Timeline: For this project, all work will be done “on site” once we arrive. No prep (but to imagine means and modes of extraction, collection, organization) necessary. The book will be complete and launched at the end of the conference.

brainstorming proposal publications project Danny

On Editorialization

Hi All, another brief note to place Marcello’s book – On Editorialization – in this group. I think it will be of interest, and a kind of guiding theory behind some of the research group’s approach to thinking about the activities of this gathering:


Also, here is the wikipedia entry on the term in English: https://en.wikipedia.org/wiki/Editorialization

And in French: https://fr.wikipedia.org/wiki/%C3%89ditorialisation

editorialization editorialisation Michael

Workshop notes

Instagram - messages on post-it notes / Instagram for creative writing? Handwritten notes on instagram - a smart move? Books, writing, etc.; how to have meaningful conversations

Problems with publishing / the question would be: what publishing is? How to articulate ideas; The format of the book makes it really difficult to trace its own lineage Annotating the text rather than reviewing the reviews (regarding a review of retrospective; Jon Rafman)

How to trace the usage; using the map to try an make sense of the different keywords discussed during the collective brainstorming –> Recognizing patterns.

Which words are not being used at all?

National/natural language / on the language “barrier” the most important fact of the 21st century would be that most publishing is done by/for machines / humans are taken out of the equation * we can’t read because we don’t know the language * computer languages / binary / forms of language

Relationship between computers read languages but don’t understand it.

On the importance of print (F. Bon). We use digital devices as a way to organize our narratives. How can we create an interaction with others? Your own presence, your own questions can be sufficient. We can write, do anything but being present is sufficient. What is code? code is embodied Ex: GoPro camera is a bipedal device / it requires hands, legs to move, etc.

The interaction in itself is the question What if the action is relevant in itself?

different recording mechanisms is already a documentary project is itself.

Language is minerating / the narrowness of language. Language as game.

The human interaction // editorial interaction; why does something like twitter need keywords that are human generated? why can’t twitter process it? There is a gap between the intended curation of one’s message and what is actually being said. (The hashtag were accidental, they were built into twitter after users have implemented it) * ex: Tik Tok; where the algorithm is in total contral of what comes up to your eyes / DS: much of Tik tok is actually pen & paper

Instagram and facebook as working tools

In an accelerated technical era where certain machines can do more, lots of the roles can be conflated. Typography organizes language. The specific technical activity //defining music as organized listening //organizing information

Scripting sounds ex: editors trying to transcribe everything, all the information –> how one’s takes the genetic text and presents it as poetry

How can we relate scripting? interface, rapid production? The idea of markup scripts / a markup language

Project idea; a markup language to translate interactions

Group wants to establish their own protocol / team will decide what the markup language would be How to treat the conference participants as specialists that advise on the language. creating ties to engage with other folks. * how to translate using actual graphic symbols?

The idea of a markup language; * the difference between what gets set * Listening

Forms of “not-socially significant” languages / languages that can be articulated but not clearly expressed? How can we render these kinds of language in print? Must hover somewhere between the graphics and the graphemics It seems like the range is still limited. at what point do we have a vocabulary that is enough/too large.

  • The markup language has to say what’s not evident to the reader / at what point does it become indiosyncratic to the reader?
    • ex: who decides what becomes an emoji? there’s no reason for a dumpling to be an emoji / emojis express moves/objects as pictograms
  • Listen to/listen at - are different actions / these forms of relation engagement must have a significant markup

What are we actually marking up? What it is the overarching term for what it is we’re looking at; * markups as applied for things that can’t be marked up / ex: awkward pause when switching languages / * play on words: public/publishing sphere

Examples: Pauses/stutter; * ’’’ as representative of pauses/stutter (english) * Kid/dad example: translating the physical interaction between the father and the child

The protocol must precede; it has to be part of the document but can’t be part of the document. The protocol still has more authority than the document. * Ex: structure (gameplay) - recognizing a situation/transcribing it * Ex: I noticed you did this –> how would you describe that as a symbol?

What type of perimeter should be created for the user What is the markup for conversations about publishing?

How can we translate the ambiguities in conversations? For example, what would be the symbol for the switch between écouter and entendre? * the descriptive language of things that happen or scripting languages (i.e music score) * markup that could be scripted

What are we marking up? * Marking up encounters * what is the abstract language we’re marking up? * the markup should capture relations/encounters * An argument starting from this specific time/people/space and that all interactions are bilingual interactions even when people are speaking the same language

Bring together, a markup for encounters * team will be working on a protocol

Questions/perimeters * Two different ways Procedure of establishing the symbols / pre + post: “this happens-here is the symbol” and “this happened what would be the symbol” * Inflexions of symbols are allowed * When the symbol is jotted down, we must write down what occured. * People must write on the posters * “What is the duration of the interaction listening at and reading at?” –> as long as the conversation is interesting? –> 10 minutes. * Suggestion to turn it into a game * Materialize it into something portable (ex: a bookmark) - anything compact * Suggestion to print it at artexte (saturday) * Asking the interlocutor how long they are planning on conversing with you?

ideographic symbols Priority = gestures ; affects = underneath

Publish the book + the font.

Organize affects in gestures.

HTML (meaning) /CSS (gesture)