User:Vitrinekast/Final presentation: Difference between revisions
Vitrinekast (talk | contribs) mNo edit summary |
Vitrinekast (talk | contribs) No edit summary |
||
| Line 13: | Line 13: | ||
<span style="background-color: orange; padding: 4px; border-radius: 4px">Printers</span>, | <span style="background-color: orange; padding: 4px; border-radius: 4px">Printers</span>, | ||
<span style="background-color: orange; padding: 4px; border-radius: 4px">Smaller experiments</span> | <span style="background-color: orange; padding: 4px; border-radius: 4px">Smaller experiments</span> | ||
<div style="display: grid; grid-template-columns: 1fr 1fr"> | <div style="display: grid; grid-template-columns: 1fr 1fr"> | ||
<div> | |||
====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. | |||
</div> | |||
<span style="height: 200px; display: flex">{{#widget:Video|width=180px|height=150px|mp4=https://pzwiki.wdka.nl/mw-mediadesign/images/8/81/VIDEO-2024-02-06-19-20-00_crop.mp4}}</span> | |||
</div> | </div> | ||
<div style="display: grid; grid-template-columns: 1fr 1fr"> | <div style="display: grid; grid-template-columns: 1fr 1fr"> | ||
<div> | |||
====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. | |||
</div> | |||
<gallery mode="packed" widths="400px"> | |||
File:THHGTAAA visual promo.jpg|200px|Visual promo for the show | |||
File:20231024-worm-3.jpg|200px|Instances of Performer, Navigator and Protocoller about to get WORMHOLEd | |||
</gallery> | |||
</div> | </div> | ||
<div style="display: grid; grid-template-columns: 1fr 1fr"> | <div style="display: grid; grid-template-columns: 1fr 1fr"> | ||
<div> | |||
====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? | |||
</div> | |||
<gallery mode="packed" heights="200px" style="text-align:left;"> | |||
File:Tldr.jpg|thumb|alt=TL;DR Special Issue launch. Photo by Thijs.|TL;DR Special Issue launch. Photo by Thijs. | |||
File:Tldr1.jpg|thumb|alt=The shelf infrastructure with chopchop and the e-reader. Photo taken by Thijs.|The shelf infrastructure with chopchop and the e-reader. Photo taken by Thijs. | |||
</gallery> | |||
</div> | </div> | ||
<div style="display: grid; grid-template-columns: 1fr 1fr"> | <div style="display: grid; grid-template-columns: 1fr 1fr"> | ||
<div> | |||
==== 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? | |||
</div> | </div> | ||
<gallery mode="packed" heights="200px" style="text-align:left;"> | |||
File:workshop_1.jpg|Workshop at GR | |||
File:fiber_1.jpeg|Hacked printer during the fiber workshop | |||
</gallery> | |||
<span style="color: red;">TODO: include operator post</span> | |||
</div> | |||
<div style="display: grid; grid-template-columns: 1fr 1fr"> | |||
<div> | |||
====De Bakfiets in SI24==== | |||
</div> | |||
<gallery mode="packed" heights="200px" style="text-align:left;"> | |||
File:CTIC bakfiets.jpg | |||
</gallery> | |||
</div> | |||
<div style="display: grid; grid-template-columns: 1fr 1fr"> | <div style="display: grid; grid-template-columns: 1fr 1fr"> | ||
<div> | |||
====Printer Jam ==== | |||
Together with Riviera, I worked on a performance with printers and live coding. Using the OSC protocol, we were able to create a low-latency communication between a live coding environment and the printers. | |||
</div> | |||
<gallery mode="packed" heights="200px" style="text-align:left;"> | |||
File:Screenshot 2024-12-17 at 21.57.32.png | |||
</gallery> | |||
</div> | </div> | ||
Revision as of 20:56, 9 June 2025
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.
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?
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?
TODO: include operator post
Printer Jam
Together with Riviera, I worked on a performance with printers and live coding. Using the OSC protocol, we were able to create a low-latency communication between a live coding environment and the printers.
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.
<img src="https://i.imgflip.com/4fz7yy.jpg?a485856" width="250px" />
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❤️
During the (un)repair nights, everyone is a repair person, and everything can be a hammer. Some people are there to repair, others for laying out network infrastructures. We meet every other Thursday, and are slowly becoming a stable hangout for Rotterdam Nerds (invite your friends!, come by!).
It has been truly fantastic and amazing to see this space grow, and I really hope it will continue growing. It has been a great opportunity to meet all kinds of people that are busy with repair.
Future of the unrepair? Recently, I've been talking to other communities to see if there can be some collaboration, and also attract people that might feel a bit intimidated to come. It is here, that I do see the value in workshops again.
Alternative workshop format
Altough I did not organise the workshops originally inteneded. I did experiment with the workshop format, and tried to turn it more into an open research moment, then a workshop. Continuing on the zines made last year for the circuit bending and drone synth workshops at Operator/de kunsthal, I made forms as a way to ask questions and as a method of triggering imagination.
Graduation show & building the sound device
The last few weeks have revolved around building more recipes and building a modular sound device. Putting the actual recipes into practice creates new insights around the practice. It is a lot of back and forth between building the paper circuits, making the circuits, realising I'm missing some components and need to adjust the paper circuit (etc...etc...etc...)
Additionally, the chosen material starts to matter even more. Questions about romanticizing nostalgia, which is not something i'd like to do, arise.
During the graduation show (if i finish the sound device) there will be a short performance demo'ing the sounds. The exhibition side will focus on the field guide itself.
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