Merge branch 'master' of https://git.vvvvvvaria.org/mb/bots-as-digital-infrapunctures

content/Track 2 - Harm in Computational Infrastructures/1-introduction.md

@@ -1,11 +1,10 @@
 Title: Introduction: Harm in Computational Infrastructures
 Slug: 01-s2-introduction
 Date: 2020-11-01 12:00
-Summary: Previously we have become acquainted with a view on *digital infrastructures* that highlights their reparative and connective characteristics. In this track we will trace the term *computational infrastructures,* which forefronts how infrastructures are made from material elements and how they move said elements in the world.
+Summary: Previously we have become acquainted with a view on *digital infrastructures* that highlights their reparative and connective characteristics. In this track we will trace the term *computational infrastructures,* which forefronts how infrastructures are shaped by political, economic and social forces, how they are made from material elements and how they move said elements in the world.
 
 Previously we have become acquainted with a view on *digital infrastructures* that highlights their reparative and connective characteristics. In this track we will trace the term *computational infrastructures*, which forefronts how infrastructures are material systems that move all sorts of elements in the world.
 
 Computational infrastructures are complex entities shaped by different technological, social, economical and political dimensions. As is the case with any type of infrastructure, they come with embedded values. Their specificities and configurations shape the possibilities and restrictions of the whole system, defining what can be built on top of them and what not. The logics of computational infrastructures are shaped by global capital, material components, political values, and in turn shape labour relations, environmental ecosystems, as well as the political economies in which they operate.
 
 To formulate a more precise understanding of what computational infrastructures are, how they operate and what forms of harm they produce, we will introduce the work of Seda Gürses in this track.
-

content/Track 2 - Harm in Computational Infrastructures/2-introduction-seda.md

@@ -1,7 +1,7 @@
 Title: Introduction: Seda Gürses
 Slug: 02-s2-introduction
 Date: 2020-11-01 12:01
-Summary: Computational infrastructures and POTs (Protective Optimization Technologies)
+Summary: An introduction to computational infrastructures and Protective Optimization Technologies (POTs).
 
 Seda Gürses is an Associate Professor in the Department of Multi-Actor Systems at TU Delft at the Faculty of Technology Policy and Management, a member of The Institute for Technology in the Public Interest and an affiliate at the COSIC Group at the Department of Electrical Engineering (ESAT), KU Leuven. Beyond her academic work, she collaborated with artistic initiatives including Constant vzw, Bootlab, De-center, ESC in Brussels, Graz and Berlin. She is currently part of The Institute for Technology in the Public Interest[^titipi], a trans-practice gathering of activists, artists, engineers and theorists initiated by Myriam Aouragh, Helen Pritchard, Femke Snelting and herself.
 
@@ -9,13 +9,13 @@ Seda Gürses' work on *programmable infrastructures*, developed in collaboration
 
 Gürses (et al.) proposes forms of intervention-based optimization practices in the form of POTs: *protective optimization techniques*. The paper critically enquires current optimization approaches, the interests that feed their design and the way in which they displace their societal impact onto the shoulders of other parties and individuals. A POT is introduced as follows:
 
-> POTs provide means for affected parties to address the negative impacts of systems in the environment, expanding avenues for political contestation. POTs intervene from outside the system, do not require service providers to cooperate, and can serve to correct, shift, or expose harms that systems impose on populations and their environments. (2020, 1) 
+> POTs provide means for affected parties to address the negative impacts of systems in the environment, expanding avenues for political contestation. POTs intervene from outside the system, do not require service providers to cooperate, and can serve to correct, shift, or expose harms that systems impose on populations and their environments. (2020, 1)
 
 The work departs from a thorough consideration of multiple forms of *harm* caused by computational infrastructures framed as *externalities*[^externalities]. Examples of such externalities include lack of privacy, discrimination, low wages and surveillance. How a *POT* might engage with them is then illustrated through a range of activist, artistic and deployed examples of repurposed optimization technologies. Following Michael A. Jackson’s theory of requirements engineering, it proposes to approach computational infrastructures as being far more than a technological system alone, thus shifting focus from the system itself to the economical, political and social context in which it operates.
 
 We will introduce the work of Gürses and dive with her into the following questions:
 
-* What are computational infrastructures? 
+* What are computational infrastructures?
 * What are elements that shape (or are shaped by) computational infrastructures?
 * How can we understand the harm caused by computational infrastructures and the systems which deploy them?
 * What interventions are possible to mitigate or eliminate this harm?

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

@@ -1,7 +1,7 @@
 Title: Introduction: Bots
 Slug: 01-s3-introduction
 Date: 2020-11-01 12:00
-Summary: What type of bots are being made?
+Summary: This track will go over an introduction to what bots are, what they do and their importance in shaping power relations on digital infrastructures.
 
 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.
 

content/Track 3 - Introduction to Bots/2-infrastructural-embodiment.md

@@ -1,9 +1,9 @@
 Title: Introduction: Andreas Hepp
 Slug: 02-s3-infrastructural-embodiment
 Date: 2020-11-01 12:01
-Summary: *Communicative bots*, *communicative embodiment* and *infrastructural embodiment*.
+Summary: Unpacking the terms *Communicative bots*, *communicative embodiment* and *infrastructural embodiment*.
 
-Andreas Hepp is Professor for Media and Communications at the ZeMKI (Centre for Media, Communication and Information Research), University of Bremen, Germany. In his 2020 article[^paper], mentioned in the introduction to this chapter, he distinguishes three kinds of *communicative bots*: artificial companions, social bots and work bots. For Hepp, communicative bots are characterised through a double embodiment: a *communicative embodiment*, referring to the bots' human-like representation, and an *infrastructural embodiment*, referring to the bots being embedded in the materiality of the infrastructure on which they are active. 
+Andreas Hepp is Professor for Media and Communications at the ZeMKI (Centre for Media, Communication and Information Research), University of Bremen, Germany. In his 2020 article[^paper], mentioned in the introduction to this chapter, he distinguishes three kinds of *communicative bots*: artificial companions, social bots and work bots. For Hepp, communicative bots are characterised through a double embodiment: a *communicative embodiment*, referring to the bots' human-like representation, and an *infrastructural embodiment*, referring to the bots being embedded in the materiality of the infrastructure on which they are active.
 
 Thinking about the bots in terms of embodiment helps to situate them in relation to digital communication infrastructures and their user base.
 

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

@@ -1,7 +1,7 @@
 Title: Introduction: Bot Logic
 Slug: 01-s4-introduction
 Date: 2020-11-01 12:00
-Summary: Bots as computational infrapunctures.
+Summary: Could bots be a form of digital infrapunctures? Using the proposed concept of *bot logic*, we'll be looking at what kind of user a bot is.
 
 *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.
 

content/Track 6 - Critical Interventions Through Bots (exercise)/1-introduction.md

@@ -1,7 +1,7 @@
 Title: Critical Interventions through Bots (exercise)
 Slug: 01-s6-step-1
 Date: 2020-11-01 12:00
-Summary: Start of the bot-making excercise.
+Summary: In this track we'll be looking at the materiality of bots. Together we'll go over a simple code template which is connected to a bot running on a Mastodon instance.
 
 In this last track of the module we will make a bot in order to get hands on with the language from which bots are made: code. 🤖
 

content/Track 7 - Crossroads/1-recap.md

@@ -1,19 +1,22 @@
 Title: Recap of the different tracks
-Slug: 07-s7-step-1
+Slug: 01-s7-step-1
 Date: 2020-11-01 12:03
-Summary: Here we look at an overview of what we have been discussing in this module.
+Summary: This track is an overview of what we have been discussing in this module.
 
-These different tracks have intersected, overlapped and sometimes diverted from one another, taking us along multiple roads that were looking at:
+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 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,
+* the differences between the terms *digital infrastructure*, *computational infrastructure* and *platform* and what kind of frictions emerge from the distinctions,
 * how we can start understanding harms around, within and through computational infrastructures,
-* bots as infrastructural embodiment,
+* bots as infrastructural embodiments,
 * examples of bots as possible infrapunctures,
 * the proposed term *bot logic* in relation to platform logic,
-* bot behaviours,
+* 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.
+We also proposed two ways to engage with bot logic:
+
+* by writing a fictional dialogue script to consider the social dimensions in which bots are situated,
+* by running a simple code template which toots on the federated Mastodon instance botsin.space to dive deeper into bots' materiality.
 
 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.
 

content/Track 7 - Crossroads/2-end-of-the-module.md

@@ -1,5 +1,5 @@
 Title: Bots as Digital Infrapunctures
-Slug: 07-s7-step-2
+Slug: 02-s7-step-2
 Date: 2020-11-01 12:05
 Summary: Wrap up of the module. Thinking through infrastructural embodiments for times of infrastructural complexity.
 

themes/default/static/css/main.css

@@ -10,7 +10,8 @@ body{
 	letter-spacing: 0.25pt;
 	color: rgba(40,40,40,1);
 	/*background-color: #d0bba0;*/
-	background-color: #ecddcb;
+	/* background-color: #ecddcb; */
+	background-color: #e8d59b;
 }
 h1, h2, h3, h4, h5, h6{
 	font-family: 'Belgika-reg';
@@ -22,7 +23,7 @@ header#banner{
 }
 	header#banner h1{
 		font-family: 'Syne';
-		font-size: 7.5vw;
+		font-size: 110px;
 		line-height:1.25;
 		margin: 0.7em 0;
 	}
@@ -36,8 +37,8 @@ nav#menu{
 	margin:0 0 0 -11em;
 }
 	nav#menu li{
-		width: 10vw;
-		height:10vw;
+		width: 114px;
+		height:10em;
 		margin:1em 0;
 		padding:1em;
 		font-size: 75%;
@@ -50,7 +51,7 @@ nav#menu{
 		vertical-align: middle;
 	}
 	nav#menu li.active{
-		background-color: #95d1e6;
+		background-color: #a4e7ff;
 	}
 	nav#menu li.pagelink{
 		height: 2.5em;
@@ -60,7 +61,7 @@ nav#menu{
 	}
 
 section#content{
-	margin: 4em;
+	margin: 4em 1em;
 }
 article{
 	margin: 3em 0 2em 0;
@@ -68,7 +69,7 @@ article{
 	border-top: 1px solid;
 }
 	article:first-child{
-		background-color: #95d1e6;
+		background-color: #a4e7ff;
 		padding-bottom: 3em;
 		margin-bottom: -3em;
 	}
@@ -125,10 +126,10 @@ ul.navprevnext{
 		width: calc(50% - 17em);
 		height: 150px;
 		top:0;
-		background-color: #95d1e6;
+		background-color: #a4e7ff;
 		border-radius: 1em;
 		padding:1em 3em;
-		font-size: 11pt;
+		font-size: 9pt;
 		line-height: 1.4;
 		list-style: none;
 		border:1px solid black;
@@ -227,9 +228,7 @@ p {
 	word-break: break-word;
 }
 
-
-/* Layout phone */
-@media (max-width:770px) {
+/* @media (max-width:770px) {
 	nav#menu li {
 		width: 50vw;
 		height: 24vw;
@@ -247,7 +246,6 @@ p {
 
 }
 
-/* Layout tablet */
 @media (max-width:1024px) {
 	body {
 		margin-left: 13vw;
@@ -256,4 +254,4 @@ p {
 		nav#menu li {
 			height: 14vw;
 		}
-}
+}  */

themes/default/static/css/mobile-attempt-main.css

@@ -0,0 +1,256 @@
+@import 'fonts.css';
+
+body{
+	margin:2em auto;
+	min-width: 1080px;
+	max-width: 950px;
+	font-family: 'Basker';
+	font-size: 14pt;
+	line-height: 1.7;
+	letter-spacing: 0.25pt;
+	color: rgba(40,40,40,1);
+	/*background-color: #d0bba0;*/
+	background-color: #ecddcb;
+}
+h1, h2, h3, h4, h5, h6{
+	font-family: 'Belgika-reg';
+	margin-top:1.5em;
+}
+header#banner{
+	width: 100%;
+	text-align: center;
+}
+	header#banner h1{
+		font-family: 'Syne';
+		font-size: 7.5vw;
+		line-height:1.25;
+		margin: 0.7em 0;
+	}
+	header#banner h1 a{
+		text-decoration: none;
+		color: darkgoldenrod !important;
+	}
+nav#menu{
+	width: calc(100% + 20em);
+	text-align: center;
+	margin:0 0 0 -11em;
+}
+	nav#menu li{
+		width: 10vw;
+		height:10vw;
+		margin:1em 0;
+		padding:1em;
+		font-size: 75%;
+		line-height: 1.4;
+		color: rgba(40,40,40,1);
+		border:1px solid;
+		border-radius: 1em;
+		list-style: none;
+		display: inline-block;
+		vertical-align: middle;
+	}
+	nav#menu li.active{
+		background-color: #95d1e6;
+	}
+	nav#menu li.pagelink{
+		height: 2.5em;
+	}
+	nav#menu a{
+		text-decoration: none;
+	}
+
+section#content{
+	margin: 4em;
+}
+article{
+	margin: 3em 0 2em 0;
+	padding: 2em 3em 0;
+	border-top: 1px solid;
+}
+	article:first-child{
+		background-color: #95d1e6;
+		padding-bottom: 3em;
+		margin-bottom: -3em;
+	}
+/* start button */
+article button {
+	width: auto;
+	top:1em;
+	margin:1.5em auto;
+	padding:1.5em 3em;
+	background-color: rgba(40,40,40,1);
+	border:1px solid rgba(40,40,40,1);
+	border-radius: 0.5em;
+}
+	article a button{
+		font-family: 'Belgika-reg';
+		text-decoration: none !important;
+		color: white !important;
+		font-size: 16px;
+		letter-spacing: 0.1em;
+	}
+	article a button:hover{
+		cursor: pointer;
+	}
+article h2.page-title a{
+	text-decoration: none;
+}
+
+/* big boxes for the section titles */
+h1.category{
+	width: calc(100% - 4em);
+	background-color: rgba(40,40,40,1);
+	color:white;
+	border-radius: 1em;
+	padding: 2em 2em 3em 2em;
+	margin: 2em 0;
+	font-family: "Basker";
+	font-size: 32px;
+	text-align: center;
+	font-weight: normal;
+}
+
+/* next & prev buttons */
+ul.navprevnext{
+	position: relative;
+	display: inline-block;
+	width: calc(100% - 4em);
+	margin:3em 0 0;
+}
+	ul.navprevnext li.prev,
+	ul.navprevnext li.next,
+	ul.navprevnext li.done,
+	ul.navprevnext li.none{
+		position: relative;
+		width: calc(50% - 17em);
+		height: 150px;
+		top:0;
+		background-color: #95d1e6;
+		border-radius: 1em;
+		padding:1em 3em;
+		font-size: 9pt;
+		line-height: 1.4;
+		list-style: none;
+		border:1px solid black;
+	}
+	ul.navprevnext a{
+		text-decoration: none;
+	}
+	ul.navprevnext li.prev:before,
+	ul.navprevnext li.next:before{
+		display: block;
+		font-style:italic;
+		margin:0 0 1em 0;
+	}
+	ul.navprevnext li.prev:before{
+		content:'←\00a0\00a0\00a0Go to the previous page';
+		margin-left:-1.75em;
+	}
+	ul.navprevnext li.next:before{
+		content:'Go to the next page\00a0\00a0\00a0→';
+		margin-right:-2em;
+		text-align: right;
+	}
+	ul.navprevnext li.none,
+	ul.navprevnext li.prev{
+		float: left;
+		left:-9.5em;
+	}
+	ul.navprevnext li.next,
+	ul.navprevnext li.done{
+		float: right;
+		right: -9.5em;
+	}
+	/* you finished this section */
+	ul.navprevnext li.done{
+		background-color: rgba(40,40,40,1);
+		color: white;
+	}
+	ul.navprevnext li.none{
+		background-color: transparent;
+		color: transparent;
+		border:0;
+	}
+
+.footnote{
+	font-size: smaller;
+}
+footer{
+	font-style: normal;
+	font-size: smaller;
+	clear: both;
+}
+
+/* general elements */
+a,
+a:visited,
+a:hover,
+a:active{
+	color: rgba(40,40,40,1);
+}
+a.nounderline{
+	text-decoration: none;
+}
+
+hr{
+	width: 100%;
+	border:0;
+	border-bottom:1px solid rgba(40,40,40,1);
+	margin:3em auto;
+}
+sup{
+	line-height: 0;
+	font-size: 75%;
+	padding-left: 0.2em;
+}
+img,
+video{
+	width: calc(100% + 6em);
+	margin: 2em 0 2em -3em;
+}
+blockquote{
+	font-style: italic;
+	font-size: 125%;
+	line-height: 1.9;
+}
+pre,
+code{
+	color: #c600c6;
+}
+
+.lastupdate{
+	font-size: smaller;
+	margin:4em 0;
+}
+
+p {
+	word-break: break-word;
+}
+
+/* @media (max-width:770px) {
+	nav#menu li {
+		width: 50vw;
+		height: 24vw;
+		font-size: 2em;
+		margin: 1em 0.1em;
+	}
+
+	header#banner h1 {
+		font-size: 10vw;
+	}
+
+	body{
+		margin-left: 9.4vw;
+	}
+
+}
+
+@media (max-width:1024px) {
+	body {
+		margin-left: 13vw;
+	}
+
+		nav#menu li {
+			height: 14vw;
+		}
+}  */

themes/default/templates/base.html

@@ -6,15 +6,16 @@
 	<meta charset="utf-8" />
 	<meta name="generator" content="Pelican" />
 	<link rel="stylesheet" type="text/css" href="{{ SITEURL }}/{{ THEME_STATIC_DIR }}/css/{{ CSS_FILE }}" />
+	<!-- <meta name="viewport" content="width=device-width, initial-scale=1"> -->
 	{% endblock head %}
 </head>
 
-<body id="index" class="home"> 
+<body id="index" class="home">
 
 	<header id="banner" class="body">
 		<h1><a href="{{ SITEURL }}/">{{ SITENAME }}{% if SITESUBTITLE %} <strong>{{ SITESUBTITLE }}</strong>{% endif %}</a></h1>
 	</header>
-	
+
 	<nav id="menu"><ul>
 	{% for title, link in MENUITEMS %}
 		<a href="{{ link }}"><li>{{ title }}</li></a>
@@ -35,7 +36,7 @@
 	{% block content %}
 	{% endblock %}
 	</section>
-	
+
 	<footer id="contentinfo" class="body">
 		<hr>
 	</footer>