Chapter 2b: Server Issues: Networked Infrastructure

This page was last edited on 27 January 2025, at 12:15.
Revision as of 12:15, 27 January 2025 by Systerserver (talk | contribs)

Coordinator: SysterServer Contributors: xm (ooooo) and Mara

https://digitalcare.noho.st/pad/p/servpub

https://eth.leverburns.blue/p/servpub-2b

/

positionality of feminist servers:

  • data infrastructure literacy
  • digital solidarity networks
  • dependencies - alliancies - affinities
  • troubleshooting /debugging vulgar marxism

politics of networks

  • regulatory bodies ICAN-RFC's develop/discuss standards
  • differences between local and public/static IP --- scarcity of ipv4, how are they assigned, and ipv6. Politics and economics of IP distribution, how do they impose power structures? see internet governance talk and notes by Vesna during /etc
  • companies ( ATT/BELL, Mictosft/...) develop protocols - (udp tc/ip) / encryption protocols
history and topology of VPN
  • what types of networks? origin/evolution of terminology & use
  • break down the differences between mesh VPN, VPN for proxy
  • open vpn - diffie hellman key / cryptodance

positionality of feminist servers

[INTRO] In this chapter we will appropriate the tactics of Queercore: How To Punk A Revolution and introduce our feminist server's activities as a catalyst to push techno-feminism into existence and announce we are here to stay. The documentary explores the rise of the queercore cultural and social movement in the mid-1980s, which channeled punk angst into a biting critique of societal homophobia.

We as part of Systerserver and co-dependent on other feminist server projects (Anarchserver, Maadix, leverburns, digiticalcare...), will share ways of doing, tools & strategies to overcome/overthrow the monocultural, centralized oligopolic surveillance & technologies of control.

A server is a place where our data is hosted, the contents of our websites, where we are chatting, storing our stories and imaginaries and access the multiple online services we need to get organized (mailinglists, calendars, notes,...). We don't want to be served, we think a feminist server as an (online) space that we need to inhabit. As inhabitants,  we contribute by nurturing a safe space and a place for creativity, experimentation and justice, a place for hacking heteronormativity and patriarchy. Feminist servers have the potential to learn together, to maintain and care for a space together in a non-hierarchical way, and in a non-meritocratic way.

To be able to setup server's we need to have hardware, a machine - a single board computer (like raspberry pi, olimex, an old refurbished laptop,...) or a server in a rack in a data center, a virtual machine (vps), and the will to self host (described in chapter 1). As Systerserver, our feminist server project, we relate and organize around these servers by adopting different roles, defined in conversations in Anarchaserver. [roles]

Besides from these roles we need to encourage “data infrastructure literacy” for the ability to account for, intervene around and participate in the wider socio-technical infrastructures through which data is created, stored and analyzed. Our intent is to make space for collective inquiry, experimentation, imagination and intervention around data. Data as in binary information, suitable for processing by computers, recognizing it's intrinsic (human)labour conditions, maintenance and hence care. In becoming more literate, we cultivate our sensibilities around data politics and as well engage a wider public with digital data infrastructures.

For this reason we need to make servers visible and physical as a crucial/critical space, we need a room of our own and we need a ‘connected room’ of our own.*  or a network of one's own

  • *referring to the paranodal periodic publication and series of events and worksession in rotterdam revisting of Virgina Woolf's classic eesay.

By making infrastructures visible with the aid of drawings, diagrams, manuals, metaphors, performances, gatherings, systerserver traverses technical knowledge with an aim to de-cloud (Hilfling Ritasdatter, Gansing, 2024) our data, and redistribute our networks of machines and humans/species.

A connected room, network of one's own, with allies as co-dependencies, attributes collectivities interacting as radical references which evades hierarchies of cognitive capital based on individuals and underlines the collective efforts to resist within the hegemonic technological paradigm.


index.php?title=Category:ServPub