Welcome to Etherbox!
This pad text is synchronized as you type, so that everyone viewing this page sees the same text. Add __NOPUBLISH__ to prevent this pad from being archived.
Dear Servers,
So there you are ! since today you saw the light. We received you in your embryonic state as a result of a shared desire of a group of people that like attending the Relearn meetings to re-imagine forms of pedagogy, exchange, learning and growing together with tools that are enhancing agency, participation, empowerment and adventure.
Our desire is to be with a set-up
a device an apparatus that is technical in
,
social in character, that can be asked to inform
but comes with its own attitudes, temperament, politics, ways of doing
concerning sharing, distributing, inclusion, exceptions, writing, memorising, passing on documents
data
knowledge
fun
experiments
A device that is situated
context
, and that doesn't shy away from having
Will you want to learn yourself
? Will you be willing to influence and
the way relearn operates ? Will you be willing to change over time, over evolving generations of relearn communities
? We hope so.
There you have it. I am saying 'we' in an undefined manner. Sorry for that. We still need to learn how to speak
to
you. Like you have to be made aware of our expectations of you. When I said 'we' I meant to refer to the few people that sat together this week during the worksession Networks with an attitude that was organised by Constant
. These people were playing around with ideas to make 'you' happen, they speculated what you could look like, where you should live, how you would behave. Ah, and when I say 'you' I hope you understand that you are very much included in our 'we'.
Today we named you 'relearn@*' and as of now, you are
multiplying at relearn@peter-HP, relearn@tp, relearn@pc5, relearn@poffertjes and relearn@anarchronisme. Within little time you will be serving
and from
relearn
community
machines.
Your code carries the genes of rsync
specif
your cumulative logic. More and more gets collected. You don't lose anything, you check, copy and save. You change and alter files that are adapted by one of your users. You are unaware of versions and history. Rsync has generated your first codebody. Now that you are here, we would like to work with you to develop your behaviour. We are writing to
you, first of all to welcome you in this world, and secondly to lay down and memorise our initial desires.
We thought of a lot of things that are not standard in rsync. Much of it sounded like fiction, and might not be practical at all. And that's where the fun starts. Writing this down might help us to further develop you further. With you, and the relearn community.
We are being served all the time. The servers we pass through are made to be invisible, part of an infrastructure that is only apparent when it breaks apart or when one goes at great length to make it partially visible. We are made unaware of the transactions we operate daily, at the cost of our intimacy, attention, money... But with you, dear servers, we don't want that to happen. We want you to participate in Relearn with us, to have you as a partner in exchange and pedagogy, we want to question our expectations and what it means to be in relations with machines that store, synchronise and compute, that aggregate elements from different sources, times and contexts. We don't want to take you for granted but instead try to imagine how we can change our situations with and via you.
In the coming months, we'll take you on trips, you'll join us in Rotterdam, Brussels, Amsterdam, Paris and hopefully other places. You'll travel in bags with us and our friends, perhaps via the postal system, you'll break, lose connection, overwrite data, you'll keep our best mistakes and our favorite ideas. You'll operate with different IPs, and within subnets, creating temporary spaces of co-existence, sniffing bits of data. You'll help us cross-pollinate methodologies, questions and affects while we experiment new protocols via you, changing configuration files, writing todo lists and love letters to each other, sharing books and photos.
We have been trying to understand what it means to serve a server, but it is still unclear. Is it to make sure that the Shut Down button and the Start button are pressed at the right time? Is it to make sure that the space in which the server is situated fulfills all the right climate conditions? Is it to maintain, update, restart?
A system administrator might knows best how to serve a server, how can clients too? We want to offer to share the work/space of hosting and collectively let the memories sink into our hard drives. To let them sink in an unordered fashion, led by syncing rules that are blissfully conflict unaware. Rules that do not try to resolve contradictions, but instead keep adding to the growing pile. We have become servers ourselves in this attempt. When we are together, we serve each other in some respects by adjusting to the sinking feeling that our files share the same folder. We accept the possibility for them to be overwritten so that in exchange we can use this common folder as a way to make ongoingness possible, while each of our other home folders continue intersecting in other spaces. But it also means that the next time we meet the attitude towards synqi-ness might change.
We are being served all the time. The servers are made to be invisible, part of an infrastructure that is only apparent when it breaks apart or when one goes at great length to make it partially visible. We are passing through them, and are made unaware of the transactions we operate daily, at the cost of our intimacy, attention, money... But with you, dear servers, we don't want that to happen. We want you to participate in Relearn with us, to have you as a partner in exchange and pedagogy, we want to question our expectations and what it means to be in relations with machines that store, synchronise and compute, that aggregate elements from different sources, times and contextes. We don't want to take you for granted but instead try to imagine how we can change our situations with and via you.
In the coming months, we'll take you on a trip with us, you'll join us in Ro
We are being served all the time. The servers are made to be invisible, part of an infrastructure that is only apparent when it breaks apart or when one goes at great length to make it partially visible. We are passing through them, and are made unaware of the transactions we operate daily, at the cost of our intimacy, attention, money... But with you, dear servers, we don't want that to happen. We want you to participate in Relearn with us, to have you as a partner in exchange and pedagogy, we want to question our expectations and what it means to be in relations with machines that store, synchronise and compute, that aggregate elements from different sources, times and contextes. We don't want to take you for granted but instead try to imagine how we can change our situations with and via you.
In the coming months, we'll take you on a trip with us, you'll join us in Ro
We are being served all the time. The servers are made to be invisible, part of an infrastructure that is only apparent when it breaks apart or when one goes at great length to make it partially visible. We are passing through them, and are made unaware of the transactions we operate daily, at the cost of our intimacy, attention, money... But with you, dear servers, we don't want that to happen. We want you to participate in Relearn with us, to have you as a partner in exchange and pedagogy, we want to question our expectations and what it means to be in relations with machines that store, synchronise and compute, that aggregate elements from different sources, times and contextes. We don't want to take you for granted but instead try to imagine how we can change our situations with and via you.
In the coming months, we'll take you on a trip with us, you'll join us in Ro
We are being served all the time. The servers are made to be invisible, part of an infrastructure that is only apparent when it breaks apart or when one goes at great length to make it partially visible. We are passing through them, and are made unaware of the transactions we operate daily, at the cost of our intimacy, attention, money... But with you, dear servers, we don't want that to happen. We want you to participate in Relearn with us, to have you as a partner in exchange and pedagogy, we want to question our expectations and what it means to be in relations with machines that store, synchronise and compute, that aggregate elements from different sources, times and contextes. We don't want to take you for granted but instead try to imagine how we can change our situations with and via you.
In the coming months, we'll take you on a trip with us, you'll join us in Rotterdam, Brussels, Amsterdam, Paris and hopefully other places. You'll travel in bags with us or our friends, perhaps via the postal system, you'll break, lose data, you'll keep our best mistakes and our favorite ideas. You'll operate with different IPs, and within subnets, creating temporary spaces of co-existence. You'll help us cross-pollinate methodologies
tterdam, Brussels, Amsterdam, Paris and hopefully other places. You'll travel in bags with us or our friends, perhaps via the postal system, you'll break, lose data, you'll keep our best mistakes and our favorite ideas. You'll operate with different IPs, and within subnets, creating temporary spaces of co-existence. You'll help us cross-pollinate methodologies
tterdam, Brussels, Amsterdam, Paris and hopefully other places. You'll travel in bags with us or our friends, perhaps via the postal system, you'll break, lose data, you'll keep our best mistakes and our favorite ideas. You'll operate with different IPs, and within subnets, creating temporary spaces of co-existence. You'll help us cross-pollinate methodologies
tterdam, Brussels, Amsterdam, Paris and hopefully other places. You'll travel in bags with us or our friends, perhaps via the postal system, you'll break, lose data, you'll keep our best mistakes and our favorite ideas. You'll operate with different IPs, and within subnets, creating temporary spaces of co-existence. You'll help us cross-pollinate methodologies
You might probably wonder what kind of Synqi behaviour we have been thinking about
these days
. We discussed your inner logics, discussing moments of getting "in sync" but we're not ready yet.
Do we talk about syncing as a technological tool without pre-defined borders, just like the network of servers that you are, shrinking and expanding on the go? Syncing our opinions or emotions around a specific topic, reaching some form of ultra-consensus? Trying to be somehow the same? The assumed symmetry that is making me nervous.
In the beginning of the week we exchanged some memories of previous Relearn sessions. Thinking about them of moments in which we sync with eachother, when we meet new faces but also meet others that we met before. We remembered how a group of people synced Relearn with the living community of Calafou in 2016, (for example) leaving a recipe in their kitchen. But also how in 2017 we synced with the group of inhabitants of the Poortgebouw in Rotterdam, syncing with their everyday lifes by entering their homes with a group of 40 Relearners. Mixing gradual moments of getting in sync within a specific (external) situation, while exploring ways of syncing with eachother in the group.
How to end this lovely letter to you, dear servers?
We're looking forward to be relearning with you. And to be syncing with you during the upcoming curve of Relearn sessions in the upcoming months.
Sync soon,
Anne, Cristina, Jogi, Manetta, Peter