|
|
|
|
|
<!DOCTYPE html>
|
|
|
|
|
|
<!DOCTYPE html>
|
|
|
|
|
|
<html>
|
|
|
|
|
|
<head>
|
|
|
|
|
|
<meta charset="utf-8">
|
|
|
|
|
|
<title>Tasks of the Contingent Librarian</title>
|
|
|
|
|
|
<link rel="stylesheet" type="text/css" href="tasks.css">
|
|
|
|
|
|
<script src="tasks.js"></script>
|
|
|
|
|
|
</head>
|
|
|
|
|
|
<body>
|
|
|
|
|
|
|
|
|
|
|
|
<div class="cardback"><DOCUMENT_FRAGMENT><div class="mw-parser-output"><div class="thumb tright"><div class="thumbinner" style="width:152px;"><a class="image" href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/b/b8/House_of_leaves.jpeg/960px-House_of_leaves.jpeg"><img alt="" class="thumbimage" decoding="async" src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/b/b8/House_of_leaves.jpeg/320px-House_of_leaves.jpeg"></a> <div class="thumbcaption"><div class="magnify"><a class="internal" href="File:House_of_leaves.jpeg.html" title="Enlarge"></a></div>A spread from Danielewski’s <i>House of Leaves</i></div></div></div>
|
|
|
|
|
|
<h2><span id="text,_tbc,_an_essay"></span><span class="mw-headline" id="text.2C_tbc.2C_an_essay"><i>text, tbc</i>, an essay</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/mw-mediadesign/index.php?title=User:Simon/text_tbc&action=edit&section=T-1" title="Edit section: ">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
|
|
|
|
|
|
<div class="thumb tright"><div class="thumbinner" style="width:302px;"><a class="image" href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/b/be/Text_tbc_printed.png/960px-Text_tbc_printed.png"><img alt="" class="thumbimage" decoding="async" src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/b/be/Text_tbc_printed.png/320px-Text_tbc_printed.png"></a> <div class="thumbcaption"><div class="magnify"><a class="internal" href="File:Text_tbc_printed.png.html" title="Enlarge"></a></div><i>text tbc</i> the print version</div></div></div>
|
|
|
|
|
|
<p><i>text, tbc</i> is an essay commissioned by Onomatopee for a reader, published as part of the <i>Meeting Grounds</i> public program. In this essay I describe my interest in text's overlapping dimensions: the editorial, technical and social. The text is performed through the use of Etherpad: as a writing environment to create the text, a software to reflect on, and a live editable document which anyone may edit, if they know the URL.
|
|
|
|
|
|
</p><p>The live, editable version on Etherpad:
|
|
|
|
|
|
<a class="external free" href="https://pad.xpub.nl/p/text_tbc" rel="nofollow">https://pad.xpub.nl/p/text_tbc</a>
|
|
|
|
|
|
</p>
|
|
|
|
|
|
<h3><span id="text,_tbc"></span><span class="mw-headline" id="text.2C_tbc">text, tbc</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/mw-mediadesign/index.php?title=User:Simon/text_tbc&action=edit&section=T-2" title="Edit section: ">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
|
|
|
|
|
|
<p>Dear reader/writer,<br>
|
|
|
|
|
|
</p><p>The essay below, <i>text, tbc</i>, lives in a pad on a server hosted by Experimental Publishing (XPUB), at the Piet Zwart Institute, Rotterdam.<br>
|
|
|
|
|
|
This a live text, welcome to be edited by anyone. However, in the interests of transparency and care towards yourself and others, please be aware of the following:<br>
|
|
|
|
|
|
</p><p>VISIBILITY:<br>
|
|
|
|
|
|
This pad isn't indexed by search engines, but it is 100% public to anyone who knows its URL.
|
|
|
|
|
|
</p><p>PRIVACY:<br>
|
|
|
|
|
|
This pad is not encrypted, meaning that it is not private. Anyone who can access the server can also see its content.
|
|
|
|
|
|
</p><p>RETENTION:<br>
|
|
|
|
|
|
Text can change, rapidly and in real time, making this a dynamic, but ultimately unstable environment. Make backups regularly if you wish to keep copies.
|
|
|
|
|
|
</p><p>ACCESSIBILITY:<br>
|
|
|
|
|
|
Pads can go down for many reasons, such as scheduled server maintenance, unforeseen events, and of course, human error. It is impossible to determine the identity of an author and XPUB does not respond to pad retrieval requests.
|
|
|
|
|
|
</p><p>CONVIVIALITY:<br>
|
|
|
|
|
|
Please be as respectful and supportive towards other reader/writers as possible. Don't delete anything, just add.
|
|
|
|
|
|
</p><p>Text flies in an endless stream before your eyes. News reports, longform articles, facts and figures, documents and messages sent at all hours of the day and night; it is always daylight somewhere in the world and there is always something new to report. You see text, but you don't have the time to carefully read and absorb it. You have never read or written so much. Your phone buzzes with the input and output of messages and notifications. You are exhausted by the letters, numbers, punctuation, and spaces that make up what is usually called “text”.
|
|
|
|
|
|
</p><p>But the overwhelming presence of text is not felt just in the material form of its characters, or the spaces between them. It resides in text's overlapping dimensions and resulting viewpoints and how these influence practices of reading and writing.
|
|
|
|
|
|
</p><p>The <i>editorial</i> dimension; text is a sequence. A line of characters and spaces, the particular order that the writer sets these in. Text becomes an object, a carrier of thoughts and feelings, something that can be sent back and forth between participants in a conversation.
|
|
|
|
|
|
</p><p>The <i>technical</i> dimension; text is a process. Messages and files that we share are text-based. A computer runs on software, programmed in encoded text, often the same characters that flicker before your eyes. Texts can be assembled on-the-fly as a machine reads scripts and writes output in response to input.
|
|
|
|
|
|
</p><p>The <i>social</i> dimension; text is a framework. The English word "text" has roots in the Proto-Indo-European word <i>teks-</i>, meaning “to weave, to fabricate, to make; make wicker or wattle framework”. A piece of writing is a text, and so is a conversation; texts represent the exchange of shared concepts (words, signs, representations) woven into a fabric of communication. There is also an exchange between written and spoken texts; oral discussions which prompt writing, and writing which sparks conversations. Texts elicit further texts.
|
|
|
|
|
|
</p><p>I’m typing this now using a self-hosted, open-source, browser-based, realtime, collaborative text-editing software called Etherpad. Etherpad is many things, as you can probably tell by the string of adjectives in my previous sentence. <i>The pad</i>, as it is colloquially (somewhat affectionately) known by many users, has its own peculiar twist on online public space and subsequently, the public it makes. An environment; a combination of particular conditions set by hardware and software that determine how a user operates within it. The pad is an unstable, dynamic environment open to participation, often without notions of consistency in formatting, or singularity in authorship. For a start, anyone who knows the URL can edit what is written here. This text could easily become an unruly wall built without convention, just sitting there in the browser. And though you, dear readers, may also become writers, you will barely recognise each other as authors.
|
|
|
|
|
|
</p><p>Some of you will choose a username, some will remain <i>unnamed</i> by default. I often call myself <i>karen eliot</i> (all lowercase), a shared pen name favoured by the Neoists, an art movement famous for creating multiple definitions of itself. <i>karen eliot</i> is everyone and no-one, and on the pad, so am I. In collaborative writing sessions, what I type becomes intermingled with the writings of others until I can hardly say it is mine any more; copy-pasted, deleted, overwritten, rephrased, paraphrased and line-edited to the nth degree. As authorship colours and names change at whim, it's almost impossible for writers to know who is who unless you go back through the version history and/or sleuth the chat section for clues. But it's hardly important when the purpose is to write together.
|
|
|
|
|
|
</p><p>Sometimes I use it to write by myself, typing into the pad as the server records a mind-boggling database of every key I press, every action I undo. I slide back in time through this text (the one you're reading) to see revisions in the version history. So far the only author there is myself, although all anyone needs to do is type (even a space), and they will automatically join <i>karen eliot</i> as a listed co-author. Add multiple users at multiple keyboards, all free to edit autonomously, and the writing starts to become definitively less a work of singular authorship, and more a woven multiplicity of perspectives.
|
|
|
|
|
|
</p><p>Often the pad serves as a note-taking accompaniment to a spoken conversation, transcribing each other's words, turning our speech into text. Fingers typing rapidly, trying to keep up with the pace of dictation will make mistakes. In response, a distinct protocol develops in support of diverse ways of reading and writing. Spell-checking is often unnecessary; writers may mis-type, but ultimately, their/they're/there spelling isn't a concern as long as it doesn't get in the way of communication. I'm reminded of Samizdat publishers, who eschewed the title of "author" in favour of “typist” or “editor” due to the unwanted attention and risk it would bring to themselves and their dissident republications of censored books. Editing, typing, reproducing texts by hand; all of this encourages a slippery form of authorship through human error and idiosyncratic preferences for a new phrase, sense-for-sense translation or structure. When no writer is the discernible author, everyone becomes a text editor.
|
|
|
|
|
|
</p><p>The pad exemplifies the editorial, technical and social dimensions of text. New editors respond with reactions that range from eager enthusiasm to shy suspicion. For some, the pad seems too public, too immediate, too dynamic. What we type, delete, mis-type or mis-spell is there for all to see as we do it. But for the enthusiasts, individually-coloured sentences quickly proliferate into multicoloured streams of collaborative writing. For all its dynamic energy and realtime nature, the pad generates an aura of calm. It's not a feed which must be scrolled, there are no read receipts and no-one can be left on seen. Indeed, nothing can be sent or unsent, nor for that matter, unseen. There are no notifications, it doesn't buzz in the middle of the night. When I come back to it a day or so later, a new text has evolved. There are no other readers or writers there now, only myself, <i>karen eliot</i>. I pause, taking the time to read and absorb it.
|
|
|
|
|
|
</p><p>—Simon Browne, Rotterdam, April 2020
|
|
|
|
|
|
</p><p><i>With special thanks to Steve Rushton and Michael Murtaugh.</i>
|
|
|
|
|
|
</p>
|
|
|
|
|
|
<!--
|
|
|
|
|
|
NewPP limit report
|
|
|
|
|
|
Cached time: 20200620143703
|
|
|
|
|
|
Cache expiry: 86400
|
|
|
|
|
|
Dynamic content: false
|
|
|
|
|
|
CPU time usage: 0.017 seconds
|
|
|
|
|
|
Real time usage: 0.028 seconds
|
|
|
|
|
|
Preprocessor visited node count: 13/1000000
|
|
|
|
|
|
Preprocessor generated node count: 34/1000000
|
|
|
|
|
|
Post‐expand include size: 8222/2097152 bytes
|
|
|
|
|
|
Template argument size: 0/2097152 bytes
|
|
|
|
|
|
Highest expansion depth: 2/40
|
|
|
|
|
|
Expensive parser function count: 0/100
|
|
|
|
|
|
Unstrip recursion depth: 0/20
|
|
|
|
|
|
Unstrip post‐expand size: 0/5000000 bytes
|
|
|
|
|
|
-->
|
|
|
|
|
|
<!--
|
|
|
|
|
|
Transclusion expansion time report (%,ms,calls,template)
|
|
|
|
|
|
100.00% 3.744 1 User:Simon/text_tbc
|
|
|
|
|
|
100.00% 3.744 1 -total
|
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Saved in parser cache with key wdka_mw_mediadesign-mw_:pcache:idhash:31709-0!canonical and timestamp 20200620143703 and revision id 175226
|
|
|
|
|
|
-->
|
|
|
|
|
|
</div></DOCUMENT_FRAGMENT></div>
|
|
|
|
|
|
|
|
|
|
|
|
</body>
|
|
|
|
|
|
</html>
|
