adding a seperate intro page for deb in section 1

content/Section 1 - Digital Infrapunctures/1-introduction.md

@@ -25,14 +25,6 @@ Who is an infrastructure bringing together? And who *not*? What are the conditio
 
 And, most importantly, *who* can actually intervene in the design of infrastructures? And *how*?
 
-We invited Deb Verhoeven to respond to the following questions:
-
-* What are digital infrapunctures? 
-* How do we identify stress points in digital infrastructures? 
-* Who can create infrapunctures? 
-* Could you expand on the analogy of acupuncture in relation to infrastructures? 
-* Could you give some examples of infrapunctural interventions? 
-
 <br>
 
 # Footnotes & Further readings

content/Section 1 - Digital Infrapunctures/2-introduction-deb-verhoeven.md

@@ -1,12 +1,14 @@
-Title: Question 1: What are digital infrapunctures? 
-Slug: 02-s1-question-1
+Title: Introduction: Deb Verhoeven
+Slug: 02-s1-introduction-deb-verhoeven
 Date: 2020-11-01 12:01
-Summary: A video contribution by Deb Verhoeven.
+Summary: 
 
 Deb Verhoeven first introduced the term *infrapuncture* in 2016 at a Digital Humanities conference in Oxford. In her talk she gives the example of the Greek and Italian cinemas that appeared in Melbourne before the invention of the video tape and the influence they have had over the influx and organisation of the Italian and Greek immigrants living in Australia at the time. Her research concluded that these small cinemas that only screened subtitled Italian and Greek movies led to an increase in migrant population from those areas. Similarly, the shutting down of a cinema coincided with the dispersion of the immigrant community in the neighbourhood.
 
-In the following video contributions, Deb Verhoeven will unpack the term *infrapunctures*. She will explore how it is a useful departure point for infrastructural change that is benificial for the communities who uses them.
+In the following video contributions, Deb Verhoeven will unpack the term *infrapunctures*. She will explore how it is a useful departure point for infrastructural change that is benificial for the communities who uses them. We invited Deb Verhoeven to respond to the following questions:
 
-<video controls>
-	<source src="https://vvvvvvaria.org/archive/2018-02-16-Extratonality/dennis-not-supercut-yet.mp4" type="video/mp4">
-</video>
+* What are digital infrapunctures? 
+* How do we identify stress points in digital infrastructures? 
+* Who can create infrapunctures? 
+* Could you expand on the analogy of acupuncture in relation to infrastructures? 
+* Could you give some examples of infrapunctural interventions? 

content/Section 1 - Digital Infrapunctures/3-question-1.md

@@ -0,0 +1,8 @@
+Title: Question 1: What are digital infrapunctures? 
+Slug: 03-s1-question-1
+Date: 2020-11-01 12:02
+Summary: A video contribution by Deb Verhoeven.
+
+<video controls>
+	<source src="https://vvvvvvaria.org/archive/2018-02-16-Extratonality/dennis-not-supercut-yet.mp4" type="video/mp4">
+</video>

content/Section 1 - Digital Infrapunctures/4-question-2.md

@@ -1,6 +1,6 @@
 Title: Question 2: How do we identify stress points in digital infrastructures? 
-Slug: 03-s1-question-2
-Date: 2020-11-01 12:02
+Slug: 04-s1-question-2
+Date: 2020-11-01 12:03
 Summary: A video contribution by Deb Verhoeven.
 
 <video>

content/Section 1 - Digital Infrapunctures/5-question-3.md

@@ -1,6 +1,6 @@
 Title: Question 3: Who can create infrapunctures?
-Slug: 04-s1-question-3
-Date: 2020-11-01 12:03
+Slug: 05-s1-question-3
+Date: 2020-11-01 12:04
 Summary: A video contribution by Deb Verhoeven.
 
 <video>

content/Section 6 - Critical Interventions Through Bots (exercise)/2-materiality-of-bots.md

@@ -34,7 +34,7 @@ The term API is an acronym for Application Programming Interface. It is an code-
 
 Taina Bucher[^bucher] defines an API as an infrastructural device that is shaped (and shaping) many different things:
 
-> “Among other things, web APIs encompass: a physicality in terms of the corporeal landscape of infrastructure and technology, through to the economic logics at work (i.e. business models, ownership, licencing of the APIs), functions and services (i.e. access to data), practices of users (i.e. forms of labor, play and collaboration), discursive formations (i.e. statements, knowledge, ideas), rules and norms (i.e. design principles, terms of service, technical standards), as well as social imaginaries and desires.”
+> Among other things, web APIs encompass: a physicality in terms of the corporeal landscape of infrastructure and technology, through to the economic logics at work (i.e. business models, ownership, licencing of the APIs), functions and services (i.e. access to data), practices of users (i.e. forms of labor, play and collaboration), discursive formations (i.e. statements, knowledge, ideas), rules and norms (i.e. design principles, terms of service, technical standards), as well as social imaginaries and desires.
 
 When looking at API's from a technical perspective, we see a set of rules that applications use to communicate with each other. This (apparently) neutral conception is in reality a very complex conglomerate of imaginaries, whether technological, economical or societal.