The different tracks of this module have intersected, overlapped and sometimes diverted from one another. Roads that were not smooth or straight took us along multiple paths that were exploring:
* the differences between the terms *digital infrastructure*, *computational infrastructure* and *platform* and what kind of frictions emerge from the distinctions,
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.
As they do not require to function within server-side conditions and can be run using personal resources, bots create potential for users to express agency within the infrastructure's affordances and possibly even relations between the human and nonhuman actors present.
Bots are of course not a solution to computationally generated harm, nor are they able to repair infrastructures. Let's take for example the dependency of bots on APIs. While there is possibility to run a bot without using the API of an infrastructure, in order to have access to different functionalities than users, most bots will engage with it. It follows that with a change in an infrastructure's internal policy, the bots can easily be rejected. One example of this is the Twitter bot purge from 2018.
Nonetheless, for the purpose of this module, bots enable certain possibilities to get to know and engage with an infrastructure's material, political and social aspects. Bots may point towards ways in which infrastructures could exist differently, sometimes beyond the intent of the makers. In fact, the nonhuman agency of bots is an aspect that we have not touched upon, yet it is another important point of departure.
