Pumping pads as files into publishing frameworks!
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

469 lines
35 KiB

<html>
<head>
<script src="/versions.js"></script>
<link href="../stylesheet.css" rel="stylesheet">
<link href="https://pad.vvvvvvaria.org/p/prague-ccld" rel="alternate" title="Etherpad" type="text/html">
<link href="prague-ccld.raw.txt" rel="alternate" title="Plain text" type="text/plain">
<link href="prague-ccld.raw.html" rel="alternate" title="HTML" type="text/html">
<link href="prague-ccld.meta.json" rel="alternate" title="Meta data" type="application/json">
<meta charset="utf-8">
<title>prague-ccld</title>
</head>
<body>Title<br>
<strong>Collective infrastructures</strong>
<br>
<br>
<strong>Talk description</strong>
<br>How can we build an infrastructure together? During this talk, we will focus on the acts of collective infrastructure making that have happened in Varia, namely our homebrewed server running our website, instant messaging service, etherpad, shared calendars, etc. We will contextualize these activities by shedding some light on Varia's collective statement and the shared goals of its members.<br>
<br>Presentation link: <a href="https://demo.codimd.org/Bd20QcfmQ6Kf2jURFG-5uw#" rel="noreferrer noopener">https://demo.codimd.org/Bd20QcfmQ6Kf2jURFG-5uw#</a>
<br>
<a href="https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet" rel="noreferrer noopener">https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet</a>
<br>
<a href="https://cryptpad.fr/slide/#/2/slide/edit/vatu4ev+KvjjAl-xpQf3dIPE/" rel="noreferrer noopener">https://cryptpad.fr/slide/#/2/slide/edit/vatu4ev+KvjjAl-xpQf3dIPE/</a>
<br>
<br>
<strong>Images and diagrams</strong>
<br>
<a href="https://vvvvvvaria.org/~mb/images/varia-digital-collective-infrastructure.png" rel="noreferrer noopener">https://vvvvvvaria.org/~mb/images/varia-digital-collective-infrastructure.png</a>
<br>
<a href="https://vvvvvvaria.org/~mb/images/xmpp-connections-federation.png" rel="noreferrer noopener">https://vvvvvvaria.org/~mb/images/xmpp-connections-federation.png</a>
<br>
<a href="http://varia.zone/archive/varia-server/IMG_4379.jpg" rel="noreferrer noopener">http://varia.zone/archive/varia-server/IMG_4379.jpg</a>
<br>
<a href="http://varia.zone/archive/varia-server/varia-home-red.png" rel="noreferrer noopener">http://varia.zone/archive/varia-server/varia-home-red.png</a>
<br>
<a href="http://varia.zone/archive/varia-server/7e920c7f_Screenshot%20from%202020-03-21%2019-07-20.png" rel="noreferrer noopener">http://varia.zone/archive/varia-server/7e920c7f_Screenshot%20from%202020-03-21%2019-07-20.png</a>
<br>
<a href="http://varia.zone/images/variaecosystem.png" rel="noreferrer noopener">http://varia.zone/images/variaecosystem.png</a>
<br>
<a href="https://vvvvvvaria.org/~ccl/pictures-of-varia/" rel="noreferrer noopener">https://vvvvvvaria.org/~ccl/pictures-of-varia/</a>
<br>
<br>
<br>
<strong>References</strong>
<br>
<a href="http://varia.zone/en/the-social-in-the-media.html" rel="noreferrer noopener">http://varia.zone/en/the-social-in-the-media.html</a>
<br>
<a href="http://fuchs.uti.at/wp-content/RaymondWilliams_CommMat.pdf" rel="noreferrer noopener">http://fuchs.uti.at/wp-content/RaymondWilliams_CommMat.pdf</a>
<br>
<a href="https://donestech.net/files/iterations-spideralex-underneath-and-on-the-sidelines.pdf" rel="noreferrer noopener">https://donestech.net/files/iterations-spideralex-underneath-and-on-the-sidelines.pdf</a>
<br>
<br>
<br>
<strong>
<u>References on group conversations</u>
</strong>
<br>
<ul class="bullet">
<li>What's wrong with WhatsApp (2020) <a href="https://www.theguardian.com/technology/2020/jul/02/whatsapp-groups-conspiracy-theories-disinformation-democracy" rel="noreferrer noopener">https://www.theguardian.com/technology/2020/jul/02/whatsapp-groups-conspiracy-theories-disinformation-democracy</a>
</li>
<li>Organising Online - Thinking About Chat (2020) <a href="https://commonknowledge.coop/writing/organising-online--thinking-about-chat/" rel="noreferrer noopener">https://commonknowledge.coop/writing/organising-online--thinking-about-chat/</a>
</li>
<li>Group Chats Are Making the Internet Fun Again (2019) <a href="https://nymag.com/intelligencer/2019/05/group-chats-are-making-the-internet-fun-again.html" rel="noreferrer noopener">https://nymag.com/intelligencer/2019/05/group-chats-are-making-the-internet-fun-again.html</a>
</li>
<li>The Mechanics of Invisibility: On Habit and Routine as Elements of Infrastructure <a href="http://pne.people.si.umich.edu/PDF/Edwards%202017%20Mechanics%20of%20Invisibility.pdf" rel="noreferrer noopener">http://pne.people.si.umich.edu/PDF/Edwards%202017%20Mechanics%20of%20Invisibility.pdf</a>
</li>
</ul>
<br>
<br>
<strong>Varia</strong>
<br>
<strong>WHAT IS VARIA</strong>
<br>
<ul class="bullet">
<li>Collective Statement <a href="http://varia.zone/en/pages/collective-statement.html" rel="noreferrer noopener">http://varia.zone/en/pages/collective-statement.html</a>
</li>
<li>Code of Conduct</li>
</ul>
<strong>ORIGIN STORY</strong>
<br>
<ul class="bullet">
<li>NOOO2 Publication - Projects that set the stage for Varia:<ul class="bullet">
<li>Bibliotecha</li>
<li>homebrewserver.club</li>
<li>Relearn</li>
</ul>
</li>
</ul>
<strong>HOSTING TOGETHER</strong>
<br>
<ul class="bullet">
<li>Ananas (proposal to call the Varia server Ananas) with:<ul class="bullet">
<li>Blog</li>
<li>Website</li>
<li>Instant Messaging Service</li>
<li>Calendar</li>
<li>Etherpad<ul class="bullet">
<li>pad</li>
<li>altpad</li>
<li>writing emails together </li>
<li>keeping meeting notes</li>
<li>writing applications</li>
</ul>
</li>
</ul>
</li>
<li>Welcome to the Federation<ul class="bullet">
<li>Mastodon</li>
<li>XMPP<ul class="bullet">
<li>Bots</li>
</ul>
</li>
</ul>
</li>
</ul>
<strong>WORKING TOGETHER</strong>
<br>
<ul class="bullet">
<li>Workgroups<ul class="bullet">
<li>Feminist Hack Meetings</li>
<li>Digital Solidarity Networks</li>
<li>Read and Repair</li>
<li>Community Networks</li>
<li>Pub Club</li>
<li>Electronica Depot</li>
</ul>
</li>
</ul>
<strong>FUTURE OF VARIA</strong>
<br>
<ul class="bullet">
<li>
<ul class="bullet">
<li>wiki</li>
<li>Rosa server</li>
</ul>
</li>
</ul>
<br>
<br>
<br>
<br>
<strong>==PRESENTATION EXPANDED==</strong>
<br>
<br>
<br>INTRO: Good afternoonevening, we are Lídia and Cristina, two of sixteen Varia members. Thank you so much for this opportunity be in this company and to present Varia and its collective infrastructure. When we say infrastructure, we mean the digital, physical and, most important, social systems we have developed as part of our shared practices. <br>
<br>QUOTE: Infrastructure: To build a home or something that can sustain you from somewhere (unlike those offered on the market). To create communities in many places. Spideralex, <em>Underneath and on the sidelines: Sustaining feminist infrastructures using speculative fiction</em>
<br>
<br>Although we are two people doing this presentation, we will be using texts and ideas written and developed in diverse occasions by the entirety of Varia members. Also, some of the pictures that we have been using for this presentation are taken from our group chat, they are the behind the scenes of what's going on in Varia.<br>
<br>We will start this talk by introducing the space, its activities and shared values. In doing this we will provide the background that explains our shared ways of working, supported (and at times hindered) by our homebrewed digital, yet very material, infrastructure.<br>
<br>
<strong>WHAT IS VARIA (ccl)</strong>
<br>
<ul class="indent">
<li>Pics: <a href="https://vvvvvvaria.org/~ccl/pictures-of-varia/photo6008344555306463875.jpg" rel="noreferrer noopener">https://vvvvvvaria.org/~ccl/pictures-of-varia/photo6008344555306463875.jpg</a>
</li>
</ul>
<ul class="bullet">
<li>Collective Statement <a href="http://varia.zone/en/pages/collective-statement.html" rel="noreferrer noopener">http://varia.zone/en/pages/collective-statement.html</a> ccl</li>
</ul>
<ul class="indent">
<li>
<ul class="indent">
<li>Where is Varia's home?</li>
<li>Not here, but ... here. </li>
<li>Sometimes it looks like this.</li>
<li>And other times like this.</li>
<li></li>
<li>Varia is a Rotterdam-based initiative launched in 2017. We work with free/libre/open source software (FLOSS) to encourage participatory forms of art and design making. The themes we are interested in span media literacy, media archaeology, technological interdependence, feminism, DIY culture, self-organization and labour activism. </li>
<li></li>
<li>The initiative emerged from a group of five people who had the realization that there was an affinity of values and attitude among their members. They felt the need to open up their practices to other practitioners, and in the meanwhile Varia grew to be having 16 members. </li>
<li></li>
<li>We organise workshops, lectures, concerts, or reading rooms. Our activities are guided by the concept of <strong>**everyday technology**</strong>. Focusing on everyday technology means questioning the hierarchies in place within technical objects and therefore the valorisation of skills needed to design or use these objects. </li>
<li></li>
<li>Everyday technology means that a sewing machine is no less important than a laptop, that a tailor's work is by no means less meaningful than that of a computer scientist. Everyday technology means reconsidering the hegemony of high tech: cheap, artisanal solutions are our method of choice. </li>
<li></li>
<li>With our work, we try to show that low-tech solutions can be complex, inventive and joyful. Everyday technology means to believe that not only experts should have access and decisive power in regards to how things should work. This is why we design and contribute to convivial tools, namely, tools that guarantee a certain degree of autonomy to their users. </li>
<li></li>
<li>Everyday technology means keeping in mind multiple and entangled perspectives, needs, and aspirations when it comes to the understanding of a technical object. We are rooted in the context of art and design, but we actively try to build bridges with other fields. To do so, we encourage participation of people from varied backgrounds and disciplines.</li>
<li></li>
<li>We want to:</li>
<li>- work towards the eventual <strong>**disentanglement from the radical monopoly of Big Tech corporations**</strong> (Google, Apple, Facebook, Amazon, Microsoft, among others) by collectively building digital infrastructures that foreground care and conviviality.</li>
<li></li>
<li>- To <strong>**demystify the complexities of technical objects**</strong> and find ways to adapt them to the needs of different communities by providing a space for long-term, sustainable, critical, artistic, hands-on, <strong>**dialogical learning**</strong> about everyday technology.</li>
<li></li>
<li>- To move away from the ideological dichotomies that inform the adoption and use of technology, such as "old" versus "new" media, "low" versus "high" tech, "smart" versus "dumb" devices. We focus instead on notions like <strong>**appropriateness, accessibility, maintainance, and public interest**</strong>.</li>
<li></li>
<li>- To <strong>**transform critical thinking into action</strong>** by explicitly engaging with technologies which do not rely on exploitative business models and which promote non-discriminatory standpoints.</li>
<li></li>
</ul>
</li>
</ul>
<ul class="bullet">
<li>Code of Conduct <a href="https://vvvvvvaria.org/en/pages/code-of-conduct.html" rel="noreferrer noopener">https://vvvvvvaria.org/en/pages/code-of-conduct.html</a> lídia </li>
</ul>*missing: how does the previous connect to the code of conduct, what is the relation to the infrastructure?*<br>Pics: <br>
<br>
<ul class="indent">
<li>
<ul class="indent">
<li>Why is the COC important in relation to the infrastructures? It is a reflection of the shared values and ethics that hold varia together, but also a way to emphasise that infrastructure maintenance not only includes technical relationships, but also social ones.</li>
</ul>
</li>
</ul>
<br>
<ul class="indent">
<li>
<ul class="indent">
<li>In the past years, more and more collectives and free software projects started to work with a *Code of Conduct*. A good example of this is Python Foundation, which made the presence of such a document a requirement in order to grant interested projects a sponsorship. With that statement, they triggered other initiatives to create frameworks to engage with complaints and social misbehaviour. The code of conduct is a set of guidelines that help establish shared values and ensure that behaviour that may harm participants is avoided.</li>
</ul>
</li>
<li>
<ul class="indent">
<li>Writing a *Code of Conduct* was for us an attempt to answer the very important question: How do we resolve/identify/engage with conflict in a way that feels safe to those involved? The growing interest in the *Code of Conduct* within the field of software development and community initiatives gave us many examples to start with the writing of our own. However, as none of us had experience in writing a *Code of Conduct*, we invited ginger coons, *insert small bio for ginger* , as an external advisor.</li>
</ul>
</li>
<li>
<ul class="indent">
<li>As Varia had grown from 5 initial members to the current number of 16 members, it was clear that we needed a document that could engage with unavoidable frictions. At the same time we also become more and more aware of our responsibility towards the people that visit Varia for public events. During these occasions anyone can walk into the space and any sort of trouble or frictional situation might emerge.</li>
<li></li>
<li>Working together in groups is always a vulnerable social process. Writing Varia's *Code of Conduct* has specifically been important to acknowledge this vulnerability, as the document creates space for urgent conversations about power hierarchies and exclusions across the lines of gender, sex, race, ability, etc. Acknowledging the importance of tackling these issues, the Code of Conduct is an important first step towards ensuring the creation of a safe and inclusive work situation.</li>
</ul>
</li>
</ul>
<br>
<strong>ORIGIN STORY (ccl)</strong>
<br>
<ul class="bullet">
<li>NOOO2 Publication - Projects that set the stage for Varia:</li>
</ul>
<ul class="indent">
<li>Pics: <a href="https://vvvvvvaria.org/~ccl/pictures-of-varia/photo6008344555306463904.jpg" rel="noreferrer noopener">https://vvvvvvaria.org/~ccl/pictures-of-varia/photo6008344555306463904.jpg</a> , <a href="http://varia.zone/archive/2019-09-28-nooo2/P1910627.JPG" rel="noreferrer noopener">http://varia.zone/archive/2019-09-28-nooo2/P1910627.JPG</a> , <a href="http://varia.zone/archive/2019-09-28-nooo2/P1910668.JPG" rel="noreferrer noopener">http://varia.zone/archive/2019-09-28-nooo2/P1910668.JPG</a>
</li>
<li></li>
<li>
<u>INTRO:</u> To provide a contextualization of how the importance of needing a physical space and infrastructure emerged, we will briefly introduce a project that itself contains three other projects from a proto-Varia phase and which reflect on the benegits and some of the challenges of working together.</li>
<li></li>
<li>
<em>Three Takes on Taking Care</em> is the second issue of Networks of One’s Own, a publication series initiated by Brussels-based cultural association Constant. The series is taken care of by related but independent collectives. For each of the episodes, it proposes different experimental and collective practices for situated writing, technical learning and (digital) publishing. Each issue is thought of as the release of a software stack, documenting a set of tools, experiences and ways of working. </li>
<li></li>
<li>
<em>Three Takes on Taking Care</em> was an occasion to revisit three very different projects that have been important for the emergence of the physical space, and for its individual members: Bibliotecha, homebrewserver.club and Relearn. </li>
<li></li>
<li>As we work with and around free/libre open source technology collaboratively, the authorship of the tools and research that we develop is shared, not just amongst us at Varia but also with a wider international network. Multiple agents are involved at different moments, with varying intensity and for a range of different reasons. This results in intricate interrelationships of ownership which complicate documentation and long-term maintenance. </li>
<li></li>
<li>By collapsing maintenance work with publishing, we found a form that enabled this collective care work to happen and to spend the necessary concentrated time together.</li>
<li></li>
<li>lídia:</li>
</ul>
<ul class="bullet">
<li>
<ul class="bullet">
<li>Bibliotecha</li>
</ul>
</li>
</ul>
<ul class="indent">
<li>
<ul class="indent">
<li>Pics: <a href="https://networksofonesown.varia.zone/Bibliotecha/images/BibliotechaAtVaria-arrows.jpg" rel="noreferrer noopener">https://networksofonesown.varia.zone/Bibliotecha/images/BibliotechaAtVaria-arrows.jpg</a>
</li>
<li>Bibliotecha proposes an alternative model of distribution for digital texts. It allows specific communities to form and share their collections, through a single-board computer running free software to share books over a local WIFI hotspot.</li>
<li>Bibliotecha’s history begins in the Piet Zwart Institute, where there was an active culture of reading and sharing study material made available via a common bookshelf. While digital formats and the internet should make it easier than ever to share books, digital rights management and repressive copyright systems make the physical book paradoxically easier to share than its digital counterpart. In response to this came up with what would eventually be Bibliotecha, a digital library that was available via its own off-line network.</li>
<li></li>
</ul>
</li>
</ul>
<ul class="bullet">
<li>
<ul class="bullet">
<li>homebrewserver.club</li>
</ul>
</li>
</ul>
<ul class="indent">
<li>
<ul class="indent">
<li>Pics: <a href="https://networksofonesown.varia.zone/Homebrewserver.club/images/dontturnofthisisaserv2.png" rel="noreferrer noopener">https://networksofonesown.varia.zone/Homebrewserver.club/images/dontturnofthisisaserv2.png</a>
</li>
<li>The homebrewserver.club started in 2014 after attending a few editions of the Rotterdam Crypto Party. While Crypto Parties were focused on encryption and privacy — essentially offering cryptography as a solution to surveillance and corporate dominance — there was a parallel interest to look at the more systemic issues of corporate platforms. Out of this interest the homebrewserver.club was founded as a way to learn about hosting one’s own on-line services rather than relying on corporate ones. Its members host from their homes rather than from data centers, for and with their communities rather than just for themselves. </li>
<li>The club has worked as place for collective learning and skill building, where technological choices get contextualized on the axes political-economy and DIY amateurism.</li>
<li></li>
</ul>
</li>
</ul>
<ul class="bullet">
<li>
<ul class="bullet">
<li>Relearn</li>
</ul>
</li>
</ul>
<ul class="indent">
<li>
<ul class="indent">
<li>Pics: <a href="https://vvvvvvaria.org/~ccl/pictures-of-varia/photo6008344555306463899.jpg" rel="noreferrer noopener">https://vvvvvvaria.org/~ccl/pictures-of-varia/photo6008344555306463899.jpg</a>
</li>
<li>Relearn is a collective learning experiment with as many teachers as it has participants, week-long gatherings that have been taking place since 2013. In 2017 a group of people now involved in Varia decided to organise an edition of Relearn in Rotterdam. It also happened again in 2019 and we are aiming to do it again in 2020.</li>
<li></li>
<li>Conclusion: *how these connect to infrastructure making and Varia* </li>
<li>All of these projects touch on topics that have become central to the making of our physical and digital infrastructure. From the development of bespoke tools for knowledge sharing exemplified by Bibliotecha, to the socio-political contextualization of self-hosting forwarded by homebrewserver.club and the pedagogical principles of Relearn, these practices continue to inform Varia's activities on a daily basis. </li>
<li>In the following section of this presentation, we will see how these practically manifest:</li>
<li></li>
</ul>
</li>
</ul>
<strong>HOSTING TOGETHER (ccl)</strong>
<br>
<ul class="bullet">
<li>Server with:</li>
</ul>   Pics: <a href="http://varia.zone/archive/varia-server/IMG_4379.jpg" rel="noreferrer noopener">http://varia.zone/archive/varia-server/IMG_4379.jpg</a> , <a href="http://varia.zone/images/variaecosystem.png" rel="noreferrer noopener">http://varia.zone/images/variaecosystem.png</a>, <a href="https://vvvvvvaria.org/~mb/images/varia-digital-collective-infrastructure.png" rel="noreferrer noopener">https://vvvvvvaria.org/~mb/images/varia-digital-collective-infrastructure.png</a>
<br>   We host some of our own services, while also relying on other people hosting theirs. In fact, we are more fond of the idea of interdependence than that of autonomy. <br>   This is a picture of our current server in the space. It looks very inconspicious there in the corner, but if the electricity or internet is down in the neighbourhood, our main infrastructure is also down, the website is unreachable, out group chats stop working and so on. Some of the things we host on this server are the following:<br>
<ul class="bullet">
<li>
<ul class="bullet">
<li>Ecosystem<ul class="bullet">
<li>Lurk.org is a volunteer group that hosts, facilitates and archives discussions around net- and computational culture and politics, proto- and post-free culture practices, experimental, sound, new media, software art.</li>
</ul>
</li>
<li>Website<ul class="bullet">
<li>The website is using a static file generator called Pelican and we use the Gitea interface to add content to the website.</li>
<li>Static file websites mean that the site is generated once when content is uploaded, and not on the fly on the user's side. In this way it consumes less resources.</li>
</ul>
</li>
<li>Instant Messaging</li>
</ul>
</li>
</ul>
<ul class="indent">
<li>
<ul class="indent">
<li>For our Instant Messaging Infrastructure, we are using Prosody, an XMPP server. XMPP is a communications protocol designed as an open standard.</li>
<li></li>
<li>To quote from the homebrewserver.club article "Have you Considered the Alternative": "Such an approach, rather than suggesting a singular and proprietary solution, allows for the existence of different free and open source software servers which can be combined with different free and open source software clients.(...) These clients can range from general instant messengers to custom <strong>
<u>XMMP bots</u>
</strong>."</li>
<li></li>
<li>For example within the Varia group chat, these are the servers hosting Prosody that interact with each other.</li>
</ul>
</li>
</ul>
<ul class="bullet">
<li>
<ul class="bullet">
<li>
<ul class="bullet">
<li>Bots<ul class="bullet">
<li>Hosting our own server also means that we can customise our services. Within some XMPP chats, we have hosted bots alongside the XMPP server. Some bots that add bibliography </li>
</ul>
</li>
</ul>
</li>
<li>Etherpad<ul class="bullet">
<li>Etherpad is an online editor providing collaborative editing in really real-time. It has become central to how we organise ourselves. We take notes from meetings on the Etherpad, write emails together, write applications together. During the lockdown we also used Etherpad to hold collective reading events. This is an excerpt for example of a session held by one of Varia's friends.</li>
<li>Hosting it ourselves means that we can experiment with making new interfaces for it. This is an alternative interface to the same text we were looking at before, but without authorship colours.</li>
<li>We also use the Etherpump, a deviation of Etherdump, as an engine to generate html files. We are looking at the Digital Solidarity Networks pad translated to a html. Every hour the page regenerates itself based on the content of the pad.</li>
</ul>
</li>
<li>Calendar<ul class="bullet">
<li>Our shared calendar is used to let each other know when we are using the space, when someone is planning an event, when deadlines are due, but also to share interesting events going on in the city. On the other hand, the calendar also points towards the vulnerabilities of hosting one's own services. Fo already a while, someone's client is acting up and deleting the events from time to time, so someone else uploads a back up copy to replace it again. Due to the lack of time to investigate this further, we haven't yet been able to figure out what causes the glitch.</li>
</ul>
</li>
</ul>
</li>
<li>Welcome to the Federation lídia</li>
</ul>
<ul class="indent">
<li>Pics: <a href="http://varia.zone/archive/2018-12-WttF-Mastodon-and-the-Fediverse/photo5791687760443190857.jpg" rel="noreferrer noopener">http://varia.zone/archive/2018-12-WttF-Mastodon-and-the-Fediverse/photo5791687760443190857.jpg</a> , <a href="https://varia.zone/wttf/images/the-ecosystem-is-moving.worksession-0.jpg" rel="noreferrer noopener">https://varia.zone/wttf/images/the-ecosystem-is-moving.worksession-0.jpg</a> , <a href="https://varia.zone/wttf/images/the-ecosystem-is-moving.conversation-2.jpg" rel="noreferrer noopener">https://varia.zone/wttf/images/the-ecosystem-is-moving.conversation-2.jpg</a>
</li>
<li>Welcome to the Federation was a project initiated by Varia members Roel Roscam Abbing and Manetta Berends. In their own words: "Welcome to the Federation explores alternative federated ecosystems for online services such as <strong>social media</strong> and <strong>chat</strong>. (...) The WttF question is to explore how arts and design communities can play a supportive role in these processes by contributing skills, knowledge, time and exposure." </li>
<li>In the context of this project, two events were organized:<ul class="indent">
<li>
<ul class="indent">
<li>- The first, called "The Ecosystem is Moving", involved a lecture by and worksession with Daniel Gultsch, developer of XMPP-based messaging application Conversations, about federated instant messaging, open source software and the sustainability of open systems.</li>
<li>- The second, called "Mastodon and The Fediverse", involved <em>a </em>worksession for translating and documentation of the Mastodon project and a public discussion providing a general introduction into Mastodon and the Fediverse, hosted together by an administrator of a large Mastodon community and an administrator of a small Mastodon community. It is important to mention here that this small Mastodon community is post.lurk.org, an instance for discussions around cultural freedom, experimental, new media art, net and computational culture, where Varia has an account.</li>
<li></li>
<li>
<u>Hosting together</u>
</li>
<li>This relates back to the general philosophy of hosting together that is pervasive to Varia: the focus is more on the social and community aspect of the infrastructure and less on the technological aspect. In this case, a community that is closely related to many of our members (with some overlaps!) was already hosting an instance, so it would have been a waste of resources to be hosting our own. To quote from the homebrewserver manifesto: "we try to host for and with our communities rather than just for ourselves".</li>
<li></li>
<li></li>
</ul>
</li>
</ul>
</li>
</ul>
<strong>WORKING TOGETHER ccl</strong>
<br>
<ul class="bullet">
<li>Workgroups ccl<ul class="bullet">
<li>As the infrastructure is being built, it supports and allows us to work together in different ways, one of which are the workgroups. Workgroups happen both with members and non-members and as opposed to events, happen on a long term basis. We will briefly mention a few to give an idea of what kind of things are going on.</li>
<li>Feminist Hack Meetings</li>
</ul>
</li>
</ul>
<ul class="indent">
<li>
<ul class="indent">
<li>Pics: <a href="https://vvvvvvaria.org/~ccl/pictures-of-varia/photo6008344555306463887.jpg" rel="noreferrer noopener">https://vvvvvvaria.org/~ccl/pictures-of-varia/photo6008344555306463887.jpg</a>
</li>
<li>The <em>Feminist Hack Meetings</em> are a series of research meetings and workshops that explore the potentialities and imaginaries of feminist technological collectives. These gatherings aim to challenge who counts as a hacker, and what counts as hacking. The diverse activities of these gatherings will include sociopolitical discussions around technology and feminism, storytelling, prototyping and skill-sharing, as well as art experiments.</li>
</ul>
</li>
</ul>
<ul class="bullet">
<li>
<ul class="bullet">
<li>Digital Solidarity Networks</li>
</ul>
</li>
</ul>
<ul class="indent">
<li>
<ul class="indent">
<li>Pics: <a href="https://vvvvvvaria.org/~ccl/pictures-of-varia/photo6008344555306463882.jpg" rel="noreferrer noopener">https://vvvvvvaria.org/~ccl/pictures-of-varia/photo6008344555306463882.jpg</a>
</li>
<li>Digital Solidarity Networks started within the context of the global pandemic as a shared listing of tools, practices and readings for digital solidarity and conviviality. It currently lives as one of the many pads on the Varia server and it contains examples of collective digital alternative practices, in a time where everything points to the further consolidation and accelerated normalization of the Big Tech industry (Zoom, Facebook groups, Slack, Microsoft Teams, Skype, etc.).</li>
</ul>
</li>
</ul>
<ul class="bullet">
<li>
<ul class="bullet">
<li>Read and Repair (ccl)</li>
</ul>
</li>
</ul>
<ul class="indent">
<li>
<ul class="indent">
<li>Pics: <a href="https://vvvvvvaria.org/~ccl/pictures-of-varia/photo6008344555306463886.jpg" rel="noreferrer noopener">https://vvvvvvaria.org/~ccl/pictures-of-varia/photo6008344555306463886.jpg</a>
</li>
<li>
<em>Read &amp; Repair Sessions </em>is a type of reading club happening on the final Sunday of each month. <em>Read &amp; Repair Sessions </em>have a focus on community building and self-organised learning through collective reading tactics. For these sessions, a guest is invited to share a text that connects to their research, which they discuss together with the participants.</li>
</ul>
</li>
</ul>
<ul class="bullet">
<li>
<ul class="bullet">
<li>Other workgroups existing in Varia at diverse stages of development are:<ul class="bullet">
<li>Community Networks, which focuses on Varia's relationship with the neighboring community</li>
<li>Pub Club, which focuses on dialogical and generative publishing systems</li>
<li>Electronica Depot, a community resource where members can purchase common parts parts at a low cost</li>
</ul>
</li>
</ul>
</li>
</ul>
<br>CONCLUSION<br>
<ul class="indent">
<li></li>
<li>(ccl)</li>
<li>Although hosting our own services and being in a constant flux of making and remaking our infrastructure, it is of course not always a smooth process. Working on our own infrastructure also means that there are frictions sometimes: faulty syntaxes on our event announcements mean the website becomes unavailable every once in a while, quickly expanding log files have crashed our etherpad instance more than once, electricity failures and accidental pushes of the on/off button have temporarily sent our server to sleep. These occasions highlight not only the physicality on which our digital infrastructure is dependent, but also the amount of care and maintenance work necessary to keep things running. For this, we are dependent on the availability of our members, or their physical proximity to the server in cases of emergency.</li>
<li></li>
<li>(lidia)</li>
<li>We don't consider, however, that this in any way detracts from the validity of our efforts: indeed, we are wary of smoothly running technology. Very often this obscures the intensive extractivism which allows it to run: appaling working conditions, depletion of natural resources, heavy environmental impact etc.</li>
<li></li>
<li>Small-scale, community-focused and low-tech are our methods of choice not because we believe in isolationist perspectives, but because we want to give our contribution to the development of alternative approaches to everyday technology for the benefit of more than just a small minority.<strong> </strong>Slowly, we want to make Varia a home not just to ourselves but other communities too.</li>
</ul>
<br>
<br>
<br>
<br>
<br>
<br>__PUBLISH__<br>
<br>
</body>
</html>