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.
74 Commits
1 Branch
0 Tags
9.4 MiB
 
Branch: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
bots-of-conduct/Previous iterations/README_Collective_Condition...

11 KiB
Raw Permalink Blame History

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 free software 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: transit.py;

action mode: announces when someone enters or leaves the room;

situation: finding non-verbal ways of communicating through presence and absence; making presence felt otherwise;


name: gather.py;

action mode: generates a shared language; it creates a collective document;

situation: a collective discursive setting that generates its own vocabulary;



name: greet.py;

action mode: sends a message when it enters the room;

situation: when there is a theme, for example: "send a reference to an existing or imaginary code of conduct, complaint, guideline, bug report, open letter, license or other social-technical protocol and explain why it is of interest to you."; how one wants to be introduced;



name: spark.py;

action mode: replies to a specific word; brings alternatives into the situation; tries to create new habits and terminologies;

situation: potentially in moments when a situation seems difficult and there is a need for more joyful interactions;



name: whisper.py

action mode: takes what someone says to it in confidentiality and echoes it to a group chat, thus anonymising it;

situation: there are remarks or complaints in the room, but the person does not feel comfortable to bring up the issue themselves;


Split into groups of maximum 4-5 (mixed interest in code).


BREAK — 10 minutes ;)


16:10-16:30 — creating situations

Imagine you are a collective-space with your group peers and you have been active for 5 days;

  • create a name for the chatroom:

    • or rooms /sites of action/ environments ..to open up the imagination of what a chatroom may be like!

  • imagine 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;

  • action modes: 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);
    • what apart from language can be used as a way of conducting? what other modes of non-linguistic expression?

  • further questions:

    • how could the bot be physically enacted? what gestures would it perform?
    • some (non-exhaustive) attributes of 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 gather.py which uses a txt file for adding words to a glossary);
    • 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?



installing and running the bots (optional)

For computers running Windows OS

For computers running MacOS

  • open the terminal
  • check which version of python you have:

    python -V

  • if you have a python 2 version, you could install Anaconda with python 3

For computers running Linux OS

  • open the terminal

  • check which version of python you have:

    python -V python3 -V

  • if you have a python 2 version, you could install python 3

    sudo apt-get install python3 sudo apt-get install python3-pip

  • download the bots from this page

  • go to the folder where you have installed them

  • run the following commands in the terminal:

pip3 install slixmpp requests

  • to run a bot, you can copy paste the commands which are already mentioned in the bot file, but a general command looks like this:

python3 bot.py -d -j administratorbot@conversejs.org -r botsofconduct@muc.vvvvvvaria.org -n bot -p testing

  • where:

    • j stands for JID (jabber id)
    • r means room
    • n stands for bot nickname
    • o stands for for output
    • . means here

  • if you dont have a code editor, we can suggest (among others) Sublime Text

  • to install the conversations app on your phone, you could use either Conversations or Quicksy for Android phones (among others)



17:00-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: iterations, repetition, ...



17:30-18:00 - discussion and performing



Footnotes

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

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

  2. ↩︎