ccl
/
bots-of-conduct
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Ongoing collection of bots for the Bots of Conduct workshop. This repository will be gathering code written by many people during various moments (Relearn 2017, Relearn 2019, ongoing Varia work).
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.
36 Commits
1 Branch
0 Tags
9.4 MiB
 
Tree: b93568e8c2
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'b93568e8c2'
${ noResults }
Cristina Cochior b93568e8c2
changed small thing 		5 years ago
.DS_Store new bots 5 years ago
README.md Update 'README.md' 5 years ago
gather.py changed small thing 5 years ago
greet.py changed small thing 5 years ago
spark.py changed small thing 5 years ago
transit.py changed small thing 5 years ago
whisper.py changed small thing 5 years ago

README.md

Bots of Conduct

a workshop by Cristina Cochior and Joana Chicau for Constant's work session Collective Conditions, Brussels 2019

15:00-15:30 - collective digital infrastructures

Varia's server

Varia is a collective-space 1 in Rotterdam focused on everyday technologies. We keep a trail of photographs of what we've done.

Together, we try to experiment with various tools for collaborative processes, as well as collective infrastructure making and self-hosting.

In October 2019, we wrote our own first CoC.

In June 2019, during Relearn Rotterdam, some of the participants had discussions about codes of conduct and conducting codes and bots of conduct.

Infrapunctural bots for stress relief

Slide from a 2018 presentation by Deb Verhoeven on digital infrapunctures

Inspired by the potential of digital infrapunctures by Deb Verhoeven, we would like to propose considering what a bot logic might look like:

  • where platform logic accumulates, bot logic disperses
  • where platform logic centralises, bot logic fragments
  • where platform logic creates distance between user and infrastructure, bot logic develops an intimate knowledge of the platform
  • where platform logic reinforces habitual behaviour, bot logic encourages new habit formation

A few examples:

What would bots of conduct act like?

What would it mean to become more entangled with bots, redistribute the labour of making and maintaining a collective, but without falling into the metaphorical understanding of bot as a servant?

Varia members use XMPP as a chat protocol because it enables us to self-host our own instance and federate with other chat servers. We use bots both to communicate and to document our exchanges. Our initial idea was to develop new forms of note-taking based on our interaction habits. We share a lot of different types of information in group chats, from news to recommendations of articles to instigations to clean the fridge. Starting from the conversational nature of our exchanges, we are experimenting with two different bot-users in the chat: one that gathers images shared on the main Varia channel and displays them online, and another one, focused specifically on the topic of digital interdependencies, that gathers images, quotes and looks for books' citations.

Working on our own digital infrastructure allows us to adapt the tools to our own needs and behaviours; meaning that these bots make sense to us, but they may not make sense to someone else.

Currently, we use:

  • Streambot: a bot that saves the images sent to the main Varia group chat and creates an html page for them.

  • Logbot: a bot that logs the quotes that are sent to it.

  • You can find a genealogy of the bots around Varia in this footnote 2



15:30-15:45 - bot as conductor or bot as conductive

Conducting: "the art of directing the simultaneous performance of several players or singers by the use of gesture." [https://en.wikipedia.org/wiki/Conducting]. There are many roles as conductors [https://en.wikipedia.org/wiki/Conductor] Also, in connection to the enviroment: "a substance, body, or device that readily conducts heat, electricity, sound".

Looking into the bots examples

name: cross.py;

action mode:

situation:


name: gather.py;

action mode:

situation:


name: greet.py;

action mode:

situation:


name: spark.py;

action mode:

situation:


name: whisper.py (we don't have this one yet)

action mode:

situation:



  • split into groups of maximum 5 (mixed interest in code)



BREAK — 10 minutes ;)



15:45-16:25 — creating situations

Imagine you are a collective-space with your group peers and you have been active for 2 years

  • create a name for the chatroom:

    • to open up the imagination (rooms /sites of action/ environments);

  • imagine a situations:

    • from your own experiences working in collaboration, or with a collective, or having read a CoC, try to recall a specific moment which can define an action mode;

    • which situation to think through? / if a code of conduct would exist for a situation?

  • embody the situation through a conductor / conductive bot:

    • in relation to the situation, does your bot act as conductor or as conductive?

    • what are your "action modes" (for eg.: sitting; dancing; witnessing; listening; gathering; greeting; sparking; whispering; reminders is a specific kind of action); action modes that create (or perform within specific) situations (for eg.:conversation is unbalanced);

    • how can bots be embodied / physically enacted? what gestures would it perform?

    • what apart from language can be used as a way of conducting? what other modes of expression (non-linguistic)?

    • other possibilities for bot behaviour:

    • iteration, repetition;

    • lack of memory

    • other temporalities (duration / tempo);

    • will your bot perform in other space extensions? speaking to other (chat)rooms? to other spatial formats (file systems, like the glossary and the txt file);

    • will your bot be a channel between private to public? semi-public to semi-public? semi-public to private? private to private?

    • will your bot relate to other bots?

    • thinking of distance and proximities between members and bots: is it listening to a specific member? is it listening to other bots?



16:25-16:40 - round of ideas-sharing



16:40-17:10 - installing

optional: for anyone who would like to install and run the bots:

  1. are there any Windows users?

  2. open the Terminal application on your computer

  3. install python3

dependencies (pip install slixmpp requests, install python3, pip3, text editor)

  1. download the bots: https://git.vvvvvvaria.org/ccl/bots-of-conduct/src/branch/master

  2. run a bot in the terminal (be sure to be in the same directory of the files):

  3. show & explain the parts where one can intervene

$ python3 bot.py -j user@vvvvvvaria.org -p password -r tuwazap@muc.vvvvvvaria.org -n nickname -o .

  • -j means JID (the xmpp protocol)

  • -r means room

  • -n means bot nickname

  • -o output

  • . means here





17:10-17:30 - bot in the situation

  • experimenting with bots: either adapt the ones we provided (experiment with code) or enact the bots' behaviours iteratively (bot behaviour);

  • bot behaviour: iteration, repetition



17:30-18:00 - present and perform



Footnotes

Link to reference's pad — further references and materials assembled by Joana and Cristina - feel free to add your owns!

  1. Varia is not merely a collective, nor merely a space. Varia is an interdependent concatenation of both ↩︎

  2. ↩︎