Chapter 2a: Server Issues: Platform Infrastructure: Difference between revisions

This page was last edited on 12 December 2024, at 10:50.
No edit summary
(Added a broad introduction)
Line 3: Line 3:
Coordinator: In-grid (Katie)
Coordinator: In-grid (Katie)


Contributors: Winnie, Becky, Batool, Pablo, Katie
Contributors: Winnie, Becky, Batool, Katie


Wiki4print, the raspberry pi which hosts https://wiki4print.servpub.net/ travels with us. We have constructed our network of servers in such a way that we can keep it's hardware by our side as we use it, teach with it and share it with others. This chapter will consider the materiality of our particular network of nodes, our reasoning for arranging our infrastructure in this way and what it means to move through the world with these objects. By considering our movement from one place to another we can begin to understand how an ambulent server allows us to locate the boundaries of the software processes, the idiosyncrachies of hardware and estates issues, and how we fit into larger networked infrastructures. How we manage departures, arrivals, and points of transcience, reveals boundaries of access, permission, visibility, precarity and luck.


In this chapter we will explain our decision to arrange our physical infrastructure in this way; mobile and in view. To do this we will map our collective experiences in a series of ''types'' of space. These spaces are reflective of our relative positions as artist*technologist*activist*academic (delete as appropriate):
   * EDUCATIONAL INSTITUTIONS
   * DOMESTIC SPACES
   * CULTURAL SPACES
   * INBETWEENS: BORDERS/TRAVEL
More complete sections of this section will be shared on this page, but you can watch us draft sections of this chapter here:
https://pad.riseup.net/p/PlatformInfrastructure-keep
https://pad.riseup.net/p/PlatformInfrastructure-keep




<noinclude>
<noinclude>
[[Category:ServPub]]
[[index.php?title=Category:ServPub]]
</noinclude>
</noinclude>

Revision as of 10:50, 12 December 2024

Platform infrastructure

Coordinator: In-grid (Katie)

Contributors: Winnie, Becky, Batool, Katie

Wiki4print, the raspberry pi which hosts https://wiki4print.servpub.net/ travels with us. We have constructed our network of servers in such a way that we can keep it's hardware by our side as we use it, teach with it and share it with others. This chapter will consider the materiality of our particular network of nodes, our reasoning for arranging our infrastructure in this way and what it means to move through the world with these objects. By considering our movement from one place to another we can begin to understand how an ambulent server allows us to locate the boundaries of the software processes, the idiosyncrachies of hardware and estates issues, and how we fit into larger networked infrastructures. How we manage departures, arrivals, and points of transcience, reveals boundaries of access, permission, visibility, precarity and luck.

In this chapter we will explain our decision to arrange our physical infrastructure in this way; mobile and in view. To do this we will map our collective experiences in a series of types of space. These spaces are reflective of our relative positions as artist*technologist*activist*academic (delete as appropriate):

   * EDUCATIONAL INSTITUTIONS

   * DOMESTIC SPACES

   * CULTURAL SPACES

   * INBETWEENS: BORDERS/TRAVEL

More complete sections of this section will be shared on this page, but you can watch us draft sections of this chapter here: https://pad.riseup.net/p/PlatformInfrastructure-keep



index.php?title=Category:ServPub