User:)biyibiyibiyi(/RW&RM 04/proposal 0 1 0: Difference between revisions
Line 12: | Line 12: | ||
===What is your time table?=== | ===What is your time table?=== | ||
During October, I will continue on developing Channel Channel project. I am at the phase of writing tutorials and DIY kits for home brew VPN. Meanwhile, I am identifying aspects of the textual implication of tutorials that account toward experimental publishing. I am also experimenting with building a distributive VPN network based on P2P infrastructure. I hope to try the distributive network first on VPS. During the process of setting up the network I would like to identify and draft textual basis for the network, such codes of conduct and manifesto. Similar to treating the writing of tutorial as a form a experimental publishing. | During October, I will continue on developing Channel Channel project. I am at the phase of writing tutorials and DIY kits for home brew VPN. Meanwhile, I am identifying aspects of the textual implication of tutorials that account toward experimental publishing. I am also experimenting with building a distributive VPN network based on P2P infrastructure. I hope to try the distributive network first on VPS. During the process of setting up the network I would like to identify and draft textual basis for the network, such codes of conduct and manifesto. Similar to treating the writing of tutorial as a form a experimental publishing. | ||
In November, I would like to push the project timeline backwards, to research instances of centralization and decentralization in media archaeology. The interest in media archaeology is twofold. Theoretically, I want to look at the lineage of how certain protocols, infrastructure and network become dominant, and how notions of centralization and decentralization become implemented and materialized in early days of networking. The example of ARPANET provides both notions of decentralization and centralization. Decentralization to maintain network communication once one of the nodes suffer attack from the USSR; centralization to maintain bureaucratic efficiency, that no subversive operations can be conducted other than sending top-down commands and receiving commands. Media archaeology documented numerous counter narratives to ARPANET, such as usenet, referred to as the poor man's ARPANET; Computer Lib – You can and must understand computers NOW. Practically, I want to start building resistant networks from antiquated media. The networks present resistance to censorship and surveillance since they are antiquated thus out of radar frequency. The need for building resistant, undercover networks derives from subversive nature of decentralization and hacktivism, such as circumventing censorship, surveillance and challenging established authoritative organizations. | |||
===why do you want to make it?=== | ===why do you want to make it?=== |
Revision as of 09:18, 20 October 2019
What do you want to make?
I propose to produce a series of tutorials, manuals, blogs, and hacked objects within the context of DIY networking. Grass root DIY networking has been an topic of interest during the last fifteen years in Europe and North America, as a response towards pathologies of the modern networked world, such as opacity of network infrastructure and asymmetry of power between network monopolies and users (Dragona & Charitos, 2017). The building and facilitation of DIY networks utilize Free/Libre Open Source Software (F/LOSS) tools and adhere to its core principles of freedom to use, modify and redistribute. As F/LOSS advocate for radical openness and promise a democratic model of collaborative framework, certain barriers remain visible, such as low participating rate of female contributors, technical barriers for laypersons, and meritocracy within the system (Nafus, 2011). The writing of technical textual mediums of tutorials and manuals tend to imply these hindrances as well. While these textual mediums tend to be plain, instructive and serve as textual interfaces for participants to be able to utilize and modify the tools and hold discussions around the community, the sociality of these textual medium are often undermined. The expression “RTFM”, Read the F*** Manual illustrates an example of disassociation of caring social relationship between the creator and users (Nafus, 2011). My project attempt to re-investigate the role of textual mediums within DIY/DIWO networking projects. I want to emphasize the participatory potentials of technical textual mediums. I see technical textual mediums as sites to share, invite, interject discourses despite of participants' varied technical skills; through these reciprocal actions, the social dimension of technical texts can be amplified, and facilitate environment for further critical collective making.
How do you plan to make it?
The re-investigation of tutorials, manuals, blogs happens within three types of circulation process. Within the first process, I identify myself as the ignorant user. While trying to set up networks myself, I am in a perpetual state of encountering frustrations reading technical documentation. Upon identifying a technical difficulty, I try to make my frustration visible by contacting the source creator, or other members within the community who are more technically more knowledgeable. I identify this process not only as knowledge transfer process from technically abled to the less abled, but also a process of making public what are the aspects that hinder user from participating in open source collaborative networking.
The second process involves rewriting of the technical texts based on my experiences. In the process of rewriting, I want to address the context within which I perform technical instructions. These contexts are social, cultural and political. The purpose of situating technical instruction within social, cultural and political contexts is to create space to have discourses around technology unlimited to technical lingos.
The third process invite collective reflection by collective writing. As DIY/DIWO networking is a collective process, participants share common interests and objectives, at the same time differ in their individualities. Collective writing invites participants within the network to to share their individual experiences and make consensus on maintaining and facilitating the network.
What is your time table?
During October, I will continue on developing Channel Channel project. I am at the phase of writing tutorials and DIY kits for home brew VPN. Meanwhile, I am identifying aspects of the textual implication of tutorials that account toward experimental publishing. I am also experimenting with building a distributive VPN network based on P2P infrastructure. I hope to try the distributive network first on VPS. During the process of setting up the network I would like to identify and draft textual basis for the network, such codes of conduct and manifesto. Similar to treating the writing of tutorial as a form a experimental publishing.
In November, I would like to push the project timeline backwards, to research instances of centralization and decentralization in media archaeology. The interest in media archaeology is twofold. Theoretically, I want to look at the lineage of how certain protocols, infrastructure and network become dominant, and how notions of centralization and decentralization become implemented and materialized in early days of networking. The example of ARPANET provides both notions of decentralization and centralization. Decentralization to maintain network communication once one of the nodes suffer attack from the USSR; centralization to maintain bureaucratic efficiency, that no subversive operations can be conducted other than sending top-down commands and receiving commands. Media archaeology documented numerous counter narratives to ARPANET, such as usenet, referred to as the poor man's ARPANET; Computer Lib – You can and must understand computers NOW. Practically, I want to start building resistant networks from antiquated media. The networks present resistance to censorship and surveillance since they are antiquated thus out of radar frequency. The need for building resistant, undercover networks derives from subversive nature of decentralization and hacktivism, such as circumventing censorship, surveillance and challenging established authoritative organizations.