User:Kim/Projects That May or May Not Be Made
Protocol
- What is it?
- Why make it?
- Workflow
- Timetable
- Rapid prototypes (scratches)
- Write one sentence instruction for a work.
- Make it.
- Previous practice
- Relation to a wider context (personal reader?)
- Choice made
change approach: flush out, dream! big!, write pmoms you would never make, write pmoms for another person, imagine you are a different person writing pmoms for yourself
General
favourites
- opening things up: a toolkit (syllabus) or like the tiny tools for electronics
- experimental cms (experimental from server side, with to print, distribution - mail? -, interfaces!)(book cms, book server)
- diagrammatic keyword writing (graphviz - make a workshop with Claudio) more thesis format wise
formats
- Workshop (series)
- Tool (?)
- Browser Extension
- Website
- Collection/ Archive
- Reading, Performance
- Newsletter
- Book
- iterative publication (series)
interests
- paratext (footnotes, comments, links, page numbers, postscripts, index)
- server (side)
- manuals, handbooks, encyclopedia
- use, user, hacking, piracy
1
1. What
A collection of (fabulated, imaginary, fictional) interfaces. Not focussing on, but including websites.
2. Why
To counter tendencies of over simplification of interfaces and make space for agency and exploration. To Question 'use'.
3. Workflow
- collect One sentence Interfaces
- small rapid prototype like realisation
- versioning over perfection
4. Timetable
Over a fixed Period (4 Weeks) realize one Interface a day.
5. Rapid Prototypes
One Sentence Interface
- An Interface that gets worn down with use.
- An unconfident (uncertain) interface that needs a lot of reassurance, frequently changes its opinion and is generally viewless.
- An Interface that has no boundaries - You loose yourself in it
- no - exit interface
- An Interface that tells you something about itself.
- An ineffective Interface.
- Text as interface.
- An Interface that situates its user.
- A very active Interface that is made of verbs only.
- An Interface that sabotages itself.
- An urgent Interface.
- a recycled interface like an old, used canvas.
7. Context
User:Kim/reading/N. Katherine Hayles: Writing Machines
User:Kim/reading/Johanna Drucker: Performative Materiality
DATA browser 06 EXECUTING PRACTICES, 2018 User:Kim/reading/Executing Micro-Temporality
2
1. What
The same content in different back ends.
2. Why
To study how th organisation of information impacts its front end presentation and possibilities for interaction/ use. And meanwhile explore what (low tech) options exist besides proprietary platforms or template builders.
3. Workflow
- come up with a content
- put it into aspired back end format
- open question of styling + presentation
5. Rapid Prototypes
A back end that is
- a single txt file
- Table / CSV
- pdfs
- a wiki
- a library (of physical books)
- another website
- a nested List
- a notes app
- a chat
- an etherpad
I made this website entirely based on are.na channels: https://network-matters.xyz/ or this one based on a wiki page: https://hub.xpub.nl/cerealbox/~kim/assessment-frontend/
7. Context
User:Kim/reading/Dividing and Sharing
3 collective pmom with wyn and feline
1 what
performance that uses different keyboards
1. 'bread' (qwerty) is standard? (remember the keys)
then use the keys on different keyboards in the end read out loud what words emerge
2. broken telephone (stille post)
sit in a circle, one starts with typing a word, their neighbour has to repeat the typing gesture by using the exact same keys (difference of keyboards is welcome) without looking at the screen, once the word has made the circle, it is read out loud
3. write code on different keyboards
one person writes some code/ function, the other persons use the same keys, no matter if the code stays the same or not -- this is interesting because special characters differ a lot in different keyboards
2 why
different in keyboards is usually seen as a barrier or annoying, while it could also be fruitful to look at language mistakes, misinterpretation and "wrong" gestures, also the moment when a tool we use often breaks attunes us more to how it works and brings back our attention to how we type, a motion, a gesture, a letter, a word, performing it because we usually want to hide mistakes, although they dont have to be bad! and differences in keyboards only become apparent as soon as we compare ours/ are forced to type on one which we are not used to
inquires/ criticizes standardization with english language, especially in programming
3 workflow
get different keyboards get a bunch of people/ participants iterative do it often then compare, discuss different outcomes
5 prototype
wyn and feline agree on a word "Experimental Publishing" wyn types the word on QWerty, feline watches closely and presses the same keys as wyn is:
experimental publishing eyperimentaö puböishing
its interesting but will be more fun with more different keyboard
6 previous practice
feline: is insterested in the meaing of words and what they mean to us specificly compared to the dictionary kim: likes to think about gestures involved in interacting with computers or text, gets excited about moments when something (tool, software, language...) breaks, works differently than expected and makes itself and its own way of working present wyn: is insterested in thinking different rules and systems in a alternative way
7 wider context
Mezangelle is a poetic coding language by mez breeze: https://rhizome.org/editorial/2016/dec/15/mezangelle-an-online-language-for-codework-and-poetry/ coding language is centered on english language, here is a thesis about this topic: https://thesis.digitale-grafik.com/media/pages/unlearning-of-a-web-code/20e15e024e-1745966631/fernanda_braun_santos_ma_thesis_20240403_combined.pdf (german language)
8 comments
- claudio recommended to open up/ scan keyboards
4
1. What is it?
Mapping digital citation
2. Why make it?
to see its inter (and intra) relations, where it resides, where it reaches in the processes, what does it need
3. Workflow
- examine different citation practices on the web
- pic one (or a few) objects
- determine its resources, location, links and trace it
4. Rapid prototypes (scratches)
5. Write one sentence instruction for a work.
5.1. Make it.
trace locations and dependencies of a digital footnote in a graph
6. Previous practice
On Contamination (document performance), Intertextual Intimacies
7. Relation to a wider context (personal reader?)
- targets question of citation in digital spaces
- citation as a necessity (feminist practice), not because of authorship but (open) resources
5
1
A footnote reader (software, tool, interface)
2
open a text and immediately get all its footnotes and their content (without main text), like a scraper - redirect focus of what is 'main' source
3
- think about where/ what kind of tool: browser extension, terminal script, web editor ...
- what specific functions should it have?
- how to operate / interface with
- develop
5
Write a bash script that extracts footnotes from a text (md or pdf?) and outputs them into an extra file
6
same as above (no 4)
6
1
readme.list a reading list sharing platform, too, interface, aggregator (web based or?)