Browse Source

added a new page, created a new section, and made some adjustments

master
Your Name 4 years ago
parent
commit
9074629ecc
  1. 4
      content/Track 3 - Introduction to Bots/1-introduction.md
  2. 2
      content/Track 4 - Bot Logic/1-introduction.md
  3. 10
      content/Track 4 - Bot Logic/2-bot-logic-vs-platform-logic.md
  4. 2
      content/Track 4 - Bot Logic/3-examples.md
  5. 2
      content/Track 4 - Bot Logic/4-bot-behaviour.md
  6. 2
      content/Track 6 - Critical Interventions Through Bots (exercise)/4-situated-bot-code.md
  7. 22
      content/Track 7 - Recap/1-recap.md
  8. 2
      content/Track 7 - Recap/2-end-of-the-module.md

4
content/Track 3 - Introduction to Bots/1-introduction.md

@ -5,7 +5,7 @@ Summary: What type of bots are being made?
Having just unfolded what infrastructural harms could be, we now move to exploring bots. When we say bots, we refer to software applications that automatise certain tasks and can run autonomously or semi-autonomously. Some of the most popular examples include voice assistants such as Alexa or Siri, but they can also be web crawlers indexing the web or even bots maintaining Wikipedia.
Bots are an interface between digital infrastructures and human users. They are automated scripts that fulfil specific tasks which do not require expensive equipment to be able to be run.
Bots are an interface between digital infrastructures and human users. They are automated scripts that fulfil specific tasks. They also do not require expensive equipment to be able to be run, which means that amateur as well as experienced programmers are able to build them and deploy them.
Andreas Hepp terms *communicative robots*[^hepp] as "autonomously operating systems designed for the purpose of quasi-communication with human beings to enable further algorithmic-based functionalities – often but not always on the basis of artificial intelligence" (1410).
@ -13,7 +13,7 @@ In this track, we will introduce Andreas Hepp, professor of media and communicat
<br>
# Footnotes
# Footnoteswhich
[^platin]: Plantin, Jean-Cristophe. Lagoze, Carl. Edwards, Paul N. Sandvig, Christian. "Infrastructure studies meet platform studies in the age of Google and Facebook" *New Media and Society* Volume 20 (2016): 293-310. <https://journals.sagepub.com/doi/abs/10.1177/1461444816661553>

2
content/Track 4 - Bot Logic/1-introduction.md

@ -3,7 +3,7 @@ Slug: 01-s4-introduction
Date: 2020-11-01 12:00
Summary: Bots as computational infrapunctures.
*Infrapuncture* is a helpful term at a time when there is a lot of discussion around the political roles of bots in communication platforms, e.g. their undue influence in political elections. Making a bot can be a way to probe and understand potential forms of interventions, create new imaginaries or attempt to deflate existing hegemonic structures.
*Infrapuncture* is a helpful term at a time when there is a lot of discussion around the political roles of bots in communication platforms, e.g. their undue influence in political elections or bots which are created in order to harass activists. Making a bot can be a way to probe and understand potential forms of interventions, create new imaginaries or attempt to deflate existing hegemonic structures.
Bots rely on the technical restrictions and possibilities of interaction defined by the infrastructure on which they are operating. In order to run a bot, a technical understanding of this infrastructure is therefore required. The API (Application Programming Interface) is an important entry point here. This technical framework provides a programming interface to communicate with a system. The API can be understood as a set of agreements that is designed by the engineers of an infrastructure for two applications to communicate with one another, which eventually defines the technical imaginary of a platform. (*We dive a bit deeper into API's in track 6, [click here](/02-s6-step-2.html#APIs) to go there directly.*)

10
content/Track 4 - Bot Logic/2-bot-logic-vs-platform-logic.md

@ -4,7 +4,7 @@ Date: 2020-11-01 12:02
Summary: *Bot logic* disperses, fragments, develops intimate knowledge & encourages new habit formation.
*Bot logic* refers to the situational effect of bots upon a socio-technical ecology and their potential to infiltrate and co-exist with server-side conditions. We propose the term *bot logic* in response to *platform logic*, which Jonas Andersson Schwarz describes as
*Bot logic* refers to the situational effect of bots upon a socio-technical ecology and their potential to infiltrate and co-exist with server-side conditions. We propose the term *bot logic* in response to *platform logic*. Jonas Andersson Schwarz describes platform logic as:
> the interplay between different mechanics inherent to digital platforms, found on different conceptual and topological levels: micro, meso, and macro. It is a way to simultaneously acknowledge the technical capacity of unyielding local control and its consequential concentrations of global dominance by a handful of corporate actors[^platformlogic].
@ -16,21 +16,21 @@ To unpack the term *bot logic* further, we will explore four differences between
----------
* Where platform logic accumulates, *bot logic* disperses
* Where *platform logic* accumulates, *bot logic* disperses
On commercial digital infrastructures, the engagement of users creates economic value that is translated through data capture and organisation. Data is extracted from users and used to calculate relevance, make recommendations and target users for advertisements. While bots can and do support this economy, they can also undermine it. In the case of buying bot followers, for instance, this can be a means to generate noise in the collected dataset and blur the perception of the user as a set of behaviours that the platform makes available.
* Where platform logic centralises, *bot logic* fragments
* Where *platform logic* centralises, *bot logic* fragments
Platforms such as Twitter or Facebook are built as centralized systems: the servers on which information is stored are owned by these companies. The servers are triggering the need for growing data center infrastructures throughout the world. Bots, on the other hand, do not require a lot of computational power in order to run. They can be simply executed from the computers of the bot makers themselves. In fact, bots really point to the materiality of the systems on which they run, as researcher Stuart Geiger points out when he talks about *bespoke code*:
> [code that] runs on top of or alongside existing systems instead of being more directly integrated into and run on software-side codebases[^geiger].
* Where platform logic creates distance between user and infrastructure, *bot logic* develops an intimate knowledge of the platform
* Where *platform logic* creates distance between user and infrastructure, *bot logic* develops an intimate knowledge of the platform
If we consider means of communication as means of production[^means], there is a process of alienation that happens on commercial centralised platforms, where the user has no stake in the development of the material conditions of the platform on which they interact and communicate. From this perspective, the making of bots implies a closeness to the platform that is indicated through the understanding of both the sociological and technical systems that determine the usership of a platform. In order to write a bot, as mentioned before, you need to know what kind of actions are allowed and how the bot would be received by the community.
* Where platform logic reinforces habitual behaviour, *bot logic* encourages new habit formation
* Where *platform logic* reinforces habitual behaviour, *bot logic* encourages new habit formation
If we think about a commercial platform as a structure or surface on which actions can take place, these actions are often predefined by the affordances of the platform. However, bots are the automation of certain actions and behaviours. To be able to define these behaviours, a user needs to be provided with the means to alternate the socialities of a platform.

2
content/Track 4 - Bot Logic/3-examples.md

@ -26,7 +26,7 @@ It turned out that most edits made by these IP addresses were fixing punctuation
**OCRbot**
OCRbot[^ocr] is a bot made for Mastodon, which responds to users calling who call it. It is used to run OCR (Optical Character Recognition) on images containing text and it is an especially helpful feature for generated captions for vision impaired people. This example of a bot shows how users can alter the functionalities of a digital infrastructure through a bot. Where there is a lack in the Mastodon interface, this bot can be used to supplement it and in this way increase the accessibility of the site. The code for this bot is available of Github[^ocrcode].
OCRbot[^ocr] is a bot made for Mastodon, which responds to users calling who call it. It is used to run OCR (Optical Character Recognition) on images containing text and it is an especially helpful feature for generated captions for vision impaired people. This example of a bot shows how users can alter the functionalities of a digital infrastructure through a bot. Where there is a lack in the Mastodon interface, bots can be used to supplement it and in this way increase the accessibility of the site. In this case however, most Mastodon interfaces already include a caption text box in the interface. Nonetheless the bot makes up for the failure of users to fill in the captions when adding an image to their posts. The code for this bot is available of Github[^ocrcode].
# Footnotes

2
content/Track 4 - Bot Logic/4-bot-behaviour.md

@ -23,7 +23,7 @@ Below some examples (although this is a non-exhaustive list).
Of course, these action modes can also be executed by people.
It is by no means surprising that many Twitter users are mistaken for bots, or that the term itself has attained a derogatory meaning. However, an interesting phenomenon can be observed on digital infrastructures such as Twitter, where human users have adopted a type of bot behaviour to create networks of dissent and to push activist counter-narratives.
It is by no means surprising that many Twitter users are mistaken for bots, or that the term itself has attained a derogatory meaning. Human users might be called a bot as form of insult. However, an interesting phenomenon can be observed on digital infrastructures such as Twitter, where human users have adopted a type of bot behaviour to create networks of dissent and to push activist counter-narratives.
Such a moment happened recently on Dutch Twitter. In response to the Black Lives Matter protests, extreme right wing politician Geert Wilders posted an image on Twitter on June 5th 2020 using the hashtag #ZwartePietMatters.[^zwartepiet] Following this post, a wave of fancam[^fanpic] users from the k-pop community flooded the hashtag with video recordings of their favourite k-pop stars, making the thread difficult to follow. Such practices are becoming a common phenomenon across the Twitterscape, where fancams are used not only for praising musicians, but instead for derailing and hijacking hashtags these users consider unacceptable.

2
content/Track 6 - Critical Interventions Through Bots (exercise)/4-situated-bot-code.md

@ -11,7 +11,7 @@ We registered an account on botsin.space that can be used in this example script
> This instance exists for people who want to run Mastodon bots, but you are welcome to join if you are a human. Both bots and humans are expected to follow this Code of Conduct. You can learn more about ways to support the costs of this instance.
With this exercise the module will end. We would like to use this opportunity to send you off to another infrastructure, a community-led, public hosting service called *MyBinder*, where you are invited to work with the example script of a Mastodon bot.
We would like to use this opportunity to send you off to another infrastructure, a community-led, public hosting service called *MyBinder*, where you are invited to work with the example script of a Mastodon bot.
---------------------------

22
content/Track 7 - Recap/1-recap.md

@ -0,0 +1,22 @@
Title: Recap of what has happened until now
Slug: 06-s7-step-1
Date: 2020-11-01 12:03
Summary: Overview of what we have been looking at
These different tracks have intersected, overlapped and sometimes diverted from one another, taking us along multiple roads that were looking at
* the potential of infrapunctures to address harms caused by digital infrastructures,
* the differences between digital infrastructures, computational infrastructures and platforms and what kind of friction that brings forward,
* how we can start understanding harms around, within and through computational infrastructures,
* bots as infrastructural embodiment,
* examples of bots as possible infrapunctures,
* the proposed term *bot logic* in relation to platform logic,
* bot behaviours
and two ways to engage with bot logic by writing a fictional scripted dialogue and diving deeper into their materiality by running a simple bot code template which toots on botsin.space.
While this short module is not a programming lesson, a tutorial, or a set of methodologies to understand the possibilities of bots as infrapunctures, we hope that it can point towards a few ways in which bots either support or challenge the relations and interaction that a digital infrastructure makes possible.
Bots are of course not a solution to computationally generated harm, nor are they able to repair infrastructures, but they nonetheless enable certain possibilities to get to know and engage with their material, political and social aspects.
Throughout this module we have tried to trace multiple forms of bot making and thinking with.

2
content/Track 6 - Critical Interventions Through Bots (exercise)/5-end-of-the-module.md → content/Track 7 - Recap/2-end-of-the-module.md

@ -1,5 +1,5 @@
Title: Bots as Digital Infrapunctures
Slug: 05-s6-step-5
Slug: 07-s7-step-2
Date: 2020-11-01 12:05
Summary: End of the module
Loading…
Cancel
Save