User:Vitrinekast/Final presentation

If i would sum up XPUB in terms of Y1 and Y2, it would be that Y1 has been a lot about exploring the technologies and methodologies that revolve around XPUB (that resonated) and alternative ways of prototyping trough collaboration . This, at times, created resentment from my side, as I feel like I've been prototyping the last 30 years. At times, to me, prototyping is a method of making without committing, an excuse to leave the lorem ipsum.*

Hence the excitement during Y2. Sometimes still resentment (PMOMM's), but overall challenging and very insightful. Being able to, and sometimes having to, commit to a long term research using the methods & technologies introduced in Y1. And also looking forward/moving outside of the academy, where collaboration turned into *community*.

Y1 Prototypes & contributions to the special issue

Year 1's special issues and things that did not make it to a special issue

Servers, Games, Workshops, Printers, Smaller experiments

Exploring servers trough their logs

Experiments with the pen plotters and server logs. This script draws a rectangle (almost) every time a GET request is done to the server.

The Hitchhiker’s Guide to an Active Archive

Choose-Your-Own-Adventure style radio program with Anita and Thijs, performed live at Radio worm. Complete with audience participation and infinite loops. Amazing to see how much we could create in such a short time.

Visual promo for the show
Instances of Performer, Navigator and Protocoller about to get WORMHOLEd

SI23(?) TL'DR with Senka and Thijs

Continuation of the deep dive into server logs: How to change the reading experience. In TL'DR a server maintainer can read annotated logs via an E-reader. Which users were created? What packages are outdated?

TL;DR Special Issue launch. Photo by Thijs.
The shelf infrastructure with chopchop and the e-reader. Photo taken by Thijs.

Hosting and attending many many workshops

Hosted and participated in workshops around permacomputing, circuit bending and soldering. What initially started as a fantastic format, now leaves me with questions. How to get rid of the tutor-student hierarchy in a workshop? How to trigger meaningfull conversation? How to deal with the waste?

Workshop at GR
Hacked printer during the fiber workshop

TODO: include operator post

De Bakfiets in SI24

Printer Jam

Y2: Narrowing things down

Y2 was all about the research project discussed in my thesis: A field guide to salvaging sound devices. Within this umbrella, multiple topics & themes come up.

a field guide to Salvaging Sound Devices

As you've all read this thesis, I will not dive too much into it ;) The field guide gives a reader the tools to make their own sound devices using trash, whilst discussing (some off) the issues that created the waste in the first place. From the gathering of the waste to the creation of sound devices trough so called recipes.

In the research I've tried to figure out how and if I can adjust the practice of building sound devices and hosting workshops to incorporate the ideas of salvage computing.

Reading & writing

Trough the research for the thesis, I tried to expand/develop my reading/writing workflow. All references are collected in Zotero, annotated, and then (if relevant) I'll write a short note/description. Using pandoc/markdown, references can be tagged in the thesis, and then automagically be compiled into a reference list. While this did work really well for reading/gathering information, it wasn't an ideal method to formulate your own text.

Near the end I started writing shorter pieces of text (similar to the wordhole we made in Y1) about the theme's and topics of the thesis. If I had to do the whole process again, I would start with this earlier on.

Workshop format

In the initial proposal for this project, there was a big emphasis on using workshops as a method of sharing research. Both me and Riviera had joined the klankschool, and saw this as an opportunity to collaborate and host various workshops. Looking back, this has not happened due to two reasons:

The (un)repair cafe was started
I underestimated the difficulty of building synthesizers, and had difficulty with turning it into an accessible, hands-on workshop.

HOWEVER

❤️The (un)repair cafe was started❤️

Web2print

I had a lot of fun using web2print for this thesis. The repository can be found on Klankschool's git.

Thesis & long term project
More workshops,

but change the format

paged.js
(un)repair cafe
sneak preview grad show