User:Kim/writing/Thesis outline draft - Revision history

Kim: /* Intro */

2025-10-15T19:47:07Z

Intro

← Older revision		Revision as of 21:47, 15 October 2025
Line 16:		Line 16:
	==step 2==		==step 2==
	===Intro===		===Intro===
	In this text I will examine the role of meta data <ref name=":1" /> <ref name=":2" /> in publishing practices through the lense of invisibility and separation of labor. I will look at historical developments in the production of text through early forms of markup such as marginalia and the pecia system <ref name=":3" /> and consider different digital characteristics for instance source code comments or protocols		In this text I will examine the role of meta data <ref name=":1" /> <ref name=":2" /> in publishing practices through the lense of invisibility and separation of labor. I will look at historical developments in the production of text through early forms of markup such as marginalia and the pecia system <ref name=":3" /> and consider different digital characteristics for instance source code comments or protocols.

	Later I will turn towards ~~specifically including~~ meta data in digital/hybrid publishing projects, not only as means to an end of production but making them part of the text, the body of work at hand.		Later I will turn towards the inclusion of meta data, specifically in digital/hybrid publishing projects, not only as means to an end of production but making them part of the text, the body of work at hand.

	In the last part of the introduction I will define meta-data (or what ever terminology I come up with for this), and a contextualize my interests in-, and wider relevance of this text.		In the last part of the introduction I will define meta-data (or what ever terminology I come up with for this), and a contextualize my interests in-, and wider relevance of this text.
	===KI 1 invisibility===		===KI 1 invisibility===
	invisibility of 'software' <ref>Wendy Hui Kyong Chun "On Software, or the persistence of visual knowledge"</ref> culture of ~~compliance (resulting from prescriptive technologies)~~ enforcing todays user condition (as opposed to programmer <ref>Melanie Hoff "Always Already Programming"</ref> but also as passive, dependent~~, convenience~~ ... witfully outlined by Silvio Lorusso "User Condition" <ref>https://theusercondition.computer/</ref>)		In this chapter I wan to look at invisibility: of 'software' <ref>Wendy Hui Kyong Chun "On Software, or the persistence of visual knowledge"</ref> or in computation in general. Companies instrumentalize culture of convenience enforcing todays user condition (as opposed to programmer <ref>Melanie Hoff "Always Already Programming"</ref> but also as passive, dependent ... witfully outlined by Silvio Lorusso "User Condition" <ref>https://theusercondition.computer/</ref> ) through fragmentation of processes and seamless interactions.

	also had some ideas about interfaces <ref>Galloway, the interface effect, especially ''chapter 1: unworkable interface,'' where he inquires interfaces as windows and doors and general questions of visibility (seamfullness) as much as functionality (un-productiveness, un-workability) of those</ref>. invisibility of interface <ref>Donald Norman "Why Interfaces dont work"</ref>, ~~whats~~ their role here?, ~~bc thats~~ how we see (inside) and interact with a computer?		also had some ideas about interfaces <ref>Galloway, the interface effect, especially ''chapter 1: unworkable interface,'' where he inquires interfaces as windows and doors and general questions of visibility (seamfullness) as much as functionality (un-productiveness, un-workability) of those</ref>. invisibility of interface <ref>Donald Norman "Why Interfaces dont work"</ref>, what is their role here?, interfaces are how we see (inside) and interact with a computer.

	ambiguity of visibility: its not always be good to be visible / legible (to whom? / whose benefit?)		It is then important to bring up ambiguity of visibility: its not always good to be visible / legible, but has to be viewed in context. visible to whom? and for whose benefit?
	# include "the right to opacity" <ref>Édouard Glissant called for a “right to opacity” throughout his works "Poetics of Relation", "Philosophy of Relation" and "Caribbean Discourse". I encountered the concept in "Imperfect Solidarities" by Aruna D'Souza, where she describes it as the right to remain intranslatable and unrecorded into western thought.</ref> bc visibility must be understood contextually. could "right to opacity" also have implications for this specific technology / practice of publishing i am discussing?		# include "the right to opacity" <ref>Édouard Glissant called for a “right to opacity” throughout his works "Poetics of Relation", "Philosophy of Relation" and "Caribbean Discourse". I encountered the concept in "Imperfect Solidarities" by Aruna D'Souza, where she describes it as the right to remain intranslatable and unrecorded into western thought.</ref> bc visibility must be understood contextually. could "right to opacity" also have implications for this specific technology / practice of publishing i am discussing?
	# consider what it means to be (hyper-) legible. meta data provides additional textual information, that it is important to question, for whom? Issue machine readability and indexing / scraping for LLMs and SEO.		# consider what it means to be (hyper-) legible. meta data provides additional textual information, that it is important to question, for whom? Issue machine readability and indexing / scraping for LLMs and SEO.
	===KI 2 Paratexts===		===KI 2 Paratexts===
	Paratexts: historically conceptualized for print / literature (~~include~~ page numbers, headers, pre-and post faces, footnotes and other marginalia ...) - possibilities for digital paratext?, What implications do paratexts hold for present day digital / hybrid publishing? >> "paratext mediates between text and reader", what mediates relation between text and user?<br>		Paratexts are historically conceptualized for print / literature (e.g. page numbers, headers, pre-and post faces, footnotes and other marginalia ...) I would here like to examine possibilities for digital paratext: What implications do paratexts hold for present day digital / hybrid publishing? If "paratext mediates between text and reader", what mediates relation between text and user?<br>
	<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>		<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>
	===KI 3 Labor===		===KI 3 Labor===
Line 54:		Line 54:

	===Conclusion===		===Conclusion===
	* meta-data in publishing as a possibility for resisting (invisibility)		* ''meta-data in publishing as a possibility for resisting (invisibility)''
	* the program is part of the writing		* ''the program is part of the writing''
	* making apparent software, process, how we write but also are written by technology		* ''making apparent software, process, how we write but also are written by technology''

	==References==		==References==

Kim: /* KI 3 Labor */

2025-10-15T16:01:22Z

KI 3 Labor

← Older revision		Revision as of 18:01, 15 October 2025
Line 33:		Line 33:
	<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>		<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>
	===KI 3 Labor===		===KI 3 Labor===
	holistic- vs prescriptive technologies and how the later enabled a division of labor <ref>in "Dividing and Sharing" Femke Snelting writes on the division of labor as a consequence of the separation of design from content in web programming (and standardization) https://gitlab.com/km_kt/xp-reader/-/blob/main/SI26/dividing-and-sharing.md?ref_type=heads#divisions-of-labour</ref> ~~(here also: using early markup "pecia system" fostered division of labor in print production)~~ resulting in opaque processes and culture of compliance. I here also want to refer to "< ? ~~p h p~~ > Invisible Code and the Mystique of Web Writing" <ref name=":0">"<?php> - invisible code and the mystique of web writing" in "From A to <A> - Keywords of Markup" https://gitlab.com/km_kt/xp-reader/-/blob/main/browsing/from-a-to-%3Ca%3E.md?ref_type=heads#php---invisible-code-and-the-mystique-of-web-writing</ref>, especially its point about the invisibility of server side writing (such as php, which is written but never viewed by the end user, opposed to e.g. html which you can read in the web inspector).		holistic- vs prescriptive technologies and how the later enabled a division of labor <ref>in "Dividing and Sharing" Femke Snelting writes on the division of labor as a consequence of the separation of design from content in web programming (and standardization) https://gitlab.com/km_kt/xp-reader/-/blob/main/SI26/dividing-and-sharing.md?ref_type=heads#divisions-of-labour</ref> resulting in opaque processes and culture of compliance. I here also want to refer to "<? php > Invisible Code and the Mystique of Web Writing" <ref name=":0">"<?php> - invisible code and the mystique of web writing" in "From A to <A> - Keywords of Markup" https://gitlab.com/km_kt/xp-reader/-/blob/main/browsing/from-a-to-%3Ca%3E.md?ref_type=heads#php---invisible-code-and-the-mystique-of-web-writing</ref>, especially its point about the invisibility of server side writing (such as php, which is written but never viewed by the end user, opposed to e.g. html which you can read in the web inspector). In this section I also want to lay out a brief history of text production starting with copying practices in the manuscript era that involved an early form of markup.

	===KI 4 (?)===		===KI 4 (?)===

Kim: /* KI 4 (?) */

2025-10-15T15:55:20Z

KI 4 (?)

← Older revision		Revision as of 17:55, 15 October 2025
Line 7:		Line 7:
	I aim to write a text that is concise, yet playful in its form. It will be about the role of meta data <ref name=":1">or information? this lets me think about how information is formatted data - what exactly am I aiming for in this case?</ref> <ref name=":2">but for sure "paratext"</ref> in (post) digital publishing practices. I will explore historical developments in the production of text by looking at early forms of markup such as marginalia and the pecia system <ref name=":3">The Pecia system was developed in the 13th century in the so called Manuscript culture - a time in between oral and print based knowledge production, preservation and circulation. The Pecia system allowed for books to be split in several parts (peciae) which could then be transcribed by several copiers, working simultaneously, producing a copy in a significantly shorter amount of time than a single person working alone. Pecia marks were crucial to this whole process as they allowed for communication between copiers.</ref>, different digital characteristics for instance source code comments or protocols and will finally propose version control software for (collaborative, experimental) writing and making public. The meta data of the present text is a crucial part of the text and the process of writing itself.		I aim to write a text that is concise, yet playful in its form. It will be about the role of meta data <ref name=":1">or information? this lets me think about how information is formatted data - what exactly am I aiming for in this case?</ref> <ref name=":2">but for sure "paratext"</ref> in (post) digital publishing practices. I will explore historical developments in the production of text by looking at early forms of markup such as marginalia and the pecia system <ref name=":3">The Pecia system was developed in the 13th century in the so called Manuscript culture - a time in between oral and print based knowledge production, preservation and circulation. The Pecia system allowed for books to be split in several parts (peciae) which could then be transcribed by several copiers, working simultaneously, producing a copy in a significantly shorter amount of time than a single person working alone. Pecia marks were crucial to this whole process as they allowed for communication between copiers.</ref>, different digital characteristics for instance source code comments or protocols and will finally propose version control software for (collaborative, experimental) writing and making public. The meta data of the present text is a crucial part of the text and the process of writing itself.

	===2. Outline (three) key issues you want to explore===		===2. Outline (three) key issues (KI) you want to explore===
	# hiddeness (veiled, closed source, seamless) in present day technology/ interfaces but also in the sense of invisible labor (in writing, rendering, reading?)		# hiddeness (veiled, closed source, seamless) in present day technology/ interfaces but also in the sense of invisible labor (in writing, rendering, reading?)
	# paratexts		# paratexts
Line 29:		Line 29:
	# include "the right to opacity" <ref>Édouard Glissant called for a “right to opacity” throughout his works "Poetics of Relation", "Philosophy of Relation" and "Caribbean Discourse". I encountered the concept in "Imperfect Solidarities" by Aruna D'Souza, where she describes it as the right to remain intranslatable and unrecorded into western thought.</ref> bc visibility must be understood contextually. could "right to opacity" also have implications for this specific technology / practice of publishing i am discussing?		# include "the right to opacity" <ref>Édouard Glissant called for a “right to opacity” throughout his works "Poetics of Relation", "Philosophy of Relation" and "Caribbean Discourse". I encountered the concept in "Imperfect Solidarities" by Aruna D'Souza, where she describes it as the right to remain intranslatable and unrecorded into western thought.</ref> bc visibility must be understood contextually. could "right to opacity" also have implications for this specific technology / practice of publishing i am discussing?
	# consider what it means to be (hyper-) legible. meta data provides additional textual information, that it is important to question, for whom? Issue machine readability and indexing / scraping for LLMs and SEO.		# consider what it means to be (hyper-) legible. meta data provides additional textual information, that it is important to question, for whom? Issue machine readability and indexing / scraping for LLMs and SEO.
	===~~KI2~~ Paratexts===		===KI 2 Paratexts===
	Paratexts: historically conceptualized for print / literature (include page numbers, headers, pre-and post faces, footnotes and other marginalia ...) - possibilities for digital paratext?, What implications do paratexts hold for present day digital / hybrid publishing? >> "paratext mediates between text and reader", what mediates relation between text and user?<br>		Paratexts: historically conceptualized for print / literature (include page numbers, headers, pre-and post faces, footnotes and other marginalia ...) - possibilities for digital paratext?, What implications do paratexts hold for present day digital / hybrid publishing? >> "paratext mediates between text and reader", what mediates relation between text and user?<br>
	<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>		<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>
	===KI 3 Labor===		===KI 3 Labor===
	holistic- vs prescriptive technologies and division of labor <ref>in "Dividing and Sharing" Femke Snelting writes on the division of labor as a consequence of the separation of design from content in web programming (and standardization) https://gitlab.com/km_kt/xp-reader/-/blob/main/SI26/dividing-and-sharing.md?ref_type=heads#divisions-of-labour</ref> (here also: using early markup "pecia system" ~~enabled~~ division of labor in print production) resulting in opaque processes and culture of compliance, refer to ~~php key text~~ <ref name=":0">"<?php> - invisible code and the mystique of web writing" in "From A to <A> - Keywords of Markup" https://gitlab.com/km_kt/xp-reader/-/blob/main/browsing/from-a-to-%3Ca%3E.md?ref_type=heads#php---invisible-code-and-the-mystique-of-web-writing</ref> ~~and~~ its point about server side writing ~~and invisible labor <mark>add more explicit ref here</mark>~~		holistic- vs prescriptive technologies and how the later enabled a division of labor <ref>in "Dividing and Sharing" Femke Snelting writes on the division of labor as a consequence of the separation of design from content in web programming (and standardization) https://gitlab.com/km_kt/xp-reader/-/blob/main/SI26/dividing-and-sharing.md?ref_type=heads#divisions-of-labour</ref> (here also: using early markup "pecia system" fostered division of labor in print production) resulting in opaque processes and culture of compliance. I here also want to refer to "< ? p h p > Invisible Code and the Mystique of Web Writing" <ref name=":0">"<?php> - invisible code and the mystique of web writing" in "From A to <A> - Keywords of Markup" https://gitlab.com/km_kt/xp-reader/-/blob/main/browsing/from-a-to-%3Ca%3E.md?ref_type=heads#php---invisible-code-and-the-mystique-of-web-writing</ref>, especially its point about the invisibility of server side writing (such as php, which is written but never viewed by the end user, opposed to e.g. html which you can read in the web inspector).

	===KI 4 (?)===		===KI 4 (?)===

Kim: /* KI 4 (?) */

2025-10-15T15:41:36Z

KI 4 (?)

← Older revision		Revision as of 17:41, 15 October 2025
Line 36:		Line 36:

	===KI 4 (?)===		===KI 4 (?)===
	~~<mark>~~i feel this chapter should contain more of my own stand point / towards (end) thesis~~</mark>~~ <br>		''i feel this chapter should contain more of my own stand point / towards (end) thesis <br>
	''why am i writing about this?''		why am i writing about this?''
	* ''pushing against fragmentalization on the side of production (user / developer) and use (hiddenness / black box of today technology) as those are instrumentalized and beneficial for few''		* ''pushing against fragmentalization on the side of production (user / developer) and use (hiddenness / black box of today technology) as those are instrumentalized and beneficial for few''
	* ''notion of hidden hides non-canon histories and voices in technology, hides uncertainty and inconsistency <ref>thinking of Johanna Druckers "Performative Materiality and Theoretical Approches to Interface" in which the author arguments towards interfaces that render visible and affirm acts of interpretation</ref> while portraying technology as smooth, efficient and friendly''		* ''notion of hidden hides non-canon histories and voices in technology, hides uncertainty and inconsistency <ref>thinking of Johanna Druckers "Performative Materiality and Theoretical Approches to Interface" in which the author arguments towards interfaces that render visible and affirm acts of interpretation</ref> while portraying technology as smooth, efficient and friendly''

Kim: /* KI 4 (?) */

2025-10-15T11:12:20Z

KI 4 (?)

← Older revision		Revision as of 13:12, 15 October 2025
Line 36:		Line 36:

	===KI 4 (?)===		===KI 4 (?)===
	i feel this chapter should contain more of my own stand point / towards (end) thesis <br>		<mark>i feel this chapter should contain more of my own stand point / towards (end) thesis</mark> <br>
	''why am i writing about this?''		''why am i writing about this?''
	* ''pushing against fragmentalization on the side of production (user / developer) and use (hiddenness / black box of today technology) as those are instrumentalized and beneficial for few''		* ''pushing against fragmentalization on the side of production (user / developer) and use (hiddenness / black box of today technology) as those are instrumentalized and beneficial for few''
Line 52:		Line 52:

	I could then introduce git as infrastructure for programming work. in the sense of version control it also relates to the laborious tasks of programming (especially the writing of commit -m, which some have a system for but most pose a burden to overcome).		I could then introduce git as infrastructure for programming work. in the sense of version control it also relates to the laborious tasks of programming (especially the writing of commit -m, which some have a system for but most pose a burden to overcome).

	===Conclusion===		===Conclusion===
	* meta-data in publishing as a possibility for resisting (invisibility)		* meta-data in publishing as a possibility for resisting (invisibility)

Kim: /* Key issue 1 = chapter 1 (invisibility) */

2025-10-15T11:11:53Z

Key issue 1 = chapter 1 (invisibility)

← Older revision		Revision as of 13:11, 15 October 2025
Line 15:		Line 15:

	==step 2==		==step 2==
	===Intro ~~(what is this text about?)~~===		===Intro===
	In this text I will examine the role of meta data <ref name=":1" /> <ref name=":2" /> in publishing practices through the lense of invisibility and separation of labor. I will look at historical developments in the production of text through early forms of markup such as marginalia and the pecia system <ref name=":3" /> and consider different digital characteristics for instance source code comments or protocols		In this text I will examine the role of meta data <ref name=":1" /> <ref name=":2" /> in publishing practices through the lense of invisibility and separation of labor. I will look at historical developments in the production of text through early forms of markup such as marginalia and the pecia system <ref name=":3" /> and consider different digital characteristics for instance source code comments or protocols

Line 21:		Line 21:

	In the last part of the introduction I will define meta-data (or what ever terminology I come up with for this), and a contextualize my interests in-, and wider relevance of this text.		In the last part of the introduction I will define meta-data (or what ever terminology I come up with for this), and a contextualize my interests in-, and wider relevance of this text.
	===~~Key issue~~ 1 ~~= chapter 1 (~~invisibility)===		===KI 1 invisibility===
	~~ambiguity of visibility: its not always be good to be visible / legible (to whom? / whose benefit?)~~
	# include "the right to opacity" <ref>Édouard Glissant called for a “right to opacity” throughout his works "Poetics of Relation", "Philosophy of Relation" and "Caribbean Discourse". I encountered the concept in "Imperfect Solidarities" by Aruna D'Souza, where she describes it as the right to remain intranslatable and unrecorded into western thought.</ref> bc visibility must be understood contextually. could "right to opacity" also have implications for this specific technology / practice of publishing i am discussing?
	~~# write about being legible, bc meta data is additional text (for whom?) write about machine readability and indexing / scraping~~
	invisibility of 'software' <ref>Wendy Hui Kyong Chun "On Software, or the persistence of visual knowledge"</ref> culture of compliance (resulting from prescriptive technologies) enforcing todays user condition (as opposed to programmer <ref>Melanie Hoff "Always Already Programming"</ref> but also as passive, dependent, convenience ... witfully outlined by Silvio Lorusso "User Condition" <ref>https://theusercondition.computer/</ref>)		invisibility of 'software' <ref>Wendy Hui Kyong Chun "On Software, or the persistence of visual knowledge"</ref> culture of compliance (resulting from prescriptive technologies) enforcing todays user condition (as opposed to programmer <ref>Melanie Hoff "Always Already Programming"</ref> but also as passive, dependent, convenience ... witfully outlined by Silvio Lorusso "User Condition" <ref>https://theusercondition.computer/</ref>)

	also had some ideas about interfaces <ref>Galloway, the interface effect, especially ''chapter 1: unworkable interface,'' where he inquires interfaces as windows and doors and general questions of visibility (seamfullness) as much as functionality (un-productiveness, un-workability) of those</ref>. invisibility of interface <ref>Donald Norman "Why Interfaces dont work"</ref>, whats their role here?, bc thats how we see (inside) and interact with a computer?		also had some ideas about interfaces <ref>Galloway, the interface effect, especially ''chapter 1: unworkable interface,'' where he inquires interfaces as windows and doors and general questions of visibility (seamfullness) as much as functionality (un-productiveness, un-workability) of those</ref>. invisibility of interface <ref>Donald Norman "Why Interfaces dont work"</ref>, whats their role here?, bc thats how we see (inside) and interact with a computer?

	===~~Key issue 2 = chapter 2 (~~Paratexts)===		ambiguity of visibility: its not always be good to be visible / legible (to whom? / whose benefit?)
			# include "the right to opacity" <ref>Édouard Glissant called for a “right to opacity” throughout his works "Poetics of Relation", "Philosophy of Relation" and "Caribbean Discourse". I encountered the concept in "Imperfect Solidarities" by Aruna D'Souza, where she describes it as the right to remain intranslatable and unrecorded into western thought.</ref> bc visibility must be understood contextually. could "right to opacity" also have implications for this specific technology / practice of publishing i am discussing?
			# consider what it means to be (hyper-) legible. meta data provides additional textual information, that it is important to question, for whom? Issue machine readability and indexing / scraping for LLMs and SEO.
			===KI2 Paratexts===
	Paratexts: historically conceptualized for print / literature (include page numbers, headers, pre-and post faces, footnotes and other marginalia ...) - possibilities for digital paratext?, What implications do paratexts hold for present day digital / hybrid publishing? >> "paratext mediates between text and reader", what mediates relation between text and user?<br>		Paratexts: historically conceptualized for print / literature (include page numbers, headers, pre-and post faces, footnotes and other marginalia ...) - possibilities for digital paratext?, What implications do paratexts hold for present day digital / hybrid publishing? >> "paratext mediates between text and reader", what mediates relation between text and user?<br>
	<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>		<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>
	===KI 3 = Labor===		===KI 3 Labor===
	holistic- vs prescriptive technologies and division of labor <ref>in "Dividing and Sharing" Femke Snelting writes on the division of labor as a consequence of the separation of design from content in web programming (and standardization) https://gitlab.com/km_kt/xp-reader/-/blob/main/SI26/dividing-and-sharing.md?ref_type=heads#divisions-of-labour</ref> (here also: using early markup "pecia system" enabled division of labor in print production) resulting in opaque processes and culture of compliance, refer to php key text <ref name=":0">"<?php> - invisible code and the mystique of web writing" in "From A to <A> - Keywords of Markup" https://gitlab.com/km_kt/xp-reader/-/blob/main/browsing/from-a-to-%3Ca%3E.md?ref_type=heads#php---invisible-code-and-the-mystique-of-web-writing</ref> and its point about server side writing and invisible labor <mark>add more explicit ref here</mark>		holistic- vs prescriptive technologies and division of labor <ref>in "Dividing and Sharing" Femke Snelting writes on the division of labor as a consequence of the separation of design from content in web programming (and standardization) https://gitlab.com/km_kt/xp-reader/-/blob/main/SI26/dividing-and-sharing.md?ref_type=heads#divisions-of-labour</ref> (here also: using early markup "pecia system" enabled division of labor in print production) resulting in opaque processes and culture of compliance, refer to php key text <ref name=":0">"<?php> - invisible code and the mystique of web writing" in "From A to <A> - Keywords of Markup" https://gitlab.com/km_kt/xp-reader/-/blob/main/browsing/from-a-to-%3Ca%3E.md?ref_type=heads#php---invisible-code-and-the-mystique-of-web-writing</ref> and its point about server side writing and invisible labor <mark>add more explicit ref here</mark>

	===~~Key issue 4 = chapter~~ 4===		===KI 4 (?)===
	i feel this chapter should contain more of my own stand point / towards (end) thesis <br>		i feel this chapter should contain more of my own stand point / towards (end) thesis <br>
	''why am i writing about this?''		''why am i writing about this?''
Line 42:		Line 42:
	* ''highlighting that writing technologies (print and digital) have contiguous history and are not opposed to another''		* ''highlighting that writing technologies (print and digital) have contiguous history and are not opposed to another''
	* ''whats the role of labor in all this?''		* ''whats the role of labor in all this?''
	'''~~publishing otherwise~~:'''		'''community / tools:'''

	Move away from proprietary, bloated platforms and applications. Highlight the necessity of agency and collective autonomy both in the process of creation and over public objects. Discuss adjacent tools and attempts (octomode etc). Framing my attempt of making the hidden visible as possibility for breaking with closed off objects discussed in chapter 1. Here introduce git and version control: excurs into history and version control, socio-cultural embededdness of git, present gitpub project.		Move away from proprietary, bloated platforms and applications. Highlight the necessity of agency and collective autonomy both in the process of creation and over public objects. Discuss adjacent tools and attempts (octomode etc). Framing my attempt of making the hidden visible as possibility for breaking with closed off objects discussed in chapter 1. Here introduce git and version control: excurs into history and version control, socio-cultural embededdness of git, present gitpub project.

Kim: /* KI 3 = Labor */

2025-10-15T11:05:47Z

KI 3 = Labor

← Older revision		Revision as of 13:05, 15 October 2025
Line 33:		Line 33:
	<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>		<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>
	===KI 3 = Labor===		===KI 3 = Labor===
	~~labor:~~ holistic- vs prescriptive technologies and division of labor <ref>in "Dividing and Sharing" Femke Snelting writes on the division of labor as a consequence of the separation of design from content in web programming (and standardization) https://gitlab.com/km_kt/xp-reader/-/blob/main/SI26/dividing-and-sharing.md?ref_type=heads#divisions-of-labour</ref> (here also: using early markup "pecia system" enabled division of labor in print production) resulting in opaque processes and culture of compliance, refer to php key text <ref name=":0">"<?php> - invisible code and the mystique of web writing" in "From A to <A> - Keywords of Markup" https://gitlab.com/km_kt/xp-reader/-/blob/main/browsing/from-a-to-%3Ca%3E.md?ref_type=heads#php---invisible-code-and-the-mystique-of-web-writing</ref> and its point about server side writing and invisible labor		holistic- vs prescriptive technologies and division of labor <ref>in "Dividing and Sharing" Femke Snelting writes on the division of labor as a consequence of the separation of design from content in web programming (and standardization) https://gitlab.com/km_kt/xp-reader/-/blob/main/SI26/dividing-and-sharing.md?ref_type=heads#divisions-of-labour</ref> (here also: using early markup "pecia system" enabled division of labor in print production) resulting in opaque processes and culture of compliance, refer to php key text <ref name=":0">"<?php> - invisible code and the mystique of web writing" in "From A to <A> - Keywords of Markup" https://gitlab.com/km_kt/xp-reader/-/blob/main/browsing/from-a-to-%3Ca%3E.md?ref_type=heads#php---invisible-code-and-the-mystique-of-web-writing</ref> and its point about server side writing and invisible labor <mark>add more explicit ref here</mark>

	===Key issue 4 = chapter 4===		===Key issue 4 = chapter 4===

Kim: /* Key issue 4 = chapter 4 */

2025-10-15T11:04:20Z

Key issue 4 = chapter 4

← Older revision		Revision as of 13:04, 15 October 2025
Line 37:		Line 37:
	===Key issue 4 = chapter 4===		===Key issue 4 = chapter 4===
	i feel this chapter should contain more of my own stand point / towards (end) thesis <br>		i feel this chapter should contain more of my own stand point / towards (end) thesis <br>
	why am i writing about this?		''why am i writing about this?''
	* pushing against fragmentalization on the side of production (user / developer) and use (hiddenness / black box of today technology) as those are instrumentalized and beneficial for few		* ''pushing against fragmentalization on the side of production (user / developer) and use (hiddenness / black box of today technology) as those are instrumentalized and beneficial for few''
	* notion of hidden hides non-canon histories and voices in technology, hides uncertainty and inconsistency <ref>thinking of Johanna Druckers "Performative Materiality and Theoretical Approches to Interface" in which the author arguments towards interfaces that render visible and affirm acts of interpretation</ref> while portraying technology as smooth, efficient and friendly		* ''notion of hidden hides non-canon histories and voices in technology, hides uncertainty and inconsistency <ref>thinking of Johanna Druckers "Performative Materiality and Theoretical Approches to Interface" in which the author arguments towards interfaces that render visible and affirm acts of interpretation</ref> while portraying technology as smooth, efficient and friendly''
	* highlighting that writing technologies (print and digital) have contiguous history and are not opposed to another		* ''highlighting that writing technologies (print and digital) have contiguous history and are not opposed to another''
	* whats the role of labor in all this?		* ''whats the role of labor in all this?''
	'''publishing otherwise:'''		'''publishing otherwise:'''

Kim: /* Key issue 4 = chapter 4 */

2025-10-15T11:03:49Z

Key issue 4 = chapter 4

← Older revision		Revision as of 13:03, 15 October 2025
Line 38:		Line 38:
	i feel this chapter should contain more of my own stand point / towards (end) thesis <br>		i feel this chapter should contain more of my own stand point / towards (end) thesis <br>
	why am i writing about this?		why am i writing about this?
	* pushing against fragmentalization of: user / developer~~, against hidenness~~ / black box of today technology,		* pushing against fragmentalization on the side of production (user / developer) and use (hiddenness / black box of today technology) as those are instrumentalized and beneficial for few
	* notion of hidden hides non canon histories and voices in technology, hides uncertainty and inconsistency <ref>thinking of Johanna Druckers "Performative Materiality and Theoretical Approches to Interface" in which the author arguments towards interfaces that render visible and affirm acts of interpretation</ref>		* notion of hidden hides non-canon histories and voices in technology, hides uncertainty and inconsistency <ref>thinking of Johanna Druckers "Performative Materiality and Theoretical Approches to Interface" in which the author arguments towards interfaces that render visible and affirm acts of interpretation</ref> while portraying technology as smooth, efficient and friendly
	* highlighting that writing technologies (print and digital) have contiguous history and are not opposed to another		* highlighting that writing technologies (print and digital) have contiguous history and are not opposed to another
	* whats the role of labor in all this?		* whats the role of labor in all this?
Line 47:		Line 47:

	or '''Infrastructure:'''<br>		or '''Infrastructure:'''<br>
	The last chapter could also have a rather infrastructural focus through which we arrive at the git software and gitpub ~~(which~~ would serve as examples for my argument). Infrastructure is commonly perceived as invisible <ref>S. Lee Star asserts that Infrastructures only become visible when they break, a claim that Brian Larkin counters in "Politics and Poetics of Infrastructure" while raising the importance of examining how this apparent ''opacity'' of infrastructures is instrumentailized and why.</ref> what would my take or understanding of infrastructure be in this context? To some extend, it relates to paratext, which enables circulation and mediates a relationship/ action, just as infrastructure does. ~~But infrastructure here must also be seen from a more technical perspective. (wait, am I using the terms ''infrastructure'' and technology ''synonymously'' right now?)~~		The last chapter could also have a rather infrastructural focus through which we arrive at the git software and gitpub, both would serve as examples for my argument.
	* git is interesting bc it is connected to labor of programming (especially the writing of commit -m) it carries quite a lot of invisibility in itself

			Infrastructure is commonly perceived as invisible <ref>S. Lee Star asserts that Infrastructures only become visible when they break, a claim that Brian Larkin counters in "Politics and Poetics of Infrastructure" while raising the importance of examining how this apparent ''opacity'' of infrastructures is instrumentailized and why.</ref> what would my take or understanding of infrastructure be in this context? To some extend, it relates to paratext, which enables circulation and mediates a relationship/ action, just as infrastructure does. But infrastructure here must also be seen from a more technical perspective, relating to protocol and physical artifacts. (wait, am I using the terms ''infrastructure'' and ''technology'' synonymously right now?)

	''the ~~program is part~~ of the writing''		I could then introduce git as infrastructure for programming work. in the sense of version control it also relates to the laborious tasks of programming (especially the writing of commit -m, which some have a system for but most pose a burden to overcome).

	~~''making apparent software~~, ~~process, how we write~~ but ~~also are written by technology''~~

	===Conclusion===		===Conclusion===
	* meta-data in publishing as a possibility for resisting (invisibility)		* meta-data in publishing as a possibility for resisting (invisibility)
			* the program is part of the writing
			* making apparent software, process, how we write but also are written by technology

	==References==		==References==

Kim: /* Key issue 4 = chapter 4 (publishing otherwise) (infrastructures) */

2025-10-15T10:47:16Z

Key issue 4 = chapter 4 (publishing otherwise) (infrastructures)

← Older revision		Revision as of 12:47, 15 October 2025
Line 33:		Line 33:
	<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>		<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>
	===KI 3 = Labor===		===KI 3 = Labor===
	labor: holistic- vs prescriptive technologies and division of labor <ref>in "Dividing and Sharing" Femke Snelting writes on the division of labor as a consequence of the separation of design from content in web programming (and standardization) https://gitlab.com/km_kt/xp-reader/-/blob/main/SI26/dividing-and-sharing.md?ref_type=heads#divisions-of-labour</ref> (here also: using early markup "pecia system" enabled division of labor in print production) <ref name=":0">"<?php> - invisible code and the mystique of web writing" in "From A to <A> - Keywords of Markup" https://gitlab.com/km_kt/xp-reader/-/blob/main/browsing/from-a-to-%3Ca%3E.md?ref_type=heads#php---invisible-code-and-the-mystique-of-web-writing</ref~~> resulting in opaque processes and culture of compliance, refer to php key text <ref name=":0" /~~> and its point about server side writing and invisible labor		labor: holistic- vs prescriptive technologies and division of labor <ref>in "Dividing and Sharing" Femke Snelting writes on the division of labor as a consequence of the separation of design from content in web programming (and standardization) https://gitlab.com/km_kt/xp-reader/-/blob/main/SI26/dividing-and-sharing.md?ref_type=heads#divisions-of-labour</ref> (here also: using early markup "pecia system" enabled division of labor in print production) resulting in opaque processes and culture of compliance, refer to php key text <ref name=":0">"<?php> - invisible code and the mystique of web writing" in "From A to <A> - Keywords of Markup" https://gitlab.com/km_kt/xp-reader/-/blob/main/browsing/from-a-to-%3Ca%3E.md?ref_type=heads#php---invisible-code-and-the-mystique-of-web-writing</ref> and its point about server side writing and invisible labor

	===Key issue 4 = chapter 4 ~~(publishing otherwise) (infrastructures)~~===		===Key issue 4 = chapter 4===
	i feel this chapter should contain more of my own stand point / towards (end) thesis <br>		i feel this chapter should contain more of my own stand point / towards (end) thesis <br>
	why am i writing about this?		why am i writing about this?
	* pushing against fragmentalization of: user / developer, against hidenness / black box of today technology,		* pushing against fragmentalization of: user / developer, against hidenness / black box of today technology,
	* ~~accepting~~ notion of hidden, hides non canon histories and voices in technology, hides uncertainty and inconsistency <ref>thinking of Johanna Druckers "Performative Materiality and Theoretical Approches to Interface" in which the author arguments towards interfaces that render visible and affirm acts of interpretation</ref>		* notion of hidden hides non canon histories and voices in technology, hides uncertainty and inconsistency <ref>thinking of Johanna Druckers "Performative Materiality and Theoretical Approches to Interface" in which the author arguments towards interfaces that render visible and affirm acts of interpretation</ref>
	* highlighting that writing technologies (print and digital) have contiguous history and are not opposed to another		* highlighting that writing technologies (print and digital) have contiguous history and are not opposed to another
	away from proprietary, bloated platforms and applications. ~~highlight~~ necessity of agency and collective autonomy both in the creation ~~process~~ and over public objects. ~~discuss~~ adjacent tools and attempts (octomode etc). making the hidden visible as ~~possible~~ breaking with closed ~~of/ invisibility~~ discussed in 1 ~~- present~~ git and version control. excurs into history and version control, socio-cultural embededdness of git, present gitpub.<br>		* whats the role of labor in all this?
	~~maybe the~~ last chapter could also have a rather infrastructural focus through which we arrive at the git software and gitpub? what would my take or understanding of infrastructure be in this context? it ~~does relate~~ to paratext ~~in the sense of enabling~~ circulation~~, it also~~ mediates a relationship/ action, just as infrastructure does		'''publishing otherwise:'''

			Move away from proprietary, bloated platforms and applications. Highlight the necessity of agency and collective autonomy both in the process of creation and over public objects. Discuss adjacent tools and attempts (octomode etc). Framing my attempt of making the hidden visible as possibility for breaking with closed off objects discussed in chapter 1. Here introduce git and version control: excurs into history and version control, socio-cultural embededdness of git, present gitpub project.

			or '''Infrastructure:'''<br>
			The last chapter could also have a rather infrastructural focus through which we arrive at the git software and gitpub (which would serve as examples for my argument). Infrastructure is commonly perceived as invisible <ref>S. Lee Star asserts that Infrastructures only become visible when they break, a claim that Brian Larkin counters in "Politics and Poetics of Infrastructure" while raising the importance of examining how this apparent ''opacity'' of infrastructures is instrumentailized and why.</ref> what would my take or understanding of infrastructure be in this context? To some extend, it relates to paratext, which enables circulation and mediates a relationship/ action, just as infrastructure does. But infrastructure here must also be seen from a more technical perspective. (wait, am I using the terms ''infrastructure'' and technology ''synonymously'' right now?)
	* git is interesting bc it is connected to labor of programming (especially the writing of commit -m) it carries quite a lot of invisibility in itself		* git is interesting bc it is connected to labor of programming (especially the writing of commit -m) it carries quite a lot of invisibility in itself