Chapter 1: Collectivities and Methods: Difference between revisions

This page was last edited on 5 December 2025, at 16:46.
No edit summary
No edit summary
 
(90 intermediate revisions by 8 users not shown)
Line 1: Line 1:
'''Collectivities and Methods (to serve and publish)'''
It should be Chapter 1: Being Book


Pad for working
Pad for working
https://ctp.cc.au.dk/pad/p/servpub_methods
https://ctp.cc.au.dk/pad/p/servpub_methods


Coordinator: Winnie & Geoff
==Collectivities and Working Methods==
Contributors: In-grid, CC, Systerserver, Winnie & Geoff
<!-- COMMENTS FROM SHAPE
We really liked the chapter. It is well-written, interesting and we recognise ourselves in it – for instance, in the ways it carefully makes reference to everybody's contributions. Thank you :-)
One thing we discussed was the readership of the book. What is plain language to some (in some chapters) might be difficult technical explanations to others - or complex academic style.
There are many voices and different discourses in the book, and we wonder if this introductory chapter needs to align expectations? That is, should the many possible readers be addressed more explicitly?
This also relates to the kinds of values and contributions readers might find in the book - some, perhaps more drawn to the elaboration of how things are done on socio-technical levels, others to its questioning of publishing and acdemic writing.


Some futher notes:


What does it mean to publish? Publishing is the act of sharing and passing on knowledge, creating a dynamic relationship between authors/writers/producers and readers. It makes space for others to tune in a particular theme or topic, shaped by a specific medium, format, approach, and structure. At its core, publishing is inherently a social and political process—it builds communities, invites action, and inspires new ways of thinking. To put simply, publishing means making something public, but in this apparently simple act, there’s a lot at stake, not simply what we publish, but how. The process involves resources, tools, technology and infrastructures. In other words, publishing also entails recognizing the post-digital landscape and understanding the political and economic forces that shape the practice.  
Page 8':  "Open source operates as a smokescreen for business as usual".
... Change open souce to open access?
... This section is interesting as it might also relate to a broader audience interested in academic publishing, e.g. within science studies or library studies.
There is a currency in the critique of open access (though, there are many different models for this - some more extractive than others, which perpahs deserves mentioning). This book offers a different perspective - one, not just focused on access. And maybe this needs to be emphasized.
Page 8: "against dominant big tech infrastructures"
... Is this of the the infrasrtuctures of the “predators” or more generally? Maybe be more speciic.
Page 9 - "just as architecture was once killed by the book with the introduction of the Gutenberg printing press."
  ... Perhaps this phrase needs elaboration to the outsider
Page 10: "the trick of the tech industry is to make these operations barely noticeable, in this sense ideological, as it hides its underlying structures and naturalises its operating system"
... Would it be an idea to include a paragraph on how platforms work as infrastructures (Paul Edwards’ argument in Platforms on Fire)?
E.g. tools like word processors are (as an example) not just tools for producing content, but also infrastructures in the form of a platform - conditioning the organisation of writing and valorisation.


This book is an intervention in these ongoing debates [ref], emerging out of a particular history of experimental publishing and shaped by the collaborative efforts of various art-tech collectives, operating both within and beyond academic contexts, who are all invested in how to make things public and find ways to publish outside of commercial and institutional norms [1]. Crucially, the ethics of Free/Libre and Open Source Software (FLOSS), particular its emphasis on the freedom to study, modify and share (Klang 2005; Mansoux and de Val 2008), operate as one of our core principles in working on this book, enabling possibilities for modification and versioning with a broader community in mind. What links these traditions is the need to address the social relations that experimental publishing can help to expose and activate differently.
Page 17: Issues of ongoing maintenance become foregrounded and become shared responsibility of the group necessitating an agreed code of conduct."
... "Become" twice in the same sentence. Perhaps: "become foregrounded and a shared responsibility"?


Our working premise is that despite the trend towards open access (White 2023; Leigh-Ann et al 2023), relatively little has changed in academic publishing and scholars still seek to distribute their work through enclosures and based on lumpen workflows that still follow a model that is largely unchanged since industrialism. This book is an attempt to draw attention to these material conditions for the production of books, and to strengthen the possibility of working alternatives to mainstream publishing [2]. Our concern is that books, and academic books in particular, follow a model of production that belies their criticality. By criticality, we mean to go beyond a criticism of conventional publishing and acknowledge the ways in which we are implicated at all levels in political choices when we engage in how to produce books. It's this kind of reflexivity that has guided our approach.  
Page 33: "Here we are also introduced to Sara Ahmed’s intervention in the politics of referencing in which they choose to exclude white men from citation to somewhat balance the books.50 If we are to take an intersectional approach here, then clearly there are other exclusions which we need to engage that relate to the broader project of epistemic justice."
... As much as we also like Ahmed's work, we're also betting on McKittrick's critique of the 'smartness' of Ahmed's proposal - or, a further problematization. Is it enough to simply replace some names
by others, leaving the structure intact? And “Do we unlearn whom we do not cite?” McKittrick’s proposal is that we “stay with the trouble” of referencing. that is, that we don't just question who is referenced – but what kinds of collectives are implied and elicited by different forms of referencing... -->


The book is a kind of a manual to build and think with -- to register the importance of its own coming into being as a book (as an onto-epistemological object if you like). It is produced in a reflexive manner so that the content and the form through which it is produced are recognised as interconnected. [winnie to winnie note: will think more with this and how to talk more about reflexivity]
<!-- The collectives are mentioned a lot. Would it be useful to have short blurbs on each group and what they did for reference, incase it's confusing? -->


Background
<unicode> ͚  ཀྵ 書 📖</unicode>


More pragmatically, the aim is to develop a radical alternative platform and workflow for publishing. We build upon previous projects and collaborations in the field of experimental publishing such as Aesthetic Programming (Soon & Cox, 2020) in which the authors developed a book about software as if it were software. All the contents were offered as an open resource, to encourage others to fork copies and customize their own versions of the book. In FLOSS culture, more than one programmer contributes to writing and documenting code. Contributors might be unknown and are able to update or improve the software by forking—making changes and submitting merge requests to incorporate updates—in which the software is built together as part of a community. To merge, in this sense, is to agree to make a change, to approve it as part of a process of collective decision-making and with mutual trust. This is common practice in software development particularly in the case of FLOSS in which developers place versions of their programs in version control repositories (such as GitLab) so that others can download, clone, and fork them. We were curious to explore how the concept of forking in software practice might inspire new practices. By encouraging new versions to be produced by others, the book set out to challenge publishing conventions and make effective use of the technical infrastructures through which we make ideas public. Clearly wider infrastructures are especially important to understand how alternatives emerge from the need to configure and maintain more sustainable and equitable networks for publishing.  
What does it mean to publish? Put simply, publishing means making something public (from the Latin publicare, ‘make public’) but there’s a lot more at stake, not simply concerning what we publish and for whom, but how we publish. It is inherently a social and political process, and builds on wider infrastructures that involve communities and publics, and as such requires reflexive thinking about the socio-technical systems we use to facilitate production and distribution, including the choice of specific tools and devices. In other words, publishing entails understanding the wider political-economic forces, structures and infrastructures that shape it as a practice and cultural form.  


It is with this in mind that we have tried to engage more fully with the politics of infrastructure that supports the production and distribution of books. In this way we would argue that the project responds to the pressing need for publishing to acknowledge its broader apparatus. This follows both a technical and social protocol, and it is crucially important that this is a collective enterprise, taking further inspiration from "A Transversal Network of Feminist Servers", a collaborative project that builds on selfhosting infrastructural practicies that follow intersectional feminist principles. The aim is to rethink the current landscape of publishing infrastructure and digital knowledge organization, and offer a viable alternative which can support new and existing publishing initiatives. Part of the motivation was the perceived need to develop a community of shared interest around experimental publishing and affective infrastructures in London. We could see similar initiatives elsewhere, in particular in the Netherlands and Belgium, and were envious.  
This book is an intervention into these concerns, emerging out of a particular history and experimental practice often associated with collective struggle.<ref>Janneke Adema, "Experimental Publishing as Collective Struggle: Providing Imaginaries for Posthumanist Knowledge Production," <i>Culture Machine</i> 23 (2024), https://culturemachine.net/vol-23-publishing-after-progress/adema-experimental-publishing-collective-struggle/.</ref> It is shaped by the collaborative efforts of various collectives involved in experiemntal publishing, operating both within and beyond academic contexts (and hopefully serving to undermine the distinction between them), all invested in the process of how to publish outside of the mainstream commercial and institutional norms.<ref>Influential here is the Experimental Publishing masters course (XPUB) at Piet Zwart Institute in Rotterdam, where students, guests and staff make 'publications' that extend beyond print media. See: https://www.pzwart.nl/experimental-publishing/special-issues/. Amongst others, two grassroot collectives based in the Netherlands are significant to mention, Varia and Hackers & Designers, and in Belgium, Constant and Open Source Publishing. All have focused on developing and sharing free and open source publishing tools, including web-to-print techniques. See, for example  https://varia.zone/en/tag/publishing.html and https://www.hackersanddesigners.nl/experimental-publishing-walk-in-workshop-ndsm-open.html. The colophon offers a more comprehensive list of the geneology of these publishing practices and tools.</ref> So-called "predatory publishing" has become the default business model for much academic publishing, designed to lure prospective and career-minded researchers into a restrictive model, that profits from the payment of fees for low quality services.<ref>Jeffrey Beall, "Predatory publishers are corrupting open access", <i>Nature</i> 489, 179 (2012): https://doi.org/10.1038/489179a.</ref> For the most part, academics are unthinkingly complicit, compelled by a research culture that values metrics and demands productivity above all else, and tend not to consider the means of publishing as intimately connected to the argument of their papers. As a result there's often a disjunction between form and content.


[to be continued...]
<h4> Public-ation </h4>


+++
Despite its apparent recuperation by the mainstream, the ethics of Free/Libre and Open Source Software (FLOSS) still provides a foundation for our approach, as it places emphasis on the freedom to study, modify and share information.<ref>Mathias Klang, "Free software and open source: The freedom debate and its consequences," <i>First Monday</i> (2005): https://firstmonday.org/ojs/index.php/fm/article/view/1211.</ref> These remain core values for any publishing project that wants to maximise its reach and use, as well as enable re-use within a broader and expandible community.<ref>Lucie Kolb, "Sharing Knowledge in the Arts: Creating the Publics-We-Need," <i>Culture Machine</i> 23 (2024): https://culturemachine.net/vol-23-publishing-after-progress/kolb-sharingknowledge-in-the-arts/.</ref> What FLOSS and experimental publishing have in common is the need to address the intersection of technology and sociality, and support communities to constitute themselves as publics not simply in terms of the ability to speak and act in public, but through being able to construct their own platforms, what Christopher M. Kelty has referred to as a "recursive public."<ref>To explain more fully, "A recursive public is a public that is vitally concerned with the material and practical maintenance and modification of the technical, legal, practical, and conceptual means of its own existence as a public; it is a collective independent of other forms of constituted power and is capable of speaking to existing forms of power through the production of actually existing alternatives." Christopher M. Kelty, <i>Two Bits: The Cultural Significance of Free Software</i> (Duke University Press, 2020), 3; available as free download at https://twobits.net/pub/Kelty-TwoBits.pdf.</ref>
Research publication // Academic book futures: more from Christian, Geoff


Smth on how ServPub relates to a longer history of making PhD workshops, "building" (rendering) research, and the institutional or other challenges of this + peer review process
For the most part, distribution of academic publications is still largely organised behind pay-walls and through reputation or prestige economies, dominated by major commercial publishers in the Global North.<ref>The “big four” (Elsevier, Springer Nature, Wiley, Taylor & Francis) earned over $7.1 billion in 2024, maintaining profit margins of around 30–37%. Whereas researchers work for free, spending over 130 million unpaid hours annually on peer review alone. In addition, commercial publishers dominate not only journals but also evaluation systems (Scopus, Clarivate, COPE), reproducing knowledge-power in the Global North and marginalizing other community-led and regional models. See Fernanda Beigel, Dan Brockington, Paolo Crosetto, Gemma Derrick, Aileen Fyfe, Pablo Gomez Barreiro, Mark A. Hanson, Stefanie Haustein, Vincent Larivière, Christine Noe, Stephen Pinfield, James Wilsdon, "The Drain of Scientific Publishing," 2005: arXiv:2511.04820, https://doi.org/10.48550/arXiv.2511.04820.</ref> When open access is adopted, for the most part it remains controlled by a select few companies that operate oligopolistic structures to protect their profit margins and positions in the markeplace.<ref>Leigh-Ann Butler, Lisa Matthias, Marc-André Simard, Philippe Mongeon, Stefanie Haustein, "The oligopoly’s shift to open access: How the big five academic publishers profit from article processing charges," <i>Quantitative Science Studies</i> (2023) 4 (4): 778–799. https://doi.org/10.1162/qss_a_00272.</ref> As such it is not suprising to realise that the widespread adoption of open access principles in academic publishing, once intended to democratize knowledge, have become a new profit engine for publishers. In these hands, open access provides as a smokescreen for business as usual, much like greenwashing for the environment.


'''1. Structure'''
This book is an attempt to draw some red lines here concerning the historical and material conditions for their production and distribution, while offering an alternative model -- and one that is less extractive in terms of resources and labour power. Our approach is grounded in collective working practices and shared values that push back against dominant big tech infrastructures and the drive toward seamless interfaces and scale-up efficiency. To repeat, our concern lies in the disjunction between the critical rigour of academic texts and the use of conventional modes through which they are produced that lack criticality. By criticality, we mean to go beyond a criticism of conventional publishing and to further acknowledge the ways in which we are implicated at all levels in the choices we make when we engage with publishing practices. This includes not only the tools we use -- to design, write, review and edit -- but also the broader infrastructures such as the platforms and servers, within, and through which, they operate. It is this kind of reflexivity that has guided our approach throughout the project: moving beyond the notion of the book as a discrete object and instead conceiving of it as a relational assemblage in which its constituent parts mutually depend on and transform one another in practice.  


The book charts the development of a bespoke publishing infrastructure that draws together previously separated processes such as writing, editing, peer review, design, print, distribution. Each chapter unpacks practical steps alongside a discussion of some of the poltical implications of our approach.
<h4>Infrastructure</h4>


[go on to describe each chapter in detail]
We have adopted the phrase "publishing as collective infrastructure" as our title because we want to stress these wider relational properties and how power is distributed, as part of the hidden substrate that includes tools and devices but also logistical operations, shared standards and laws, as Keller Easterling has put it. Infrastructure allows information to invade public space, she argues -- interestingly, just as architecture was killed by the book with the introduction of the Gutenberg printing press.<ref>Keller Easterling, <i>Extrastatecraft: The Power of Infrastructure Space</i> (London: Verso, 2014). Before print, buildings such as cathedrals conveyed stories and cultural memory. With the Gutenberg press and mass literacy, the production and distribution of knowledge moved from architecture to print.</ref> This is why we consider it important to not only expose its workings but also acquire the necessary skills -- both technical and conceptual -- to be able to make infrastructures otherwise.


'''2. Collectivities'''
The argument of Easterling, and others, recognises that infrastructure has become a medium of information and mode of governance, exercised through actions that determine how objects and content are organised and circulated. Susan Leigh Star is another who has also emphasised that "infrastructure is a fundamentally relational concept," operationalised through practices and wider ecologies.<ref>Susan Leigh Star & Karen Ruhleder, Steps Toward an Ecology of Infrastructure: Design and Access for Large Information Spaces, <i>Information Systems Research</i> 7(1) (1996), 111-113, https://doi.org/10.1287/isre.7.1.111. Thanks to Rachel Falconer for reminded us of this reference.</ref> Put simply, infrastructures involve "boring things,"<ref>Susan Leigh Star. "The Ethnography of Infrastructure," <i>American Behavioral Scientist</i> 43(3) (2016): 377–391. doi: 10.1177/00027649921955326.</ref> and the trick of the tech industry is to make these operations barely noticeable, so in this sense they are ideological as the underlying structures seem natural. The infrastructures of publishing are powerful in this way as they distribute information on the page through words, and at the same time through the wider operating systems on which they are dependent. If we are to reinvent academic publishing, this must occur at every layer and scale -- what we might call a 'full-stack' transformation -- which includes the social and cultural aspects that technology influences and is influenced by. Here we make reference to 'full stack feminism' which calls for a rethinking of how digital systems are developed, applying the principles of intersectional feminism -- itself an infrastructural critique of method -- to critically engage with all layers of implementation.<ref>See: https://fullstackfeminismdh.pubpub.org/pub/iqztanz3/release/4?readingCollection=ee61d2f6</ref>


- short semi-structured interviews with each collective
<h4> Backround-foreground </h4>


.......0. What characterizes your collective as collective?  
In summary, the book you are reading is a book about publishing a book, a tool for thinking and making one differently, drawing attention to these wider structures and recursions. It sets out to acknowledge and register its own process of coming into being -- as an onto-epistemological object so-to-speak -- and to highlight the interconnectedness of its contents and the multiple processes and forms through which it takes shape in ''becoming book''.
Given these concerns, we ccontinue to find it perverse that academic books are still predominantly written by individual authors and distributed by publishers as fixed objects in time and space. It would surely be more in keeping with the affordances of the technology to stress collaborative authorship, community peer review and annotation, as well as other messy realities of production. This would allow for the development of versions over time, as Janneke Adema has argued, "an opportunity to reflect critically on the way the research and publishing workflow is currently (teleologically and hierarchically) set up, and how it has been fully integrated within certain institutional and commercial settings."<ref>The Community-led Open Publication Infrastructures for Monographs research project, of which Adema has been part, is an excellent resource for this discussion, including the section "Versioning Books" from which the quote is taken, https://compendium.copim.ac.uk/. Also see Janneke Adema’s "Versioning and Iterative Publishing" (2021), https://commonplace.knowledgefutures.org/pub/5391oku3/release/1 and "The Processual Book How Can We Move Beyond the Printed Codex?" (2022), LSE blog, https://blogs.lse.ac.uk/lsereviewofbooks/2022/01/21/the-processual-book-how-can-we-move-beyond-the-printed-codex/; Janneke Adema and Rebekka Kiesewetter, "Experimental Book Publishing: Reinventing Editorial Workflows and Engaging Communities" (2022), https://commonplace.knowledgefutures.org/pub/8cj33owo/release/1.</ref> An iterative approach would suggest other possibilities that draw publishing and research processes closer together, and within which the divisions of labour between writers, editors, designers, software developers could become entangled in non-linear workflows and interactions. Through the sharing of resources and their open modification, generative possibilities emerge that break out of protectionist conventions perpetuated by tired academic procedures (and tired academics) that assume knowledge to be produced in standardised ways, and imparted through the reductive logic of input/output.


.......1. What are your approaches in working together as a group and working with others?
Our approach is clearly not new. It draws on multiple influences, from the radical publishing tradition of small independent presses and artist books as well as other experimental attempts to make interventions into research cultures and pedagogy. We might immodestly point to some of our own previous work in this connection, including <i>Aesthetic Programming</i>, a book about software, imagined as if software.<ref>Winnie Soon & Geoff Cox, <i>Aesthetic Programming</i> (London: Open Humanities Press, 2021). Link to downloadable PDF and online version can be found at https://aesthetic-programming.net/; and Git repository at https://gitlab.com/aesthetic-programming/book. See also Winnie Soon, "Writing a Book As If Writing a Piece of Software", in <i>A Peer-reviewed Newspaper about Minor Tech</i> 12 (1) (2023).</ref> It draws upon the practice of forking in which programmers are able to make changes and submit merge requests to incorporate updates to software using version control repositories (such as GitLab). The book explores how the concept of forking can inspire new practices of writing by offering all contents as an open resource, with an invitation for other researchers to fork a copy and customise their own versions of the book, with new references and reflections, even additional chapters, all aspects open for modification and re-use.<ref>In response to this invitation to fork the book, Mark Marino and Sarah Ciston added chapter 8 and a half (sandwiched between chapters 8 and 9) to address a perceived gap in the discussion of chatbots. Their reflections on this can be found in an article, see Sarah Ciston & Mark C. Marino, "How to Fork a Book: The Radical Transformation of Publishing," <i>Medium</i> (2021). https://markcmarino.medium.com/how-to-fork-a-book-the-radical-transformation-of-publishing-3e1f4a39a66c. In addition, we have approached the book’s translation into Mandarin as a fork. See Shih-yu Hsu, Winnie Soon, Tzu-Tung Lee, Chia-Lin Lee​​, Geoff Cox, "Collective Translation as Forking (分岔)," <i>Journal of Electronic Publishing</i> 27 (1): 195-221. https://doi.org/10.3998/jep.5377(2024).</ref> By encouraging new versions to be produced by others in this way, we aim to challenge publishing conventions and exploit the technical affordances of the technologies we use that encourage collectivity. Clearly wider infrastructures are especially important to understand how alternatives emerge from the need to configure and maintain more sustainable and equitable networks for publishing, and that remain sensitive to all that contribute to the shared effort (concerning readers, writers and programmers alike). All this goes against academic conventions that require books to be fixed in time and follow narrow conventions of attribution and copyright.<ref>Although cultural differences should be acknowledged, see for instance: Fei-Hsien Wang, <i>Pirates and Publishers: A Social History of Copyright in Modern China</i> (Princeton University Press, 2019). Thanks to our collaborator Chia-Lin Lee at Zimu Culture for this reference.</ref>


.......2. How does your group work with infrastructure?
The collaborative workshops co-organised by the Digital Aesthetics Research Center at Aarhus University and transmediale festival for art and digital culture based in Berlin provide a further example of this in practice. Since 2012, these workshops have attempted to make interventions into how academic research is conducted and disseminated.<ref>Details of the workshops and associated publications can be found at https://aprja.net/. To explain in brief, an annual open call is released based loosely on the transmediale festival theme of that year, targeting diverse researchers but especially eraly career. Accepted participants are asked to share a short essay of 1000 words, upload it to a wiki, and respond online using a linked pad, as well as attend an in-person workshop, at which they offer peer feedback and then on this basis reduce their texts to 500 words for publication in a "newspaper" to be presented and launched at the festival. Lastly, the participants are invited to submit full-length articles of approximately 5000 words for the online open access journal <i>APRJA</i>, https://aprja.net/. The down/up scaling of the text is part of the pedagogical conceit, condensing the argument to identify key arguments and then expanding it once more to make substantive claims.</ref> Those taking part are encouraged to not only engage with their research questions and offer critical feedback to each other through an embodied peer review process, but also to engage with the conditions for producing and disseminating their research as a shared intellectual resource.


.......3. What do you want to work on Servpub?
The <i>Minor Tech</i> workshop from 2023 made these concerns explicit, setting out to address alternatives to big (or major) tech by drawing attention to the institutional hosting, both at the in-person event and online.<ref>The newspaper and journal publications in 2023 and 2024 were produced iteratively in collaboration with Simon Browne and Manetta Berends using wiki-to-print tools, based on MediaWiki software, Paged Media CSS techniques and the JavaScript library Paged.js, which renders the PDF, much like how this book has been produced. As mentioned, an account of the development of these tools, developed through an iteractive process and by differeht communities, is included in the colophon. This includes, for example, wiki-to-print development and F/LOSS redesign by Manetta Berends for <i>Volumetric Regimes</i> edited by Possible Bodies (Jara Rocha and Femke Snelting) (DATA browser/Open Humanities Press, 2022), available for free download at http://www.data-browser.net/db08.html.</ref> In this way, the publishing platform developed for the workshop can be understood to have a pedagogic function in itself, allowing for thinking and learning to take place as part of the wider socio-technical infrastructure. Building on this, the subsequent workshop <i>Content/Form</i> further developed this approach, working in collaboration with Systerserver and In-grid. Using the ServPub project as a technical infrastructure on which to ground the pedagogy, we were able to exempify how the tools and practices used for our writing shape it, whether acknowledged or not.<ref>More details on the <i>Content/Form</i> workshop and the newspaper publication can be found at https://wiki4print.servpub.net/index.php?title=Content-Form. The research workshop was organised by SHAPE Digital Citizenship & Digital Aesthetics Research Center, Aarhus University, and the Centre for the Study of the Networked Image (CSNI), London South Bank University, with transmediale festival for digital art & culture, Berlin.</ref> The process of setting up the server is described in subsequent chapters, but for now it is important to register how its presence in the same space as the workshop helped to place emphasis on the material conditions for collective working and autonomous publishing -- for ''publishing as collective infrastructure''.


.......4. How do social relations become transformed?
<h4> Self-hosted servers</h4>


[minor composition]
The server needs be set up but also requires care, but rather differently to the ways care has become weaponised in mainstream institutions. As Nishant Shah describes, care has become something that institutions purport to do, with endless policies and promises for well-being and support, but without threatening the structures of power that produce the need in the first place.<ref>See Nishant Shah, "Weaponization of Care," nachtkritik.de, 2021, https://nachtkritik.de/recherche-debatte/nishant-shah-on-how-art-and-culture-institutions-refuse-dismantling-their-structures-of-power.</ref>In our case, we would argue for something more along the lines of "pirate care," in which the coming together of care and technology can question "the ideology of private property, work and metrics."<ref>See "The Pirate Care Project", https://pirate.care/pages/concept/.</ref> Care in this sense comes closer to the work of feminist scholars such as Maria Puig de La Bellacasa who draws attention to relations that "maintain and repair a world so that humans and non-humans can live in it as well as possible in a complex life-sustaining web."<ref>We steal this quote from The Pirate Care Project, see Maria Puig de La Bellacasa, <i>Matters of Care: Speculative ethics in more than human worlds</i> (University of Minnesota Press 2017), 97.</ref> 


2a. social relations meets tech
Feminist servers follow these principles, wherein practices of care and maintenance are understood as acts of collective responsibility. It is with this in mind that we have tried to engage more fully with affective infrastructures that are underpinned by intersectional and feminist methodologies. Systerserver, for instance, operate as a feminist, queer, and anti-patriarchal network, which prioritises care and maintenance, offers services and hosting to its community, and acts as a space to learn system administration skills and inspire others to do the same.<ref>See https://systerserver.net/</ref> Our further inspiration is "A Transversal Network of Feminist Servers" (ATNOFS), a project formed around intersectional, feminist, ecological servers whose communities exchanged ideas and practices through a series of meetings in 2022.<ref>"A Traversal Network of Feminist Servers", available at https://atnofs.constantvzw.org/. The ATNOFS project drew upon "Are You Being Served? A Feminist Server Manifesto 0.01," available at htps://areyoubeingserved.constantvzw.org/Summit_aterlife.xhtm. For a fuller elaboration of Feminist servers, produced as a collective outcome of a Constant meeting in Brussels, December 2013, see https://esc.mur.at/en/werk/feminist-server. Marloes de Valk contributed to the ATNOFS publication and has also written about this extensively in her PhD thesis, <i>The Image at the End of the World: Communities of practice redefining technology on a damaged Earth</i> (CSNI, London South Bank University, 2025).</ref> The publication that emerged from these meetings was released in a manner that reflects the collective ethos of the project. A limited number of copies were printed and distributed through the networks of participants and designed to be easily printed and assembled at home, thus reinforcing commitment to collaboration and access. More on this project is included in the following chapter. For now, it is worth adding that the project responded to the need for federated support for self-hosted and self-organised computational infrastructures across Europe although the UK was notably absent. Indeed part of our motivation for ServPub is to address the perceived need to develop a parallel community of shared interest around experimental publishing and affective infrastructures in London.<ref>Groups involved in ATNOFS were from The Netherlands (Varia, LURK), Romania (hypha), Austria (esc mkl), Greece (Feminist Hack Meetings), and Belgium (Constant). We saw similar initiatives elsewhere, but not in the UK at this time, although in the past we might point to the ongoing efforts of James Stevens at Backspace in 1996 and ongoing with SPC in Deptford, as well as the Art Servers Unlimited event in 2001, organised by Manu Luksch and Armin Medosch. See Davide Bevilacqua, ed. <i>Artists Running Data Centers</i> (servus.at, 2024), 11. https://publications.servus.at/2024-Artists-Running-Data-Centers/ArtistsRunningDataCenters-servus-at_2024.pdf.</ref>


....... and minor compositions here
<h4>Socio-technical forms</h4>


2b. ideas of the commons and autonomia/anarchism
We hope it is clear by now that our intention for this publication is not to valorize feminist servers or free and open-source culture as such but to stress how technological and social forms come together to expose power relations. This comes close to the position that Stevphen Shukaitis and Joanna Figiel have elaborated in "Publishing to Find Comrades," a phrase which they borrow from the Surrealist André Breton. Their emphasis is not to publish pre-existing knowledge and communicate this to a fixed reader but to work towards developing the appropriate social conditions for the co-production of meaning and action. 


'''3. Methods'''
<blockquote>The openness of open publishing is thus not to be found with the properties of digital tools and methods, whether new or otherwise, but in how those tools are taken up and utilized within various social milieus. [...]
Thus, publishing is not something that occurs at the end of a process of thought, a bringing forth of artistic and intellectual labor, but rather establishes a social process where this may further develop and unfold.
In this sense, the organization of the productive process of publishing could itself be thought to be as important as what is produced.</blockquote>
<ref>Stevphen Shukaitis & Joanna Figiel, "Publishing to Find Comrades: Constructions of Temporality and Solidarity in Autonomous Print Cultures," <i>Lateral</i> 8.2 (2019), https://doi.org/10.25158/L8.2.3. For another use of the phrase, see Eva Weinmayr, "One publishes to find comrades," in <i>Publishing Manifestos: an international anthology from artists and writers</i>, edited by Michalis Pichler (The MIT Press, 2018).</ref></blockquote>


Feminist, intersectionality, queer, radical referencing
We agree. The process of making a book is not merely a way to communicate the contents but to invent organisational forms with wider social and political purpose. Can something similar be said of the ServPub project and our book? Maybe. Attention to infrastructure is significant here, as well as the affordances of the tools we use, in allowing for reflection on divisions of labour, the conditions of production, the dependencies of support networks, and sustainability of our practice as academics and/or cultural workers. Moreover, the political impulse for our work draws upon the view that the tools of oppression offer limited scope to examine that oppression and their rejection is necessary for genuine change in publishing practices. Here we paraphrase Audre Lorde of course.<ref>Audre Lorde, <i>The Master’s Tools Will Never Dismantle the Master’s House</i> (1979), available at https://theanarchistlibrary.org/library/audre-lorde-the-master-s-tools-will-never-dismantle-the-master-s-house.</ref>


doing and making and thinking
[[File:Etherpad.png|center|Caption: A screenshot of Etherpad]]


development of tools perhaps too
As for the specific tools for this book, we have used Etherpad for drafting our texts, a free and open source writing software which allows us to collaborate and write together asynchronously. As an alternative to established proprietary writing platforms that harvest data, a pad allows for a different paradigm for the organisation and development of projects and other related research tasks. To explore the public nature of writing, Etherpad makes the writing process visible, as anyone of us can see how the text evolves through additions, deletions, modifications, and reordering. One of its features is the timeline function (called Timeslider in the top menu bar), which allows users to track version history and re-enact the process performatively. This transparency over the sociality and temporality of form not only shapes interaction among writers but also potentially engages unknown readers in accessing the process, before and after the book itself.<ref>We might say it turns readers into writers, following Walter Benjamin in his 1934 essay "The Author as Producer,", in <i>Walter Benjamin: Selected Writings: Volume 2, Part 2, 1931-34</i> (Belnap Press of Harvard University Press, 2005), 777. "What matters, therefore, is the exemplary character of production, which is able, first, to induce other producers to produce, and, second, to put an improved apparatus at their disposal. And this apparatus is better, the more consumers it is able to turn into producers — that is, readers or spectators into collaborators."</ref> Another feature of a pad is that authors are identifiable through colours, usernames are optional and writing is anonymous by default. Martino Morandi has described this as "organizational writing," quoting Michel Callon’s description of "writing devices that put organization-in-action into words," and how writing in this way collectively "involves conflict and leads to intense negotiation; and such collective work is never concluded".<ref>Martino Morandi, "Constant Padology," <i>MARCH</i>, January 2023, https://march.international/constant-padology/. The source Morandi is drawing upon is Michel Callon’s "Writing and (Re)writing Devices as Tools for Managing Complexity," in <i>Complexities</i>, John Law & Annemarie Mol (eds.) (Durham, NC: Duke University Press, 2002), 203.</ref>


artistic practice/research/artivist approach
<h4> Logistical operations </h4>


Apart from writing the book, and drawing attention to its organisational form, it is important to register that we are collectively involved in all aspects of its making. The production process -- including writing and peer review, copyediting and design -- is reflected in the choice of other tools and platforms that we are using as well as the constitution of the collectives involved. Using MediaWiki software and web-to-print layout techniques, ServPub is an attempt to circumvent standard academic workflows and instead conflate traditional roles of writers, editors, designers, developers alongside the affordances of the technologies. To put it plainly, this means rejecting proprietary software such as Abode Creative Cloud and designing by other means, as indicated by the ironic naming of Creative Crowds (CC) as part of our working group.<ref>More on Creative Crowds can be found at https://cc.vvvvvvaria.org/wiki/Main_Page. They describe themselves as engaged with "collective research on the entanglements of web-to-print/experimental publishing/design practices with tools, cultures and infrastructure." Although they run a server, they stress they are not a service but participate in the projects they support.</ref> Indeed, the distributed nature of our endeavour is reflected in the combinations of those involved, directly and indirectly, across the different entities involved who provide the necessary skills and support for the project's realisation. This includes building on the work of others involved in the development of the tools such as the various iterations of 'wiki-to-print' and 'wiki2print', not least involving CC, which In-grid have further adapted as 'wiki4print' for this book.<ref>Again, see the colophon for further details of versions.</ref> The book object is just one output of a complex set of interactions and exchanges of knowledge across time and space.


end chapter with idea of Book as reflexive practice - reiteratung this point - book about its own making.  
As mentioned, the divisions of labour are somewhat collapsed, and the activities that make up the publishing pipeline are reinvented in relation to the various tools and the platforms they support. This is inevitably not without its challenges, especially when such a diverse group of people are involved, each with their own experiences, positionalities, life and employment situations. One of the many challenges of a project like this has been to account for these differences, which include the complexities of unpaid and paid labour. We have tried to address or acknowledge potential 'discomfort' associated with the project throughout our work together in our meetings.<ref>See, for example, the blog post "The (Im)possibility of Non-Extractive Collaboration," https://copim.pubpub.org/pub/pilot-project-documentation-servpub4-non-extractive-collab/release/1, also available as an audio recording.</ref> Perhaps this is particularly important when engaging grassroots collectives who often remain suspicious of academia as a zone of privilege without recognising other factors such as cultural differences and rising precarity in the sector.    


+++footnote+++
Discomfort is important to the praxis of ServPub, emerging as we navigated complex questions related to reputation hierarchies and accreditation, as well as the nature of the institutional infrastructures that support the work. Challenges include uneven access to resources, disparities in institutional support, and the ongoing negotiation of additional labour which reveals some of the power struggles individuals/collectives face within their own particular situations, even as they remain committed to the project. All embrace feminist methodologies, but this commitment is not without differences of interpretation. Language itself also acts as a destabilizing factor, as not all contributors are native English speakers, leading to subtle miscommunication and moments that demand continuous exercise of trust, open communication and negotiation of meaning. Consensus-building within this diverse project entails negotiating differing expectations and end-goals, from contributing to community and personal research interests to advancing academic careers. Issues are further complicated by the politics of documentation and attribution, as contributors strive to fairly represent both individual and collective labour while remaining vigilant against replicating extractive academic norms and hierarchies. Rather than glossing over the inevitable contradictions, we have tried to approach them openly, slowing down the collective decision-making processes, and leaving space for open dialogue, to foster solidarity that allows any tensions to become spaces for mutual learning and collective growth.


[1] need to check in: such as xpub, hackers and designers, ATHOS, Varia, OSP and a list of people and communities
In the article by Shukaitis and Figiel, these tensions are characterised as a question of who has access to resources and the reliance on forms of free labour in cultural work,<ref>Shukaitis & Figiel</ref> although it should be noted that they are mindful not to reduce everything to the question of financial remuneration. Mirroring what commonly takes place in the arts, they refer to how unseen and unpaid labour is central to academic publishing, in particular we can refer to the peer review process, and how particular kinds of labour are valorised over others.<ref>Shukaitis and Figiel cite Kathleen Fitzpatrick's <i>Planned Obsolescence: Publishing, Technology, and the Future of the Academy</i> (New York: New York University Press, 2011). On the related issue of unpaid female labour, see Silvia Federici, <i>Revolution at Point Zero: Housework, Reproduction, and Feminist Struggle</i> (Oakland: PM Press, 2012).</ref> Careful consideration must be given to the divisions of labour in publishing, with sensitivity to how roles and subject positions are shaped by intersectional structures of race, gender, class, and other forms of oppression.


[2] here can add open humanities press - liquid series, data browser e.g volumetric regimes wiki to print, and MIT Press pubpub
This attentiveness to the social and material relations of publishing — as a means of establishing new social relations and engaging critically with infrastructure — further resonates with what Fred Moten and Stefano Harney have described as the "logisticality of the undercommons".<ref>Stefano Harney & Fred Moten, <i>The Undercommons: Fugitive Planning & Black Study</i> (Wivenhoe/New York/Port Watson: Minor Compositions, 2013).</ref> In <i>The Undercommons</i>, they refer to how logistics — the invisible infrastructures that move people, goods, and information — are central to how institutions function under global capitalism. The undercommons refers to spaces or modes of being that exist outside of formal institutions like the university or the state. Although we cannot claim to be part of the undercommons, we learn from its ways of knowing, relating, and organising that don't reproduce existing power structures. This also resonates with David Graeber's rejection of academic elitism and instead embraces lived experience and collective imagination.<ref>Thanks to Marloes de Valk for reminding us of this reference. See David Graeber, <i>Fragments of an Anarchist Anthropology</i> (Prickly Paradigm Press, 2004).</ref> Like Jack Halberstam’s articulation of "low theory" in <i>The Queer Art of Failure</i>, this a way to rethink failure and engage theory from the margins, rather than from rigid and legitimated systems of knowledge often published in academic journals.<ref>Jack Halberstam, <i>The Queer Art of Failure</i> (Duke University Press, 2011).</ref> These ideas help us to reflect on how to share resources, how to organise together, and how to circulate our ideas, without reproducing the structures of power-knowledge associated with academia publishing.


++++Bibilography+++
<h4> Minor publishing </h4>


- Mathias Kling 2005, Free software and open source: The freedom debate and its consequences, first monday: https://firstmonday.org/ojs/index.php/fm/article/view/1211
As the publisher of Harney and Moten's work, and this book, Minor Compositions follows such an approach. Its naming resonates here too, alluding to Gilles Deleuze & Félix Guattari's book on Kafka, the subtitle of which is "Towards a Minor Literature."<ref>Gilles Deleuze & Félix Guattari, <i>Kafka: Toward a Minor Literature</i> [1975], trans. Dana Polan (Minneapolis, MN: University of Minnesota Press, 1986).</ref> As mentioned above, we previously used this reference for our 'minor tech' workshop and followed the three main characteristics identified in Deleuze and Guattari's essay, namely deterritorialization, political immediacy, and collective value.<ref>See Editorial satatement of <i>A Peer-Reviewed Journal About Minor Tech</i> 12 (1) (2023), https://aprja.net//issue/view/10332.</ref> As well as exploring our shared interests and understanding of minor tech in terms of subject matter, we sought to implement these operational principles in practice. This maps onto our book project well and its insistence on small scale production, as well as the use of the ServPub infrastructure to prepare the publication and to challenge some of the production models of journals and conference proceedings.


- Mansoux, Aymeric and de Val, Marloes. 2008. Floss + Art. Poitiers: GOTO10
The publishing project of Minor Compositions is explained succinctly by Stevphen Shukaitis as deriving "not from a position of ‘producer consciousness’ ('we’re a publisher, we make books') but rather from a position of protagonist consciousness ('we make books because it is part of participating in social movement and struggle')".<ref>"About - Minor Compositions," excerpted from an interview with AK Press, https://www.minorcompositions.info/?page_id=2.</ref> Aside from the allusion to minor literature, the naming aslo makes explicit connection to the post-Marxism of autonomist thinking and practice, building on the notion of collective intelligence, or what Marx referred to, in "Fragment on Machines", as general (or mass) intellect.<ref>"Fragment on Machines" is an infamous passage in Karl Marx, ''Grundrisse: Foundations of the Critique of Political Economy (Rough Draft)'' (Penguin Books in association with New Left Review, 1973), available at https://www.marxists.org/archive/marx/works/1857/grundrisse/.</ref> The idea of general intellect remains a useful concept for us as it describes the coming together of technological expertise and social intellect, or general social knowledge, and recognition that although the introduction of machines under capitalism broadly oppresses workers, they also offer potential liberation from these conditions. The same in the case with infrastructure as we have tried to argue.  


- Daley White 2023: Historical Trends and Growth of OA: https://blog.cabells.com/2023/02/08/strongopen-access-history-20-year-trends-and-projected-future-for-scholarly-publishing-strong/
In the case of publishing, our aim has been to extend its potential beyond its functionary role to make books as fixed objects and generate surplus value for publishers, and instead engage with how thinking with others might establish other social relations. In our interview sessions with the organisers of Open Book Futures (our sponsors), we have identified that working together is a way to learn together, a way to share skills and knowledge, often taken from experience of computational practice and then applied to publishing, trying to think outside of the established conventions of both. This is the case even when the practices of publishing is relatively unknown, as identified by In-grid. Systerserver, on the other hand, build on their experience making zines for technical documentation The combination of our experiences here leads us to speculate on new forms and brings us back to the term 'composition' (or recomposition) inasmuch as it emphasises that power in the form of infrastructure does not transform itself as the result of evolution but from struggles that arise from how labour is technically arranged. Our point is that what we refer to as academic publishing comes with its own set of conventions that tend to go against the grain of radical self-organisation.


- Leigh-Ann et al 2023, The oligopoly’s shift to open access: How the big five academic publishers profit from article processing charges, https://direct.mit.edu/qss/article/4/4/778/118070/The-oligopoly-s-shift-to-open-access-How-the-big
Radical referencing is a good example of this, as a way to address the canon and offering other positions and voices that tend to be left out of the discussion. The book has tried to take this approach seriously, diverting from the reliance on big name academics in recognition that ideas evolve far more organically through conversations and encounters in everyday situations. The last chapter explores this in more detail and it becomes clear that hierarchies of knowledge are reinforced through referencing and the cultural capital attached to certain theorists and theory that comes and goes with academic fashions. In the last chapter, Celia Lury's notion of ‘epistemic infrastructure’ points to how organisational structures shape the processes by which knowledge becomes knowledge.<ref>See Celia Lury, <i>Problem Spaces: How and Why Methodology Matters</i> (John Wiley & Sons, 2020), 3.</ref> Here we are also introduced to Sara Ahmed’s intervention in the politics of referencing in which they choose to exclude white men from citation to somewhat balance the books.<ref>Sara Ahmed, <i>Living a Feminist Life</i> (Durham: Duke University Press, 2016).</ref> If we are to take an intersectional approach here, then clearly there are other exclusions in addition to gender which we need to engage that relate to the broader project of epistemic justice.
 
<h4> Structure of the book </h4>
 
Each chapter unpacks practical steps alongside a discussion of the implications of our approach.
[go on to describe each chapter in detail]<!-- This chapter is already long. Adding more description for each chapter will render it rather tiresome and potentially repetitive. Suggestion: in each section you already have written include where those practices are to be read in more detail in which chapter, like you do beatifully for the radical reference chapter in the minor publishing. -->
<!-- The collectives are mentioned a lot. Would it be useful to have short blurbs on each group and what they did for reference, incase it's confusing? -->
 
<h4> Autonomous publishing </h4>
 
The different groups have tried to identify some of the challenges and opportunities in making a book like this. In our interview sessions they state that working together is a way to express autonomy and choose our dependencies. For instance, we reached out to Tuxic.nl, a company within the extended network of Systerserver, regarding the domain registration (www.servpub.net) because they provide open-source software and hardware solutions. Members of servpub interviewed Jaap Vermaas, the person behind Tuxic.nl, <!-- Is this the written interview Mara (me) and Winnie conducted about system administration role? In any case, lets reference the interview properly in the footnote, when, how, by whom. -->who shared his frustration with the evolving hacker scene, particularly its lack of diversity (2023). He explained that he used to be a regular visitor at hacker festivals but stopped attending. He stated: "Still, 95% is white male and the DIY spirit has been replaced by either a "get rich quick" or "let's work for security services" attitude, which is why I stopped going".<ref>His reflections reveal concerns about the commercialization and the mainstreaming of the hacker ethos, as well as the underrepresentation of marginalized groups within this space, and offers services particularly for NGOs, political action groups and small businesses, supporting a wide range of creative and socially driven projects. It is also worth mentioning that once we confirmed the quote via email, Tuxic.nl promptly registered the domain and setup the configuration, incurring costs on their side — all before receiving any payment. This level of trust reflects their dedication to supporting projects with integrity and confidence.</ref>
 
This relates to the issue of consent according to one of the members of In-grid, and a baseline solidarity about what everyone is working towards and has agreed to, as part of a wider ecology of software development and community. "We're choosing to be reliant on software's open source practices, drawing upon the work of other communities, and in this sense are not autonomous." As such, it seems important to clarify what we mean by autonomy or autonomous publishing in this intentional interdependence, grounded in solidarity. There’s a complex discussion here that we simply don’t have space to rehearse in this book but broadly connects to the idea of artistic autonomy and practices to undermine the kinds of autonomy attached to the formalist discourse of art history.<ref>For an account of the autonomy of art as a social relation, amongst others, see Kim West's <i>The Autonomy of Art Is Ordinary: Notes in Defense of an Idea of Emancipation</i> (Sternberg Press, 2024).</ref> One way to understand this better would turn to the etymology of the term which reveals ‘autos’ as self and ‘nomos’ as law, together suggesting the ability to write your own laws or self-govern. But clearly individuals are not able to do this in isolation from social context, and any laws operate in social context too and as part of broader infrastructures. It is no wonder much contemporary cultural practices are performed by self-organised collectives that both critique and follow institutional structures, managerial and logistical forms. No different is our own nested formation of a collective of collectives. 
 
Making reference to collective struggle and autonomia allows us to draw attention to our understanding of the value of labour in our project as well as subjectivity of the worker.<ref>Autonomia refers to post-Marxist attempts to open up new possibilities for the theory and practice of workers' struggle in the 1970s following the perceived failure of strike action. There's much more to say here, and about the context of Italy, but we perhaps stray from the point of the book. For more on Autonomia, see Sylvère Lotringer and Christian Marazzi, eds., <i>Autonomia: Post-Political Politics</i> (Semiotexte, 2007).</ref> Whereas Capital valorises work, and tries to re-establish the wage-work relation at all costs (even when speaking of house work as unpaid), an autonomist approach politicises work and attempts to undermine spurious hierarchies related to qualifications and different wage levels from full-time employment to casualisation in ways that resonate with the different statuses across our team. This has relevance, especially in the collective formation of collectives where some are waged and others not, some positioned as early career researchers and others with established positions. Who and how we get paid or gift our time, and what motivates this effort is variable and contested. As we have suggested earlier, that's important but not really the point.
 
All the same, an anarchist position is an attempt to dismantle some of the centralised (State-like) structures and replace them with more distributed forms that are self-organised. But this is not to say that power goes away of course. In our various collectives this power relation leads to inevitable feeling of discomfort as our precarities are expressed differently according to the situations in which we find ourselves. Yet when we recognise the system is broken, subject to market forces and extractive logic, Systerserver remind us that repair is possible, along with a sense of justice, other possibilities that are more nurturing of change. We'd like to think that our book is motivated in this way, not to just publish our work to gratify ourselves or develop academic careers or generate surplus value for publishers or Universities, but to exert more autonomy over the publishing process and engage more fully with publishing infrastructures and recognise that they operate under specific conditions that are not immovable. Our aim is to rethink publishing infrastructure and knowledge organization, to contest normalised forms and the politics they support, and to encourage others to do the same.
 
The publication that has emerged from this process reflects ongoing conversations and collective writing sessions between the various communities that have supported the development of our ideas in such a way that we no longer know who thought what, or who wrote this sentence when reading later. No matter. The book is a by-product of these lived relations, open to ongoing transformation and the creation of differences, and operating across shifting modes of knowing and becoming. 


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

Latest revision as of 16:46, 5 December 2025

It should be Chapter 1: Being Book

Pad for working https://ctp.cc.au.dk/pad/p/servpub_methods

Collectivities and Working Methods

<unicode> ͚  ཀྵ 書 📖</unicode>

What does it mean to publish? Put simply, publishing means making something public (from the Latin publicare, ‘make public’) but there’s a lot more at stake, not simply concerning what we publish and for whom, but how we publish. It is inherently a social and political process, and builds on wider infrastructures that involve communities and publics, and as such requires reflexive thinking about the socio-technical systems we use to facilitate production and distribution, including the choice of specific tools and devices. In other words, publishing entails understanding the wider political-economic forces, structures and infrastructures that shape it as a practice and cultural form.

This book is an intervention into these concerns, emerging out of a particular history and experimental practice often associated with collective struggle.[1] It is shaped by the collaborative efforts of various collectives involved in experiemntal publishing, operating both within and beyond academic contexts (and hopefully serving to undermine the distinction between them), all invested in the process of how to publish outside of the mainstream commercial and institutional norms.[2] So-called "predatory publishing" has become the default business model for much academic publishing, designed to lure prospective and career-minded researchers into a restrictive model, that profits from the payment of fees for low quality services.[3] For the most part, academics are unthinkingly complicit, compelled by a research culture that values metrics and demands productivity above all else, and tend not to consider the means of publishing as intimately connected to the argument of their papers. As a result there's often a disjunction between form and content.

Public-ation

Despite its apparent recuperation by the mainstream, the ethics of Free/Libre and Open Source Software (FLOSS) still provides a foundation for our approach, as it places emphasis on the freedom to study, modify and share information.[4] These remain core values for any publishing project that wants to maximise its reach and use, as well as enable re-use within a broader and expandible community.[5] What FLOSS and experimental publishing have in common is the need to address the intersection of technology and sociality, and support communities to constitute themselves as publics not simply in terms of the ability to speak and act in public, but through being able to construct their own platforms, what Christopher M. Kelty has referred to as a "recursive public."[6]

For the most part, distribution of academic publications is still largely organised behind pay-walls and through reputation or prestige economies, dominated by major commercial publishers in the Global North.[7] When open access is adopted, for the most part it remains controlled by a select few companies that operate oligopolistic structures to protect their profit margins and positions in the markeplace.[8] As such it is not suprising to realise that the widespread adoption of open access principles in academic publishing, once intended to democratize knowledge, have become a new profit engine for publishers. In these hands, open access provides as a smokescreen for business as usual, much like greenwashing for the environment.

This book is an attempt to draw some red lines here concerning the historical and material conditions for their production and distribution, while offering an alternative model -- and one that is less extractive in terms of resources and labour power. Our approach is grounded in collective working practices and shared values that push back against dominant big tech infrastructures and the drive toward seamless interfaces and scale-up efficiency. To repeat, our concern lies in the disjunction between the critical rigour of academic texts and the use of conventional modes through which they are produced that lack criticality. By criticality, we mean to go beyond a criticism of conventional publishing and to further acknowledge the ways in which we are implicated at all levels in the choices we make when we engage with publishing practices. This includes not only the tools we use -- to design, write, review and edit -- but also the broader infrastructures such as the platforms and servers, within, and through which, they operate. It is this kind of reflexivity that has guided our approach throughout the project: moving beyond the notion of the book as a discrete object and instead conceiving of it as a relational assemblage in which its constituent parts mutually depend on and transform one another in practice.

Infrastructure

We have adopted the phrase "publishing as collective infrastructure" as our title because we want to stress these wider relational properties and how power is distributed, as part of the hidden substrate that includes tools and devices but also logistical operations, shared standards and laws, as Keller Easterling has put it. Infrastructure allows information to invade public space, she argues -- interestingly, just as architecture was killed by the book with the introduction of the Gutenberg printing press.[9] This is why we consider it important to not only expose its workings but also acquire the necessary skills -- both technical and conceptual -- to be able to make infrastructures otherwise.

The argument of Easterling, and others, recognises that infrastructure has become a medium of information and mode of governance, exercised through actions that determine how objects and content are organised and circulated. Susan Leigh Star is another who has also emphasised that "infrastructure is a fundamentally relational concept," operationalised through practices and wider ecologies.[10] Put simply, infrastructures involve "boring things,"[11] and the trick of the tech industry is to make these operations barely noticeable, so in this sense they are ideological as the underlying structures seem natural. The infrastructures of publishing are powerful in this way as they distribute information on the page through words, and at the same time through the wider operating systems on which they are dependent. If we are to reinvent academic publishing, this must occur at every layer and scale -- what we might call a 'full-stack' transformation -- which includes the social and cultural aspects that technology influences and is influenced by. Here we make reference to 'full stack feminism' which calls for a rethinking of how digital systems are developed, applying the principles of intersectional feminism -- itself an infrastructural critique of method -- to critically engage with all layers of implementation.[12]

Backround-foreground

In summary, the book you are reading is a book about publishing a book, a tool for thinking and making one differently, drawing attention to these wider structures and recursions. It sets out to acknowledge and register its own process of coming into being -- as an onto-epistemological object so-to-speak -- and to highlight the interconnectedness of its contents and the multiple processes and forms through which it takes shape in becoming book.

Given these concerns, we ccontinue to find it perverse that academic books are still predominantly written by individual authors and distributed by publishers as fixed objects in time and space. It would surely be more in keeping with the affordances of the technology to stress collaborative authorship, community peer review and annotation, as well as other messy realities of production. This would allow for the development of versions over time, as Janneke Adema has argued, "an opportunity to reflect critically on the way the research and publishing workflow is currently (teleologically and hierarchically) set up, and how it has been fully integrated within certain institutional and commercial settings."[13] An iterative approach would suggest other possibilities that draw publishing and research processes closer together, and within which the divisions of labour between writers, editors, designers, software developers could become entangled in non-linear workflows and interactions. Through the sharing of resources and their open modification, generative possibilities emerge that break out of protectionist conventions perpetuated by tired academic procedures (and tired academics) that assume knowledge to be produced in standardised ways, and imparted through the reductive logic of input/output.

Our approach is clearly not new. It draws on multiple influences, from the radical publishing tradition of small independent presses and artist books as well as other experimental attempts to make interventions into research cultures and pedagogy. We might immodestly point to some of our own previous work in this connection, including Aesthetic Programming, a book about software, imagined as if software.[14] It draws upon the practice of forking in which programmers are able to make changes and submit merge requests to incorporate updates to software using version control repositories (such as GitLab). The book explores how the concept of forking can inspire new practices of writing by offering all contents as an open resource, with an invitation for other researchers to fork a copy and customise their own versions of the book, with new references and reflections, even additional chapters, all aspects open for modification and re-use.[15] By encouraging new versions to be produced by others in this way, we aim to challenge publishing conventions and exploit the technical affordances of the technologies we use that encourage collectivity. Clearly wider infrastructures are especially important to understand how alternatives emerge from the need to configure and maintain more sustainable and equitable networks for publishing, and that remain sensitive to all that contribute to the shared effort (concerning readers, writers and programmers alike). All this goes against academic conventions that require books to be fixed in time and follow narrow conventions of attribution and copyright.[16]

The collaborative workshops co-organised by the Digital Aesthetics Research Center at Aarhus University and transmediale festival for art and digital culture based in Berlin provide a further example of this in practice. Since 2012, these workshops have attempted to make interventions into how academic research is conducted and disseminated.[17] Those taking part are encouraged to not only engage with their research questions and offer critical feedback to each other through an embodied peer review process, but also to engage with the conditions for producing and disseminating their research as a shared intellectual resource.

The Minor Tech workshop from 2023 made these concerns explicit, setting out to address alternatives to big (or major) tech by drawing attention to the institutional hosting, both at the in-person event and online.[18] In this way, the publishing platform developed for the workshop can be understood to have a pedagogic function in itself, allowing for thinking and learning to take place as part of the wider socio-technical infrastructure. Building on this, the subsequent workshop Content/Form further developed this approach, working in collaboration with Systerserver and In-grid. Using the ServPub project as a technical infrastructure on which to ground the pedagogy, we were able to exempify how the tools and practices used for our writing shape it, whether acknowledged or not.[19] The process of setting up the server is described in subsequent chapters, but for now it is important to register how its presence in the same space as the workshop helped to place emphasis on the material conditions for collective working and autonomous publishing -- for publishing as collective infrastructure.

Self-hosted servers

The server needs be set up but also requires care, but rather differently to the ways care has become weaponised in mainstream institutions. As Nishant Shah describes, care has become something that institutions purport to do, with endless policies and promises for well-being and support, but without threatening the structures of power that produce the need in the first place.[20]In our case, we would argue for something more along the lines of "pirate care," in which the coming together of care and technology can question "the ideology of private property, work and metrics."[21] Care in this sense comes closer to the work of feminist scholars such as Maria Puig de La Bellacasa who draws attention to relations that "maintain and repair a world so that humans and non-humans can live in it as well as possible in a complex life-sustaining web."[22]

Feminist servers follow these principles, wherein practices of care and maintenance are understood as acts of collective responsibility. It is with this in mind that we have tried to engage more fully with affective infrastructures that are underpinned by intersectional and feminist methodologies. Systerserver, for instance, operate as a feminist, queer, and anti-patriarchal network, which prioritises care and maintenance, offers services and hosting to its community, and acts as a space to learn system administration skills and inspire others to do the same.[23] Our further inspiration is "A Transversal Network of Feminist Servers" (ATNOFS), a project formed around intersectional, feminist, ecological servers whose communities exchanged ideas and practices through a series of meetings in 2022.[24] The publication that emerged from these meetings was released in a manner that reflects the collective ethos of the project. A limited number of copies were printed and distributed through the networks of participants and designed to be easily printed and assembled at home, thus reinforcing commitment to collaboration and access. More on this project is included in the following chapter. For now, it is worth adding that the project responded to the need for federated support for self-hosted and self-organised computational infrastructures across Europe although the UK was notably absent. Indeed part of our motivation for ServPub is to address the perceived need to develop a parallel community of shared interest around experimental publishing and affective infrastructures in London.[25]

Socio-technical forms

We hope it is clear by now that our intention for this publication is not to valorize feminist servers or free and open-source culture as such but to stress how technological and social forms come together to expose power relations. This comes close to the position that Stevphen Shukaitis and Joanna Figiel have elaborated in "Publishing to Find Comrades," a phrase which they borrow from the Surrealist André Breton. Their emphasis is not to publish pre-existing knowledge and communicate this to a fixed reader but to work towards developing the appropriate social conditions for the co-production of meaning and action.

The openness of open publishing is thus not to be found with the properties of digital tools and methods, whether new or otherwise, but in how those tools are taken up and utilized within various social milieus. [...]

Thus, publishing is not something that occurs at the end of a process of thought, a bringing forth of artistic and intellectual labor, but rather establishes a social process where this may further develop and unfold.

In this sense, the organization of the productive process of publishing could itself be thought to be as important as what is produced.

[26]

We agree. The process of making a book is not merely a way to communicate the contents but to invent organisational forms with wider social and political purpose. Can something similar be said of the ServPub project and our book? Maybe. Attention to infrastructure is significant here, as well as the affordances of the tools we use, in allowing for reflection on divisions of labour, the conditions of production, the dependencies of support networks, and sustainability of our practice as academics and/or cultural workers. Moreover, the political impulse for our work draws upon the view that the tools of oppression offer limited scope to examine that oppression and their rejection is necessary for genuine change in publishing practices. Here we paraphrase Audre Lorde of course.[27]

Caption: A screenshot of Etherpad
Caption: A screenshot of Etherpad

As for the specific tools for this book, we have used Etherpad for drafting our texts, a free and open source writing software which allows us to collaborate and write together asynchronously. As an alternative to established proprietary writing platforms that harvest data, a pad allows for a different paradigm for the organisation and development of projects and other related research tasks. To explore the public nature of writing, Etherpad makes the writing process visible, as anyone of us can see how the text evolves through additions, deletions, modifications, and reordering. One of its features is the timeline function (called Timeslider in the top menu bar), which allows users to track version history and re-enact the process performatively. This transparency over the sociality and temporality of form not only shapes interaction among writers but also potentially engages unknown readers in accessing the process, before and after the book itself.[28] Another feature of a pad is that authors are identifiable through colours, usernames are optional and writing is anonymous by default. Martino Morandi has described this as "organizational writing," quoting Michel Callon’s description of "writing devices that put organization-in-action into words," and how writing in this way collectively "involves conflict and leads to intense negotiation; and such collective work is never concluded".[29]

Logistical operations

Apart from writing the book, and drawing attention to its organisational form, it is important to register that we are collectively involved in all aspects of its making. The production process -- including writing and peer review, copyediting and design -- is reflected in the choice of other tools and platforms that we are using as well as the constitution of the collectives involved. Using MediaWiki software and web-to-print layout techniques, ServPub is an attempt to circumvent standard academic workflows and instead conflate traditional roles of writers, editors, designers, developers alongside the affordances of the technologies. To put it plainly, this means rejecting proprietary software such as Abode Creative Cloud and designing by other means, as indicated by the ironic naming of Creative Crowds (CC) as part of our working group.[30] Indeed, the distributed nature of our endeavour is reflected in the combinations of those involved, directly and indirectly, across the different entities involved who provide the necessary skills and support for the project's realisation. This includes building on the work of others involved in the development of the tools such as the various iterations of 'wiki-to-print' and 'wiki2print', not least involving CC, which In-grid have further adapted as 'wiki4print' for this book.[31] The book object is just one output of a complex set of interactions and exchanges of knowledge across time and space.

As mentioned, the divisions of labour are somewhat collapsed, and the activities that make up the publishing pipeline are reinvented in relation to the various tools and the platforms they support. This is inevitably not without its challenges, especially when such a diverse group of people are involved, each with their own experiences, positionalities, life and employment situations. One of the many challenges of a project like this has been to account for these differences, which include the complexities of unpaid and paid labour. We have tried to address or acknowledge potential 'discomfort' associated with the project throughout our work together in our meetings.[32] Perhaps this is particularly important when engaging grassroots collectives who often remain suspicious of academia as a zone of privilege without recognising other factors such as cultural differences and rising precarity in the sector.

Discomfort is important to the praxis of ServPub, emerging as we navigated complex questions related to reputation hierarchies and accreditation, as well as the nature of the institutional infrastructures that support the work. Challenges include uneven access to resources, disparities in institutional support, and the ongoing negotiation of additional labour which reveals some of the power struggles individuals/collectives face within their own particular situations, even as they remain committed to the project. All embrace feminist methodologies, but this commitment is not without differences of interpretation. Language itself also acts as a destabilizing factor, as not all contributors are native English speakers, leading to subtle miscommunication and moments that demand continuous exercise of trust, open communication and negotiation of meaning. Consensus-building within this diverse project entails negotiating differing expectations and end-goals, from contributing to community and personal research interests to advancing academic careers. Issues are further complicated by the politics of documentation and attribution, as contributors strive to fairly represent both individual and collective labour while remaining vigilant against replicating extractive academic norms and hierarchies. Rather than glossing over the inevitable contradictions, we have tried to approach them openly, slowing down the collective decision-making processes, and leaving space for open dialogue, to foster solidarity that allows any tensions to become spaces for mutual learning and collective growth.

In the article by Shukaitis and Figiel, these tensions are characterised as a question of who has access to resources and the reliance on forms of free labour in cultural work,[33] although it should be noted that they are mindful not to reduce everything to the question of financial remuneration. Mirroring what commonly takes place in the arts, they refer to how unseen and unpaid labour is central to academic publishing, in particular we can refer to the peer review process, and how particular kinds of labour are valorised over others.[34] Careful consideration must be given to the divisions of labour in publishing, with sensitivity to how roles and subject positions are shaped by intersectional structures of race, gender, class, and other forms of oppression.

This attentiveness to the social and material relations of publishing — as a means of establishing new social relations and engaging critically with infrastructure — further resonates with what Fred Moten and Stefano Harney have described as the "logisticality of the undercommons".[35] In The Undercommons, they refer to how logistics — the invisible infrastructures that move people, goods, and information — are central to how institutions function under global capitalism. The undercommons refers to spaces or modes of being that exist outside of formal institutions like the university or the state. Although we cannot claim to be part of the undercommons, we learn from its ways of knowing, relating, and organising that don't reproduce existing power structures. This also resonates with David Graeber's rejection of academic elitism and instead embraces lived experience and collective imagination.[36] Like Jack Halberstam’s articulation of "low theory" in The Queer Art of Failure, this a way to rethink failure and engage theory from the margins, rather than from rigid and legitimated systems of knowledge often published in academic journals.[37] These ideas help us to reflect on how to share resources, how to organise together, and how to circulate our ideas, without reproducing the structures of power-knowledge associated with academia publishing.

Minor publishing

As the publisher of Harney and Moten's work, and this book, Minor Compositions follows such an approach. Its naming resonates here too, alluding to Gilles Deleuze & Félix Guattari's book on Kafka, the subtitle of which is "Towards a Minor Literature."[38] As mentioned above, we previously used this reference for our 'minor tech' workshop and followed the three main characteristics identified in Deleuze and Guattari's essay, namely deterritorialization, political immediacy, and collective value.[39] As well as exploring our shared interests and understanding of minor tech in terms of subject matter, we sought to implement these operational principles in practice. This maps onto our book project well and its insistence on small scale production, as well as the use of the ServPub infrastructure to prepare the publication and to challenge some of the production models of journals and conference proceedings.

The publishing project of Minor Compositions is explained succinctly by Stevphen Shukaitis as deriving "not from a position of ‘producer consciousness’ ('we’re a publisher, we make books') but rather from a position of protagonist consciousness ('we make books because it is part of participating in social movement and struggle')".[40] Aside from the allusion to minor literature, the naming aslo makes explicit connection to the post-Marxism of autonomist thinking and practice, building on the notion of collective intelligence, or what Marx referred to, in "Fragment on Machines", as general (or mass) intellect.[41] The idea of general intellect remains a useful concept for us as it describes the coming together of technological expertise and social intellect, or general social knowledge, and recognition that although the introduction of machines under capitalism broadly oppresses workers, they also offer potential liberation from these conditions. The same in the case with infrastructure as we have tried to argue.

In the case of publishing, our aim has been to extend its potential beyond its functionary role to make books as fixed objects and generate surplus value for publishers, and instead engage with how thinking with others might establish other social relations. In our interview sessions with the organisers of Open Book Futures (our sponsors), we have identified that working together is a way to learn together, a way to share skills and knowledge, often taken from experience of computational practice and then applied to publishing, trying to think outside of the established conventions of both. This is the case even when the practices of publishing is relatively unknown, as identified by In-grid. Systerserver, on the other hand, build on their experience making zines for technical documentation The combination of our experiences here leads us to speculate on new forms and brings us back to the term 'composition' (or recomposition) inasmuch as it emphasises that power in the form of infrastructure does not transform itself as the result of evolution but from struggles that arise from how labour is technically arranged. Our point is that what we refer to as academic publishing comes with its own set of conventions that tend to go against the grain of radical self-organisation.

Radical referencing is a good example of this, as a way to address the canon and offering other positions and voices that tend to be left out of the discussion. The book has tried to take this approach seriously, diverting from the reliance on big name academics in recognition that ideas evolve far more organically through conversations and encounters in everyday situations. The last chapter explores this in more detail and it becomes clear that hierarchies of knowledge are reinforced through referencing and the cultural capital attached to certain theorists and theory that comes and goes with academic fashions. In the last chapter, Celia Lury's notion of ‘epistemic infrastructure’ points to how organisational structures shape the processes by which knowledge becomes knowledge.[42] Here we are also introduced to Sara Ahmed’s intervention in the politics of referencing in which they choose to exclude white men from citation to somewhat balance the books.[43] If we are to take an intersectional approach here, then clearly there are other exclusions in addition to gender which we need to engage that relate to the broader project of epistemic justice.

Structure of the book

Each chapter unpacks practical steps alongside a discussion of the implications of our approach.

[go on to describe each chapter in detail]

Autonomous publishing

The different groups have tried to identify some of the challenges and opportunities in making a book like this. In our interview sessions they state that working together is a way to express autonomy and choose our dependencies. For instance, we reached out to Tuxic.nl, a company within the extended network of Systerserver, regarding the domain registration (www.servpub.net) because they provide open-source software and hardware solutions. Members of servpub interviewed Jaap Vermaas, the person behind Tuxic.nl, who shared his frustration with the evolving hacker scene, particularly its lack of diversity (2023). He explained that he used to be a regular visitor at hacker festivals but stopped attending. He stated: "Still, 95% is white male and the DIY spirit has been replaced by either a "get rich quick" or "let's work for security services" attitude, which is why I stopped going".[44]

This relates to the issue of consent according to one of the members of In-grid, and a baseline solidarity about what everyone is working towards and has agreed to, as part of a wider ecology of software development and community. "We're choosing to be reliant on software's open source practices, drawing upon the work of other communities, and in this sense are not autonomous." As such, it seems important to clarify what we mean by autonomy or autonomous publishing in this intentional interdependence, grounded in solidarity. There’s a complex discussion here that we simply don’t have space to rehearse in this book but broadly connects to the idea of artistic autonomy and practices to undermine the kinds of autonomy attached to the formalist discourse of art history.[45] One way to understand this better would turn to the etymology of the term which reveals ‘autos’ as self and ‘nomos’ as law, together suggesting the ability to write your own laws or self-govern. But clearly individuals are not able to do this in isolation from social context, and any laws operate in social context too and as part of broader infrastructures. It is no wonder much contemporary cultural practices are performed by self-organised collectives that both critique and follow institutional structures, managerial and logistical forms. No different is our own nested formation of a collective of collectives.

Making reference to collective struggle and autonomia allows us to draw attention to our understanding of the value of labour in our project as well as subjectivity of the worker.[46] Whereas Capital valorises work, and tries to re-establish the wage-work relation at all costs (even when speaking of house work as unpaid), an autonomist approach politicises work and attempts to undermine spurious hierarchies related to qualifications and different wage levels from full-time employment to casualisation in ways that resonate with the different statuses across our team. This has relevance, especially in the collective formation of collectives where some are waged and others not, some positioned as early career researchers and others with established positions. Who and how we get paid or gift our time, and what motivates this effort is variable and contested. As we have suggested earlier, that's important but not really the point.

All the same, an anarchist position is an attempt to dismantle some of the centralised (State-like) structures and replace them with more distributed forms that are self-organised. But this is not to say that power goes away of course. In our various collectives this power relation leads to inevitable feeling of discomfort as our precarities are expressed differently according to the situations in which we find ourselves. Yet when we recognise the system is broken, subject to market forces and extractive logic, Systerserver remind us that repair is possible, along with a sense of justice, other possibilities that are more nurturing of change. We'd like to think that our book is motivated in this way, not to just publish our work to gratify ourselves or develop academic careers or generate surplus value for publishers or Universities, but to exert more autonomy over the publishing process and engage more fully with publishing infrastructures and recognise that they operate under specific conditions that are not immovable. Our aim is to rethink publishing infrastructure and knowledge organization, to contest normalised forms and the politics they support, and to encourage others to do the same.

The publication that has emerged from this process reflects ongoing conversations and collective writing sessions between the various communities that have supported the development of our ideas in such a way that we no longer know who thought what, or who wrote this sentence when reading later. No matter. The book is a by-product of these lived relations, open to ongoing transformation and the creation of differences, and operating across shifting modes of knowing and becoming.


index.php?title=Category:ServPub

  1. Janneke Adema, "Experimental Publishing as Collective Struggle: Providing Imaginaries for Posthumanist Knowledge Production," Culture Machine 23 (2024), https://culturemachine.net/vol-23-publishing-after-progress/adema-experimental-publishing-collective-struggle/.
  2. Influential here is the Experimental Publishing masters course (XPUB) at Piet Zwart Institute in Rotterdam, where students, guests and staff make 'publications' that extend beyond print media. See: https://www.pzwart.nl/experimental-publishing/special-issues/. Amongst others, two grassroot collectives based in the Netherlands are significant to mention, Varia and Hackers & Designers, and in Belgium, Constant and Open Source Publishing. All have focused on developing and sharing free and open source publishing tools, including web-to-print techniques. See, for example https://varia.zone/en/tag/publishing.html and https://www.hackersanddesigners.nl/experimental-publishing-walk-in-workshop-ndsm-open.html. The colophon offers a more comprehensive list of the geneology of these publishing practices and tools.
  3. Jeffrey Beall, "Predatory publishers are corrupting open access", Nature 489, 179 (2012): https://doi.org/10.1038/489179a.
  4. Mathias Klang, "Free software and open source: The freedom debate and its consequences," First Monday (2005): https://firstmonday.org/ojs/index.php/fm/article/view/1211.
  5. Lucie Kolb, "Sharing Knowledge in the Arts: Creating the Publics-We-Need," Culture Machine 23 (2024): https://culturemachine.net/vol-23-publishing-after-progress/kolb-sharingknowledge-in-the-arts/.
  6. To explain more fully, "A recursive public is a public that is vitally concerned with the material and practical maintenance and modification of the technical, legal, practical, and conceptual means of its own existence as a public; it is a collective independent of other forms of constituted power and is capable of speaking to existing forms of power through the production of actually existing alternatives." Christopher M. Kelty, Two Bits: The Cultural Significance of Free Software (Duke University Press, 2020), 3; available as free download at https://twobits.net/pub/Kelty-TwoBits.pdf.
  7. The “big four” (Elsevier, Springer Nature, Wiley, Taylor & Francis) earned over $7.1 billion in 2024, maintaining profit margins of around 30–37%. Whereas researchers work for free, spending over 130 million unpaid hours annually on peer review alone. In addition, commercial publishers dominate not only journals but also evaluation systems (Scopus, Clarivate, COPE), reproducing knowledge-power in the Global North and marginalizing other community-led and regional models. See Fernanda Beigel, Dan Brockington, Paolo Crosetto, Gemma Derrick, Aileen Fyfe, Pablo Gomez Barreiro, Mark A. Hanson, Stefanie Haustein, Vincent Larivière, Christine Noe, Stephen Pinfield, James Wilsdon, "The Drain of Scientific Publishing," 2005: arXiv:2511.04820, https://doi.org/10.48550/arXiv.2511.04820.
  8. Leigh-Ann Butler, Lisa Matthias, Marc-André Simard, Philippe Mongeon, Stefanie Haustein, "The oligopoly’s shift to open access: How the big five academic publishers profit from article processing charges," Quantitative Science Studies (2023) 4 (4): 778–799. https://doi.org/10.1162/qss_a_00272.
  9. Keller Easterling, Extrastatecraft: The Power of Infrastructure Space (London: Verso, 2014). Before print, buildings such as cathedrals conveyed stories and cultural memory. With the Gutenberg press and mass literacy, the production and distribution of knowledge moved from architecture to print.
  10. Susan Leigh Star & Karen Ruhleder, Steps Toward an Ecology of Infrastructure: Design and Access for Large Information Spaces, Information Systems Research 7(1) (1996), 111-113, https://doi.org/10.1287/isre.7.1.111. Thanks to Rachel Falconer for reminded us of this reference.
  11. Susan Leigh Star. "The Ethnography of Infrastructure," American Behavioral Scientist 43(3) (2016): 377–391. doi: 10.1177/00027649921955326.
  12. See: https://fullstackfeminismdh.pubpub.org/pub/iqztanz3/release/4?readingCollection=ee61d2f6
  13. The Community-led Open Publication Infrastructures for Monographs research project, of which Adema has been part, is an excellent resource for this discussion, including the section "Versioning Books" from which the quote is taken, https://compendium.copim.ac.uk/. Also see Janneke Adema’s "Versioning and Iterative Publishing" (2021), https://commonplace.knowledgefutures.org/pub/5391oku3/release/1 and "The Processual Book How Can We Move Beyond the Printed Codex?" (2022), LSE blog, https://blogs.lse.ac.uk/lsereviewofbooks/2022/01/21/the-processual-book-how-can-we-move-beyond-the-printed-codex/; Janneke Adema and Rebekka Kiesewetter, "Experimental Book Publishing: Reinventing Editorial Workflows and Engaging Communities" (2022), https://commonplace.knowledgefutures.org/pub/8cj33owo/release/1.
  14. Winnie Soon & Geoff Cox, Aesthetic Programming (London: Open Humanities Press, 2021). Link to downloadable PDF and online version can be found at https://aesthetic-programming.net/; and Git repository at https://gitlab.com/aesthetic-programming/book. See also Winnie Soon, "Writing a Book As If Writing a Piece of Software", in A Peer-reviewed Newspaper about Minor Tech 12 (1) (2023).
  15. In response to this invitation to fork the book, Mark Marino and Sarah Ciston added chapter 8 and a half (sandwiched between chapters 8 and 9) to address a perceived gap in the discussion of chatbots. Their reflections on this can be found in an article, see Sarah Ciston & Mark C. Marino, "How to Fork a Book: The Radical Transformation of Publishing," Medium (2021). https://markcmarino.medium.com/how-to-fork-a-book-the-radical-transformation-of-publishing-3e1f4a39a66c. In addition, we have approached the book’s translation into Mandarin as a fork. See Shih-yu Hsu, Winnie Soon, Tzu-Tung Lee, Chia-Lin Lee​​, Geoff Cox, "Collective Translation as Forking (分岔)," Journal of Electronic Publishing 27 (1): 195-221. https://doi.org/10.3998/jep.5377(2024).
  16. Although cultural differences should be acknowledged, see for instance: Fei-Hsien Wang, Pirates and Publishers: A Social History of Copyright in Modern China (Princeton University Press, 2019). Thanks to our collaborator Chia-Lin Lee at Zimu Culture for this reference.
  17. Details of the workshops and associated publications can be found at https://aprja.net/. To explain in brief, an annual open call is released based loosely on the transmediale festival theme of that year, targeting diverse researchers but especially eraly career. Accepted participants are asked to share a short essay of 1000 words, upload it to a wiki, and respond online using a linked pad, as well as attend an in-person workshop, at which they offer peer feedback and then on this basis reduce their texts to 500 words for publication in a "newspaper" to be presented and launched at the festival. Lastly, the participants are invited to submit full-length articles of approximately 5000 words for the online open access journal APRJA, https://aprja.net/. The down/up scaling of the text is part of the pedagogical conceit, condensing the argument to identify key arguments and then expanding it once more to make substantive claims.
  18. The newspaper and journal publications in 2023 and 2024 were produced iteratively in collaboration with Simon Browne and Manetta Berends using wiki-to-print tools, based on MediaWiki software, Paged Media CSS techniques and the JavaScript library Paged.js, which renders the PDF, much like how this book has been produced. As mentioned, an account of the development of these tools, developed through an iteractive process and by differeht communities, is included in the colophon. This includes, for example, wiki-to-print development and F/LOSS redesign by Manetta Berends for Volumetric Regimes edited by Possible Bodies (Jara Rocha and Femke Snelting) (DATA browser/Open Humanities Press, 2022), available for free download at http://www.data-browser.net/db08.html.
  19. More details on the Content/Form workshop and the newspaper publication can be found at https://wiki4print.servpub.net/index.php?title=Content-Form. The research workshop was organised by SHAPE Digital Citizenship & Digital Aesthetics Research Center, Aarhus University, and the Centre for the Study of the Networked Image (CSNI), London South Bank University, with transmediale festival for digital art & culture, Berlin.
  20. See Nishant Shah, "Weaponization of Care," nachtkritik.de, 2021, https://nachtkritik.de/recherche-debatte/nishant-shah-on-how-art-and-culture-institutions-refuse-dismantling-their-structures-of-power.
  21. See "The Pirate Care Project", https://pirate.care/pages/concept/.
  22. We steal this quote from The Pirate Care Project, see Maria Puig de La Bellacasa, Matters of Care: Speculative ethics in more than human worlds (University of Minnesota Press 2017), 97.
  23. See https://systerserver.net/
  24. "A Traversal Network of Feminist Servers", available at https://atnofs.constantvzw.org/. The ATNOFS project drew upon "Are You Being Served? A Feminist Server Manifesto 0.01," available at htps://areyoubeingserved.constantvzw.org/Summit_aterlife.xhtm. For a fuller elaboration of Feminist servers, produced as a collective outcome of a Constant meeting in Brussels, December 2013, see https://esc.mur.at/en/werk/feminist-server. Marloes de Valk contributed to the ATNOFS publication and has also written about this extensively in her PhD thesis, The Image at the End of the World: Communities of practice redefining technology on a damaged Earth (CSNI, London South Bank University, 2025).
  25. Groups involved in ATNOFS were from The Netherlands (Varia, LURK), Romania (hypha), Austria (esc mkl), Greece (Feminist Hack Meetings), and Belgium (Constant). We saw similar initiatives elsewhere, but not in the UK at this time, although in the past we might point to the ongoing efforts of James Stevens at Backspace in 1996 and ongoing with SPC in Deptford, as well as the Art Servers Unlimited event in 2001, organised by Manu Luksch and Armin Medosch. See Davide Bevilacqua, ed. Artists Running Data Centers (servus.at, 2024), 11. https://publications.servus.at/2024-Artists-Running-Data-Centers/ArtistsRunningDataCenters-servus-at_2024.pdf.
  26. Stevphen Shukaitis & Joanna Figiel, "Publishing to Find Comrades: Constructions of Temporality and Solidarity in Autonomous Print Cultures," Lateral 8.2 (2019), https://doi.org/10.25158/L8.2.3. For another use of the phrase, see Eva Weinmayr, "One publishes to find comrades," in Publishing Manifestos: an international anthology from artists and writers, edited by Michalis Pichler (The MIT Press, 2018).
  27. Audre Lorde, The Master’s Tools Will Never Dismantle the Master’s House (1979), available at https://theanarchistlibrary.org/library/audre-lorde-the-master-s-tools-will-never-dismantle-the-master-s-house.
  28. We might say it turns readers into writers, following Walter Benjamin in his 1934 essay "The Author as Producer,", in Walter Benjamin: Selected Writings: Volume 2, Part 2, 1931-34 (Belnap Press of Harvard University Press, 2005), 777. "What matters, therefore, is the exemplary character of production, which is able, first, to induce other producers to produce, and, second, to put an improved apparatus at their disposal. And this apparatus is better, the more consumers it is able to turn into producers — that is, readers or spectators into collaborators."
  29. Martino Morandi, "Constant Padology," MARCH, January 2023, https://march.international/constant-padology/. The source Morandi is drawing upon is Michel Callon’s "Writing and (Re)writing Devices as Tools for Managing Complexity," in Complexities, John Law & Annemarie Mol (eds.) (Durham, NC: Duke University Press, 2002), 203.
  30. More on Creative Crowds can be found at https://cc.vvvvvvaria.org/wiki/Main_Page. They describe themselves as engaged with "collective research on the entanglements of web-to-print/experimental publishing/design practices with tools, cultures and infrastructure." Although they run a server, they stress they are not a service but participate in the projects they support.
  31. Again, see the colophon for further details of versions.
  32. See, for example, the blog post "The (Im)possibility of Non-Extractive Collaboration," https://copim.pubpub.org/pub/pilot-project-documentation-servpub4-non-extractive-collab/release/1, also available as an audio recording.
  33. Shukaitis & Figiel
  34. Shukaitis and Figiel cite Kathleen Fitzpatrick's Planned Obsolescence: Publishing, Technology, and the Future of the Academy (New York: New York University Press, 2011). On the related issue of unpaid female labour, see Silvia Federici, Revolution at Point Zero: Housework, Reproduction, and Feminist Struggle (Oakland: PM Press, 2012).
  35. Stefano Harney & Fred Moten, The Undercommons: Fugitive Planning & Black Study (Wivenhoe/New York/Port Watson: Minor Compositions, 2013).
  36. Thanks to Marloes de Valk for reminding us of this reference. See David Graeber, Fragments of an Anarchist Anthropology (Prickly Paradigm Press, 2004).
  37. Jack Halberstam, The Queer Art of Failure (Duke University Press, 2011).
  38. Gilles Deleuze & Félix Guattari, Kafka: Toward a Minor Literature [1975], trans. Dana Polan (Minneapolis, MN: University of Minnesota Press, 1986).
  39. See Editorial satatement of A Peer-Reviewed Journal About Minor Tech 12 (1) (2023), https://aprja.net//issue/view/10332.
  40. "About - Minor Compositions," excerpted from an interview with AK Press, https://www.minorcompositions.info/?page_id=2.
  41. "Fragment on Machines" is an infamous passage in Karl Marx, Grundrisse: Foundations of the Critique of Political Economy (Rough Draft) (Penguin Books in association with New Left Review, 1973), available at https://www.marxists.org/archive/marx/works/1857/grundrisse/.
  42. See Celia Lury, Problem Spaces: How and Why Methodology Matters (John Wiley & Sons, 2020), 3.
  43. Sara Ahmed, Living a Feminist Life (Durham: Duke University Press, 2016).
  44. His reflections reveal concerns about the commercialization and the mainstreaming of the hacker ethos, as well as the underrepresentation of marginalized groups within this space, and offers services particularly for NGOs, political action groups and small businesses, supporting a wide range of creative and socially driven projects. It is also worth mentioning that once we confirmed the quote via email, Tuxic.nl promptly registered the domain and setup the configuration, incurring costs on their side — all before receiving any payment. This level of trust reflects their dedication to supporting projects with integrity and confidence.
  45. For an account of the autonomy of art as a social relation, amongst others, see Kim West's The Autonomy of Art Is Ordinary: Notes in Defense of an Idea of Emancipation (Sternberg Press, 2024).
  46. Autonomia refers to post-Marxist attempts to open up new possibilities for the theory and practice of workers' struggle in the 1970s following the perceived failure of strike action. There's much more to say here, and about the context of Italy, but we perhaps stray from the point of the book. For more on Autonomia, see Sylvère Lotringer and Christian Marazzi, eds., Autonomia: Post-Political Politics (Semiotexte, 2007).