<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/8f/R_w_x_symbols.jpeg/640px-R_w_x_symbols.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/8f/R_w_x_symbols.jpeg/320px-R_w_x_symbols.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:R_w_x_symbols.jpeg.html"title="Enlarge"></a></div>Permissions in UNIX and UNIX-like systems</div></div></div>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/8f/R_w_x_symbols.jpeg/960px-R_w_x_symbols.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/8f/R_w_x_symbols.jpeg/320px-R_w_x_symbols.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:R_w_x_symbols.jpeg.html"title="Enlarge"></a></div>Permissions in UNIX and UNIX-like systems</div></div></div>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/0/03/USB_drives_as_libraries.jpeg/640px-USB_drives_as_libraries.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/0/03/USB_drives_as_libraries.jpeg/320px-USB_drives_as_libraries.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:USB_drives_as_libraries.jpeg.html"title="Enlarge"></a></div>USB drives as libraries</div></div></div>
<liclass="toclevel-1"><ahref="#Auto-mount_an_external_drive_on_boot"><spanclass="tocnumber">1</span><spanclass="toctext">Auto-mount an external drive on boot</span></a>
<ul>
<liclass="toclevel-2"><ahref="#Step_1_.E2.80.93_Plug_In_The_Device"><spanclass="tocnumber">1.1</span><spanclass="toctext">Step 1 – Plug In The Device</span></a></li>
<liclass="toclevel-2"><ahref="#Step_2_.E2.80.93_Identify_The_Device.27s_Unique_ID"><spanclass="tocnumber">1.2</span><spanclass="toctext">Step 2 – Identify The Device's Unique ID</span></a></li>
<liclass="toclevel-2"><ahref="#Step_3_.E2.80.93_Create_a_Mount_Point"><spanclass="tocnumber">1.3</span><spanclass="toctext">Step 3 – Create a Mount Point</span></a></li>
<liclass="toclevel-2"><ahref="#Step_4_.E2.80.93_Manually_Mount_The_Drive"><spanclass="tocnumber">1.4</span><spanclass="toctext">Step 4 – Manually Mount The Drive</span></a></li>
<liclass="toclevel-2"><ahref="#Step_5_.E2.80.93_Un-mounting_The_Drive"><spanclass="tocnumber">1.5</span><spanclass="toctext">Step 5 – Un-mounting The Drive</span></a></li>
<liclass="toclevel-2"><ahref="#Step_6_.E2.80.93_Auto_Mount"><spanclass="tocnumber">1.6</span><spanclass="toctext">Step 6 – Auto Mount</span></a></li>
<liclass="toclevel-2"><ahref="#An_Extra_Note_About_File_Systems"><spanclass="tocnumber">1.7</span><spanclass="toctext">An Extra Note About File Systems</span></a></li>
<h3><spanclass="mw-headline"id="Auto-mount_an_external_drive_on_boot">Auto-mount an external drive on boot</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/automount_a_drive_on_boot&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h3>
<h4><spanid="Step_1_–_Plug_In_The_Device"></span><spanclass="mw-headline"id="Step_1_.E2.80.93_Plug_In_The_Device">Step 1 – Plug In The Device</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/automount_a_drive_on_boot&action=edit&section=T-2"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h4>
<h4><spanid="Step_2_–_Identify_The_Device's_Unique_ID"></span><spanclass="mw-headline"id="Step_2_.E2.80.93_Identify_The_Device.27s_Unique_ID">Step 2 – Identify The Device's Unique ID</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/automount_a_drive_on_boot&action=edit&section=T-3"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h4>
<p>In order to find the unique reference (UUID) for your drive run the following command in the terminal:
</p><p><code>ls -l /dev/disk/by-uuid/</code>
</p><p>This will give you an output that should list your drive:
</p><p>The line will usually refer to “/sda” and in this example it is “sda1”. My ID is “989B-E900”. Note down yours.
You would need to repeat this step if you wanted to use a different device as the UUID would be different.
</p>
<h4><spanid="Step_3_–_Create_a_Mount_Point"></span><spanclass="mw-headline"id="Step_3_.E2.80.93_Create_a_Mount_Point">Step 3 – Create a Mount Point</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/automount_a_drive_on_boot&action=edit&section=T-4"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h4>
<p>A mount point is a directory that will point to the contents of your flash drive. Create a suitable folder:
</p><p><code>sudo mkdir /media/usb</code>
</p><p>I’m using “usb” but you can give it whatever name you like. Keep it short as it saves typing later on. Now we need to make sure the Pi user owns this folder:
<h4><spanid="Step_4_–_Manually_Mount_The_Drive"></span><spanclass="mw-headline"id="Step_4_.E2.80.93_Manually_Mount_The_Drive">Step 4 – Manually Mount The Drive</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/automount_a_drive_on_boot&action=edit&section=T-5"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h4>
<p>To manually mount the drive use the following command:
</p><p><code>sudo mount /dev/sda1 /media/usb -o uid=pi,gid=pi</code>
</p><p><br>
This will mount the drive so that the ordinary Pi user can write to it. Omitting the “-o uid=pi,gid=pi” would mean you could only write to it using “sudo”.
Now you can read, write and delete files using “/media/usb” as a destination or source without needing to use sudo.
</p>
<h4><spanid="Step_5_–_Un-mounting_The_Drive"></span><spanclass="mw-headline"id="Step_5_.E2.80.93_Un-mounting_The_Drive">Step 5 – Un-mounting The Drive</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/automount_a_drive_on_boot&action=edit&section=T-6"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h4>
<p>You don’t need to manually un-mount if you shutdown your Pi but if you need to remove the drive at any other time you should un-mount it first. Only the user that mounted the drive can un-mount it.
</p><p><code>umount /media/usb</code>
</p><p>If you used the fstab file to auto-mount it you will need to use:
</p><p><code>sudo umount /media/usb</code>
</p><p>If you are paying attention you will notice the command is “<i>u</i>mount” NOT “<i>un</i>mount”!
</p>
<h4><spanid="Step_6_–_Auto_Mount"></span><spanclass="mw-headline"id="Step_6_.E2.80.93_Auto_Mount">Step 6 – Auto Mount</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/automount_a_drive_on_boot&action=edit&section=T-7"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h4>
<p>When you restart your Pi your mounts will be lost and you will need to repeat Step 4. If you want your USB drive to be mounted when the system starts you can edit the fstab file:
</p><p>The “nofail” option allows the boot process to proceed if the drive is not plugged in. The “noatime” option stops the file access time being updated every time a file is read from the USB stick. This helps improve performance.
</p><p>Make sure you set the correct UUID. Use CTRL-X followed by Y to save and exit the nano editor.
</p><p>Now reboot:
</p><p><code>sudo reboot</code>
</p><p>Your USB drive should be auto-mounted and available as “/media/usb”.
</p>
<h4><spanclass="mw-headline"id="An_Extra_Note_About_File_Systems">An Extra Note About File Systems</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/automount_a_drive_on_boot&action=edit&section=T-8"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h4>
<p>In the examples above I specified “vfat” as the file system of the device as it was formatted as FAT32. If you need to change the file system replace references of “vfat” with “ntfs-3g”, “ext3” or “ext4”.
If you are using NTFS you will also need to install the following package:
<p>This technique suits my applications but the main disadvantage is that it is specific to a known USB device given we are using the device ID. However if you created a few mount points in advance you could manually mount a new device to a spare mount point without worrying about updating the fstab file.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/0/03/USB_drives_as_libraries.jpeg/960px-USB_drives_as_libraries.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/0/03/USB_drives_as_libraries.jpeg/320px-USB_drives_as_libraries.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:USB_drives_as_libraries.jpeg.html"title="Enlarge"></a></div>USB drives as libraries</div></div></div>
<p><ahref="automount_a_drive_on_boot.html"title="User:Simon/Trim4/prototypes/automount a drive on boot">User:Simon/Trim4/prototypes/automount_a_drive_on_boot</a>
</p>
<!--
NewPP limit report
Cached time: 20200616120017
Cached time: 20200620063734
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.020 seconds
Real time usage: 0.088 seconds
Preprocessor visited node count: 12/1000000
Preprocessor generated node count: 32/1000000
Post‐expand include size: 3863/2097152 bytes
CPU time usage: 0.005 seconds
Real time usage: 0.006 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/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)
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/6/65/Tracing_paper_annotations.jpeg/640px-Tracing_paper_annotations.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/6/65/Tracing_paper_annotations.jpeg/320px-Tracing_paper_annotations.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Tracing_paper_annotations.jpeg.html"title="Enlarge"></a></div>Tracing paper bearing carbon-copied annotations from Marginal Conversations</div></div></div>
<liclass="toclevel-1"><ahref="#15.06.19_interfaces_for_annotation"><spanclass="tocnumber">1</span><spanclass="toctext">15.06.19 interfaces for annotation</span></a>
<liclass="toclevel-1"><ahref="#The_Carrier_Bag_Theory_of_Fiction"><spanclass="tocnumber">2</span><spanclass="toctext">The Carrier Bag Theory of Fiction</span></a></li>
</ul>
</div>
<h2><spanclass="mw-headline"id="15.06.19_interfaces_for_annotation">15.06.19 interfaces for annotation</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Retention_and_transformation_of_annotations&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>The formal qualities of annotations are defined by the tools used to make them, and also the cultural uses of these. Given a pen, most people will write, although it is also possible to draw or use it in other ways. With a keyboard it seems most appropriate to type. With a mouse, one can click on things, and select them.
</p><p>What happens when these are retained, transformed and isolated from the source?
<p>Retained digital annotations are rare in the wild, but I found one PDF of Jorge Luis Borges "The Garden of Forking Paths" that had underlinings and highlighted text. The interesting thing is that these change appearance slightly depending on the e-reader software used to display the text.
</p><p>The first two spreads of the Borges PDF:<br>
<p>Another text that came pre-annotated was Ursula K Le Guin's "The Carrier Bag Theory of Fiction". For this, I placed scans in a vector graphics program and digitised pen marks. I also included the text that was annotated with circles, underlines and lines in the margins.
</p><p><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/5d/Carrier_bag_01.png/640px-Carrier_bag_01.png"><imgalt="Carrier bag 01.png"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/5d/Carrier_bag_01.png/320px-Carrier_bag_01.png"></a>
<aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/f/f7/Carrier_bag_02.png/640px-Carrier_bag_02.png"><imgalt="Carrier bag 02.png"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/f/f7/Carrier_bag_02.png/320px-Carrier_bag_02.png"></a><br>
<small>Hand-drawn annotations digitally transcribed from a PDF of Ursula K. Le Guin's "The Carrier Bag Theory of Fiction"</small>
</p>
<h2><spanclass="mw-headline"id="The_Carrier_Bag_Theory_of_Fiction">The Carrier Bag Theory of Fiction</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/The_Carrier_Bag_Theory_of_Fiction&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
Text stock: Clairefontaine Trophee (ivory) 120gsm<br>
Binding: Staple bound<br>
Pages: 16pp
</p><p>Ursula K. Le Guin's short essay appears in a compilation called <i>Dancing at the Edge of the World</i>, which I've found impossible to find online through the usual pirate libraries such as Library Genesis, aaaaaarg.fail and Monoskop. Perhaps this points to a gender bias in what is perceived as knowledge (Le Guin was a woman wrote mostly science-fiction)? In lieu of not being able to find the compilation, I decided to print this book in a very small size (90x120mm) and retain the annotations from the PDF I found. I digitised them by making them into vectors, and printed the text and annotations in green. In this way I wanted to speculate on what would happen when a reader was confronted with annotations that seemed to be part of the source, not a para-text added after publication.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/6/65/Tracing_paper_annotations.jpeg/960px-Tracing_paper_annotations.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/6/65/Tracing_paper_annotations.jpeg/320px-Tracing_paper_annotations.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Tracing_paper_annotations.jpeg.html"title="Enlarge"></a></div>Tracing paper bearing carbon-copied annotations from Marginal Conversations</div></div></div>
<p><ahref="Retention_and_transformation_of_annotations.html"title="User:Simon/Retention and transformation of annotations">User:Simon/Retention and transformation of annotations</a>
</p><p><ahref="The_Carrier_Bag_Theory_of_Fiction.html"title="User:Simon/The Carrier Bag Theory of Fiction">User:Simon/The_Carrier_Bag_Theory_of_Fiction</a>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/85/Being_kind_to_the_reader_mmwac.jpeg/640px-Being_kind_to_the_reader_mmwac.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/85/Being_kind_to_the_reader_mmwac.jpeg/320px-Being_kind_to_the_reader_mmwac.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Being_kind_to_the_reader_mmwac.jpeg.html"title="Enlarge"></a></div>A bootleg copy of <i>My Mother Was A Computer</i>with ample space for annotations</div></div></div>
<p>Snippets:
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/85/Being_kind_to_the_reader_mmwac.jpeg/960px-Being_kind_to_the_reader_mmwac.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/85/Being_kind_to_the_reader_mmwac.jpeg/320px-Being_kind_to_the_reader_mmwac.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Being_kind_to_the_reader_mmwac.jpeg.html"title="Enlarge"></a></div>A bootleg copy of <i>My Mother Was A Computer</i>with ample space for annotations</div></div></div>
</p><p>I made this book with and for Luke (a friend), as a favour, and also to show him how to bootleg a book. I'd already redesigned the text, and printed it double-sided on laser paper. What he wanted to know how to bind books. Luke had been helping me out a lot with getting the bookscanner running, and it seemed like a nice way to repay him. The problem came when we tried to bind the book using the hot-glue machine, which was once again not working as it should and the result we got was less than optimal. So, I showed him how to notch-bind using cold glue, and he took the text block home with him to try out the technique himself, using a DIY book press made from two chopping boards. One the text block was dry, he brought it back to me to show him how to apply the cover. I'd already printed the cover on a piece of paper, but had been using it to write quick notes on in the interim. It's ironic, I'm surrounded by paper, but scrap paper can be hard to come by. Rather than printing the cover again, I decided to tear away all the areas I'd written notes on it, and then photocopy this with the lid open, leaving black where there was no paper. It was another impromptu, make-do decision, but one that lent an interesting mark - removal of all that is not necessary - and in line with the type of radical pedagogical approaches the author of the text was aiming at.
</p><p>I decided to print another copy of <i>Deschooling Society</i> for the physical bootleg library when the hot glue machine was working properly again. It was interesting to compare the differences between the two different binding methods - not something I usually see as I don't often bootleg more than one copy of a book.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/58/Real_bootlegger.jpeg/640px-Real_bootlegger.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/58/Real_bootlegger.jpeg/320px-Real_bootlegger.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Real_bootlegger.jpeg.html"title="Enlarge"></a></div>A “bootlegger” concealing a flask in the leg of a boot</div></div></div>
<h2><spanclass="mw-headline"id="kind_of_a_nomadic_mini-bieb">kind of a nomadic mini-bieb</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/The_physical_bootleg_library&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>The physical bootleg library is housed in a disused champagne crate. It contains books that I have bootlegged myself, or ones that others have. It also contains books donated by visitors to wherever the library is (temporarily) installed. The library travels, and is part of bootleg library sessions held at PZI and at other locations.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/58/Real_bootlegger.jpeg/960px-Real_bootlegger.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/58/Real_bootlegger.jpeg/320px-Real_bootlegger.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Real_bootlegger.jpeg.html"title="Enlarge"></a></div>A “bootlegger” concealing a flask in the leg of a boot</div></div></div>
<p>The IKEA trolley the physical bootleg library usually travels on. Biyi lent me the trolley, and in return, I bootlegged the IKEA logo to read AIKE (Biyi's husband's name)
</p>
</div>
</div></li>
</ul>
<!--
NewPP limit report
Cached time: 20200616133847
Cached time: 20200620083155
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.041 seconds
Real time usage: 0.118 seconds
Preprocessor visited node count: 11/1000000
Preprocessor generated node count: 42/1000000
Post‐expand include size: 427/2097152 bytes
CPU time usage: 0.006 seconds
Real time usage: 0.006 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/40
Expensive parser function count: 0/100
Unstrip recursion depth: 0/20
Unstrip post‐expand size: 2799/5000000 bytes
Unstrip post‐expand size: 0/5000000 bytes
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/a/a3/Hidden_characters.jpg/640px-Hidden_characters.jpg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/a/a3/Hidden_characters.jpg/320px-Hidden_characters.jpg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Hidden_characters.jpg.html"title="Enlarge"></a></div>Hidden characters (e.g. tabs, spaces, carriage and ‘soft’ returns)</div></div></div>
<p>Snippets:
</p>
<h2><spanclass="mw-headline"id="Extracting_text_from_a_PDF">Extracting text from a PDF</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/Extracting_text_from_PDF&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>In Al Sweigart's <i>Automate the Boring Stuff with Python</i>, there's a nice section on a Python library called PyPDF2 that allows you to work with the contents of PDFs. To begin with, I thought I'd try extracting text from a PDF of William S. Burrough's <i>The Electronic Revolution</i>. I chose this PDF as the only version I've found of it online is a 40pp document published by ubuclassics (which I suppose is the publishing house for ubuweb.com). There was no identifier other than this (no ISBN etc.), and it was impossible locating any other version online. What's more, the PDF had very small text, which was uncomfortable to read when I ran the <ahref="Michaels_booklet_script_for_PDF_imposition.html"title="User:Simon/Trim4/Michaels booklet script for PDF imposition">booklet.sh</a> script on it.
</p><p>I thought it would be worthwhile laying out this book again for print reading purposes, and the first step is to get the text from the PDF. Pandoc is usually my go to for extracting text, but it doesn't work with PDFs, so I tried <aclass="external text"href="https://pythonhosted.org/PyPDF2/index.html"rel="nofollow">PyPDF2</a>.
<p>I began by copying a file called electronic_revolution.pdf to a folder, then in the terminal <code>cd</code> into that directory. Then I initiated the interactive python interpreter with this command:
</p>
<pre>$ python3</pre>
<p>Next I wrote the following commands in Python 3 (comments above each line):
</p>
<pre># First, import the PyPDF2 module
>>> import PyPDF2
# Then open electronic_revolution.pdf in read binary mode and store it in pdfFileObj
# To get a PdfFileReader object that rep- resents this PDF, call PyPDF2.PdfFileReader() and pass it pdfFileObj. Store this PdfFileReader object in pdfReader
# The total number of pages in the document is stored in the numPages attribute of a PdfFileReader object
>>> pdfReader.numPages
>>> 40
# The PDF has 40 pages. To extract text from a page, you need to get a Page object, which represents a single page of a PDF, from a PdfFileReader object.
# You can get a Page object by calling the getPage() method on a PdfFileReader object and passing it the page number of the page you’re interested in — in our case, 0
>>> pageObj = pdfReader.getPage(0)
# Once you have your Page object, call its extractText() method to return a string of the page’s text
>>> pageObj.extractText()
>>> 'ubuclassics2005WILLIAM S. BURROUGHSTheElectronic\nRevolution'
</pre>
<p>This returns the value for total page count, and the text for the first page (0). What I want to get is the text for the whole document. I have no idea how to do this!!!
<spanclass="lineno"> 4 </span><spanclass="n">filename</span><spanclass="o">=</span><spanclass="nb">input</span><spanclass="p">(</span><spanclass="s2">"name of the file: "</span><spanclass="p">)</span>
<spanclass="lineno"> 9 </span><spanclass="k">for</span><spanclass="n">page_number</span><spanclass="ow">in</span><spanclass="nb">range</span><spanclass="p">(</span><spanclass="n">number_of_pages</span><spanclass="p">):</span><spanclass="c1"># use xrange in Py2</span>
<p>The next step is to then begin cleaning up the text by removing the line-breaks. We wrote a simple shell script for this that runs the Python script, then a command to take out line breaks:
</p>
<pre>$ python3 extract_text.py
$ grep -v "^$" input.txt > output.txt
</pre>
<p>Only problem is that the names of the txt files that are produced will all be "input.txt", which means that if you run this on more than one PDF, you'll have to move input.txt to another directory before running again, rename the file manually, or perhaps I could write another Python script that renames the file and include it in the shell script after the last line.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/a/a3/Hidden_characters.jpg/960px-Hidden_characters.jpg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/a/a3/Hidden_characters.jpg/320px-Hidden_characters.jpg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Hidden_characters.jpg.html"title="Enlarge"></a></div>Hidden characters (e.g. tabs, spaces, carriage and ‘soft’ returns)</div></div></div>
<p><ahref="Extracting_text_from_PDF.html"title="User:Simon/Trim4/Extracting text from PDF">User:Simon/Trim4/Extracting text from PDF</a>
</p>
<!--
NewPP limit report
Cached time: 20200617092147
Cached time: 20200620063856
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.034 seconds
Real time usage: 0.356 seconds
Preprocessor visited node count: 21/1000000
Preprocessor generated node count: 70/1000000
Post‐expand include size: 2494/2097152 bytes
CPU time usage: 0.005 seconds
Real time usage: 0.006 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/40
Expensive parser function count: 0/100
Unstrip recursion depth: 0/20
Unstrip post‐expand size: 3957/5000000 bytes
Unstrip post‐expand size: 0/5000000 bytes
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/e4/Bls_mg_onomatopee.jpeg/640px-Bls_mg_onomatopee.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/e4/Bls_mg_onomatopee.jpeg/320px-Bls_mg_onomatopee.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Bls_mg_onomatopee.jpeg.html"title="Enlarge"></a></div>bootleg library session at Onomatopee Projects, 6th March, 2020</div></div></div>
<pre>/ b \ o / o \ t / l \ e / g \ l / i \ b / r \ a / r \ y /
\ a / t \
/ m \ e / e \ t / i \ n / g \ g / r \ o / u \ n / d \ s
-------------------------------------------
the bootleg library
https://hub.xpub.nl/bootleglibrary
-------------------------------------------
book sharing & annotation
calibre
ebook manager - you can download this, run it on your computer and share books over a local network using the content server function
https://calibre-ebook.com/
calibre-web
web app that the bootleg library runs on (a fork of the open-source calibre software)
https://github.com/janeczku/calibre-web
Annotation on the web - the holy grail with lots of projects:
https://beepb00p.xyz/annotating.html
also done very simply and effectively with genius:
https://genius.com/
-------------------------------------------
pirate/shadow/"extra-legal" libraries
Monoskop
https://monoskop.org/Monoskop
Library Genesis (collection is HUGE and mirrored) - i usually use the russian site
http://gen.lib.rus.ec/
Memory of the World
https://library.memoryoftheworld.org/#/books/
aaaaarg (only accessible by members. simon can invite you - just send him an email)
https://aaaaarg.fail/
ask for PDFs from people with institutional access
group for informal PDF sharing through a social network
https://www.facebook.com/groups/850609558335839/
Sci-Hub (this is mirrored too, try googling if the link is down):
https://mg.scihub.ltd/
ubu-web
kenneth goldsmith's baby - an archive of avant-garde cinema and writing
http://ubu.com/
Leeszaal
not an online pirate library, but a volunteer-run place in Rotterdam where you can borrow books, look up information, learn how to use LINUX, study or just read the newspaper. Books are not catalogued, and if you want to borrow one, just take it off the shelf and walk out with it:)
https://www.leeszaalrotterdamwest.nl/
-------------------------------------------
legal online libraries & archives
Project Gutenberg
books are within the public domain (70+ years after death of the author), so free of copyright restrictions:
https://www.gutenberg.org/
The Internet Archive
hosts a collection of books and more, also has the wayback machine (snapshots of web pages going back to the 90s)
https://archive.org/
--------------------------------------------
projects & open letters in support of and about piracy/peeracy
In solidarity with Library Genesis and Sci-Hub
an open letter calling for shadow librarians to come out of the shadows
http://custodians.online/
Alexandra Elbakyan to Mr. Robert W. Sweet (presiding judge in the Elsevier vs Sci-Hub et al court case)
https://torrentfreak.com/images/sci-hub-reply.pdf
and publishing
http://andpublishing.org/
The Piracy Project
http://andpublishing.org/the-piracy-project/
--------------------------------------------
loose thoughts from our conversation
misspellings on ebay - how to exploit this to find undiscovered items http://fatfingers.com
bootlegged DVDs and PS1 games - "chipping" to play bootlegged games
social capital accumulated from having a chipped console
The Pirate Book
historical stories of piracy - warez, demoscene, music etc:
https://hub.xpub.nl/bootleglibrary/read/290/pdf
selling unauthorised copies out of a car boot = "boot"legging?
why do we feel it's more threatening to pirate books than movies/music/games etc?
where does the text reside?
what if i read a book out loud and make a file on youtube - is it bootlegging?
can the library also have audio/visual media?
yes - the library is running on open-source software, so definitely possible. this requires an upgrade of the computer and data storage
what is more of a risk - a shared google drive of PDFs or the bootleglib?
a shared google drive is more risky - the bootleg library has several security measures in place to keep it private
will i get into trouble for using the bootleg library?
haha - not very likely:)
can readers communicate with each other through the bootleglib?
not directly, but possible by adding links to etherpads (like this one) in the description fields
--------------------------------------------
some interesting things to watch & read on archives, libraries, piracy and activism
things to read:
the science of piracy and the piracy of science by bodo balasz (an economist researching use of pirate libraries)
Part 1: http://copyrightblog.kluweriplaw.com/2019/03/06/the-science-of-piracy-the-piracy-of-science-who-are-the-science-pirates-and-where-do-they-come-from-part-1/
Part 2: http://copyrightblog.kluweriplaw.com/2019/03/21/the-science-of-piracy-the-piracy-of-science-who-are-the-science-pirates-and-where-do-they-come-from-part-2/
a view from elsewhere on authorship, copyright and creativity by eva weinmayr (of and publishing and the piracy project)
"Our memory is dissipating. Hard drives only last five years, a web page is forever changing and there’s no machine left that reads 15-year old floppy disks. Digital data is vulnerable. Yet entire libraries are shredded and lost to budget cuts, because we assume everything can be found online."
"The Internet's Own Boy depicts the life of American computer programmer, writer, political organizer and Internet activist Aaron Swartz. It features interviews with his family and friends as well as the internet luminaries who worked with him. The film tells his story up to his eventual suicide after a legal battle, and explores the questions of access to information and civil liberties that drove his work."
--------------------------------------------
King Gizzard And The Lizard Wizard
Polygondwanaland is free for everybody and you can do with what you.
From the band's post accompanying links to different digital packs:
"This album is FREE. Free as in, free. Free to download and if you wish, free to make copies.
Make tapes, make CD’s, make records.
[...]
Ever wanted to start your own record label? GO for it! Employ your mates, press wax, pack boxes. We do not own this record. You do. Go forth, share, enjoy."
Bootleg Britney / A bootleg CD bought at the market in Montenegro had 3 extra unpublished songs in comparison to the actual album on sale in the shops - what message was Britney sending me?! i <3 this story
</pre>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/e4/Bls_mg_onomatopee.jpeg/960px-Bls_mg_onomatopee.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/e4/Bls_mg_onomatopee.jpeg/320px-Bls_mg_onomatopee.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Bls_mg_onomatopee.jpeg.html"title="Enlarge"></a></div>bootleg library session at Onomatopee Projects, 6th March, 2020</div></div></div>
<p><ahref="20_03_06_Bootleg_Library_at_Meeting_Grounds_pad_dump.html"title="User:Simon/20 03 06 Bootleg Library at Meeting Grounds pad dump">User:Simon/20 03 06 Bootleg Library at Meeting Grounds pad dump</a>
</p>
<!--
NewPP limit report
Cached time: 20200616232600
Cached time: 20200620063918
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.018 seconds
Real time usage: 0.035 seconds
Preprocessor visited node count: 6/1000000
Preprocessor generated node count: 24/1000000
Post‐expand include size: 31/2097152 bytes
CPU time usage: 0.010 seconds
Real time usage: 0.010 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/40
Expensive parser function count: 0/100
Unstrip recursion depth: 0/20
Unstrip post‐expand size: 7427/5000000 bytes
Unstrip post‐expand size: 0/5000000 bytes
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/0/05/The_physical_digital_bl.jpeg/640px-The_physical_digital_bl.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/0/05/The_physical_digital_bl.jpeg/320px-The_physical_digital_bl.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:The_physical_digital_bl.jpeg.html"title="Enlarge"></a></div>The physical bootleg library contained in a disused champagne crate, and the digital bootleg library running from a Raspberry Pi computer</div></div></div>
<p><i>Text Laundrette</i> is a workshop in which we use a home-made, DIY book scanner, and open-source software to scan, process, and add digital features to printed texts brought by the participants to the workshop. These are included in the “bootleg library”, a shadow library accessible over a local network.
</p><p>Shadow libraries operate outside of legal copyright frameworks, in response to decreased open access to knowledge. This workshop aims to extend our research on libraries, their sociability, and methods by which we can add provenance to texts included in public or private, legal or extra-legal collections.
<p>The workshop ran over 2 hours with invited guests from the academy. It was an ambitious workflow, but we managed to run through several iterations of watermarking, scanning, processing and uploading. The realisation of how much work is involved in digitising and processing texts was certainly a take-home for participants. An interesting moment occurred when uploading - who was the author of the altered text?
<h2><spanclass="mw-headline"id="Feminist_Art_Manifestos">Feminist Art Manifestos</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Feminist_Art_Manifestos&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
</p><p>This book took quite some time to lay out. The original publication exists as an EPUB. You have to buy it, and it's not available in this format from the usual pirate libraries, but I did find an HTML version on <aclass="external free"href="https://monoskop.org/media/text/feminist_art_manifestos/"rel="nofollow">https://monoskop.org/media/text/feminist_art_manifestos/</a>
</p><p>I ran pandoc on the HTML file to turn it into a .rtf so that I could lay it out in InDesign using this command:
</p>
<pre> $ pandoc -s source.html -o new_source.rtf
</pre>
<p>This retained italics and hyperlinks (which was super nice), but there were lots of line-breaks that I didn't need and had to remove manually as find/change in InDesign is indiscriminate...
</p><p>In some ways the digital book is superior to the printed version as you can click on the hyperlinks to visit the source pages of many of these texts, something which is obviously impossible in the printed version, although it does say where the manifestos can be found.
</p><p>The interesting thing about doing this as a book sprint is the speed at which you have to make design decisions. This makes the design quite minimal, and the only typographic conceit here was with a decision to use a variety of indentation styles, which refers to the multiplicity of feminist manifestos. The interesting thing for me about these texts is that they show many different artistic views of feminism which don't necessarily agree with each other.
</p><p>During the time I was laying out this publication, I was invited by Artemis to join her and Paloma in applying to present our Marginal Conversations workshop in Athens at the ETC (Eclectic Tech Conference) festival. We were all pretty excited about the prospect, however as it turned out, some of the organisers were unsure about me presenting a workshop as a cis-gendered hetero man. Although I was disappointed, I understood the reasoning, as due to the nature of this particular conference (which started as a way for women and queer, trans & non-binary folk to share skills outside of a patriarchal male-dominated tech culture. I was reassured that this was not the opinion of all of the organisers, but of some, however, they were trying to reach a compromise with me and each other. I found this an interesting sidenote to the publication I was producing, in which there is a plurality of views that co-exist.
</p><p>I decided to print a second edition of this book for two reasons; 1) someone had borrowed the first edition three months ago and it hadn't been returned, and 2) what's a books of Feminist Art Manifestos without any images?
</p><p>I spent quite some time tracking down images to use in the book. Oftentimes I couldn't find an image that directly corresponded to the writer/writers of each manifesto, which created an interesting opportunity to think about who is represented by each text. Sometimes it was an image of an artwork (if the manifesto was written by an artist), sometimes an image of a collective or the publications they produces, often a portrait of the author or authors, sometimes an image of the manifesto as it appeared in print originally. Each manifesto text is prefaced by an image - abutting the text of a previous manifesto. This creates an interesting connection between seemingly disparate elements and waves of feminist movements. The book was printed in the same size as the first edition, with a grey cover, and noticeably more pages due to the addition of so many colour images.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/0/05/The_physical_digital_bl.jpeg/960px-The_physical_digital_bl.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/0/05/The_physical_digital_bl.jpeg/320px-The_physical_digital_bl.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:The_physical_digital_bl.jpeg.html"title="Enlarge"></a></div>The physical bootleg library contained in a disused champagne crate, and the digital bootleg library running from a Raspberry Pi computer</div></div></div>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c1/Books_are_for_use.jpeg/640px-Books_are_for_use.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c1/Books_are_for_use.jpeg/320px-Books_are_for_use.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Books_are_for_use.jpeg.html"title="Enlarge"></a></div>The first law of S. R. R. Rangathan’s <i>5 Laws of Library Science</i>, 1931</div></div></div>
<h2><spanclass="mw-headline"id="From_the_books:_SLV_RBRR_000-099">From the books: SLV RBRR 000-099</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/From_the_Books:_SLV_RBRR_000-099&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>Date of publication: March 2016<br>
Publisher: Print>Imprint<br>
ISBN: 9780646954691<br>
Dewey number: 028.9099451
</p><p><br>
<i>From the books: SLV RBRR 000-099</i> is a publication that explores marks left in over 300 books by visitors to the 000-099 section of the State Library of Victoria (SLV) Redmond Barry Reading Room (RBRR). The tactile materiality of the publication is emphasised by its form; section-sewn, with an unglued spine, allowing it to incorporate other components of the publication; such as a zine (with a commissioned essay by Federico Antonini) tucked inside the front cover, and a collection of 4" x 6" photographs taken at the SLV which are randomly inserted between pages. Transcripts of sounds recorded in the RBRR appear as intermittent typographic spreads within the layout. On the cover of the book is a list of the terms we defined to categorise the types of marks discovered. The preface to the book is an essay I wrote on the changing role of libraries, and in the end-matter there is a tongue-in-cheek "bibliography" which gives publication details and a Dewey Decimal reference of each book that appears in the publication. The marks we catalogued include (but are not limited to) examples such as marginalia, underlined text, dog-ears, stains, wear and tear, and objects left within books, such as photographs, scraps of paper or letters to future readers.
The publication developed from a collaborative research project with graphic designer Masaki Miwa. This initially involved a time-consuming process in which we removed each book, inspected for marks, scanned results, and then identified, catalogued and inserted them into the layout of the publication. The process of identifying marks and ascribing meaning to them prompted questions of intent and conventions within mark-making. Other research included interviews with librarians at the SLV on marks within rare books. A key development from this research was the discovery of how mark-making can indicate provenance, (e.g. markings on a map which can determine that it was owned by Captain James Cook) or give certain historical value to books, that result in relocation to less publicly-accessible areas of the library. The photographs and transcriptions of sounds were included in order to give an impression (beyond the merely textual) of this particular area of the SLV. In order to contextualise our findings within a wider realm of public discourse on the social role of libraries, I wrote an essay on the contemporary shift from libraries acting as repositories of knowledge to active social spaces as collections are slowly being digitised. Federico Antonini's essay explores mark-making as a deliberate creative strategy in the design of artist's books, offering speculative answers to questions of intent and meaning around the marks we discovered in the SLV.
</p><p>The project began with an interest in this phenomenon, and curiosity about the possible intentions of mark-makers. Part of my own interest was from a typographic perspective, exploring the range of symbols used when marking texts. Through our research we became interested in this phenomenon of books being used as vehicles for communication by readers, and through categorising them and exploring commonalities in mark-making, attempt a kind of subjective taxonomy within the limited context of this section, at that particular time in history. Our interviews with SLV librarians and research into the shifting role of libraries prompted us to expand the scope of our publication beyond the small section of books we surveyed, and connect our research to a wider contemporary discourse on attitudes towards libraries. The publication was (perhaps ironically) acquired by the SLV, and now sits within its collection of artist's books.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c1/Books_are_for_use.jpeg/960px-Books_are_for_use.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c1/Books_are_for_use.jpeg/320px-Books_are_for_use.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Books_are_for_use.jpeg.html"title="Enlarge"></a></div>The first law of S. R. R. Rangathan’s <i>5 Laws of Library Science</i>, 1931</div></div></div>
<p><ahref="From_the_Books:_SLV_RBRR_000-099.html"title="User:Simon/From the Books: SLV RBRR 000-099">User:Simon/From_the_Books:_SLV_RBRR_000-099</a>
</p>
<!--
NewPP limit report
Cached time: 20200616234539
Cached time: 20200620063939
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.054 seconds
Real time usage: 0.211 seconds
Preprocessor visited node count: 13/1000000
Preprocessor generated node count: 50/1000000
Post‐expand include size: 3892/2097152 bytes
CPU time usage: 0.012 seconds
Real time usage: 0.013 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/40
Expensive parser function count: 0/100
Unstrip recursion depth: 0/20
Unstrip post‐expand size: 3551/5000000 bytes
Unstrip post‐expand size: 0/5000000 bytes
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
<h2><spanclass="mw-headline"id="07.05.19_workshop_with_bodo_balasz">07.05.19 workshop with bodo balasz</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Workshop_Bodo_Balasz&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
</p><p>Reading: Bodó, Balázs (2019): <i>The science of piracy, the piracy of science. Who are the science pirates and where do they come from</i><aclass="external text"href="http://copyrightblog.kluweriplaw.com/2019/03/06/the-science-of-piracy-the-piracy-of-science-who-are-the-science-pirates-and-where-do-they-come-from-part-1/"rel="nofollow">Part I</a> + <aclass="external text"href="http://copyrightblog.kluweriplaw.com/2019/03/21/the-science-of-piracy-the-piracy-of-science-who-are-the-science-pirates-and-where-do-they-come-from-part-2/"rel="nofollow">Part II</a>
</p><p>Workshop with economist Bodo Balasz, whose research is on shadow libraries and the forces that drive them, taking the point of view that "if you do not understand the black market, you can not organize legality". Bodo's recent work is on the dataset of the biggest shadow libraries (which for certain reason, I won't name here). The most striking conclusions drawn from his analysis show that use of the shadow library has increased dramatically in the developing world, it is actually those in the privileged, richer countries that are using the service most, raising questions if cost competition is the driving factor of use of shadow libraries. Also examined are file formats, which reveals interesting facts about the duplication process involved in creating copies.
</p><p>The process differs historically between Eastern and Western countries due to cultural and technological differences. In the East (particularly in Russia and eastern bloc countries) texts were initially re-typed. This follows the tradition established in samizdat publishing of duplicating texts by hand. The need to have developed systems of private distribution was higher in former Soviet countries. In the West, most texts were photocopied or scanned initially, due to cheaper access to the technology.
</p><p>Bodo examines the dataset using a browser-based interactive python server. By running code on the csv file of the dataset, it is possible to establish trends and make inferences on the behaviour of the users of the shadow library. Certain problems may arise due to the metadata associated with each file - different character sets, errors, lack of information and "inaccurate" information can make some analyses difficult to pin down. Using interactive python, we did single variable analysis, and also two-dimensional analysis.
<h2><spanid="Information_ages_:_literacy,_numeracy,_and_the_computer_revolution"></span><spanclass="mw-headline"id="Information_ages_:_literacy.2C_numeracy.2C_and_the_computer_revolution">Information ages: literacy, numeracy, and the computer revolution</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Information_Ages&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
</p><p>I could only find this as a printed book available for purchase online, or to borrow from the closest library, which is the Koninklijke Bibliotheek in The Hague. So, I went to the KB in the Hague, registered a membership (costing 7,50 euro per year) and borrowed the book. I scanned the book on a photocopier back at PZI (it took about 40 mins and many apologies to those who wanted to use it), and then printed and bound it by hand using a cold glue binding technique. The file produced by scanning actually took longer to be transferred over the network than it did to scan the entire book. I optimised the file after receiving it, which produced splotchy text and images (in some places the print looked damaged by water). The cover was an impromptu decision - to use the same method. The copy was made in about 2 hours.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/5a/Chronicle_of_current_events.jpeg/640px-Chronicle_of_current_events.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/5a/Chronicle_of_current_events.jpeg/320px-Chronicle_of_current_events.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Chronicle_of_current_events.jpeg.html"title="Enlarge"></a></div>Facsimile of A Chronicle of Current Events (Russian: Хро́ника теку́щих собы́тий)</div></div></div>
<h2><spanclass="mw-headline"id="Description_of_task">Description of task</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Etherpad_timed_writing/editing_experiment&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>In November 2018, I experimented with a timed writing task using Etherpad, a collaborative realtime browser-based text editor. Etherpad automatically assigns authorship colours to users, and I wanted to explore how a text that I was writing, reading and editing over a specific time period could be visualised.
<p>The method was to write for one hour. I begin by writing a text about what I was doing (writing, reading and editing). For time constraints, I established writing periods of 3 minutes, and a rest period of 2 minutes. After 6 iterations, this shifted to 5 minutes for both respectively. I kept writing and opening up new private tabs in my browser to give each iteration new authorship colours. These are lost when exported, so I recreated the text and authorship colours to make visualisations.<br>
</p><p><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/a/aa/18_11_21_Pad_difs_01.jpg/640px-18_11_21_Pad_difs_01.jpg"title="The entire text, recreated with authorship colours"><imgalt="The entire text, recreated with authorship colours"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/a/aa/18_11_21_Pad_difs_01.jpg/320px-18_11_21_Pad_difs_01.jpg"></a>
</p><p><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/9/9a/18_11_21_Pad_difs_colours_all.jpg/640px-18_11_21_Pad_difs_colours_all.jpg"title="Authorship colours with text removed"><imgalt="Authorship colours with text removed"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/9/9a/18_11_21_Pad_difs_colours_all.jpg/320px-18_11_21_Pad_difs_colours_all.jpg"></a>
</p><p>The experiment showed me that editing is a way of writing, kind of like making growing a tree while making furniture from it. Whatever is written is there to be pruned and shaped into pieces that are joined together to form a supportive text structure. Etherpad makes this visible with its authorship colours, all the more so when it is used as it has been designed; collaboratively.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/5a/Chronicle_of_current_events.jpeg/960px-Chronicle_of_current_events.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/5a/Chronicle_of_current_events.jpeg/320px-Chronicle_of_current_events.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Chronicle_of_current_events.jpeg.html"title="Enlarge"></a></div>Facsimile of A Chronicle of Current Events (Russian: Хро́ника теку́щих собы́тий)</div></div></div>
<h2><spanid="11.12.19_-_lunchmeeting_#3,_in_the_Research_Station"></span><spanclass="mw-headline"id="11.12.19_-_lunchmeeting_.233.2C_in_the_Research_Station">11.12.19 - lunchmeeting #3, in the Research Station</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/fieldwork/WdKA_Research_Station&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>Wilma Knol (embedded librarian in the Research Station) invited me to a lunchmeeting, a series of informal hour-long open meetings based on a directive to "future-proof" the collection. Wilma is part of a group that is determining news ways for acquisitions to take place within the WdKA Research Station/Library. Other members of the group are ginger coons and Jojanneke Gijsen, both teachers at WdKA. The group have established certain directions and strategies, highlighting these interests:
</p>
<ul><li>acquisition requests</li>
<li>the legacy of the collection</li>
<li>displaying and distributing the collection</li></ul>
<p>I'm interested to see if the bootleg library can be of assistance with this directive - especially in informing a bottom-up method of acquiring new books by looking at what is being read/downloaded/uploaded.
</p>
<h2><spanid="Researching_aaaaarg.fail,_ubuweb_&_Project_Gutenberg_with_Tancredi:"></span><spanclass="mw-headline"id="Researching_aaaaarg.fail.2C_ubuweb_.26_Project_Gutenberg_with_Tancredi:">Researching aaaaarg.fail, ubuweb & Project Gutenberg with Tancredi:</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Profiling_shadow_libraries&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
How much? PDFs - a lot! (hard to see how many, but 26,000+ and counting...) theory and critical theory
</p><p><b>Users: Who is using / uploading / downloading?</b>
Used by researchers, academics, students, people interested in theory who can become members by invitation. Members of the site can upload and download, and request new titles through a messageboard.
</p><p><b>Catalog: What is the system? How is it organised? How about its ontology?</b>
Indexed, by "catalog" (listing by author name), "collection" (listing by topic), and also by "requests" (listing by new requests, most requested, unrequested, and everything - also with RSS feed)
</p><p><b>Infrastructure: What are technical specs? Software? Hardware?<</b>
Probably runs on self-hosted server - you access it through a browser
No advertising on site - no information about sponsors or donations on site either...
</p><p><b>Law: How does it interface?<</b>
Brazen defiance
</p>
<pre> UBUWEB <aclass="external free"href="http://www.ubu.com/"rel="nofollow">http://www.ubu.com/</a> info >><aclass="external free"href="http://www.ubu.com/resources/"rel="nofollow">http://www.ubu.com/resources/</a> p.66 <aclass="external free"href="https://bit.ly/2HN5IST"rel="nofollow">https://bit.ly/2HN5IST</a>
</pre>
<p><b>Content: What is in the library? How much?</b>
(PDF, VIDEO, AUDIO...) art, media, theater... in the contest of avant-gard in 2011 over 7,500 artists and over 2500 full-length avant-garde films and videos
Users: Who is using / uploading / downloading? editors + volunteers + users + artists
</p><p><b>Catalog: What is the system? How is it organised? How about its ontology?</b>
each section has an editor who brings to the site their area of expertise / structured as a research project, index with descriptions
</p><p><b>Infrastructure: What are technical specs? Software? Hardware?</b>
servers donated by several universities as a means of study
</p><p><b>Politics: What is the attitude?</b>
library which is ever-expanding in uncanny—and often uncategorizable—directions / no logo,advertise,donation / anti-institutional / Act as a museum
alternative by invoking a gift economy of plentitude with a strong emphasis on global education
Economy: Sponsors? Donation? Advertising? volunteering / no advertising / free download / autonomous no sponsors
Law: How does it interface? no financial interest but educational approach. VS copyright
<p><b>Content: What is in the library? How much?</b>
Project Gutenberg started in 1971. Texts in the library are those that have entered the public domain after exceeding the statute of limitations (in 1971 it was 14 years after death of the author, then 28, now 50 years). The website offers 58,000+ free "eBooks" (ePUB, Kindle, HTML and plain text formats). The collection is described as being comprised of three core types of text, "light literature" (e.g. Alice In Wonderland), "heavy literature" (e.g. Shakespeare), and "references" (e.g. encyclopedias)
</p><p><b>Users: Who is using / uploading / downloading?</b>
Anyone can download without registering an account. Only the site admin can upload.
</p><p><b>Catalog: What is the system? How is it organised? How about its ontology?</b>
Indexed alphabetically by author, title, language, "special categories" and recent uploads. Also includes a search function based on U.S. Library of Congress Subject Headings (LCSH), and Yahoo and Google search (using metadata)
</p><p><b>Infrastructure: What are technical specs? Software? Hardware?</b>
Runs off a wiki. Hosted by ibiblio.org ("one of the largest free information databases online"). Accessed through the browser.
</p><p><b>Politics: What is the attitude? Based on democratic principle of shared knowledge.</b>
Operates (mostly) within the law. Heavily affiliated, with sister organisations in many countries, as well as partnerships with many other libraries and organisations that provide software to help read eBooks.
Project Gutenberg began with a serendipitous grant to Michael Hart (founder of Project Gutenberg) of an operator's account with $100,000,000 of computer time in it in 1971. Now, donations are accepted, run by volunteers (also makes calls for volunteer help - "digitizing, proofreading and formatting, recording audio books, or reporting errors").
</p><p><b>Law: How does it interface?</b>
(mostly) Legally, as most texts are within the public domain.
</p>
<h2><spanid="Writing_task_with_Artemis_&_Bo"></span><spanclass="mw-headline"id="Writing_task_with_Artemis_.26_Bo">Writing task with Artemis & Bo</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Profiling_shadow_libraries&action=edit&section=T-2"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p><br>
A) DESCRIPTION: an abstract of what each shadow library is [Steve suggests: make this 300 words or so]<br>
B) QUESTIONS: what type of questions does it raise? (e.g. what type of assumptions are implicit in its ontology?)
</p><p><br>
</p>
<pre> PROJECT GUTENBERG
</pre>
<p>Abstract — Project Gutenberg, initiated in 1971 by Michael Hart, is the world's oldest digital library of "eBooks", that is, books that are available electronically as PDFs, HTML, ePUB and plain text format. The collection has more recently expanded to include audio books, and texts in a variety of languages other than English. On the wiki-based website www.gutenberg.org, more than 58,000 eBooks are indexed by author, title, language and "recently posted". The search function allows users to look for titles by US Library of Congress search terms, as well as by going through Google and Yahoo metadata. The majority of these books are within the public domain and therefore free from copyright restrictions, although undoubtedly there are some that are orphaned by subsequent changes to US copyright terms (which in most cases of published texts, is now 70 years after the death of the author). Due to this, as well as differences in copyright law internationally, the complete legal legitimacy of its collection is in question, despite careful attempts to comply with US copyright law. It is important to note that Project Gutenberg is a project, rather than a single library, with sister affiliations in many countries (Project Gutenberg Australia, Project Gutenberg Europe among many others). This, alongside its non-profit stance (Project Gutenberg accepts donations, and also calls for volunteer help with proofreading and digitization of books, as well as recording audio books) lends moral legitimacy to its online distribution of texts.
</p><p>Questions —
Looks like a classic collection; the interface is classic; based on a wiki; speaks of legitimacy
</p><p><b>Who is responsible and what are they responsible for?</b>This is all the stuff that's in the public domain...<br>
<b>What could be the motivation to make such a library?</b><br>
<b>What values does it communicate?</b> Good. Air of legitimacy; “library of congress search terms” and google to collect information. On this way they seek legitimacy from the on-line and off-line agents.<br>
<b>What do they mean 'a project'? (is this an agent of legitimacy?)</b> Involves many people; projects into the future; mutable (not set in stone)<br>
<b>What is it filtered out and what are the political implications of that?</b><br>
<b>How does the codex form limit what is available?</b><br>
<b>Who does the library serve?</b> user friendly interface; Also limitations of content, classic collection<br>
<b>Who is responsible and what are they responsible for?</b>
</p><p><br>
</p>
<pre> AAAAARG.FAIL
</pre>
<p>Abstract — Out of the necessity for a library, for artist Sean Dockray's LA-based educational institution called "The Public School", aaaaarg.fail (formerly aaarg.org, then aaaarg.org) is a website that hosts a collection of mostly theory and critical theory texts, and an online forum for members. Access to the collection comes from registering an account (you must be invited by a member first). Members can upload and download texts, as well as request titles via the forum. The changes in the domain name for the library come from repeated copyright infringement allegations from publishers of works that have been made accessible on the site, including the Australian publisher Macmillan. The publisher hired Mark Taylor, a former music industry executive, who was instrumental in bringing forth a cease and desist order against aaarg.org. Dockray later called this "another case where university students are conceived of as consumers, as carriers of debt for everything from degrees to consumer electronics to intellectual property" (<aclass="external free"href="http://unprojects.org.au/magazine/issues/issue-4-2/the-future-and-the-public-school/"rel="nofollow">http://unprojects.org.au/magazine/issues/issue-4-2/the-future-and-the-public-school/</a> ).
</p><p>Questions —
</p><p><b>Who does the library serve? (who are the customers?)</b> Intellectual snobs. You have to be invited<br>
<b>Forum? What affordance does that give?</b>Sociability? There is a set of manners<br>
The forum produces a text (a form of collective annotation); a discussion on the texts in the library. Because you can make requests it is much more personal. You can also select by "most requested", which means that a hierarchy of information is produced within the forum.(by the discussion of the members)<br>
</p><p><b>How is it different if you can participate in discussing the content of a library, than just be a viewer-receiver of the content?</b><br>
<b>Who is responsible and what are they responsible for?</b><br>
<b>How is it different to be an exclusive member in order to have access to the content of a library, compared to have no restrictions in accessing it?</b><br>
<b>How does the collection (and discourse around it) represent the members of the library?</b><br>
<b>If the library is based on user requests, it's a mirror of the members interests/social status/credentials/ideologies/clout</b><br>
<b>Does this platform require a certain degree of library literacy and research skills?</b><br>
<b>Does the background of the librarians affect the content presented in a library?</b><br>
</p><p><br>
</p>
<pre> UBUWEB.COM
</pre>
<p>Abstract — UbuWeb.com is a large web-based, free, non-commercial resource for avant-garde poetry, music, film, literature and more, founded in 1996 by poet Kenneth Goldsmith. It offers visual, concrete and sound poetry, expanding to include film and sound art mp3 archives. The site's architecture limits retrieval to keyword searching and browsing by media type and artist/project name. In addition, sustainability is a concern for this website as it was never intended to be a permanent archive. Still, there is no comparable commercial source for the content on UbuWeb so it is valuable as a resource for libraries to point users toward so long as librarians are aware of its limitations. It is a library which is ever-expanding in uncanny—and often uncategorizable—directions. Each section has an editor who brings to the site their area of expertise. UbuWeb is not n to any academic institution, instead relying on alliances of interest and benefiting from bandwidth donations from its partnerships with GreyLodge, WFMU, PennSound, The Electronic Poetry Center, The Center for Literary Computing, and ArtMob. UbuWeb was founded in response to the marginal distribution of crucial avant-garde material. It remains non-commercial and operates on a gift economy. UbuWeb ensures educational open access to out-of-print works that find a second life through digital art reprint while also representing the work of contemporaries. It addresses problems in the distribution of and access to intellectual materials.
</p><p>Questions —
</p><p><b>Who does the library serve?</b><br>
<b>What could be the motivation to make such a library?</b><br>
<b>What values does it communicate?</b><br>
<b>How can the material available in a library shape the discourse around a particular field?</b>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/1/13/Pdf_access.jpeg/960px-Pdf_access.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/1/13/Pdf_access.jpeg/320px-Pdf_access.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Pdf_access.jpeg.html"title="Enlarge"></a></div>Flow chart from Facebook group <i>Ask for PDFs from People with Institutional Access</i></div></div></div>
<p><ahref="WdKA_Research_Station.html"title="User:Simon/Trim4/fieldwork/WdKA Research Station">User:Simon/Trim4/fieldwork/WdKA Research Station</a>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/9/96/Glossed_manuscript.jpeg/640px-Glossed_manuscript.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/9/96/Glossed_manuscript.jpeg/320px-Glossed_manuscript.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Glossed_manuscript.jpeg.html"title="Enlarge"></a></div>A glossed manuscript of a late-thirteenth-century Latin translation of a medical work by Hippocrates</div></div></div>
<p>Main question: How can annotation be useful to us, and a third party?
</p><p>Possible ways
</p><p>Keep text and annotations together
</p>
<ul><li>scan and overlay transparencies (more like a graphical representation but perhaps not very readable)</li>
<li>write, re-write, cut and paste the annotations in a bigger paper all together</li>
<li>use the annotation bot (a digital tool)(it would be cool if you could underline, etc - yes! including graphic elements)</li>
<li>if digital, create the possibility to turn on and off the annotations to keep the original text</li>
<li>bind the pages into books and make a bootleg library with them</li></ul>
<p>Separate text and annotations (deconstruction / structure analysis)
</p>
<ul><li>only underlined text (in many ways: lines, circles, waves...)</li>
<li>list of questions, tags, notes + composition and mapping of them (different mapping techniques)</li>
<li>historical timeline</li>
<li>only drawings?</li>
<li>free graphical interpretation</li></ul>
<p>Computer driven annotation
</p>
<ul><li>scrape the text (words processing)</li>
<li>pattern recognition</li>
<li>delete all articles and implicit elements</li></ul>
<p>Combine the above possibilities
</p>
<ul><li>overlay of analog annotations to represent "heat patterns" (parts of the text with lots of/little engagement), as well as a digital version that is more legible</li></ul>
<p>HOW DO I KNOW WHAT I AM READING? We are discussing form how do we talk about content?<br>
How do you make the content readable for others?<br>
How do you communicate what you're interpreting?<br>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/9/96/Glossed_manuscript.jpeg/960px-Glossed_manuscript.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/9/96/Glossed_manuscript.jpeg/320px-Glossed_manuscript.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Glossed_manuscript.jpeg.html"title="Enlarge"></a></div>A glossed manuscript of a late-thirteenth-century Latin translation of a medical work by Hippocrates</div></div></div>
<p><ahref="Annotations_08.05.19.html"title="User:Simon/Reading,Writing & Research Methodologies SI9/Annotations 08.05.19">User:Simon/Reading,Writing & Research Methodologies SI9/Annotations 08.05.19</a>
</p>
<!--
NewPP limit report
Cached time: 20200616184413
Cached time: 20200620064546
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.010 seconds
Real time usage: 0.060 seconds
Preprocessor visited node count: 4/1000000
Preprocessor generated node count: 16/1000000
Post‐expand include size: 1464/2097152 bytes
CPU time usage: 0.012 seconds
Real time usage: 0.012 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/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)
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/4/49/Mcluhan_read_guess.jpeg/640px-Mcluhan_read_guess.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/4/49/Mcluhan_read_guess.jpeg/320px-Mcluhan_read_guess.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Mcluhan_read_guess.jpeg.html"title="Enlarge"></a></div>A quote from Marshall McLuhan during a live television broadcast, 1977</div></div></div>
<h3><spanclass="mw-headline"id="Abstract_of_workshop">Abstract of workshop</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Final_Workshop&action=edit&section=T-2"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h3>
<p>We read texts, and write notes in the margins; usually in private, isolated from other readers. We come across texts with others' notes on them; the author unknown, their thoughts obscure. What happens when we share our notes, vocalise and perform them?
</p><p>In this workshop...we'll read, annotate and discuss an open letter which asks for pirate library practices to come out from the shadows. We'll read aloud and perform parts of the text, enriched by our doubts, sympathies, tensions and diverse understandings. We'll personalise the text, opening it up for collective conversations. Our voices will occupy the space and leave traces on the text and in the library.
Meet each other: have a quick round of saying something about ourselves and what do we know about pirate/shadow libraries. Short description of the steps of the workshop and let people know we'll be recording.
</p><p>Overview of what happens in this workshop in one sentence:
</p><p>1st part: Reading/Annotating, heatmap<br>
2nd part: Discussion, Rehearsal of Performative reading and recording of performance.
</p><p><br>
Topic: pirate libraries - topic of special Issue 9<br>
Text: "In solidarity with Library Genesis & Sci-Hub" letter<br>
Aim: 2-3 sentences of what is the aim of this workshop. Why this collective reading-conversations matter?
</p><p>- We see "annotations" as a way to express our understandings/questions/comments/disagreements/ tensions/positions about what we read. So we can discuss about it and form a collective understanding of the text. Our aims are to:
</p><p>- open up a conversation about pirate libraries, through a deeper collective understanding of a specific text that refers to this topic (enrichment comes through collectively reading and annotating the text)
</p><p>- develop ways in which texts can become conversations through annotating together
</p><p>- make public what we have learned about pirate libraries and annotation, and to reflect on the public's response(s)
Materials: "In Support of Library Genesis & Sci-Hub" English language letter (on A3 spread), A3 tracing paper, ballpoint pens (annotation pack)<br>
</p><p>- We provide the solidarity letter in an A3 pack
</p><p>- Read the text individually
</p><p>- Annotate the text in English. (It will be traced through carbon paper to the tracing paper underneath.)
</p><p><br>
<b>STEP 2: Heatmap and discussion through the annotations</b> (20min) SIMON<br>
Materials: Same as Step 1<br>
Participants: Whole group/Small groups<br>
Archiving step: Photographs of annotated texts, discussion<br>
</p><p>Create a "heatmap" of the text by placing tracing papers with annotations on top of each other, showing which areas are interesting/remarkable to others.
</p>
<ul><li>We can focus in the most "annotated", thus "active", "interesting", "relevant" parts of the text. At the end of the heatmap stage we introduce the discussion by identifying common areas of annotation, and also listing things that need further definition. Why did you annotate this part? What is the "global north"? etc.</li>
<li>Comment generally on the text, what was interesting? Did you make sense? Are there specific parts you want to discuss?</li>
<li>Conclusions? Comments? Discuss the most commented.</li>
<li>Discuss this experience and anything we want to discuss about pirate libraries, this text, our experiences.</li>
<li>Collectively determine strategies to "amplify" specific parts of the texts that either</li></ul>
Participants: All together (if more than 10, divide into two groups???)<br>
Materials: Annotated "In Support of Library Genesis & Sci-Hub" letter, audio recording device (ZOOM rented from WdKA shop/smartphone), (maybe speakers?)<br>
Archiving step: Voice recording
</p>
<ul><li>Introduce by saying: "We are going to read aloud the text in turns, while also performing our annotations. Try to perform your comment to make your position/understanding of the text clear. If you have an annotation, please do or say something (e.g. interrupt, whisper, raise your hand, make a noise, use an accent, use intonation to convey emotion etc)."</li>
<li>The text becomes a "play", a performance, a discussion between us</li>
<li>The purpose is to activate a text, by transforming it into a conversation through spoken annotation</li>
<li>This reading will be recorded (ask)</li>
<li>Decide on an "interesting" way of performing and record that. It could be more than one language in this audio piece.</li></ul>
<p><br>
OUTPUT:<br>
At Leeszaal:
</p>
<ul><li>Play the collective recording from speakers placed in shelves at Leeszaal (Bluetooth)</li></ul>
<p>Later:
</p>
<ul><li>Printed version with the overlapping of individual comments - heatmap - pocket version???</li>
<li>Printed URL on annotated tracing paper to direct readers to the online versions of the texts?</li>
<li>Bookmark or some object (it can be the pocket version) to introduce it in some books in Leeszaal, understanding that as a way to spread the letter (like sowing seeds)</li></ul>
<p><br>
</p><p>POST-WORKSHOP MATERIAL:
</p>
<ul><li>Transcription of the voice performance (we can be inspired by film transcriptions) - perhaps we could annotate this as well:<br></li></ul>
<aclass="external text"href="https://pad.xpub.nl/p/sh_encoding_decoding%7C"rel="nofollow">Annotations on Stuart Hall's <i>Encoding, Decoding</i></a>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/4/49/Mcluhan_read_guess.jpeg/960px-Mcluhan_read_guess.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/4/49/Mcluhan_read_guess.jpeg/320px-Mcluhan_read_guess.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Mcluhan_read_guess.jpeg.html"title="Enlarge"></a></div>A quote from Marshall McLuhan during a live television broadcast, 1977</div></div></div>
</p><p><aclass="external text"href="https://pad.xpub.nl/p/sh_encoding_decoding%7C"rel="nofollow">Annotations on Stuart Hall's <i>Encoding, Decoding</i></a>
</p>
<!--
NewPP limit report
Cached time: 20200617092208
Cached time: 20200620064609
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.030 seconds
Real time usage: 0.094 seconds
Preprocessor visited node count: 6/1000000
Preprocessor generated node count: 20/1000000
Post‐expand include size: 5529/2097152 bytes
CPU time usage: 0.006 seconds
Real time usage: 0.008 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/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.209 1 User:Simon/Final_Workshop
100.00% 3.209 1 -total
100.00% 0.000 1 -total
-->
<!-- Saved in parser cache with key wdka_mw_mediadesign-mw_:pcache:idhash:31742-0!canonical and timestamp 20200617092208 and revision id 174227
<!-- Saved in parser cache with key wdka_mw_mediadesign-mw_:pcache:idhash:31742-0!canonical and timestamp 20200620064609 and revision id 175080
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/a/ae/Proper_posture_for_writing_with_pen.jpeg/640px-Proper_posture_for_writing_with_pen.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/a/ae/Proper_posture_for_writing_with_pen.jpeg/320px-Proper_posture_for_writing_with_pen.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Proper_posture_for_writing_with_pen.jpeg.html"title="Enlarge"></a></div>‘Proper posture for writing with pen’</div></div></div>
Cover stock: Heavy green stock (unknown brand) - around 210gsm<br>
Text stock: Laser 80gsm<br>
Binding: Perfect bound, hot glue<br>
Pages: 330pp
</p><p>Johanna Drucker's <i>The Alphabetic Labyrinth</i> is a book that traces the history and development of the alphabet. Full of diagrams and densely populated with these histories, it demands printing and reading in physical form. A PDF just won't do. I printed this from a PDF that I laid out quickly in InDesign using my trusty placemultiplePDFpages script. The cover was made on the photocopier, a technique I was well-acquainted with from my days as a teacher, where lessons would be literally cut and pasted together to be copied on the glass. The task that took the most time was making sure the pages would be printed at reasonable size, while economising on paper. For this reason, I wanted to print it double-sided on A4 paper with minimal excess. The annotations (interestingly, many in Greek - a coincidence as the book focuses for some time on development of the Greek alphabet) and artefacts from scanning were retained (such as darkened page edges), creating a materiality that reminds one the book is most definitely loved, copied, and shared.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/a/ae/Proper_posture_for_writing_with_pen.jpeg/960px-Proper_posture_for_writing_with_pen.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/a/ae/Proper_posture_for_writing_with_pen.jpeg/320px-Proper_posture_for_writing_with_pen.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Proper_posture_for_writing_with_pen.jpeg.html"title="Enlarge"></a></div>‘Proper posture for writing with pen’</div></div></div>
<h2><spanid="what_is_a_library?"></span><spanclass="mw-headline"id="what_is_a_library.3F">what is a library?</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/Running_backwards_through_the_library&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>A basic definition of a library, because it's called for, because we've moved so far from it being simply a collection of books:
</p>
<pre>A library retains:
* a collection of texts
A library produces:
* sociability
A library gives access to:
* knowledge</pre>
<p>Each statement declares the verb and object predicated by the subject of "A library". What if these objects were exchanged between these sentences?
</p><p>So
</p><p>It becomes
</p>
<pre>A library retains sociability, produces a collection of texts, and gives access to knowledge.
A library retains knowledge, produces sociability, and gives access to a collection of texts.
A library retains a collection of texts, produces knowledge, and gives access to sociability.</pre>
<h2><spanclass="mw-headline"id="Perspectives_on_current_and_potential_libraries">Perspectives on current and potential libraries</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/Running_backwards_through_the_library&action=edit&section=T-2"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>By changing parts of speech (the verb and its object), we can imagine different scenarios that potential (and current) libraries can play out. For example:
</p>
<pre>A library retains knowledge</pre>
<p>Retention of knowledge points towards the desire to acquire information that has high value; intellectual, social, practical etc.
</p>
<pre>produces a collection of texts</pre><p>
What are the texts that can be produced? Metadata, annotations and marginalia, infrastructural interfaces for readers (signage, an index, a classification system)
</p><pre>and gives access to sociability</pre>
<p>How does the library give access to sociability? What are the necessary actions for sociability to become accessible, and what are the limits to accessibility?
<p><ahref="Running_backwards_through_the_library.html"title="User:Simon/Trim4/Running backwards through the library">User:Simon/Trim4/Running backwards through the library</a>
</p>
<!--
NewPP limit report
Cached time: 20200616220301
Cached time: 20200620064647
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.012 seconds
Real time usage: 0.016 seconds
Preprocessor visited node count: 20/1000000
Preprocessor generated node count: 68/1000000
Post‐expand include size: 1193/2097152 bytes
CPU time usage: 0.010 seconds
Real time usage: 0.010 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/40
Expensive parser function count: 0/100
Unstrip recursion depth: 0/20
Unstrip post‐expand size: 546/5000000 bytes
Unstrip post‐expand size: 0/5000000 bytes
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
</p><p>Hope A Olson's text "Mapping Beyond Dewey's Boundaries" on spatial representations in classification systems, explored through a project that attempted to cross-reference two classification systems - <aclass="external text"href="https://www.amazon.com/Womens-Thesaurus-Index-Language-Ellen/dp/0061811718"rel="nofollow"><i>A Woman's Thesaurus</i></a> and Dewey Decimal Classification by <aclass="external text"href="http://capekconsulting.com/about-mary-ellen-capek/"rel="nofollow">Mary Ellen S Capek</a>. Stating that "classifications are locational systems" suggests that spatial representations can be used with various effect; describing, exposing, and when used as metaphors, shifting the discourse.
</p><p><b>1. Spatial representation of classification systems reveals the ideological conditions that form them.</b>
</p><p>Olson refers to spatial representations of classification systems in the form of diagrams.
</p><p>The first diagram is one that shows distribution of subjects, with the idea of a mainstream core that diffuses towards the margins. The second is a Venn diagram that illustrates how "mainstream" or "core" descriptors actually eventuate in very small "cores" due to limitations by Boolean "ands'. Venn diagrams operate on the basis of duality - something is or isn't part of a set.<br>
</p><p><b>2. The concepts of "paradoxical space" and "rhetorical space". </b>
</p><p>Paradoxical space is described in a similar way to the paranodal; being "both inside and outside, center and margins".
</p>
<h2><spanid="thoughts_&_reflections"></span><spanclass="mw-headline"id="thoughts_.26_reflections">thoughts & reflections</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/spatial_classification&action=edit&section=T-2"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>How to utilise a "paradoxical space"? The text seems to suggest focusing on connections, relationships between subjects rather than differences? What could an associative classification system look like?
</p><p>The space of a page is crucial in the printed format - the text block excludes the margin - clearly delineating what is recognized as authored, and what is not. Book printing has many terms to cut up a page into a layout - deciding on "safe areas" to print and areas to leave open. In my own experience, shaping the text block is the first consideration when laying out a page.
</p><p>However, some formats of digital books (e.g. EPUB) do not have the notion of a page. There is the space of the screen, but this is mutable, whereas a printed page is not.
<p>Eva Weinmayr's Piracy Project invites submissions of pirated books. The books are collected in public places (e.g galleries, art book fairs) where visitors are available to read them.
</p><p>Of particular interest are the editorial decisions made in the pirating of the books. Copying of a book invites an inevitable comparison between the "source" and the "copy". It is not as straightforward as assuming a hierarchy based on chronology - such as in the case of a leaked manuscript - the "origin" may have been published after the "copy". Instead, a list of words describing the possible motivations are devised to examine the possible motivation for pirating:
</p><p>Borrowing<br>
Poaching<br>
Plagiarising<br>
Pirating<br>
Stealing<br>
Gleaning<br>
Referencing<br>
Leaking<br>
Copying<br>
Imitating<br>
Adapting<br>
Faking<br>
Paraphrasing<br>
Quoting<br>
Reproducing<br>
Using<br>
Counterfeiting<br>
Repeating<br>
Translating<br>
Cloning<br>
</p>
<hr>
<p>We added a few to the list based on our analyses:
</p><p>Silencing<br>
Editing<br>
Omitting<br>
Reducing<br>
Appending<br>
Redirecting<br>
Recontextualising<br>
Focusing<br>
(Faithfully) Reproducing<br>
Caring<br>
Reformatting<br>
Bootlegging<br>
Reframing<br>
Retracing<br>
</p><p>This reminds me of the list of words I devised for my FTB project - however my list was of names of types of "marks of use" made in books from a section of a public collection in a library. Using verbs instead of nouns is a subtle shift away from concrete definitions of modifications between the published book and its counterpart towards a actions that may have produced these modifications.
</p>
<h2><spanclass="mw-headline"id="two_books_from_the_project_-_an_analysis">two books from the project - an analysis</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Workshop_Eva_Weinmayr&action=edit&section=T-2"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>Artemis & I examined two pirated books, speculating on the strategies behind their duplication and making notes and questions related to each one:
</p>
<pre> Book 1: <i>Teignmouth Electron - Tacita Dean</i>
<b>Notes & Questions:</b> A caring reproduction from an independent editorial project, showing special value on the content. Seems that there is collaboration with the artist, but don't have permission from the previous publisher.
Has an isbn number. It seems not like a pirate version but as an official published version.
Making a choice between what should and shouldn't be translated - e.g. Space Oddity appears in both English and Spanish.
The text is privileged over the images, and reproduction comes into play with the different printing methods. Photography as a visual medium that relies on reproduction.
It's an adaption in that it drastically changes the format (and slightly changes the content) to meet a need (to connect with a larger audience of Spanish speakers), and can be seen as vastly different from the source.
Is the translator the author? What happens with copyright in this case?
</p>
<pre> Book 2: <i>Shampoo by Robert Towne and Warren Beatty, silenced by K. Lassinaro</i>
</pre>
<p><b>Strategies:</b> Silencing, Reducing, Redirecting, Reframing, Recontextualising,(re)Focusing, (Translating (from an aural/oral/visual source to a literate destination), Re-mediating, censoring, critiquing, deleting violating<br>
<b>Notes & Questions:</b> What is the source? Is it a film, or the manuscript? Is the manuscript published? We found it easily in the web. Is a manuscript a publication? Does this constitute fair use? The pirate edition makes space for the imagination of the reader to fill the gaps. The focus seems to be the "container bag" instead of the "content". The "source" was focusing in a visual experience, while the pirate version does the opposite. The dialogues don't matter / Critique on the content
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/7/7e/Author_book_signing.jpeg/960px-Author_book_signing.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/7/7e/Author_book_signing.jpeg/320px-Author_book_signing.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Author_book_signing.jpeg.html"title="Enlarge"></a></div>An author signing a book</div></div></div>
<p><ahref="Workshop_Eva_Weinmayr.html"title="User:Simon/Workshop Eva Weinmayr">User:Simon/Workshop Eva Weinmayr</a>
</p>
<!--
NewPP limit report
Cached time: 20200617092213
Cached time: 20200620064724
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.021 seconds
Real time usage: 0.050 seconds
Preprocessor visited node count: 5/1000000
Preprocessor generated node count: 18/1000000
Post‐expand include size: 3886/2097152 bytes
CPU time usage: 0.009 seconds
Real time usage: 0.010 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/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% 2.667 1 User:Simon/Workshop_Eva_Weinmayr
100.00% 2.667 1 -total
100.00% 0.000 1 -total
-->
<!-- Saved in parser cache with key wdka_mw_mediadesign-mw_:pcache:idhash:31743-0!canonical and timestamp 20200617092213 and revision id 174093
<!-- Saved in parser cache with key wdka_mw_mediadesign-mw_:pcache:idhash:31743-0!canonical and timestamp 20200620064724 and revision id 175084
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/2/26/A6_invitations_bl.jpeg/640px-A6_invitations_bl.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/2/26/A6_invitations_bl.jpeg/320px-A6_invitations_bl.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:A6_invitations_bl.jpeg.html"title="Enlarge"></a></div>A6 invitations for the bootleg library</div></div></div>
04.128 (A small office in the drawing station, by the printer)<br>
<b>Things to bring:</b> a computer (or a USB drive) with some of your favourite texts on it, a cup for tea or coffee if you want some (there will be spare cups if needed)<br>
<br>
<b>bootleg library sessions</b><br>
During these sessions, we'll have an introduction to the bootleg library, and create user accounts. Once you have a user account you will have full access to useful features of the library, such as arranging the collection through public and private "shelves", as well as downloading and uploading texts. If we have time, we can discuss the things we're reading, and how we'd like to use this library. These sessions are free and open for all to attend, and tea, coffee and snacks will be provided.
</p><p><b>about the bootleg library</b><br>
The bootleg library is a local collection of texts, available in digital (mostly PDFs and EPUB) and physical (printed) form. The digital library is available over a local network, at this URL: <aclass="external free"href="http://145.24.131.15:20190"rel="nofollow">http://145.24.131.15:20190</a>. Much of the collection has been “bootlegged”, meaning that the books have been copied, modified, and redistributed, unauthorised, as fairly faithful reproductions of a source publication.
</p><p>The physical library is a growing collection of republished books, mostly made by Simon Browne (XPUB), sometimes donated by visitors. These books, currently stored in a box on a shelf in the Lens-Based studio, are available to be read, borrowed and annotated, with a condition that they are returned.
</p><p>The digital library runs on calibre-web <aclass="external free"href="https://github.com/janeczku/calibre-web"rel="nofollow">https://github.com/janeczku/calibre-web</a>, a web interface for Calibre, which is open-source software for ebook management. Calibre allows storage and conversion of ebooks in many file formats, which can all be listed under the one catalogue entry, providing a diversity of formats for different reading needs; print, full text search, copy/paste, hyperlinked references, etc. The software also allows users to manually or automatically enter cataloguing details, and create and edit "shelves". These shelves are either public or private, so users may organise the collection together, and also create their own sections of books that are individually organised.
</p><p>The bootleg library has a smaller collection than many other libraries, but it is personalised, collective, and local. It has a curated collection of eclectic texts, individually uploaded and catalogued by readers who want to share them. Readers, and the texts they read, are represented in the library, and by way of alternative library practices this representation produces a certain kind of sociability. Through using this library, readers and texts become active participants in the collection. If you know the person you know something about the book, and vice-versa, or if you don't there is the opportunity to find out more.
</p>
<hr>
<p>The conditions for uploading are that;
</p>
<ol><li>the contributor is familiar with the text, and</li>
<li>the contributor completes the metadata on each upload</li></ol>
<p>Most important are the description and page fields; these are completed subjectively. Texts are tagged with keywords that indicate the subject, such as “Media Theory”, “Fiction”, “Technical manuals” etc., and also (if applicable) the person who referred them, which can be the contributor, or another person e.g. “Amy’s books”, “Steve’s books”, “Simon’s books” etc. Anyone who is on the local network and knows the URL can download or upload texts, but only those with a user account will have access to its more useful features, such as the ability to create and edit public and private “shelves”, which is how the collection may be both collectively, and individually organised.
</p><p>During these workshops, we will engage in a variety of activities;
</p>
<ul><li>creating user accounts</li>
<li>collectively determining the development of desired features in the library</li>
<li>uploading and cataloguing texts</li>
<li>classifying texts in shelves, both public and private</li>
<li>downloading, reading, annotating and discussing texts</li>
<li>digitising printed matter, including scanning and OCR</li>
<li>designing, printing and binding books for the physical bootleg library</li></ul>
<p>The Bootleg Library represents its readers through various strategies;
</p>
<ul><li>a horizontal approach to classification through collective organisation of public shelves</li>
<li>personalisation of the catalogue through subjective descriptions and tags, elevating the position of the reader in regard to texts</li>
<li>ability to navigate the collection through the sociability of its users - if you know a person whose name appears as a tag in the metadata, you know something about the text, and vice-versa</li>
<li>development of a collection and interface made by and for its readers, containing texts that are personally chosen and shared within our community</li></ul>
<p>The workshop sessions are open to all who are interested, and will be published on the media design calendar. Registration is not necessary, but please refer to the calendar entries for any other specific requirements for each workshop.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/2/26/A6_invitations_bl.jpeg/960px-A6_invitations_bl.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/2/26/A6_invitations_bl.jpeg/320px-A6_invitations_bl.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:A6_invitations_bl.jpeg.html"title="Enlarge"></a></div>A6 invitations for the bootleg library</div></div></div>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/82/Bl_announcement_poster.jpeg/640px-Bl_announcement_poster.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/82/Bl_announcement_poster.jpeg/320px-Bl_announcement_poster.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Bl_announcement_poster.jpeg.html"title="Enlarge"></a></div>Poster announcing the bootleg library, July 2019</div></div></div>
<liclass="toclevel-2"><ahref="#Creating_a_unit_file"><spanclass="tocnumber">1.1</span><spanclass="toctext">Creating a unit file</span></a></li>
<liclass="toclevel-2"><ahref="#Starting_the_calibre-server_service"><spanclass="tocnumber">1.2</span><spanclass="toctext">Starting the calibre-server service</span></a></li>
<liclass="toclevel-2"><ahref="#Stopping_the_calibre-server_service"><spanclass="tocnumber">1.3</span><spanclass="toctext">Stopping the calibre-server service</span></a></li>
<liclass="toclevel-2"><ahref="#Checking_the_status_of_the_calibre-server_service"><spanclass="tocnumber">1.4</span><spanclass="toctext">Checking the status of the calibre-server service</span></a></li>
<liclass="toclevel-2"><ahref="#Enabling_the_calibre-server_service_to_start_at_boot"><spanclass="tocnumber">1.5</span><spanclass="toctext">Enabling the calibre-server service to start at boot</span></a>
<h3><spanclass="mw-headline"id="Creating_a_unit_file">Creating a unit file</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/calibre_service_file&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h3>
<p>You can easily create a unit file for calibre to run on boot on a modern (systemd) based Linux system. This means it will also restart after a crash. Create the file <code>/etc/systemd/system/calibre-server.service</code> with the contents shown below:
</p>
<pre>[Unit]
Description=Calibre.
After=syslog.target network.target
[Service]
Type=simple
User=pi
Group=pi
WorkingDirectory=/home/pi/calibre-web
ExecStart=python cps.py
Restart=always
[Install]
WantedBy=multi-user.target</pre>
<p>The <code>User</code> and <code>Group</code> should be the same ones that own the files in the calibre library directory. It's generally not a good idea to run the server as root. Also change the path to the calibre library directory to suit your system.
</p>
<h3><spanclass="mw-headline"id="Starting_the_calibre-server_service">Starting the calibre-server service</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/calibre_service_file&action=edit&section=T-2"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h3>
<h3><spanclass="mw-headline"id="Checking_the_status_of_the_calibre-server_service">Checking the status of the calibre-server service</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/calibre_service_file&action=edit&section=T-4"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h3>
<p>Check its status with:
</p><p><code>sudo systemctl status calibre-server</code>
</p>
<h3><spanclass="mw-headline"id="Enabling_the_calibre-server_service_to_start_at_boot">Enabling the calibre-server service to start at boot</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/calibre_service_file&action=edit&section=T-5"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h3>
<p>The calibre server does not need a running X server, but it does need the X libraries installed as some components it uses link against them.
</p><p>The calibre server also supports systemd socket activation, so you can use that, if needed, as well.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/82/Bl_announcement_poster.jpeg/960px-Bl_announcement_poster.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/82/Bl_announcement_poster.jpeg/320px-Bl_announcement_poster.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Bl_announcement_poster.jpeg.html"title="Enlarge"></a></div>Poster announcing the bootleg library, July 2019</div></div></div>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/ee/RFID_tag.jpeg/640px-RFID_tag.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/ee/RFID_tag.jpeg/320px-RFID_tag.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:RFID_tag.jpeg.html"title="Enlarge"></a></div>Illustration of an RFID tag</div></div></div>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/ee/RFID_tag.jpeg/960px-RFID_tag.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/ee/RFID_tag.jpeg/320px-RFID_tag.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:RFID_tag.jpeg.html"title="Enlarge"></a></div>Illustration of an RFID tag</div></div></div>
<h2><spanclass="mw-headline"id="11.11.19_Extracting_text_using_curl">11.11.19 Extracting text using curl</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/Extracting_text_from_the_web&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p><code>curl</code> is a command that can be used from the terminal to take text from a URL. It can be piped with software such as pandoc to convert the text to other formats, and in support of a workflow I'm starting to develop, this comes in quite handy.
</p><p>I'm writing text on the pad, and then converting it to markdown. This extra step isn't necessary (in fact it adds to the work) but I'm interested in using pads as multi-flow publishing tools in the future so I'm testing this out. Also, using a pad allows me to style the text simply using markdown rather than HTML.
</p><p>For example, this is a file I made from some notes on a Flusser interview about linear writing:
<p>I'm then storing the files in <aclass="external text"href="https://git.xpub.nl/simoon/thesis"rel="nofollow">my git</a>, which is public. Having texts in git allows me to use its versioning capabilities, allowing me to go back over old modified versions in the file tree - I can copy paste from these snippets that I may want to go back and retain in the future...
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/2/27/Chained_books.jpeg/640px-Chained_books.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/2/27/Chained_books.jpeg/320px-Chained_books.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Chained_books.jpeg.html"title="Enlarge"></a></div>Chained books at the medieval Hereford Library</div></div></div>
<h2><spanid="bootleg_library_at_varia,_26.01.20"></span><spanclass="mw-headline"id="bootleg_library_at_varia.2C_26.01.20">bootleg library at varia, 26.01.20</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/bootleg_lib_varia_pad&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>Transcription (and partial redaction) of a pad used to draft a text for printed matter and digital publicity of the event.
</p><p><small>flyer side 1 (main text)</small><br>
</p>
<hr>
<p><b>bootleg library sessions</b>
</p><p><b>where?</b><br>
varia, a collective-space for everyday technology (gouwstraat 3)
</p><p><b>when?</b><br>
sunday, 26.01.20, 11:00-17:00 (ongoing sessions, you can come or go anytime)
</p><p><b>what to bring?</b><br>
a computer and some of your favourite ebooks (PDF, EPUB, whatever)
</p><p><b>what will we do?</b><br>
we’ll have an introduction to the “bootleg library”, which is a shared digital and physical library of bootlegged texts. let’s make user accounts, download and upload some texts, talk about what we’re reading and how we like to organise our bookshelves, and together discuss ways the library can develop.
</p><p><small>flyer side 2 (more info)</small><br>
</p>
<hr>
<p><b>about the bootleg library</b><br>
the bootleg library is a digital, and physical collection of texts. the library consists of bootlegged texts, not in the sense of cheap knock-offs, but instead as unauthorised, fairly faithful reproductions of source publications. development of the library is ongoing, in line with feedback given during sessions.
</p><p>the physical library is a growing collection of republished books, currently stored in an old champagne case. most of these are bootlegged by library members, some donated by visitors. the digital library (running on the open-source software calibre-web) is available at this URL:
</p><p>hub.xpub.nl/bootleglibrary
</p><p>then enter in the following login details:
</p><p>user: {redacted}
password: {redacted}
</p><p><b>user accounts</b><br>
registered users can access all of the features of the library, including creating and editing public and private “shelves”, which are ways to organise the collection together, or individually. user account registrations can be made at bootleg library sessions, or by request (send an email to simon at redacted@gmail.com).
</p><p><b>the current collection</b><br>
the bootleg library is small but growing, individually uploaded and catalogued by readers who are motivated simply by the desire to share the texts they read. and so the collection represents the readers interests, which range from critical theory to feminisms to literature to technical manuals and zines (and a lot more).
varia, een collectieve ruimte voor alledaagse technologie (gouwstraat 3)
</p><p><b>wanneer?</b><br>
zondag 26.01.20, 11:00-17:00 (doorlopend, je kan op ieder moment aansluiten)
</p><p><b>wat mee te nemen?</b><br>
een computer en een paar van je favoriete digitale boeken (PDF, EPUB, wat dan ook)
</p><p><b>wat gaan we doen?</b><br>
er zal een introductie over de “bootleg library” zijn, een gedeelde digitale en fysieke bibliotheek met “bootlegged” teksten. we kunnen gebruikersaccounts maken, teksten up- en downloaden, gesprekken hebben over hetgene dat we lezen of over hoe we onze eigen boekenplanken organiseren, en samen een gesprek voeren over mogelijke ontwikkelingen van deze bibliotheek.
</p><p><small>flyer side 2 (more info)</small><br>
</p>
<hr>
<p><b>over de “bootleg library”</b><br>
de “bootleg library” is een digitale en fysieke collectie van teksten. deze bibliotheek bestaat uit “bootlegged” teksten. dit zijn geen goedkope aftreksels, maar ongeautoriseerde, vrij precieze reproducties van orginele publicaties. de bibliotheek is in ontwikkeling, en laat zich sturen door de gesprekken die tijdens sessies worden gevoerd.
</p><p>de fysieke bibliotheek is een groeiende collectie van hergepubliceerde boeken, op dit moment opgeslagen in een oude champagne doos. het grootste deel van deze publicaties zijn “bootlegs” van leden van de bibliotheek, anderen zijn gedoneerd door bezoekers. de digitale bibliotheek (die draait op het open source software project calibre-web) is te vinden op:
</p><p>hub.xpub.nl/bootleglibrary
</p><p>daar kun je de volgende login gegevens invoeren:
</p><p>user: {geredigeerd}
password: {geredigeerd}
</p><p><b>gebruikersaccounts</b><br>
geregistreerde gebruikers kunnen alle functies van de bibliotheek gebruiken, zoals het maken en aanpassen van publieke en persoonlijke “planken”, een instrument om collecties samen of individueel te beheren. gebruikersaccounts kunnen gemaakt worden tijdens “bootleg library” sessies, of op aanvraag (send an email to simon at geredigeerd@gmail.com).
</p><p><b>de huidige collectie</b><br>
the “bootleg library” is klein maar groeiende, individueel geupload en beheerd door lezers die simpelweg gemotiveerd zijn om teksten te delen die zij lezen. de collectie reflecteert daardoor de interesse van haar lezers, wat variëert van kritische theorie tot feminismes tot literatuur tot technische handleidingen en zines (en nog veel meer).
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/2/27/Chained_books.jpeg/960px-Chained_books.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/2/27/Chained_books.jpeg/320px-Chained_books.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Chained_books.jpeg.html"title="Enlarge"></a></div>Chained books at the medieval Hereford Library</div></div></div>
<p><ahref="bootleg_lib_varia_pad.html"title="User:Simon/bootleg lib varia pad">User:Simon/bootleg lib varia pad</a>
</p>
<!--
NewPP limit report
Cached time: 20200617090026
Cached time: 20200620064845
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.018 seconds
Real time usage: 0.041 seconds
Preprocessor visited node count: 5/1000000
Preprocessor generated node count: 18/1000000
Post‐expand include size: 5410/2097152 bytes
CPU time usage: 0.005 seconds
Real time usage: 0.006 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/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% 2.724 1 User:Simon/bootleg_lib_varia_pad
100.00% 2.724 1 -total
100.00% 0.000 1 -total
-->
<!-- Saved in parser cache with key wdka_mw_mediadesign-mw_:pcache:idhash:31753-0!canonical and timestamp 20200617090026 and revision id 174152
<!-- Saved in parser cache with key wdka_mw_mediadesign-mw_:pcache:idhash:31753-0!canonical and timestamp 20200620064845 and revision id 175089
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d4/What_is_publication_stadler.jpeg/640px-What_is_publication_stadler.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d4/What_is_publication_stadler.jpeg/320px-What_is_publication_stadler.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:What_is_publication_stadler.jpeg.html"title="Enlarge"></a></div>Still from <i>What is Publication?</i>, a talk by Matthew Stadler</div></div></div>
<h2><spanid="13.12.19_-_Matthew_Stadler,_at_Leeszaal"></span><spanclass="mw-headline"id="13.12.19_-_Matthew_Stadler.2C_at_Leeszaal">13.12.19 - Matthew Stadler, at Leeszaal</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/fieldwork/Matthew_Stadler_at_Leeszaal&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p><aclass="external text"href="https://en.wikipedia.org/wiki/Matthew_Stadler"rel="nofollow">Matthew Stadler</a> is a writer, and one of the founders of Publication Studio, a federated publishing house which operates worldwide. I met with him at Leeszaal, where we discussed our mutual interests in texts, reading, libraries and open access to knowledge. Matthew was able to give some valuable insights on what makes certain publishing models, (and libraries) successful, including Publication Studio, and Leeszaal, where he works as a volunteer. His response to my bootleg library was very encouraging. It affirmed some of the hypotheses I have proposed, and offered some insights that I found quite inspiring:
</p>
<ul><li>a successful publishing practice resembles an estuary, which is a fertile ecological environment formed by the confluence of saltwater, freshwater and minerals. The metaphor is extended to the practice of contingent librarianship, which doesn't opt for one stream of activity, but provides a meeting point of many</li>
<li>what I'm most interested in is readers, and shared the act of reading as the thing that binds together a library</li>
<li>the haptic experience of reading a printed book is fundamentally one of a circuit-based spatial relationship with the book - holding the verso with the left hand, and the recto with the right. In this way the body and the text form a loop</li>
<li>small, spur-of-the-moment actions, in response to immediate needs is most effective in establishing a collective publishing project; i.e. you look at what you have to do today, you print a book, tomorrow you develop the library, a little at a time, rather than as part of some grand scheme that can very quickly become oppressive and driven by ideology instead of a practical response to circumstances</li></ul>
<p>As a writer, Matthew's interests are in the extension of the life of the book post-publication, and how it survives after it is published. There is quite a proliferation of "unofficially published" books made by artists and designers, but these are usually tied to an event: an artwork, a catalogue, a book launch; soon to be forgotten. For him (like myself), the visibility of readers supports the argument for a library's existence. This was the impetus behind a series of books published by Publication Studio, which were free to annotate using software called an.notate. Further to this interest, he co-wrote and published a book called <aclass="external text"href="http://www.revolutionreader.com/"rel="nofollow">Revolution: A Reader</a>, which is a book made from annotations made on the topic of revolution. I showed him the system of annotation on the bootleg library, which at present is just a link to an etherpad in the description. He pointed out that while the etherpad is a fertile and dynamic collaborative writing environment, having annotations in a separate window to the text lacks fixidity, and proximity.
</p><p>Matthew also brought up the topic of renumeration for publication - asking if I charged a fee for the services I offer. To me, it is not only unnecessary, but also contradictory to the type of culture the bootleg library should foster. I prefer to exchange bootlegged books for something else, and I'm printing and making them at very little material costs, only my time is expensive. I realise that this luxury is one I can afford only now, and that the question of money (as a necessary part of sustaining a publishing practice) will be an important one to address in the future.
</p><p>I'm quite interested in the aspect of publication that Matthew champions; one that ensures the survival of a publication after the fanfare of the launch event. Thinking about the use of the text in 20, 30 years time gives a very different set of priorities to thinking about how it will be read as a "current" publication. The way texts are read, distributed, and most importantly shared, precipitates a form that must be durable, and suitable to the long-term needs of the public it is presented to.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d4/What_is_publication_stadler.jpeg/960px-What_is_publication_stadler.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d4/What_is_publication_stadler.jpeg/320px-What_is_publication_stadler.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:What_is_publication_stadler.jpeg.html"title="Enlarge"></a></div>Still from <i>What is Publication?</i>, a talk by Matthew Stadler</div></div></div>
<p><ahref="Matthew_Stadler_at_Leeszaal.html"title="User:Simon/Trim4/fieldwork/Matthew Stadler at Leeszaal">User:Simon/Trim4/fieldwork/Matthew Stadler at Leeszaal</a>
</p>
<!--
NewPP limit report
Cached time: 20200617011729
Cached time: 20200620064857
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.019 seconds
Real time usage: 0.061 seconds
Preprocessor visited node count: 4/1000000
Preprocessor generated node count: 16/1000000
Post‐expand include size: 3976/2097152 bytes
CPU time usage: 0.008 seconds
Real time usage: 0.010 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/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)
04.128 (A small office in the drawing station, by the printer)<br>
<b>Things to bring:</b> a computer (or a USB drive) with some of your favourite texts on it, a cup for tea or coffee if you want some (there will be spare cups if needed)<br>
<br>
<b>bootleg library sessions</b><br>
During these sessions, we'll have an introduction to the bootleg library, and create user accounts. Once you have a user account you will have full access to useful features of the library, such as arranging the collection through public and private "shelves", as well as downloading and uploading texts. If we have time, we can discuss the things we're reading, and how we'd like to use this library. These sessions are free and open for all to attend, and tea, coffee and snacks will be provided.
</p><p><b>about the bootleg library</b><br>
The bootleg library is a local collection of texts, available in digital (mostly PDFs and EPUB) and physical (printed) form. The digital library is available over a local network, at this URL: <aclass="external free"href="http://145.24.131.15:20190"rel="nofollow">http://145.24.131.15:20190</a>. Much of the collection has been “bootlegged”, meaning that the books have been copied, modified, and redistributed, unauthorised, as fairly faithful reproductions of a source publication.
</p><p>The physical library is a growing collection of republished books, mostly made by Simon Browne (XPUB), sometimes donated by visitors. These books, currently stored in a box on a shelf in the Lens-Based studio, are available to be read, borrowed and annotated, with a condition that they are returned.
</p><p>The digital library runs on calibre-web <aclass="external free"href="https://github.com/janeczku/calibre-web"rel="nofollow">https://github.com/janeczku/calibre-web</a>, a web interface for Calibre, which is open-source software for ebook management. Calibre allows storage and conversion of ebooks in many file formats, which can all be listed under the one catalogue entry, providing a diversity of formats for different reading needs; print, full text search, copy/paste, hyperlinked references, etc. The software also allows users to manually or automatically enter cataloguing details, and create and edit "shelves". These shelves are either public or private, so users may organise the collection together, and also create their own sections of books that are individually organised.
</p><p>The bootleg library has a smaller collection than many other libraries, but it is personalised, collective, and local. It has a curated collection of eclectic texts, individually uploaded and catalogued by readers who want to share them. Readers, and the texts they read, are represented in the library, and by way of alternative library practices this representation produces a certain kind of sociability. Through using this library, readers and texts become active participants in the collection. If you know the person you know something about the book, and vice-versa, or if you don't there is the opportunity to find out more.
</p>
<hr>
<p>The conditions for uploading are that;
</p>
<ol><li>the contributor is familiar with the text, and</li>
<li>the contributor completes the metadata on each upload</li></ol>
<p>Most important are the description and page fields; these are completed subjectively. Texts are tagged with keywords that indicate the subject, such as “Media Theory”, “Fiction”, “Technical manuals” etc., and also (if applicable) the person who referred them, which can be the contributor, or another person e.g. “Amy’s books”, “Steve’s books”, “Simon’s books” etc. Anyone who is on the local network and knows the URL can download or upload texts, but only those with a user account will have access to its more useful features, such as the ability to create and edit public and private “shelves”, which is how the collection may be both collectively, and individually organised.
</p><p>During these workshops, we will engage in a variety of activities;
</p>
<ul><li>creating user accounts</li>
<li>collectively determining the development of desired features in the library</li>
<li>uploading and cataloguing texts</li>
<li>classifying texts in shelves, both public and private</li>
<li>downloading, reading, annotating and discussing texts</li>
<li>digitising printed matter, including scanning and OCR</li>
<li>designing, printing and binding books for the physical bootleg library</li></ul>
<p>The Bootleg Library represents its readers through various strategies;
</p>
<ul><li>a horizontal approach to classification through collective organisation of public shelves</li>
<li>personalisation of the catalogue through subjective descriptions and tags, elevating the position of the reader in regard to texts</li>
<li>ability to navigate the collection through the sociability of its users - if you know a person whose name appears as a tag in the metadata, you know something about the text, and vice-versa</li>
<li>development of a collection and interface made by and for its readers, containing texts that are personally chosen and shared within our community</li></ul>
<p>The workshop sessions are open to all who are interested, and will be published on the media design calendar. Registration is not necessary, but please refer to the calendar entries for any other specific requirements for each workshop.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/1/16/Bls_varia.jpeg/960px-Bls_varia.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/1/16/Bls_varia.jpeg/320px-Bls_varia.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Bls_varia.jpeg.html"title="Enlarge"></a></div>bootleg library session at Varia, 26th January, 2020</div></div></div>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/0/0d/Deadheads.jpeg/640px-Deadheads.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/0/0d/Deadheads.jpeg/320px-Deadheads.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Deadheads.jpeg.html"title="Enlarge"></a></div>“Deadheads” recording a live Grateful Dead concert, 1972</div></div></div>
<pre>---
title: notes on texts
author: collective/Etherpad
---
Notes on *Notes on Texts*, with Simon Browne, contingent librarian* at the bootleg library*
## url to this editable pad
<https://pad.xpub.nl/p/Notes_on_texts>
## bootleg library
+ <https://hub.xpub.nl/bootleglibrary>
User: THENWHO
Password: WASPHONE
### we will use:
* calibre-web, the software the bootleg library runs on
<https://github.com/janeczku/calibre-web>
* Etherpad, a browser-based, realtime collaborative text editor
**2. select a PDF, choose a page from that text**<br />
**3. annotate the page in a new etherpad document (use markdown for structure)**<br />
**4. export to plain text from etherpad**<br />
**5. convert .txt to .EPUB**<br />
**6. upload to the bootleg library**<br />
**7. paste URL of the pad you used**<br />
### workflow steps in detail:
**1. upload to the bootleg library**
* Click 'upload'
* Choose a text from your computer
* Enter metadata, or download it
* Click 'submit'
**2. select a PDF, choose a page from that text**
* Click on a catalogue entry to see the book details
* Click on 'read in browser', choose 'pdf'
* Part of what calibre web does is create URLs for each book in the library, for instance, Raymond Queneau, Exercises in Style is now referenceable as....
**3. annotate the page in a new etherpad document (use markdown for structure)**
* Make a new etherpad document* using <https://pad.xpub.nl>, name it anything you want
* Add details for title and author following the example below. The title and author can be anything you want, but this metadata is required to make an EPUB, so make sure you enter something
<code>
---
title: Annotations on Exercises In Style
author: collaborative/Etherpad
date: 21/05/20
---
</code>
* Write your annotations, use markdown* if possible
Cheatsheet available here: <https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet>
### Quick Markdown guide
* You can add URLs as hyperlinked text, for example with
[Label text here](https://hub.xpub.nl/bootleglibrary)
or
* You can also add a URL like this
<https://hub.xpub.nl/bootleglibrary>
* Headings can be added like this:
# h1
## h2
### h3
and so on...
* Emphasis can be added with <code>*single asterisks*</code>, bold with <code>**double asterisks**</code>
* Add a heading, and the URL to the pdf, before exporting, for example
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/0/0d/Deadheads.jpeg/960px-Deadheads.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/0/0d/Deadheads.jpeg/320px-Deadheads.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Deadheads.jpeg.html"title="Enlarge"></a></div>“Deadheads” recording a live Grateful Dead concert, 1972</div></div></div>
<p><ahref="Notes_on_texts_workflow.html"title="User:Simon/Notes on texts workflow">User:Simon/Notes on texts workflow</a>
</p>
<!--
NewPP limit report
Cached time: 20200617092217
Cached time: 20200620064930
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.019 seconds
Real time usage: 0.094 seconds
Preprocessor visited node count: 6/1000000
Preprocessor generated node count: 24/1000000
Post‐expand include size: 31/2097152 bytes
CPU time usage: 0.006 seconds
Real time usage: 0.006 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/40
Expensive parser function count: 0/100
Unstrip recursion depth: 0/20
Unstrip post‐expand size: 4706/5000000 bytes
Unstrip post‐expand size: 0/5000000 bytes
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/86/Networking_diagrams.jpeg/640px-Networking_diagrams.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/86/Networking_diagrams.jpeg/320px-Networking_diagrams.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Networking_diagrams.jpeg.html"title="Enlarge"></a></div>Network topologies, ring, bus and mesh</div></div></div>
<liclass="toclevel-1"><ahref="#The_Network_we_.28de.29Served.2C_Part_1:_Mapping_network_topologies"><spanclass="tocnumber">1</span><spanclass="toctext">The Network we (de)Served, Part 1: Mapping network topologies</span></a>
<ul>
<liclass="toclevel-2"><ahref="#paul_baran_diagrams"><spanclass="tocnumber">1.1</span><spanclass="toctext">paul baran diagrams</span></a></li>
<liclass="toclevel-2"><ahref="#physical_map_in_XPUB_studio"><spanclass="tocnumber">1.3</span><spanclass="toctext">physical map in XPUB studio</span></a></li>
<liclass="toclevel-2"><ahref="#collection_of_texts"><spanclass="tocnumber">1.4</span><spanclass="toctext">collection of texts</span></a></li>
<liclass="toclevel-2"><ahref="#maps_and_autonomy"><spanclass="tocnumber">1.6</span><spanclass="toctext">maps and autonomy</span></a></li>
</ul>
</li>
</ul>
</div>
<h2><spanid="The_Network_we_(de)Served,_Part_1:_Mapping_network_topologies"></span><spanclass="mw-headline"id="The_Network_we_.28de.29Served.2C_Part_1:_Mapping_network_topologies">The Network we (de)Served, Part 1: Mapping network topologies</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Special_Issue_8/The_Network_we_(de)Served_part_1&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<h3><spanclass="mw-headline"id="paul_baran_diagrams">paul baran diagrams</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Special_Issue_8/The_Network_we_(de)Served_part_1&action=edit&section=T-2"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h3>
<p>We started with a reading of a text on centralised, decentralised, and distributed networks that included a diagram made by Paul Baran for the RAND corporation. This diagram displays classic ways to visualise these networks.
</p><p><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/c/c5/Networktypes.png"title="On Distributed Networks, 1964, Paul Baran, diagram for RAND research memoranda 3420"><imgalt="On Distributed Networks, 1964, Paul Baran, diagram for RAND research memoranda 3420"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c5/Networktypes.png/320px-Networktypes.png"></a>
<p>As part of the Infrastuctour, when we set up our homeservers, I worked with Artemis to create a visualisation of the dependencies involved setting them up.
<h3><spanclass="mw-headline"id="physical_map_in_XPUB_studio">physical map in XPUB studio</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Special_Issue_8/The_Network_we_(de)Served_part_1&action=edit&section=T-4"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h3>
<p>I made a map of the location of homeservers and routers, including the other (non-XPUB) network users as well as situations where it was not possible for XPUB students to connect their server to their home router, and so had to depend on others. Manetta introduced me to Inca Quipu, a way that the Inca recorded numbers by tying knots in strings.
</p><p>I connected a piece of string I'd tied knots in to represent my external IP address for my home server, as a way to visualise the idea of connecting and also the route that a client follows when connecting to my website, which is in reverse from the way I would display my IP.
<h3><spanclass="mw-headline"id="collection_of_texts">collection of texts</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Special_Issue_8/The_Network_we_(de)Served_part_1&action=edit&section=T-5"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h3>
<p>I began collecting relevant texts to my research and creating html pages to store them on my website. This has been a useful way to develop my web design knowledge and skills as well as provide theoretical basis for the research I'm undertaking into network topologies.
<br>
<br>
Tung-Hui Hu: Truckstops on the Information Superhighway<br>
</p><p>These texts introduced me to alternative models for mapping topologies such as "klein worms", referred to in both Hui (2015) and Rand's (1970) texts. Klien worms are based on the klein bottle, which falls into the category of "topologically impossible" objects (such as moebius strips etc.).<br>
<aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/1/17/Hu-02-ponsot-klein-worms-1971.png"title="Fig. 2. Klein Worms, 1971, Claude Ponsot, illustration for Paul Ryan, “Cybernetic Guerilla Warfare,” in Radical Software 1:3"><imgalt="Fig. 2. Klein Worms, 1971, Claude Ponsot, illustration for Paul Ryan, “Cybernetic Guerilla Warfare,” in Radical Software 1:3"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/1/17/Hu-02-ponsot-klein-worms-1971.png/320px-Hu-02-ponsot-klein-worms-1971.png"></a>
<p>The concept of paranode (as suggested in Constant's Feminist Server Manifesto, and further explored by Zach Blas) was intriguing, and I resolved to keep this in mind when mapping network topologies. I see the paranode as both a disruptive concept (the thing that isn't there?), also not related to physical devices (established as nodes, but instead on social and conceptual relations between people and the world). I took initial references from the SI concept of the derive as a way to rethink autonomy in public space.
</p><p>On further reading I found this article:<br>
</p><p>The author defines the paranodal in this way: <i>the space between nodes; the space that is not dead, but very much alive.</i>
</p><p>The author also uses Ranciere's terminology, saying: <i>the paranodal is "the part of those who have no part", where we experience what it is to be outside of the network while still being related to it.</i>
</p>
<h3><spanclass="mw-headline"id="maps_and_autonomy">maps and autonomy</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Special_Issue_8/The_Network_we_(de)Served_part_1&action=edit&section=T-7"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h3>
<p>I began recording some of my thoughts around the concept of contingent autonomy and how it relates to mapping. These refer to the map/territory problem, which sees a 1:1 map as redundant (and therefore useless) and also Hakim Bey's Temporary Autonomous Zone concept (introduced to me by Tancre), where the 1:1 map is the only possible way for someone to have autonomy.<br>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/86/Networking_diagrams.jpeg/960px-Networking_diagrams.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/86/Networking_diagrams.jpeg/320px-Networking_diagrams.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Networking_diagrams.jpeg.html"title="Enlarge"></a></div>Network topologies, ring, bus and mesh</div></div></div>
<p><ahref="The_Network_we_(de)Served_part_1.html"title="User:Simon/Special Issue 8/The Network we (de)Served part 1">User:Simon/Special Issue 8/The Network we (de)Served part 1</a>
</p>
<!--
NewPP limit report
Cached time: 20200617092218
Cached time: 20200620064950
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.074 seconds
Real time usage: 0.396 seconds
Preprocessor visited node count: 10/1000000
Preprocessor generated node count: 28/1000000
Post‐expand include size: 4355/2097152 bytes
CPU time usage: 0.011 seconds
Real time usage: 0.016 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/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)
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/1/1c/Bl_calibre_web_screenshot.jpeg/640px-Bl_calibre_web_screenshot.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/1/1c/Bl_calibre_web_screenshot.jpeg/320px-Bl_calibre_web_screenshot.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Bl_calibre_web_screenshot.jpeg.html"title="Enlarge"></a></div>Screenshot of calibre-web interface</div></div></div>
<td>1. There is a lot of redundancy on the "categories" page. Categories are defined by tags - which are written subjectively, or downloaded from existing data on the uploaded books. There should be a distinction between categorising texts, and tagging them.<br>
<p>2. Tags are case-sensitive, leading to multiple entries of the same tag (e.g. Media Theory vs Media theory vs media theory)
</p>
</td>
<td>
<p>1. Create a series of general categories, and then tags can exist as sub-categories. Further to this, can tags also be used dynamically? E.g. being able to highlight more popular tags? Tagging people?<br>
<td>1. We noticed that if an article is uploaded from JSTOR, the book automatically takes the JSTOR logo as the cover. Is this because it is watermarked on the first page of the PDF?<br>
</td>
<td>
<p>1. Could watermarking be a way to make covers of future uploaded PDFs?<br>
<td>1. Upload cover from local drive - currently only accepts jpegs, and the field remains empty after you choose a jpeg to upload<br>
<p>2. "Submit" button vs "Upload format" button - a bit confusing because of placement, similarity of meaning between "submit" and "upload"<br>
3. "Get" metadata is ambiguous<br>
4. Not possible to create shelves while in book view, limiting the functionality. Being able to create a shelf while looking at a book would be a more immediate use of the shelves
5. At the moment, it's not possible to see who uploaded what. This limits the sociality of the site - it might be a nice way to recommend other texts if we can see who uploaded them<br>
6. If you click on a shelf, you get the option to download its contents - this is currently done one-by-one.<br>
7. No ability to change username at present - what if people want to use a handle rather than their real name, but don't think about this when making their account?<br>
8. Journal articles - how do you enter a season, e.g. "Autumn, 1977"?<br>
9. At present, there is no ability to see the whole collection without filtering - e.g. you can only see by "recently added", "read" or "unread" etc. What if you want to see the entire collection?
<aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/7/7e/Submit_upload_format.png/640px-Submit_upload_format.png"title="2. "Submit" vs "upload format""><imgalt="2. "Submit" vs "upload format""decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/7/7e/Submit_upload_format.png/320px-Submit_upload_format.png"></a>
<aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/e0/Bootleg_book_view_shelves.png/640px-Bootleg_book_view_shelves.png"title="4. Book view - can't create shelves"><imgalt="4. Book view - can't create shelves"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/e0/Bootleg_book_view_shelves.png/320px-Bootleg_book_view_shelves.png"></a><br>
</p>
</td>
<td>1. Allow png to be accepted, and make it clearer within the interface that the cover image has been uploaded (perhaps with a thumbnail of it?)<br>
<p>2. Create a clear distinction between uploading a new format of the same text, and submitting metadata, e.g. "upload", and "add new format"<br>
3. Change "get" for "download"<br>
4. Create this functionality<br>
5. Implement a feature in book view that recommmends books that are related, and/or recommends the reader who uploaded the book<br>
6. Include an option to download everything on a shelf<br>
7. Create this functionality<br>
8. Create this functionality<br>
9. Implement a feature allowing user to browse everything without filtering
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/1/1c/Bl_calibre_web_screenshot.jpeg/960px-Bl_calibre_web_screenshot.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/1/1c/Bl_calibre_web_screenshot.jpeg/320px-Bl_calibre_web_screenshot.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Bl_calibre_web_screenshot.jpeg.html"title="Enlarge"></a></div>Screenshot of calibre-web interface</div></div></div>
<p><ahref="feedback_from_initial_bootleg_library_sessions.html"title="User:Simon/Trim4/fieldwork/feedback from initial bootleg library sessions">User:Simon/Trim4/fieldwork/feedback from initial bootleg library sessions</a>
</p>
</td></tr></tbody></table>
<!--
NewPP limit report
Cached time: 20200617092221
Cached time: 20200620065002
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.032 seconds
Real time usage: 0.077 seconds
Preprocessor visited node count: 8/1000000
Preprocessor generated node count: 24/1000000
Post‐expand include size: 4094/2097152 bytes
CPU time usage: 0.016 seconds
Real time usage: 0.017 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/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)
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d2/Woven_papyrus_sheet.jpeg/640px-Woven_papyrus_sheet.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d2/Woven_papyrus_sheet.jpeg/320px-Woven_papyrus_sheet.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Woven_papyrus_sheet.jpeg.html"title="Enlarge"></a></div>Papyrus, an early writing surface made from woven reeds</div></div></div>
<p>Snippets:
</p>
<h2><spanclass="mw-headline"id="Outlining_content_of_workshops_22.05.19">Outlining content of workshops 22.05.19</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Reading,Writing_%26_Research_Methodologies_SI9/Outlining_content_of_workshops_22.05.19&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>a) what purpose does annotation serve (in your case)?
</p><p>Annotations in the form of accumulative traces of reader's interactions with texts underline the sociability of libraries - not just collections of knowledge but discourse around them; [How?] dispels notions of the singular, authority and property in favour of collectivity and plurality and highlights the social construction of knowledge
</p><p>b) what does it do for the reader (in your case)?
</p><p>Simon: Annotation affirms the idea that a text is part of a discourse - not in isolation from other texts/writers - and that knowledge is socially constructed. Annotation is a way for a reader to become visible to others and part of this discourse. It avoids authorship, and singular notions of knowledge production.
</p><p>c) what does it do for the annotators (in your case)?
</p><p>Simon: In my case, the annotators are the readers. Annotation exists as an action in response to the text, or to existing annotations. It can be idiosyncratic, and readable only to the annotator, therefore revealing (some) elements of how that particular person interprets the text. But, more often there are unspoken conventions to the types of annotations typically used, e.g. underlining, highlighting, circling, asterisks, dots etc. These can be defined by the technical limitations of the technology used, or linguistic (and typographic) conventions. This commonality begins to create a shared vocabulary through which readers read each other's responses to texts (here "read" can mean interpret, or access, like a file).
</p><p>YOUR PROJECT<br>
<b>look at your project descriptions and use them as a basis to make a plan</b>
</p>
<ol><li>define your aim [see above]</li>
<li>what needs to be done?</li>
<li>make a timetable</li>
<li>what needs to be developed further?</li>
<li>who can help you? and how?</li>
<li>consider how you can organise your upcoming methods sessions (5 & 19 June) so they can help you realise your aim.</li></ol>
<p>General question: what is the interface to your part the project. OR How do you invite people in to your project?
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d2/Woven_papyrus_sheet.jpeg/960px-Woven_papyrus_sheet.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d2/Woven_papyrus_sheet.jpeg/320px-Woven_papyrus_sheet.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Woven_papyrus_sheet.jpeg.html"title="Enlarge"></a></div>Papyrus, an early writing surface made from woven reeds</div></div></div>
<p><ahref="Outlining_content_of_workshops_22.05.19.html"title="User:Simon/Reading,Writing & Research Methodologies SI9/Outlining content of workshops 22.05.19">User:Simon/Reading,Writing & Research Methodologies SI9/Outlining content of workshops 22.05.19</a>
</p>
<!--
NewPP limit report
Cached time: 20200616223456
Cached time: 20200620065015
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.018 seconds
Real time usage: 0.041 seconds
Preprocessor visited node count: 4/1000000
Preprocessor generated node count: 16/1000000
Post‐expand include size: 2090/2097152 bytes
CPU time usage: 0.006 seconds
Real time usage: 0.007 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/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)
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/b/b9/Makeshift_library_checkout_card.jpeg/640px-Makeshift_library_checkout_card.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/b/b9/Makeshift_library_checkout_card.jpeg/320px-Makeshift_library_checkout_card.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Makeshift_library_checkout_card.jpeg.html"title="Enlarge"></a></div>A makeshift library checkout card, usually placed in a pocket in the back of a book</div></div></div>
<liclass="toclevel-1"><ahref="#09.05.19_at_the_rietveld_library"><spanclass="tocnumber">1</span><spanclass="toctext">09.05.19 at the rietveld library</span></a>
<liclass="toclevel-2"><ahref="#republishing_as_EPUBS"><spanclass="tocnumber">1.2</span><spanclass="toctext">republishing as EPUBS</span></a></li>
<liclass="toclevel-2"><ahref="#splotr_.28semi-permanent_library_of_the_rietveld"><spanclass="tocnumber">1.3</span><spanclass="toctext">splotr (semi-permanent library of the rietveld</span></a></li>
</ul>
</li>
</ul>
</div>
<h2><spanclass="mw-headline"id="09.05.19_at_the_rietveld_library">09.05.19 at the rietveld library</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Workshop_Rietveld_Library&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>Session at the Rietveld Library, with Eva Weinmayr, An Mertens, Martino Morandi, Anita Burato, Lieven Lahaye, & XPUB1.
Central to the session was a presentation on the Rietveld's cataloguing system, which employs open-source software and also a semi-permanent library.
<p>The Rietveld Library uses <aclass="external text"href="https://evergreen-ils.org/"rel="nofollow">Evergreen</a> open-source software to catalogue its books. They have developed it with the aim of making the infrastructure of the library cataloguing system more visible. This in line with workshops with students to address the fact that students use both analog and digital books, as well as many files, docs etc that are usually disorganised.
</p>
<h3><spanclass="mw-headline"id="republishing_as_EPUBS">republishing as EPUBS</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Workshop_Rietveld_Library&action=edit&section=T-3"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h3>
<p>The EPUB format offers a lot of potential in its structure - composed of HTML files, and stored in folders according to chapter - offers a lot of potential in its structure to "bring books together" or to make "a book of a book". Based on Ivan Illich's <aclass="external text"href="https://co-munity.net/system/files/ILLICH%201973_tools_for_convivality_1.pdf"rel="nofollow">Tools for Conviviality</a>, Rietveld librarians have republished books by scanning, OCR processing and converting to EPUB.
</p>
<h3><spanid="splotr_(semi-permanent_library_of_the_rietveld"></span><spanclass="mw-headline"id="splotr_.28semi-permanent_library_of_the_rietveld">splotr (semi-permanent library of the rietveld</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Workshop_Rietveld_Library&action=edit&section=T-4"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h3>
<p><aclass="external text"href="http://splotr.rietveldacademie.nl/"rel="nofollow">splotr</a> (Calibre server running on a Raspberry Pi) is a small repository that is connected to the main catalogue of the library. This allows students to gather digital files in a device that is accessible over a local network, and associate them with files and books in the more stable, "permanent" catalogue.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/b/b9/Makeshift_library_checkout_card.jpeg/960px-Makeshift_library_checkout_card.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/b/b9/Makeshift_library_checkout_card.jpeg/320px-Makeshift_library_checkout_card.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Makeshift_library_checkout_card.jpeg.html"title="Enlarge"></a></div>A makeshift library checkout card, usually placed in a pocket in the back of a book</div></div></div>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/e5/Headquarters_of_the_Internet_Archive.jpeg/640px-Headquarters_of_the_Internet_Archive.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/e5/Headquarters_of_the_Internet_Archive.jpeg/320px-Headquarters_of_the_Internet_Archive.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Headquarters_of_the_Internet_Archive.jpeg.html"title="Enlarge"></a></div>Headquarters of The Internet Archive, San Francisco, USA</div></div></div>
<h2><spanid="Koninglijke_Bibliotheek_(Royal_Library),_The_Hague"></span><spanclass="mw-headline"id="Koninglijke_Bibliotheek_.28Royal_Library.29.2C_The_Hague">Koninglijke Bibliotheek (Royal Library), The Hague</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/Notes_on_Libraries&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>On a Monday morning I took a train to the Hague, where the Koninglijke Bibliotheek, Nationale bibliotheek van Nederland, is located. I was spurred on to visit after looking for a book that Steve recommended, which apparently was available in the collection of the Royal Library when I looked through Worldcat.
</p><p>On arrival at the Royal Library, I went straight to the reception. I asked "Is this the Royal Library?" and the receptionist replied "It's up there", pointing upstairs, "But you need a pass to enter".
</p><p>"Ok, can I get a pass there?"
"Yes, but you have to put your coat and bag downstairs in a locker".
"Ok, thanks".
</p><p>It wasn't a very warm reception. After locking my things away, I went upstairs to the front desk of the library, where I met a more helpful staff member, who patiently explained to me that I needed to register online at a computer "over there", and that I also needed a form of ID (no problem), and something with my address on it (small problem as I didn't have anything). Most of the collection is held in stacks and must be reserved to be read. There were a lot of rules to be observed, including a reading room in which computers were not allowed (the click-clacking of typing was an issue), and although the staff member could reserve the books I needed, I couldn't take them home until my address had been verified.
</p><p>He explained:
</p><p>"If you reserve before 8:30 they'll be there at 10:00, if you reserve before 10:30 they'll be there at 1:00. And if you reserve before 1:30, they'll be there at 3:00."
</p><p>Cool. I registered online, then paid an annual membership fee (usually 15 euros, but as I am a student it was 7.50). It seemed quite strange that a national library charged for membership, and I was curious as to why.
</p><p>I left, and returned the next day to collect the two books I had reserved. At the front desk was a different staff member, who carefully explained where I needed to go to pick up my books. When I got to the collection desk, a rather flustered librarian told me that the system was down. She had my books on a shelf, but had to check to see if I could take them home or not (most of the collection can not be taken outside of the library). Thankfully she improvised an old-fashioned solution by writing down my membership details and the call number of each book. It turned out that I could take the books home. I left as fast as I could, keen to get back to school where I could scan the books and liberate them from the Royal Library.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/e5/Headquarters_of_the_Internet_Archive.jpeg/960px-Headquarters_of_the_Internet_Archive.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/e5/Headquarters_of_the_Internet_Archive.jpeg/320px-Headquarters_of_the_Internet_Archive.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Headquarters_of_the_Internet_Archive.jpeg.html"title="Enlarge"></a></div>Headquarters of The Internet Archive, San Francisco, USA</div></div></div>
<p><ahref="Notes_on_Libraries.html"title="User:Simon/Trim4/Notes on Libraries">User:Simon/Trim4/Notes on Libraries</a>
</p>
<!--
NewPP limit report
Cached time: 20200617092223
Cached time: 20200620065049
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.027 seconds
Real time usage: 0.038 seconds
Preprocessor visited node count: 4/1000000
Preprocessor generated node count: 16/1000000
Post‐expand include size: 2566/2097152 bytes
CPU time usage: 0.006 seconds
Real time usage: 0.006 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/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)
</p><p>In computing, read, write, and execute are permissions that can be given to files by an administrator to user accounts, which specify how data can be used:
</p>
<ul><li>read permissions allow you to read a file</li>
@ -185,7 +33,7 @@ This promotes and encourages certain ways of writing and reading.
</p><p>There's a famous dictum in typographic history that states "People read best what they read most"
This means that what is deemed "readable" is only so because of the prevalence of a particular font. And so, preference for certain fonts may derive from how commonplace they are within the reading environments we encounter them.
</p><p>This statement was a call to arms for multiplicity of form in type design, to challenge this tendency for form to become flattened and homogenous in the name of "readability", but it also maintains that the way information is presented becomes monolithic, having its own, enclosed logic that is exclusionary to other systems or ways of doing.
@ -207,7 +55,7 @@ I can only hope to present a small overview on these interfaces, and how they vi
</p><p>First, let's look at the book as a reading interface. What we call a "book" is most often a stack of pages that are fixed at one edge to form a spine.
Reading a book is a haptic experience; the sense of touch is in many ways just as important as the sense of vision.
Alongside this strong tactile interaction is also the inclination for a reader to engage with the text by writing directly onto the page.
@ -220,18 +68,18 @@ Annotation is primarily a strategy of reading comprehension, and there are many
</p><p>From the Books is a research project conducted together with graphic designer Masaki Miwa. Together, we collected scans of any traces of use we found in a section of books from a public library in Melbourne, Australia. We then categorised them and made a catalogue which we self-published.
</p><p>These books come from a section of a specific reading room in a specific library; the 000-099 section of the Redmond Barry Reading Room, at the State Library of Victoria. In Dewey Decimal Classification, 000-099 is titled "generalities", including books about bibliographic practices as well computer and information science, and also manuscripts and rare books; kind of a meta section on the library and how it organises information.
</p>
<hr>
<p><b>Slide 7: State Library of Victoria, Redmond Barry Reading Room</b><br>
</p><p>The SLV is a very social place; visitors use the free wifi for study, and international students often use it to call their families overseas. Others do language lessons there and gather in social groups to share skills.
It's not a sacred or quiet like a church, more like a train station in terms of its noise and activity. The SLV forecourt is a customary meeting place, people eat lunch there on the grass, on Sundays it is a speaker's corner, protestors gather there for demonstrations.
</p><p>It illustrates well that public libraries do more than just make knowledge accessible, they also produce sociality. This sociality is reflected by the tendency for businesses to open in the periphery and capitalise on this foot traffic, or those that adopt library-like structures and practices (for example, cafes that offer free wifi or cosy nooks to read)
@ -239,7 +87,7 @@ It's not a sacred or quiet like a church, more like a train station in terms of
</p><p>Here are some examples of traces of use we found in the section of books we explored. We categorised them semantically under the following headings:
</p>
<ul><li>ACCIDENTAL DOG-EAR</li>
@ -284,7 +132,7 @@ It's not a sacred or quiet like a church, more like a train station in terms of
</p><p>As part of "The Library is Open", I conducted a workshop called "Marginal Conversations" with two classmates, Artemis Gryllaki and Paloma Garcia.
We held our workshop at a volunteer-run space in the inner west of Rotterdam, called "Leeszaal Rotterdam West".
</p><p>Leezaal is a kind of 'reading room', a library that does not catalogue its books, nor record when they are borrowed. Anyone may pick up a book and walk out the door.
@ -293,31 +141,31 @@ The initiative began in 2013 when small local libraries in Rotterdam began to cl
</p><p>Marginal Conversations focused on reading and annotating together, and performing our annotations. We read and annotated an open letter called "In Solidarity with Library Genesis and Sci-Hub".
</p><p>We made an annotation kit that contained the letter, a layer of carbon paper, and a sheet of translucent tracing paper. After reading and annotating the letter, we could compare our annotations by overlaying the tracing paper to create "heat maps" that established common areas of interest.
</p><p>We made a recording of this performance, and then transcribed it into a script.
</p><p>The flipping back and forth between oral and literate productions of texts is a strategy to discover the slippages in the memory of texts that occur when transcribing. Early media theory was particularly concerned with the gap between orality and literacy, and the effect writing has on the problem of memory. Writing as a technology had a considerable effect on how we think about memory and how we form cultural narratives. The view of memory as a container within which information can be stored is very much a post-literate idea, from this also comes the the notion of "verbatim" or "word perfect". This is because what is said can be recorded in written words and stored in a text, which can be checked against for discrepancies. Pre-literate cultures think of memory instead as commemorative, a communal act of remembering together through oral storytelling traditions.
</p><p>Without a writing system in which memory can be stored and retrieved, events and narratives are seen as cyclical, and the notion of things "in their place" is ascribed to external forces like the seasons, the weather and time.
</p><p>This is a work I made in 2015, called Talking Clock. I was interested in using the mechanism of a clock to produce language, including "real" and also "potential" words.
I made a spreadsheet to work out the best combinations of letters to use on the flip cards, plotting combinations of letters, and mapped words I knew existed, words which were possible (following linguistic conventions), and words which were unlikely. In total I produced 72 cards, 12 for the left side of the clock (one for each hour in a 12-hour cycle), and 60 for the right side (one for each minute).
@ -327,7 +175,7 @@ There is a sense that the machine is writing the words, but they have been pre-s
</p>
<hr>
<p><b>Slide 15: The Remington Standard Type-Writer</b><br>
</p><p>The earliest transcription machines were ones that humans operated, becoming the transcriber.
This lead to the invention of machines like typewriters, and practices like stenography, which were used in court cases to record proceedings.
The need to type quickly, to keep up pace with speech and to record spoken language "verbatim" lead to the design of interfaces and systems that trained operators to use them efficiently
@ -335,25 +183,25 @@ The need to type quickly, to keep up pace with speech and to record spoken langu
</p><p>The layout of keys (now known as the QWERTY layout) was invented by Christopher Latham Sholes, who wanted to keep the typebars from clashing when the operator typed quickly.
</p><p>He sold his design to the Remington Company, a typewriter manufacturer, who popularised it, selling their machine alongside typing courses that trained writers to use the layout, purporting it to be the best for rapid typing.
</p><p>The QWERTY arrangement of the original Remington typewriter has remained virtually universal since the 1890s, even though more efficient arrangements have been developed. There is no particular reason why this convention has taken such a strong hold. Technological advances in machinery and electronics have rendered the problem Sholes was trying to solve redundant, but still it persists. If you've ever had to use a non-QWERTY keyboard, you may struggle.
</p><p>Reportedly the Remington Company also liked its product name, "type-writer," to appear acrostically in the top row.
</p><p>Fast-forward to December 9, 1968, and computer engineer Douglas Englebart gave what is now known as "the mother of all demos" at a San Francisco computer conference.
</p>
<hr>
<p><b>Slide 18: Douglas Englebart's "Mother of all demos"</b><br>
</p><p>He presented a demonstration that includes many features of computer engineering and publishing that we now take for granted, including the mouse, video conferencing, the modern desktop-style user interface, word processing and collaborative text-editing.
</p>
<hr>
<p><b>Slide 19: Englebart's keyboard with mouse</b><br>
</p><p>About 26 mins into the presentation Englebart says "I don't know why we call it a mouse...it started that way and we never did change it."
</p><p>While the mouse is a useful tool in modern desktop-style graphic user interfaces, text editors and computer terminal windows utilise the keys and forgo the use of a mouse.
Text editors are used for a variety of writing applications, for example programming, and writing text documents, without the need to style it graphically.
@ -362,7 +210,7 @@ Most computer operating systems come with a text-editing program as part of the
</p><p>I'd like to talk about a collaborative writing environment that exemplifies the editorial, technical and social dimensions of text; the open-source software Etherpad. This software is a manifestation of what Englebart demonstrated in 1968, and through its interface and technical configuration offers an interesting twist on the notion of public space and the public it creates.
</p><p>You can install etherpad-lite on a server, and host the software for yourself or others to use
@ -374,7 +222,7 @@ Interesting social protocols emerge from collaborative use of pads concerning co
</p><p>Here is a series of solo experiments I conducted with Etherpad, where I wrote and edited text within constrained periods of time. Etherpad offers the potential for very quick visualisations of the writing and editing process through its autmoatically assigned authorship colours.
</p><p>I was interested in seeing what happened when I visualised the writing and editing process. I wrote as multiple users, opening up a new tab in a private window each time and tricking the software into thinking I was a new writer, so it gave me new authorship colours.
</p><p>This was a timed task, beginning with writing periods of 3 minutes, and a rest of 2 minutes. After 4 iterations, this shifts to 5 minutes for both respectively. I found I needed a bit more time as the text began to grow.
@ -382,7 +230,7 @@ Interesting social protocols emerge from collaborative use of pads concerning co
</p>
<hr>
<p><b>Slide 22: <i>editorial</i>, <i>technical</i>, <i>social</i> dimensions of text</b><br>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/ce/Reading-and-writing-at-the-same-time.jpeg/640px-Reading-and-writing-at-the-same-time.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/ce/Reading-and-writing-at-the-same-time.jpeg/320px-Reading-and-writing-at-the-same-time.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Reading-and-writing-at-the-same-time.jpeg.html"title="Enlarge"></a></div>Reading-and-writing-at-the-same-time, diagrammed in <i>The Principles of Psychology</i>, William James (1890)</div></div></div>
<p>An app that makes aphoristic sentences to print and display in the work space. Its use is not limited to this space, but this is taken as a departure point for testing. The app borrows from a selection of words within a limited syntax and creates new meanings in the process.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/ce/Reading-and-writing-at-the-same-time.jpeg/960px-Reading-and-writing-at-the-same-time.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/ce/Reading-and-writing-at-the-same-time.jpeg/320px-Reading-and-writing-at-the-same-time.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Reading-and-writing-at-the-same-time.jpeg.html"title="Enlarge"></a></div>Reading-and-writing-at-the-same-time, diagrammed in <i>The Principles of Psychology</i>, William James (1890)</div></div></div>
<p>Inspiration comes from ideas of <i>syntactic ambiguity</i> and <i>lexical ambiguity</i>, which are areas of linguistic study interested in sentences that may be read in several different ways. Ambiguity comes from both lexical and syntactic diversity, put simply, the range of diversity in both the meanings that words can point to, and also how the construction of a sentence influences a diversity of readings.
<p>An example of lexical ambiguity is the "Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo" sentence, first appearing in 1967 in <aclass="external text"href="https://en.wikipedia.org/wiki/Beyond_Language"rel="nofollow"><i>Beyond Language: Adventures in Word and Thought</i></a> by <aclass="external text"href="https://en.wikipedia.org/wiki/Dmitri_Borgmann"rel="nofollow">Dmitri Borgmann</a>.
<p>This particular sentence uses the word "buffalo" as 3 discrete components:
</p><p>1. A <spanstyle="color:#d33">proper noun</span> (meaning the city of Buffalo in upstate New York).<br>
2. A <spanstyle="color:#00af89">verb</span> (meaning to bully - an uncommon spoken use, but familiar to North American English speakers)<br>
3. A <spanstyle="color:#36c">common noun</span> (meaning a kind of bison indigenous to certain parts of North America)<br>
</p><p>A fluent speaker of a language parses the components of an utterance, often adding contextually implied meanings that may be common in their vernacular. So the sentence (particularly in the North American town of Buffalo) can be read as:<br>
</p><p><code>
<spanstyle="color:#d33">Buffalo</span><spanstyle="color:#36c">buffalo</span> (Buffalo from the town of Buffalo)
</code></p><p><code><spanstyle="color:#d33">Buffalo</span><spanstyle="color:#36c">buffalo</span> [that] (other buffalo from Buffalo) <spanstyle="color:#00af89">buffalo</span> (bully)
</code></p><p><code><spanstyle="color:#d33">Buffalo</span><spanstyle="color:#36c">buffalo</span> (buffalo from Buffalo)
</code>
</p><p>This is but one of many extrapolations that can be made from the combination of words in this sentence. Other readings include:
</p>
<ol><li>Buffalo buffalo (the animals called "buffalo" from the city of Buffalo) [that] Buffalo buffalo buffalo (that the animals from the city bully) buffalo Buffalo buffalo (are bullying these animals from that city).</li>
<li>[Those] buffalo(es) from Buffalo [that are intimidated by] buffalo(es) from Buffalo intimidate buffalo(es) from Buffalo.</li>
<li>Bison from Buffalo, New York, who are intimidated by other bison in their community, also happen to intimidate other bison in their community.</li>
<li>The buffalo from Buffalo who are buffaloed by buffalo from Buffalo, buffalo (verb) other buffalo from Buffalo.</li>
<p>Examples of this are diverse, including famous sentences such as Noam Chomsky's famous <aclass="external text"href="https://en.wikipedia.org/wiki/Colorless_green_ideas_sleep_furiously"rel="nofollow">"Colorless green ideas sleep furiously"</a>.
This type of sentence (as well as many other examples) introduce the idea of syntactic ambiguity. Chomsky's sentence has correct grammar - all the components are there - but it has no apparent meaning.
<p>Regular Strategies is an app that produces sentences based on random modelling of sentences. Each sentence has the same grammatical structure, each part of speech has the same function in the parse tree. An idea is to perhaps allow users to input values specific to their circumstances, and from this generate the affirmations. These can then be printed to the workplace (either as a screensaver, or as a poster).
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/87/Rebinding_hot_glue_book.jpeg/640px-Rebinding_hot_glue_book.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/87/Rebinding_hot_glue_book.jpeg/320px-Rebinding_hot_glue_book.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Rebinding_hot_glue_book.jpeg.html"title="Enlarge"></a></div>A hot-glue bound book held open with one hand</div></div></div>
<p>Snippets:
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/87/Rebinding_hot_glue_book.jpeg/960px-Rebinding_hot_glue_book.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/8/87/Rebinding_hot_glue_book.jpeg/320px-Rebinding_hot_glue_book.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Rebinding_hot_glue_book.jpeg.html"title="Enlarge"></a></div>A hot-glue bound book held open with one hand</div></div></div>
<p><ahref="Dumbstruck_A_Cultural_History_of_Ventriloquism.html"title="User:Simon/Dumbstruck A Cultural History of Ventriloquism">User:Simon/Dumbstruck A Cultural History of Ventriloquism</a>
</p>
<h2><spanid="Dumbstruck—A_Cultural_History_of_Ventriloquism"></span><spanclass="mw-headline"id="Dumbstruck.E2.80.94A_Cultural_History_of_Ventriloquism">Dumbstruck—A Cultural History of Ventriloquism</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Dumbstruck_A_Cultural_History_of_Ventriloquism&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
</p><p>This book took about 40 hours to create, the longest time it's taken so far... I found a PDF on Lib Gen, but for some reason the OCR'd text was tracked quite tight making each line look like a very long word - this was even worse when printed. After a quick search on worldcat, I discovered that this book was available to be borrowed from the Royal Library in the Hague. Off I went to borrow the book. I planned to scan it using the bookscanner, but the cameras kept crashing after scanning half the 433 page book. So, I managed to extract the text using Calibre's book convert process from PDF > RTF. However, after placing the text in an InDesign layout, all of the numbers appeared as missing characters. From the looks of the PDF it seemed that these were perhaps from an Opentype font's custom stylistic set, which would explain why they weren't turning up in my system fonts. Also, in the index at the back of the book the numbers seemed to have the appearance of hyperlinks (when hovering over the hand icon appears) but when clicked, did absolutely nothing. So I began the rather painstaking process of laying out the book with exactly the same text flow and page numbers as the source. The work included removing headers and page numbers from the RTF, scanning all photos from the printed book, endlessly wordspacing paragraphs to make sure they fit where they should on each page, styling the text, removing manually written hyphenation (this was done programmatically, and ended up with a few words that were joined together in the case of examples like "re- and dis- associate" becoming reand disassociate") and the seemingly endless task of manually entering in EVERY number. At times it felt a bit masochistic, but I used this time to reflect on the process, thinking a lot about the changes I was making to preserve the form of the original. Ironically, this also involved a lot of forced line breaks, which would make the task of anyone who wanted to bootleg this book a bit more difficult (forced line breaks are the bane of the bootlegger). Another strange thought - I'm reading these books as I redesign them, but my reading happens on a more superficial level perhaps, meaning that I'm not absorbing the content fully, but reading it like a machine would as I look for anomalies and address them.
</p><p>Clara Balaguer asked me for a copy of this book, and it seemed like a good opportunity to try a new printing and binding process. I decided to print the book double-sided on A4 paper, as opposed to the previous method of 2-up imposed printing on A3 paper. I wasn't very satisfied with how the previous printing method had produced a "split" in the book due to the paper grain direction. Yin Yin Wong at PS Rotterdam had recommended printing double sided rather than 2-up to avoid this, so this was the technique I decided to try out. I also decided on hand-binding it with cold glue, a technique which I had recently learned. Cold glue binding is done with equipment and materials such as a hacksaw, scissors, medical gauze (or cheesecloth), brushes, PVA glue, bookbinding thread, a jig to hold the book in while notches are cut and the spine receives its initial gluing, and a book press to keep the book in overnight, which stops the book from warping due to the high water content of the PVA glue. Cold glue binding allows the book to lay open flat on a table, a benefit I was keen to apply to this edition of the book as I was dissatisfied by how tight the binding of the first edition was because I had used the hot glue binding machine, which takes much less time but for thick books can produce a lower quality result. I was quite pleased with how this book came out, however, when applying the cover I had to decide not to glue it to the spine. Cold glue binding results in a rough spine, and hot glue creates a smooth layer of glue that dries quickly, producing a smooth spine. The only way to avoid this is to not attach the cover to the spine if using cold glue.
<p>Beginning of image section: Source publication (left) and second edition bootleg (right). The second edition bootleg book lies open more easily due to the cold glue binding
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d5/Mladen_dolar_page_numbers.jpeg/640px-Mladen_dolar_page_numbers.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d5/Mladen_dolar_page_numbers.jpeg/320px-Mladen_dolar_page_numbers.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Mladen_dolar_page_numbers.jpeg.html"title="Enlarge"></a></div>A page from a bootleg of Mladen Dolar’s <i>A Voice and Nothing More</i></div></div></div>
<p>Snippets:
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d5/Mladen_dolar_page_numbers.jpeg/960px-Mladen_dolar_page_numbers.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d5/Mladen_dolar_page_numbers.jpeg/320px-Mladen_dolar_page_numbers.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Mladen_dolar_page_numbers.jpeg.html"title="Enlarge"></a></div>A page from a bootleg of Mladen Dolar’s <i>A Voice and Nothing More</i></div></div></div>
<p><ahref="A_Voice_and_Nothing_More.html"title="User:Simon/A Voice and Nothing More">User:Simon/A Voice and Nothing More</a>
</p>
<h2><spanclass="mw-headline"id="A_Voice_and_Nothing_More">A Voice and Nothing More</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/A_Voice_and_Nothing_More&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>Printed: 19.11.19<br>
Dimensions: 155x235mm<br>
Cover stock: Ursus glossy white 210gsm<br>
Text stock: Bio Top 80gsm<br>
Binding: Perfect bound, cold glue<br>
Pages: 226pp
</p><p>This is another book where I took a text file and laid it out again in InDesign, like the copy of <i>Dumbstruck</i> that I bootlegged. However, this time I made a code to indicate the page numbering and text flow of the source publication. This was to provide comfortable, consistent tracking to the letterspacing - one of the issues with <i>Dumbstruck</i> was that, in an attempt to keep the text flow and page numbering the same, some paragraphs were too tightly, or too loosely kerned. I feel this is a more elegant solution, however, it might pose problems if someone else tried to do the same as I had (taking the text from a source publication and laying it out) as the code is now part of the text. The cover was made with glossy paper, and custom-cut vinyl stickers. In time these will probably come off, but that's conceptually sympathetic to the content of the book, which is about the transience of the voice.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c6/Anatomy_of_Reprinting_diagram.jpeg/640px-Anatomy_of_Reprinting_diagram.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c6/Anatomy_of_Reprinting_diagram.jpeg/320px-Anatomy_of_Reprinting_diagram.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Anatomy_of_Reprinting_diagram.jpeg.html"title="Enlarge"></a></div>(clockwise from top left): imposition from a single-page PDF into a booklet, anatomy of a book, a spread</div></div></div>
<liclass="toclevel-2"><ahref="#PDF_imposition_from_scratch"><spanclass="tocnumber">1.1</span><spanclass="toctext">PDF imposition from scratch</span></a></li>
<liclass="toclevel-1"><ahref="#booklet.sh_for_PDF_imposition_into_a_booklet"><spanclass="tocnumber">2</span><spanclass="toctext">booklet.sh for PDF imposition into a booklet</span></a></li>
</p><p>The aim is to write a Python script to automate the process by iterating recursively over pages in a PDF. These will be called in Python as subprocesses using the subprocess module.
</p>
<h3><spanclass="mw-headline"id="PDF_imposition_from_scratch">PDF imposition from scratch</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/PDF_imposition&action=edit&section=T-2"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h3>
<p><b>23.09.19</b><br>
I'm working out which commands to use from the command line. The process should be as follows:<br>
</p>
<pre> #burst the source PDF, keep the name of the source plus page number (-%d)
</p><p>To identify the size of a single burst page in pixels, this is the command I used:
</p>
<pre> $ identify Carrier_burst-1.pdf
</pre>
<p>which returns this information:
</p>
<pre> Carrier_burst-1.pdf PDF 398x591 398x591+0+0 16-bit sRGB 19486B 0.000u 0:00.009
</pre>
<p><b>26.09.19</b><br>
Then for the next step, resizing each page to fit 2-up on an A4. It's easy enough to reduce to 50% if the original is A4, but in other formats it's a bit trickier...
</p>
<pre> #resize the resulting burst single page PDF (this only does one - needs Python loop to iterate recursively)
$ magick mogrify -resize 50% new_source.pdf
#or to resize to specific pixel dimensions such as 256x256
$ magick mogrify -resize 256x256 new_source.pdf
</pre>
<p>After resizing to 50%, the identify command returns these values:
</p>
<pre> Carrier_burst-1.pdf PDF 199x296 199x296+0+0 16-bit sRGB 51910B 0.000u 0:00.000
</pre>
<p><b>27.09.19</b><br>
The next steps are these:
</p>
<pre> #impose 2up on a page using imagemagick montage command
<p><aclass="external text"href="https://pypi.org/project/pdfimpose/"rel="nofollow">pdfimpose</a> is a python library that does imposition. It's quite easy and powerful, though again it is not quite set up for cutting pages. I found some Python code, which creates an imposed PDF in a 2x2 format, with folds to be made first vertically, then horizontally:
</p>
<pre> from pdfimpose import impose, VERTICAL, HORIZONTAL
</p><p><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/1/1c/E_r_2x2_imposed.png/640px-E_r_2x2_imposed.png"><imgalt="E r 2x2 imposed.png"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/1/1c/E_r_2x2_imposed.png/320px-E_r_2x2_imposed.png"></a>
</p><p>Documentation for pdfimpose can be found here:
<h2><spanclass="mw-headline"id="booklet.sh_for_PDF_imposition_into_a_booklet">booklet.sh for PDF imposition into a booklet</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/Michaels_booklet_script_for_PDF_imposition&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>I found another way to do imposition using a script Michael wrote called booklet.sh, downloadable here: <aclass="external free"href="https://git.xpub.nl/murtaugh/95layouts"rel="nofollow">https://git.xpub.nl/murtaugh/95layouts</a><br>
It's a shell script that can run in the bin folder from the home directory, which allows you to run it wherever you are in the computer - you don't have to <code>cd</code> to the folder where the script is. To enable this, first you have to echo the path for the bin folder that the scripts are in. The command to run it from the terminal is:
</p>
<pre>booklet.sh source.pdf
</pre>
<p>It needs a few dependencies to run (mainly psutils).
</p>
<ol><li>Requirements: psutils, pdftk, python3 with reportlab (make_blank_pdf.py)</li></ol>
<pre>input=$1
base=${input%.*}
echo converting $input to $base.booklet.pdf
pdftk_utils.py $input pad --multiple 4 --output $base.01.pdf
<p>Note: Comment out or delete the last line to produce three .ps files - the first one is the source PDF, the second is the PDF imposed in the correct order, the third one is the imposed PDF pages on an A4 page. This works well if all you want to do is impose, print and fold. For cutting sheets you need to position the pages 2-up, centred on the page, which I can't quite figure out how to do...
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c6/Anatomy_of_Reprinting_diagram.jpeg/960px-Anatomy_of_Reprinting_diagram.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c6/Anatomy_of_Reprinting_diagram.jpeg/320px-Anatomy_of_Reprinting_diagram.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Anatomy_of_Reprinting_diagram.jpeg.html"title="Enlarge"></a></div>(clockwise from top left): imposition from a single-page PDF into a booklet, anatomy of a book, a spread</div></div></div>
</p><p><ahref="Michaels_booklet_script_for_PDF_imposition.html"title="User:Simon/Trim4/Michaels booklet script for PDF imposition">User:Simon/Trim4/Michaels booklet script for PDF imposition</a>
</p>
<!--
NewPP limit report
Cached time: 20200617092239
Cached time: 20200620065148
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.046 seconds
Real time usage: 0.249 seconds
Preprocessor visited node count: 15/1000000
Preprocessor generated node count: 52/1000000
Post‐expand include size: 3629/2097152 bytes
CPU time usage: 0.006 seconds
Real time usage: 0.006 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/40
Expensive parser function count: 0/100
Unstrip recursion depth: 0/20
Unstrip post‐expand size: 419/5000000 bytes
Unstrip post‐expand size: 0/5000000 bytes
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/3/39/Publication_studio_London_staff.jpg/640px-Publication_studio_London_staff.jpg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/3/39/Publication_studio_London_staff.jpg/320px-Publication_studio_London_staff.jpg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Publication_studio_London_staff.jpg.html"title="Enlarge"></a></div>Staff working at Publication Studio, London</div></div></div>
<p>Snippets:
</p>
<h2><spanclass="mw-headline"id="02.12.19_The_nomadic_physical_bootleg_library">02.12.19 The nomadic physical bootleg library</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/Physical_bootleg_library_nomadic_box&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>The physical bootleg library is a collection of books, mostly made at PZI by myself and other students, or donated by visitors to PZI. The books are kept in a repurposed champagne crate, usually stored on a shelf in the Lens-Based studio. The only condition for borrowing books is that they are returned at some point. The dimensions of the box introduce certain constraints on the size and quantity of books contained within. The box is portable, allowing it to be placed in many locations:
<p>The portability of the box means that it could be an interesting container & receptacle for libraries that travel - I'm quite interested in the possibility of using the box to transport and store both printed and digital books, especially in temporary library situations (on hotspotted Raspberry Pi for example) that could be used in worksessions at various locations.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/3/39/Publication_studio_London_staff.jpg/960px-Publication_studio_London_staff.jpg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/3/39/Publication_studio_London_staff.jpg/320px-Publication_studio_London_staff.jpg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Publication_studio_London_staff.jpg.html"title="Enlarge"></a></div>Staff working at Publication Studio, London</div></div></div>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/3/3c/Rereferencing_Open_work_OCR.jpeg/640px-Rereferencing_Open_work_OCR.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/3/3c/Rereferencing_Open_work_OCR.jpeg/320px-Rereferencing_Open_work_OCR.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Rereferencing_Open_work_OCR.jpeg.html"title="Enlarge"></a></div>A bootleg copy of The Open Work by Umberto Eco. OCR software has mistaken the page number (page 80) as the word “So”</div></div></div>
<p>Snippets:
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/3/3c/Rereferencing_Open_work_OCR.jpeg/960px-Rereferencing_Open_work_OCR.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/3/3c/Rereferencing_Open_work_OCR.jpeg/320px-Rereferencing_Open_work_OCR.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Rereferencing_Open_work_OCR.jpeg.html"title="Enlarge"></a></div>A bootleg copy of The Open Work by Umberto Eco. OCR software has mistaken the page number (page 80) as the word “So”</div></div></div>
<h2><spanclass="mw-headline"id="Pre-processing_for_OCR">Pre-processing for OCR</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/self_directed_research/OCR_preprocessing&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>This script applies transformations to the image before running OCR, resulting in a clearer result:
</p><p><br>
</p>
<pre># import the necessary packages
#from PIL
import Image
import pytesseract
import argparse
import cv2
import os
# construct the argument parse and parse the arguments
<p><ahref="Using_the_bookscanner.html"title="User:Simon/Trim4/Using the bookscanner">User:Simon/Trim4/Using the bookscanner</a>
</p>
<h2><spanclass="mw-headline"id="first_trials_with_the_bookscanner">first trials with the bookscanner</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/Using_the_bookscanner&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>I tried using the Bookscanner, built as part of <ahref="OuNuPo.html"title="OuNuPo">Special Issue 5 OuNuPo</a>. The Bookscanner needed a few adjustments before it was ready to use. The documentation is rather limited, but the software is set up so that it is quite easy to work out how to use it.
</p><p>The scanner takes photos of even and odd pages, from cameras mounted above the glass. First, you have to mount a drive in which the scanned images will be stored. Then, you can adjust the zoom, and shutter speed. I found it impossible to take an image of only the page, so I will need to crop out everything around it in the future.
</p><p>I scanned a book, and made jpegs of each page. The pages are oriented from the camera's perspective, like so:
</p><p>Next, I ran a script that does OCR on jpegs that Pedro, Tancre and Bo made for their workshop <ahref="Blurry_Boundaries.html"title="Blurry Boundaries"> Blurry Boundaries</a> as part of Special Issue 9: The Library Is Open. This created two PDFs, with OCR. The next step will to be to work out how to rotate the images 90 degrees to the correct orientation, (clockwise for the odd pages, anti-clockwise for the even pages), and crop the images.
</p><p>The workflow will be like so:
</p>
<pre>1. Scan
2. Rotate images
3. Crop
4. OCR
5. Compile
</pre>
<!--
NewPP limit report
Cached time: 20200616174621
Cached time: 20200620065400
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.022 seconds
Real time usage: 0.075 seconds
Preprocessor visited node count: 7/1000000
Preprocessor generated node count: 26/1000000
Post‐expand include size: 1346/2097152 bytes
CPU time usage: 0.006 seconds
Real time usage: 0.006 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/40
Expensive parser function count: 0/100
Unstrip recursion depth: 0/20
Unstrip post‐expand size: 63/5000000 bytes
Unstrip post‐expand size: 0/5000000 bytes
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c3/Englebart_mouse_and_keyboard.jpeg/640px-Englebart_mouse_and_keyboard.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c3/Englebart_mouse_and_keyboard.jpeg/320px-Englebart_mouse_and_keyboard.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Englebart_mouse_and_keyboard.jpeg.html"title="Enlarge"></a></div>A mouse, keyboard and collaborative text-editing demonstrated in Douglas Englebart’s “Mother of All Demos”, 1968</div></div></div>
</p><p>In computing, read, write, and execute are permissions that can be given to files by an administrator to user accounts, which specify how data can be used:
</p>
<ul><li>read permissions allow you to read a file</li>
<li>write permissions allow you to change it, but not to run it</li>
<li>execute permissions allow you to run a file</li></ul>
<p>You are most likely familiar with the "read-only" permission.
For example, a document with read-only permissions given to a user means that user can only read the document, and can't edit it.
</p><p>I have chosen this title because for this presentation I want to focus on how the contingencies offered by interfaces for reading and writing produce a certain kind of reading or writing, and also a certain kind of reader or writer.
</p><p>My main interest in this presentation is to describe through several examples, the political dynamics and particular affordances of different interfaces and sites for publication, and the subsequent techno-sociologial effects these have through the way they visualise reading, writing and making things public.
</p><p>Interfaces for reading and writing are almost always visually-oriented, and their technical conditions determine how textual information is organised and processed.
This promotes and encourages certain ways of writing and reading.
</p><p>I will present examples from my own practice as an artist and graphic designer, and also some historical examples from computer science and engineering.
</p><p>Beginning with the field of type design and typography, I want to talk about ideas of legibility and readability, which often precede notions of how written language should be visualised in graphic form.
</p><p>Often someone will use illegibility as an excuse to argue against the use of a particular font or typeface. Physical limitations are certainly a factor in deciding how type should be shaped, down to the micro-level that scrutiny of readability brings, where enjoyment is hampered by exhausted eyes. A file can also be made readable by changing permissions. Allowing a file to be read has many other implications apart from the obvious visibility of content.
</p>
<hr>
<p><b>Slide 3: People read best what they read most</b><br>
</p><p>There's a famous dictum in typographic history that states "People read best what they read most"
This means that what is deemed "readable" is only so because of the prevalence of a particular font. And so, preference for certain fonts may derive from how commonplace they are within the reading environments we encounter them.
</p><p>This statement was a call to arms for multiplicity of form in type design, to challenge this tendency for form to become flattened and homogenous in the name of "readability", but it also maintains that the way information is presented becomes monolithic, having its own, enclosed logic that is exclusionary to other systems or ways of doing.
</p><p>The eye adjusts to expect certain things it has seen before, and this idea of "easy to read" is trainable, to a certain extent. We might think that a certain font is "neutral", this is because it has become invisible to us, and it is invisible to us because it is everywhere. It therefore doesn't stand out in a way that other typefaces do.
So the main point I will try to make in this presentation is that the particular interfaces we commonly use for reading and writing train us to read and write in certain ways, ways which we will become efficient within.
</p><p>When we shift to a different writing or reading interface, there is an adjustment, a period of discomfort as we adapt.
We approach new interfaces through the lens of the one that preceded it, always likening it to what we are familiar with.
The new interface presents new limitations, and also offer new, unexpected possibilities for how we imagine ourselves as participatory subjects, engaging with the text.
</p><p>The discourse around reading and writing interfaces is vast, and I do not expect to be able to cover it comprehensively in this presentation.
I can only hope to present a small overview on these interfaces, and how they visualise language, and in turn, how they create a new subjectivity in the reader or writer.
</p><p>First, let's look at the book as a reading interface. What we call a "book" is most often a stack of pages that are fixed at one edge to form a spine.
Reading a book is a haptic experience; the sense of touch is in many ways just as important as the sense of vision.
Alongside this strong tactile interaction is also the inclination for a reader to engage with the text by writing directly onto the page.
The interface of a printed book invites writing, in fact the very first books were written by hand.
It is not uncommon to come across another reader's notes, annotations scribbled in the margins of a book.
Annotation is primarily a strategy of reading comprehension, and there are many activities that fall under the umbrella of "annotation", including highlighting, underlining, glossing (which is writing explicatory texts that define unfamiliar phrases or words), as well as how pages are manipulated to mark text, for example, making a bookmark by folding the corner of a page in what is often called in English a "dog-ear".
</p><p>Despite these annotations are made at different times, by different people unbeknownst to each other, their methods are often consistent with each other. Their annotations also often serve the same purpose, as a reformatting of the text that is read. So the function is sometimes editorial; highlighting or underlining is a way of drawing attention to part of the text that is relevant to the person who is reading it, giving them a way to return to it when scanning through at a later time.
</p><p>Annotation also has a social function; inscribe the presence of reader within a book. The book then becomes a vehicle for a social paratext, one that lives alongside the source text, one that can be commented on by others. Sometimes these paratexts separate from the source and become texts of their own. Glossaries come from the practices established by medieval glossators, who wrote explanations of Roman law between the lines of manuscripts. The first dictionaries served a similar purpose.
</p><p>Books held in public collections have travelled different paths through the hands of different readers. They acquire provenance and their own particular history through how they are used. A book printed, bound and distributed in an edition of many books, a multiple with the ambition to present its text as singular, becomes diversified through its use
</p><p>From the Books is a research project conducted together with graphic designer Masaki Miwa. Together, we collected scans of any traces of use we found in a section of books from a public library in Melbourne, Australia. We then categorised them and made a catalogue which we self-published.
</p><p>These books come from a section of a specific reading room in a specific library; the 000-099 section of the Redmond Barry Reading Room, at the State Library of Victoria. In Dewey Decimal Classification, 000-099 is titled "generalities", including books about bibliographic practices as well computer and information science, and also manuscripts and rare books; kind of a meta section on the library and how it organises information.
</p>
<hr>
<p><b>Slide 7: State Library of Victoria, Redmond Barry Reading Room</b><br>
</p><p>The SLV is a very social place; visitors use the free wifi for study, and international students often use it to call their families overseas. Others do language lessons there and gather in social groups to share skills.
It's not a sacred or quiet like a church, more like a train station in terms of its noise and activity. The SLV forecourt is a customary meeting place, people eat lunch there on the grass, on Sundays it is a speaker's corner, protestors gather there for demonstrations.
</p><p>It illustrates well that public libraries do more than just make knowledge accessible, they also produce sociality. This sociality is reflected by the tendency for businesses to open in the periphery and capitalise on this foot traffic, or those that adopt library-like structures and practices (for example, cafes that offer free wifi or cosy nooks to read)
</p><p>Here in Rotterdam this is also present - Starbucks has opened a store at the Bibliotheek Rotterdam, there is a cafe above Rotterdam Centraal Station that houses part of the same collection. There's even a cafe called "The Library" at Mathenesserplein
</p><p>Here are some examples of traces of use we found in the section of books we explored. We categorised them semantically under the following headings:
</p>
<ul><li>ACCIDENTAL DOG-EAR</li>
<li>ANNOTATION</li>
<li>ASTERISK</li>
<li>BOOK PRICE</li>
<li>BOOKMARK</li>
<li>CIRCLED TEXT</li>
<li>CREASED PAGE</li>
<li>CROSS</li>
<li>DEAD ANT</li>
<li>DOG-EAR</li>
<li>ERASER RUBBING</li>
<li>ERRATA</li>
<li>FINGERPRINT</li>
<li>FOLD</li>
<li>HANDWRITTEN LETTER</li>
<li>INK BLOT</li>
<li>LIBRARY DOCUMENT</li>
<li>LIFTED PRINT</li>
<li>LINE</li>
<li>LOOSE PAGE</li>
<li>NOTEPAPER BOOKMARK</li>
<li>NOTES</li>
<li>PAGES REMOVED</li>
<li>POST-IT NOTE</li>
<li>RECEIPT BOOKMARK</li>
<li>REPLACED IMAGE</li>
<li>SCUFF</li>
<li>SMUDGE</li>
<li>SQUIGGLE</li>
<li>STAIN</li>
<li>STRIKETHROUGH</li>
<li>TICK</li>
<li>TORN PAGE</li>
<li>TORN PAPER BOOKMARK</li>
<li>UNDERLINING</li>
<li>WARPED PAGE</li>
<li>WEAR AND TEAR</li></ul>
<p>The traces were largely mundane, but revealed a consensus of mark-making and annotation. We also found readers intentionally using the book as a vehicle to pass messages to other readers, such as a handwritten note someone had deliberately placed in a book.
</p><p>This interest in annotation as a visualisation of reader's interaction with texts was developed further with a thematic project called "The Library is Open", conducted by Experimental Publishing in 2019. The Library Is Open was an afternoon of workshops in which we made visible the operations of libraries, including municipal, academic, and importantly, so-called "Shadow" libraries, which are ones that operate outside of legality, illegally distributing pirated copies of books.
</p><p>As part of "The Library is Open", I conducted a workshop called "Marginal Conversations" with two classmates, Artemis Gryllaki and Paloma Garcia.
We held our workshop at a volunteer-run space in the inner west of Rotterdam, called "Leeszaal Rotterdam West".
</p><p>Leezaal is a kind of 'reading room', a library that does not catalogue its books, nor record when they are borrowed. Anyone may pick up a book and walk out the door.
The initiative began in 2013 when small local libraries in Rotterdam began to close, and the initators asked their local community two questions; 1) Do we need a library?, and 2) How can you contribute?
</p><p>Leeszaal offers a safe space for members of the local community to gather, to learn languages and share skills, to read newspapers, learn how to use computers, use the internet, watch YouTube or just hang out. It's not a traditional library in any sense, but is sympathetic to many of the social democratic values of open access to knowlegde that public libraries embody.
</p><p>Marginal Conversations focused on reading and annotating together, and performing our annotations. We read and annotated an open letter called "In Solidarity with Library Genesis and Sci-Hub".
</p><p>We made an annotation kit that contained the letter, a layer of carbon paper, and a sheet of translucent tracing paper. After reading and annotating the letter, we could compare our annotations by overlaying the tracing paper to create "heat maps" that established common areas of interest.
</p><p>We made a recording of this performance, and then transcribed it into a script.
</p><p>The flipping back and forth between oral and literate productions of texts is a strategy to discover the slippages in the memory of texts that occur when transcribing. Early media theory was particularly concerned with the gap between orality and literacy, and the effect writing has on the problem of memory. Writing as a technology had a considerable effect on how we think about memory and how we form cultural narratives. The view of memory as a container within which information can be stored is very much a post-literate idea, from this also comes the the notion of "verbatim" or "word perfect". This is because what is said can be recorded in written words and stored in a text, which can be checked against for discrepancies. Pre-literate cultures think of memory instead as commemorative, a communal act of remembering together through oral storytelling traditions.
</p><p>Without a writing system in which memory can be stored and retrieved, events and narratives are seen as cyclical, and the notion of things "in their place" is ascribed to external forces like the seasons, the weather and time.
</p><p>This is a work I made in 2015, called Talking Clock. I was interested in using the mechanism of a clock to produce language, including "real" and also "potential" words.
I made a spreadsheet to work out the best combinations of letters to use on the flip cards, plotting combinations of letters, and mapped words I knew existed, words which were possible (following linguistic conventions), and words which were unlikely. In total I produced 72 cards, 12 for the left side of the clock (one for each hour in a 12-hour cycle), and 60 for the right side (one for each minute).
</p><p>The clock displays, or "prints" 1440 words every day (1 per minute). It's very noisy, making a loud click every time a card flips over. It's very difficult to tell the time as the sequence of numbers are replaced by a different system of letters, but it's possible at least to know that the hour has changed, with a little time spent with the clock.
There is a sense that the machine is writing the words, but they have been pre-selected by a human, myself.
</p><p>When we encounter a new word in English, it's not always possible to know how to say it, especially in English, which has different standards, and borrows words from many other languages, so spelling and pronunciation are very different sometimes. This leads to the fluidity of "potential words". Because they isn't yet a consensus on their use, there also is no consensus on their pronunciation.
</p>
<hr>
<p><b>Slide 15: The Remington Standard Type-Writer</b><br>
</p><p>The earliest transcription machines were ones that humans operated, becoming the transcriber.
This lead to the invention of machines like typewriters, and practices like stenography, which were used in court cases to record proceedings.
The need to type quickly, to keep up pace with speech and to record spoken language "verbatim" lead to the design of interfaces and systems that trained operators to use them efficiently
</p><p>In the late 19th century came the emergence of typewriters, such as this one that was produced by the American company Remington.
</p><p>The layout of keys (now known as the QWERTY layout) was invented by Christopher Latham Sholes, who wanted to keep the typebars from clashing when the operator typed quickly.
</p><p>He sold his design to the Remington Company, a typewriter manufacturer, who popularised it, selling their machine alongside typing courses that trained writers to use the layout, purporting it to be the best for rapid typing.
</p><p>The QWERTY arrangement of the original Remington typewriter has remained virtually universal since the 1890s, even though more efficient arrangements have been developed. There is no particular reason why this convention has taken such a strong hold. Technological advances in machinery and electronics have rendered the problem Sholes was trying to solve redundant, but still it persists. If you've ever had to use a non-QWERTY keyboard, you may struggle.
</p><p>Reportedly the Remington Company also liked its product name, "type-writer," to appear acrostically in the top row.
</p><p>Fast-forward to December 9, 1968, and computer engineer Douglas Englebart gave what is now known as "the mother of all demos" at a San Francisco computer conference.
</p>
<hr>
<p><b>Slide 18: Douglas Englebart's "Mother of all demos"</b><br>
</p><p>He presented a demonstration that includes many features of computer engineering and publishing that we now take for granted, including the mouse, video conferencing, the modern desktop-style user interface, word processing and collaborative text-editing.
</p>
<hr>
<p><b>Slide 19: Englebart's keyboard with mouse</b><br>
</p><p>About 26 mins into the presentation Englebart says "I don't know why we call it a mouse...it started that way and we never did change it."
</p><p>While the mouse is a useful tool in modern desktop-style graphic user interfaces, text editors and computer terminal windows utilise the keys and forgo the use of a mouse.
Text editors are used for a variety of writing applications, for example programming, and writing text documents, without the need to style it graphically.
Most computer operating systems come with a text-editing program as part of the basic package of software (e.g. Mac has "TextEdit" and Windows has "notepad"). These programs are usually used by a single user at one time.
</p><p>Some environments, such as the one Englebart demonstrates, are collaborative, allowing many users to write together in realtime.
</p><p>I'd like to talk about a collaborative writing environment that exemplifies the editorial, technical and social dimensions of text; the open-source software Etherpad. This software is a manifestation of what Englebart demonstrated in 1968, and through its interface and technical configuration offers an interesting twist on the notion of public space and the public it creates.
</p><p>You can install etherpad-lite on a server, and host the software for yourself or others to use
although most pads aren't indexed by search englines, they are 100% public, and editable to anyone who knows their URL.
</p><p>It's a very dynamic writing environment, and environment in the sense of the combinations of technical conditions of hardware and software, and how users operate within it every key you press is recorded (including deletions), building a mind-boggling database in the background which you can track in the version history, import/export text.
</p><p>The software automatically assigns authorship colours, users can change them and give themselves user names or remain "unnamed". Authorship in etherpad is blurry from the level of the user, but crystal clear from the level of the system administrator (can easily run searches on IP addresses).
Interesting social protocols emerge from collaborative use of pads concerning conviviality (not so much spell-checking or correction). Misspelling is transgressive and signals the speller's marginal status, either preeducated, uneducated, or sloppy. Ignoring misspelling in favour of transcription, recording what is said quickly introduces a type of collective, consensual authorship.
</p><p>New users react with either enthusiasm or suspicion - to the enthusiasts, it's exciting to collaborate in realtime, to others it's just a bit too public, everything you type can be seen as you type it.
</p><p>Here is a series of solo experiments I conducted with Etherpad, where I wrote and edited text within constrained periods of time. Etherpad offers the potential for very quick visualisations of the writing and editing process through its autmoatically assigned authorship colours.
</p><p>I was interested in seeing what happened when I visualised the writing and editing process. I wrote as multiple users, opening up a new tab in a private window each time and tricking the software into thinking I was a new writer, so it gave me new authorship colours.
</p><p>This was a timed task, beginning with writing periods of 3 minutes, and a rest of 2 minutes. After 4 iterations, this shifts to 5 minutes for both respectively. I found I needed a bit more time as the text began to grow.
</p><p>This experiment showed me that editing is a form of writing, like growing a tree and making furniture from it at the same time.
</p>
<hr>
<p><b>Slide 22: <i>editorial</i>, <i>technical</i>, <i>social</i> dimensions of text</b><br>
</p><p>At the beginning of this presentation I described my interest in text and its overlapping dimensions; editorial, technical and social.
</p><p>I will go into a bit more detail now to explain further:
</p>
<ul><li>editorial: 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.</li>
<li>technical: 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.</li>
<li>social: text is a framework. The English word "text" has roots in the Proto-Indo-European word teks-, 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.</li></ul>
<p>Etherpad exemplifies all three of these dimensions. The interface allows readers to become writers, and text editors, themselves. It uses the technicality of text-based software to record what is written, or deleted there in a process that is recorded in the version history. And when used collaboratively (which is what it is designed for, it creates a framework of shared concepts that come together into the one textual fabric.
</p><p>What is important about this, as well as other open-source tools for reading and writing is that they offer the potential for us to develop our own particular ways of reading and writing. There is a lot more effort that is needed in order to not just read and write, but to also determine our own definitions of what is most readable, writeable and executeable.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c3/Englebart_mouse_and_keyboard.jpeg/960px-Englebart_mouse_and_keyboard.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c3/Englebart_mouse_and_keyboard.jpeg/320px-Englebart_mouse_and_keyboard.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Englebart_mouse_and_keyboard.jpeg.html"title="Enlarge"></a></div>A mouse, keyboard and collaborative text-editing demonstrated in Douglas Englebart’s “Mother of All Demos”, 1968</div></div></div>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/eb/Reader_highlighting.jpeg/640px-Reader_highlighting.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/eb/Reader_highlighting.jpeg/320px-Reader_highlighting.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Reader_highlighting.jpeg.html"title="Enlarge"></a></div>A reader highlights text while skim-reading in order to improve retention and to create a hierarchy in a text</div></div></div>
<h2><spanclass="mw-headline"id="installing_chdk_firmware_for_the_bookscanner">installing chdk firmware for the bookscanner</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/tools/chdk_firmware_installation&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p><i>From a framapad made by erg</i>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/eb/Reader_highlighting.jpeg/960px-Reader_highlighting.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/eb/Reader_highlighting.jpeg/320px-Reader_highlighting.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Reader_highlighting.jpeg.html"title="Enlarge"></a></div>A reader highlights text while skim-reading in order to improve retention and to create a hierarchy in a text</div></div></div>
Download the correct firmware according to your camera model
http://www.mighty-hoernsche.de/
Method 2 - Using CHDK itself to make the SD card bootable.
Start out with your SD Card Lock switch in the unlocked position (the small slide switch on the side of the card - see picture above - make sure it is in the unlocked position to start this process.)
Low level format the card in camera using the camera's built-in card format menu selection. Warning: any images on the card will be erased at this point.
Remove the card from your camera and put it into the SD card reader of your PC.
The card should now contain a single FAT32 partition. If you are using a large SD card, please make sure your camera did not format the card as exFAT - see warning note at start of this section. You may need to use something like FAT32 Format to reformat the card in your PC if so.
Now please check again (by looking at the properties of your card in an SD card reader in your PC) to ensure that your card is formatted either FAT16 or FAT 32 - and not exFAT!
Unpack the appropriate build of CHDK for your camera and firmware version directly to the card (including all subdirectories).
With the Card Lock switch still in the unlocked position put the card back into your camera.
Turn on your camera by pressing the Play button (or using the Play switch on some cameras). Do not start the camera with the On/Off switch or this process will not work.
Reset factory settings on the camera in order to enable the firmware update setting (if it's not there already)
Start CHDK manually by selecting the Firmware Update option in the Canon menus.
After the CHDK logo briefly displays, start CHDK by using the <ALT> key sequence for your camera.
Enter the CHDK menu (press play button and then MENU for the CHDK menu), and select Miscellaneous stuff -'> SD Card' -> Make Card Bootable
Turn your camera off, write protect the SD card by moving the little switch on the side of the card to the lockedposition, insert the card back into your camera. Note that CHDK will cause the camera to ignore the lock switch so that you can take pictures normally.
</p><p>I wanted to read this collection of essays by Flusser during the holidays. Steve had sent me a link to an interview with Flusser in which he described the "magic" of linear writing and subsequent technologies, and I wanted to read more. I very quickly bootlegged this book by printing the PDF on the last day school was open for the year. In my haste, however, I trimmed the bottom edge a bit too close. It's still fine (at least the page numbers weren't cut off), but I wish I hadn't been in such a rush. The cover was made quickly at the photocopier as well, a no-frills effort.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/59/Rosetta_stone.jpeg/640px-Rosetta_stone.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/59/Rosetta_stone.jpeg/320px-Rosetta_stone.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Rosetta_stone.jpeg.html"title="Enlarge"></a></div><i>The Rosetta Stone</i>, a tablet discovered in 1799 inscribed with three versions of a decree written in Ancient Egyptian and Ancient Greek</div></div></div>
<h2><spanclass="mw-headline"id="traces_of_book_use_in_from_the_books">traces of book use in <i>from the books</i></span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Annotation_typologies&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>Typologies of traces of use identified from a previous project called <ahref="From_the_Books:_SLV_RBRR_000-099.html"title="User:Simon/From the Books: SLV RBRR 000-099">From the Books</a>, which explored books from the 000-099 section of the Redmond Barry Reading Room in the State Library of Victoria.
</p>
<ul><li>ACCIDENTAL DOG-EAR</li>
<li>ANNOTATION</li>
<li>ASTERISK</li>
<li>BOOK PRICE</li>
<li>BOOKMARK</li>
<li>CIRCLED TEXT</li>
<li>CREASED PAGE</li>
<li>CROSS</li>
<li>DEAD ANT</li>
<li>DOG-EAR</li>
<li>ERASER RUBBING</li>
<li>ERRATA</li>
<li>FINGERPRINT</li>
<li>FOLD</li>
<li>HANDWRITTEN LETTER</li>
<li>INK BLOT</li>
<li>LIBRARY DOCUMENT</li>
<li>LIFTED PRINT</li>
<li>LINE</li>
<li>LOOSE PAGE</li>
<li>NOTEPAPER BOOKMARK</li>
<li>NOTES</li>
<li>PAGES REMOVED</li>
<li>POST-IT NOTE</li>
<li>RECEIPT BOOKMARK</li>
<li>REPLACED IMAGE</li>
<li>SCUFF</li>
<li>SMUDGE</li>
<li>SQUIGGLE</li>
<li>STAIN</li>
<li>STRIKETHROUGH</li>
<li>TICK</li>
<li>TORN PAGE</li>
<li>TORN PAPER BOOKMARK</li>
<li>UNDERLINING</li>
<li>WARPED PAGE</li>
<li>WEAR AND TEAR<br></li></ul>
<p>These formed a loose classification system that indexed these books not by bibliographic reference, but by the frequency of occurrence, taking a "bag of words" approach.
Problems that arose were linguistic - it was difficult assigning a word to an example as this already had some assumption of intention (e.g. a doodle as an intentional drawing vs squiggle as unintentional drawing).
</p>
<h2><spanclass="mw-headline"id="thoughts_and_reflections">thoughts and reflections</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Annotation_typologies&action=edit&section=T-2"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>My approach was one of identification based on nouns, which presented problems in describing the traces we found and the possible intention (or lack of intention) in their making. To what extent could the noun communicate what had happened? Nouns point towards things affected by actions. In a sense, to name something is to own it, and things become property much more easily than actions.
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/59/Rosetta_stone.jpeg/960px-Rosetta_stone.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/5/59/Rosetta_stone.jpeg/320px-Rosetta_stone.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Rosetta_stone.jpeg.html"title="Enlarge"></a></div><i>The Rosetta Stone</i>, a tablet discovered in 1799 inscribed with three versions of a decree written in Ancient Egyptian and Ancient Greek</div></div></div>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c0/Bl_sessions_A6_card.jpeg/640px-Bl_sessions_A6_card.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c0/Bl_sessions_A6_card.jpeg/320px-Bl_sessions_A6_card.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Bl_sessions_A6_card.jpeg.html"title="Enlarge"></a></div>A6 card announcing the first bootleg library sessions, December 2019</div></div></div>
<liclass="toclevel-1"><ahref="#bootleg_library_at_wijnhaven_61.2C_27.11.19.2C_28.11.19_.26_04.12.19"><spanclass="tocnumber">1</span><spanclass="toctext">bootleg library at wijnhaven 61, 27.11.19, 28.11.19 & 04.12.19</span></a>
<p>The first bootleg library sessions were held in Wijnhaven 61, a building that houses several of the Piet Zwart Institute Master's Departments, including XPUB, Lens-Based, MIARD, and the Master in Arts Education. The building also is home to many bachelor students, and stations where students can prototype work. I decided to run introduction sessions in a small room in the drawing station. I advertised these sessions with posters and flyers, distributed throughout Wijnhaven 61 and the adjacent Blaak building. Sessions were organised as a come-as-you-are basis, running for half-hour intervals, but with an open invitation for attendees to stay as long as they liked. The initial purpose of these sessions was to acquaint attendees with the digital bootleg library, explore the interface, and create registered user accounts. There was also another purpose of meeting with other readers to discuss texts we were reading, and how we gained access to them. I kept an Etherpad document open for each session, where I could take notes on what was discussed.
bootleg library sessions pad: <aclass="external text"href="https://pad.xpub.nl/p/bootleg_library_sessions%7C"rel="nofollow">Documentation of Session</a><br>
<ahref="bootleg_library_sessions_wdka_pad_dump.html"title="User:Simon/bootleg library sessions wdka pad dump">User:Simon/bootleg library sessions wdka pad dump</a>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c0/Bl_sessions_A6_card.jpeg/960px-Bl_sessions_A6_card.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c0/Bl_sessions_A6_card.jpeg/320px-Bl_sessions_A6_card.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Bl_sessions_A6_card.jpeg.html"title="Enlarge"></a></div>A6 card announcing the first bootleg library sessions, December 2019</div></div></div>
<p><ahref="bootleg_library_at_wijnhaven_61.html"title="User:Simon/bootleg library at wijnhaven 61">User:Simon/bootleg library at wijnhaven 61</a>
</p>
<!--
NewPP limit report
Cached time: 20200617092253
Cached time: 20200620065539
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.041 seconds
Real time usage: 0.130 seconds
Preprocessor visited node count: 13/1000000
Preprocessor generated node count: 44/1000000
Post‐expand include size: 1678/2097152 bytes
CPU time usage: 0.010 seconds
Real time usage: 0.010 seconds
Preprocessor visited node count: 1/1000000
Preprocessor generated node count: 4/1000000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Highest expansion depth: 1/40
Expensive parser function count: 0/100
Unstrip recursion depth: 0/20
Unstrip post‐expand size: 1827/5000000 bytes
Unstrip post‐expand size: 0/5000000 bytes
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/ef/Hansen_Writing_Ball.jpeg/640px-Hansen_Writing_Ball.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/ef/Hansen_Writing_Ball.jpeg/320px-Hansen_Writing_Ball.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Hansen_Writing_Ball.jpeg.html"title="Enlarge"></a></div>The first commercially-produced typewriter, the Hansen Writing Ball</div></div></div>
<h2><spanclass="mw-headline"id="Setting_up_a_calibre-web_content_server_on_an_RPi">Setting up a calibre-web content server on an RPi</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/bootleglibrary/tools&action=edit&section=T-1"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/ef/Hansen_Writing_Ball.jpeg/960px-Hansen_Writing_Ball.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/e/ef/Hansen_Writing_Ball.jpeg/320px-Hansen_Writing_Ball.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Hansen_Writing_Ball.jpeg.html"title="Enlarge"></a></div>The first commercially-produced typewriter, the Hansen Writing Ball</div></div></div>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/b/b8/House_of_leaves.jpeg/640px-House_of_leaves.jpeg"><imgalt=""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><divclass="thumbcaption"><divclass="magnify"><aclass="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>
<p><i>text, tbc</i> is an essay written as a contribution to a publication, as part of Onomatopee's Meeting Grounds 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 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><br>
<b>text, tbc</b>
</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>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/b/b8/House_of_leaves.jpeg/960px-House_of_leaves.jpeg"><imgalt=""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><divclass="thumbcaption"><divclass="magnify"><aclass="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>
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c2/Amateur_librarian.jpeg/640px-Amateur_librarian.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c2/Amateur_librarian.jpeg/320px-Amateur_librarian.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Amateur_librarian.jpeg.html"title="Enlarge"></a></div>Quote from <i>Why and How to Become an Amateur Librarian</i></div></div></div>
<liclass="toclevel-2"><ahref="#If_nginx_is_compiled_and_installed_from_the_source_code"><spanclass="tocnumber">2.2</span><spanclass="toctext">If nginx is compiled and installed from the source code</span></a></li>
<h1><spanclass="mw-headline"id="nginx_service_file">nginx service file</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/nginx_configuration&action=edit&section=T-2"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h1>
<p>To enable, start, stop, or check the status of the nginx web server, a service file is needed. To create one in a systemd Linux distribution, make this file:
<h2><spanclass="mw-headline"id="If_nginx_is_compiled_and_installed_from_the_source_code">If nginx is compiled and installed from the source code</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/mw-mediadesign/index.php?title=User:Simon/Trim4/prototypes/nginx_configuration&action=edit&section=T-4"title="Edit section: ">edit</a><spanclass="mw-editsection-bracket">]</span></span></h2>
<p>If nginx binary is installed at /usr/local/nginx/sbin/nginx, enter:
<divclass="cardback"><DOCUMENT_FRAGMENT><divclass="mw-parser-output"><divclass="thumb tright"><divclass="thumbinner"style="width:152px;"><aclass="image"href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c2/Amateur_librarian.jpeg/960px-Amateur_librarian.jpeg"><imgalt=""class="thumbimage"decoding="async"src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/c/c2/Amateur_librarian.jpeg/320px-Amateur_librarian.jpeg"></a><divclass="thumbcaption"><divclass="magnify"><aclass="internal"href="File:Amateur_librarian.jpeg.html"title="Enlarge"></a></div>Quote from <i>Why and How to Become an Amateur Librarian</i></div></div></div>
