aboutsummaryrefslogtreecommitdiffhomepage
path: root/test/reference/abstraction/two_bits.christopher_kelty.en.ssp
diff options
context:
space:
mode:
authorRalph Amissah <ralph.amissah@gmail.com>2026-09-03 12:44:01 -0400
committerRalph Amissah <ralph.amissah@gmail.com>2026-09-03 15:25:55 -0400
commit569d38694b10e3de1dc493f5b5ac08f99164b1a0 (patch)
tree5fdfef70053941cd0d451329b38916d3facdfcb1 /test/reference/abstraction/two_bits.christopher_kelty.en.ssp
parentocda a fix & ssp code-style use curly braces (diff)
test-abstraction-ssp re-generated
Several structure fields (now) computed in ocda do not yet have a consumer outside the `.ssp` writer (which shares ocda fields in a PEG parsable .ssp file). Their addition is to facilitate future output processing: each representing document structure information that document output generators of various formats, such as html, epub, latex, sql and any DOM based / tree-graph (node based hierarchical) representations, previously had to, or would have to, work out for themselves based on what ocda offered (without them). Computing them (upstream) in ocda once and sharing them (and providing the .ssp), means that: - future output formats can start from prepared structure rather than deriving it; - existing generators can be simplified to consume them instead of re-deriving; - a (dlang) generator could in principle be populated either from ocda directly or from a `.ssp` file; - `.ssp` being PEG parsable puts the same prepared structure in reach of implementations in other languages. `test/test-abstraction-ssp.sh` the `.ssp` reference regression test is used to catch regression in ocda including these as yet unused fields, which otherwise would remain unseen until used by other output-format consumers. This also is the reason issues now made easily visible and are being addressed (without issue to existing output generators). (assisted by Claude-Code)
Diffstat (limited to 'test/reference/abstraction/two_bits.christopher_kelty.en.ssp')
-rw-r--r--test/reference/abstraction/two_bits.christopher_kelty.en.ssp1567
1 files changed, 751 insertions, 816 deletions
diff --git a/test/reference/abstraction/two_bits.christopher_kelty.en.ssp b/test/reference/abstraction/two_bits.christopher_kelty.en.ssp
index d961e42..b77cb42 100644
--- a/test/reference/abstraction/two_bits.christopher_kelty.en.ssp
+++ b/test/reference/abstraction/two_bits.christopher_kelty.en.ssp
@@ -726,7 +726,6 @@
.ancestors: 1 0 0 0 2 0 0 0
.ancestors_collapsed: 1 2 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: CF5FF36BC88C28F10D5792449C8EB4F9C26CB857C8553C662949C5DC3D656BF5
| To my parents, Anne and Ted
@@ -756,7 +755,6 @@
.ancestors: 1 0 0 0 4 0 0 0
.ancestors_collapsed: 1 4 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 3A14D0230BBCC528D686978CAB48CB8E6373BD66E212CDD6D1EEB51B39D1BB92
| This is a book about Free Software, also known as Open Source Software, and is meant for anyone who wants to understand the cultural significance of Free Software. Two Bits explains how Free Software works and how it emerged in tandem with the Internet as both a technical and a social form. Understanding Free Software in detail is the best way to understand many contentious and confusing changes related to the Internet, to “commons,” to software, and to networks. Whether you think first of e-mail, Napster, Wikipedia, MySpace, or Flickr; whether you think of the proliferation of databases, identity thieves, and privacy concerns; whether you think of traditional knowledge, patents on genes, the death of scholarly publishing, or compulsory licensing of AIDS medicine; whether you think of MoveOn.org or net neutrality or YouTube—the issues raised by these phenomena can be better understood by looking carefully at the emergence of Free Software. ⑆,┨[PAGE x]┣,
@@ -767,7 +765,6 @@
.ancestors: 1 0 0 0 4 0 0 0
.ancestors_collapsed: 1 4 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 963C96D12E5C2E482864CF731CD4EA657B9A3DCEAAC12FE2A42071EB372D748E
| Why? Because it is in Free Software and its history that the issues raised—from intellectual property and piracy to online political advocacy and “social” software—were first figured out and confronted. Free Software’s roots stretch back to the 1970s and crisscross the histories of the personal computer and the Internet, the peaks and troughs of the information-technology and software industries, the transformation of intellectual property law, the innovation of organizations and “virtual” collaboration, and the rise of networked social movements. Free Software does not explain why these various changes have occurred, but rather how individuals and groups are responding: by creating new things, new practices, and new forms of life. It is these practices and forms of life—not the software itself—that are most significant, and they have in turn served as templates that others can use and transform: practices of sharing source code, conceptualizing openness, writing copyright (and copyleft) licenses, coordinating collaboration, and proselytizing for all of the above. There are explanations aplenty for why things are the way they are: it’s globalization, it’s the network society, it’s an ideology of transparency, it’s the virtualization of work, it’s the new flat earth, it’s Empire. We are drowning in the why, both popular and scholarly, but starving for the how.
@@ -778,7 +775,6 @@
.ancestors: 1 0 0 0 4 0 0 0
.ancestors_collapsed: 1 4 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: BD84922474D5EE1516DBBAB077DC0FAC280B87AD0724031FB00F50357DF8E61D
| Understanding how Free Software works is not just an academic pursuit but an experience that transforms the lives and work of participants involved. Over the last decade, in fieldwork with software programmers, lawyers, entrepreneurs, artists, activists, and other geeks I have repeatedly observed that understanding how Free Software works results in a revelation. People—even (or, perhaps, especially) those who do not consider themselves programmers, hackers, geeks, or technophiles—come out of the experience with something like religion, because Free Software is all about the practices, not about the ideologies and goals that swirl on its surface. Free Software and its creators and users are not, as a group, antimarket or anticommercial; they are not, as a group, anti-intellectual property or antigovernment; they are not, as a group, pro- or anti- anything. In fact, they are not really a group at all: not a corporation or an organization; not an NGO or a government agency; not a professional society or an informal horde of hackers; not a movement or a research project.
@@ -789,7 +785,6 @@
.ancestors: 1 0 0 0 4 0 0 0
.ancestors_collapsed: 1 4 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 2332B6AE0A1E9DAFD0C792E7A020405E4248607CA6BAEEC5C95D690146392D75
| Free Software is, however, public; it is about making things public. This fact is key to comprehending its cultural significance, its ⑆,┨[PAGE xi]┣, appeal, and its proliferation. Free Software is public in a particular way: it is a self-determining, collective, politically independent mode of creating very complex technical objects that are made publicly and freely available to everyone—a “commons,” in common parlance. It is a practice of working through the promises of equality, fairness, justice, reason, and argument in a domain of technically complex software and networks, and in a context of powerful, lopsided laws about intellectual property. The fact that something public in this grand sense emerges out of practices so seemingly arcane is why the first urge of many converts is to ask: how can Free Software be “ported” to other aspects of life, such as movies, music, science or medicine, civil society, and education? It is this proselytizing urge and the ease with which the practices are spread that make up the cultural significance of Free Software. For better or for worse, we may all be using Free Software before we know it.
@@ -819,7 +814,6 @@
.ancestors: 1 0 0 0 9 0 0 0
.ancestors_collapsed: 1 9 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 417221E73A0111AAC2924EAC52F8B8155B5C5942822D3FE104019CD7670AEC97
| Anthropology is dependent on strangers who become friends and colleagues—strangers who contribute the very essence of the work. In my case, these strangers are also hyperaware of issues of credit, reputation, acknowledgment, reuse, and modification of ideas and things. Therefore, the list is extensive and detailed.
@@ -830,7 +824,6 @@
.ancestors: 1 0 0 0 9 0 0 0
.ancestors_collapsed: 1 9 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 6FD94223F7A5EF4FF6ED3FE68CA7893C41D09128B7DA59ECA78588FDCE3335EB
| Sean Doyle and Adrian Gropper opened the doors to this project, providing unparalleled insight, hospitality, challenge, and curiosity. Axel Roch introduced me to Volker Grassmuck, and to much else. Volker Grassmuck introduced me to Berlin’s Free Software world and invited me to participate in the Wizards of OS conferences. Udhay Shankar introduced me to almost everyone I know, sometimes after the fact. Shiv Sastry helped me find lodging in Bangalore at his Aunt Anasuya Sastry’s house, which is called “Silicon Valley” and which was truly a lovely place to stay. Bharath Chari and Ram Sundaram let me haunt their office and cat-5 cables ⑆,┨[PAGE xiv]┣, during one of the more turbulent periods of their careers. Glenn Otis Brown visited, drank, talked, invited, challenged, entertained, chided, encouraged, drove, was driven, and gave and received advice. Ross Reedstrom welcomed me to the Rice Linux Users’ Group and to Connexions. Brent Hendricks did yeoman’s work, suffering my questions and intrusions. Geneva Henry, Jenn Drummond, Chuck Bearden, Kathy Fletcher, Manpreet Kaur, Mark Husband, Max Starkenberg, Elvena Mayo, Joey King, and Joel Thierstein have been welcoming and enthusiastic at every meeting. Sid Burris has challenged and respected my work, which has been an honor. Rich Baraniuk listens to everything I say, for better or for worse; he is a magnificent collaborator and friend.
@@ -841,7 +834,6 @@
.ancestors: 1 0 0 0 9 0 0 0
.ancestors_collapsed: 1 9 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 1EB8D9079F7C76ACDB5D7EFB79E3F600AF4F606B26F7102A00C14414F0304511
| James Boyle has been constantly supportive, for what feels like very little return on investment. Very few people get to read and critique and help reshape the argument and structure of a book, and to appear in it as well. Mario Biagioli helped me see the intricate strategy described in chapter 6. Stefan Helmreich read early drafts and transformed my thinking about networks. Manuel DeLanda explained the term assemblage to me. James Faubion corrected my thinking in chapter 2, helped me immeasurably with the Protestants, and has been an exquisitely supportive colleague and department chair. Mazyar Lotfalian and Melissa Cefkin provided their apartment and library, in which I wrote large parts of chapter 1. Matt Price and Michelle Murphy have listened patiently to me construct and reconstruct versions of this book for at least six years. Tom and Elizabeth Landecker provided hospitality and stunningly beautiful surroundings in which to rewrite parts of the book. Lisa Gitelman read carefully and helped explain issues about documentation and versioning that I discuss in chapter 4. Matt Ratto read and commented on chapters 4-7, convinced me to drop a useless distinction, and to clarify the conclusion to chapter 7. Shay David provided strategic insights about openness from his own work and pushed me to explain the point of recursive publics more clearly. Biella Coleman has been a constant interlocutor on the issues in this book—her contributions are too deep, too various, and too thorough to detail. Her own work on Free Software and hackers has been a constant sounding board and guide, and it has been a pleasure to work together on our respective texts. Kim Fortun helped me figure it all out. ⑆,┨[PAGE xv]┣,
@@ -852,7 +844,6 @@
.ancestors: 1 0 0 0 9 0 0 0
.ancestors_collapsed: 1 9 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: D4BC03ED15A2442BDDA2830B8442E2C261E0D9BD3A8E82AF5382944FE14C533C
| George Marcus hired me into a fantastic anthropology department and has had immense faith in this project throughout its lifetime. Paul Rabinow, Stephen Collier, and Andrew Lakoff have provided an extremely valuable setting—the Anthropology of the Contemporary Research Collaboratory—within which the arguments of this book developed in ways they could not have as a solitary project. Joe Dumit has encouraged and prodded and questioned and brainstormed and guided and inspired. Michael Fischer is the best mentor and advisor ever. He has read everything, has written much that precedes and shapes this work, and has been an unwavering supporter and friend throughout.
@@ -863,7 +854,6 @@
.ancestors: 1 0 0 0 9 0 0 0
.ancestors_collapsed: 1 9 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: C8DA979CC2DDF9B129795E0F69B0087F53AC9655D201A7A8FEC3D599E3771EA7
| Tish Stringer, Michael Powell, Valerie Olson, Ala Alazzeh, Lina Dib, Angela Rivas, Anthony Potoczniak, Ayla Samli, Ebru Kayaalp, Michael Kriz, Erkan Saka, Elise McCarthy, Elitza Ranova, Amanda Randall, Kris Peterson, Laura Jones, Nahal Naficy, Andrea Frolic, and Casey O’Donnell make my job rock. Scott McGill, Sarah Ellenzweig, Stephen Collier, Carl Pearson, Dan Wallach, Tracy Volz, Rich Doyle, Ussama Makdisi, Elora Shehabbudin, Michael Morrow, Taryn Kinney, Gregory Kaplan, Jane Greenberg, Hajime Nakatani, Kirsten Ostherr, Henning Schmidgen, Jason Danziger, Kayte Young, Nicholas King, Jennifer Fishman, Paul Drueke, Roberta Bivins, Sherri Roush, Stefan Timmermans, Laura Lark, and Susann Wilkinson either made Houston a wonderful place to be or provided an opportunity to escape it. I am especially happy that Thom Chivens has done both and more.
@@ -874,7 +864,6 @@
.ancestors: 1 0 0 0 9 0 0 0
.ancestors_collapsed: 1 9 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 4290A09272D48E6E8B42BA2BF97B91494E9274126AB0B61488C64F2DE32006AB
| The Center for the Study of Cultures provided me with a Faculty Fellowship in the fall of 2003, which allowed me to accomplish much of the work in conceptualizing the book. The Harvard History of Science Department and the MIT Program in History, Anthropology, and Social Studies of Science and Technology hosted me in the spring of 2005, allowing me to write most of chapters 7, 8, and 9. Rice University has been extremely generous in all respects, and a wonderful place to work. I’m most grateful for a junior sabbatical that gave me the chance to complete much of this book. John Hoffman graciously and generously allowed the use of the domain name twobits.net, in support of Free Software. Ken Wissoker, Courtney Berger, and the anonymous reviewers for Duke University Press have made this a much, much better book than when I started. ⑆,┨[PAGE xvi]┣,
@@ -885,7 +874,6 @@
.ancestors: 1 0 0 0 9 0 0 0
.ancestors_collapsed: 1 9 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: E1325FE4429CC1E93EE73328C5EADA8136467E7839D6EF5B58C7E2AFB1DD6F6B
| My parents, Ted and Anne, and my brother, Kevin, have always been supportive and loving; though they claim to have no idea what I do, I nonetheless owe my small success to their constant support. Hannah Landecker has read and reread and rewritten every part of this work; she has made it and me better, and I love her dearly for it. Last, but not least, my new project, Ida Jane Kelty Landecker, is much cuter and smarter and funnier than Two Bits, and I love her for distracting me from it.
@@ -915,7 +903,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: B605350BC00209520B7CD8F546322663356BA630708F71BBF30AEAD6B3DD608E
| Introduction
@@ -926,7 +913,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: EC60105B0DDF1584350AB4306200DA154231B6CDE970C144A1786A29E275474D
| Around 1998 Free Software emerged from a happily subterranean and obscure existence stretching back roughly twenty years. At the very pinnacle of the dotcom boom, Free Software suddenly populated the pages of mainstream business journals, entered the strategy and planning discussions of executives, confounded the radar of political leaders and regulators around the globe, and permeated the consciousness of a generation of technophile teenagers growing up in the 1990s wondering how people ever lived without e-mail. Free Software appeared to be something shocking, something that economic history suggested could never exist: a practice of creating software—good software—that was privately owned, but freely and publicly accessible. Free Software, as its ambiguous moniker suggests, is both free from constraints and free of charge. Such characteristics seem to violate economic logic and the principles of private ownership and individual autonomy, yet there are tens of ⑆,┨[pg 2]┣, millions of people creating this software and hundreds of millions more using it. Why? Why now? And most important: how?
@@ -937,7 +923,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 319E84DF4288EC1CD6BF7ED8AD5F81B99A335B49BDBF9B270D39362DB2F05E20
.has: notes_reg
@@ -949,7 +934,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 217DE77DE2237C18F7D100444D42A78AE91D5EE46CE54CAC8E9F538089C28024
| The significance of Free Software extends far beyond the arcane and detailed technical practices of software programmers and “geeks” (as I refer to them herein). Since about 1998, the practices and ideas of Free Software have extended into new realms of life and creativity: from software to music and film to science, engineering, and education; from national politics of intellectual property to global debates about civil society; from UNIX to Mac OS X and Windows; from medical records and databases to international disease monitoring and synthetic biology; from Open Source to open access. Free Software is no longer only about software—it exemplifies a more general reorientation of power and knowledge.
@@ -960,7 +944,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 2A3AAC81E9EE7118DF09ACCCB1547004F85F7098945F99874F7CC1033BF22516
| The terms Free Software and Open Source don’t quite capture the extent of this reorientation or their own cultural significance. They ⑆,┨[pg 3]┣, refer, quite narrowly, to the practice of creating software—an activity many people consider to be quite far from their experience. However, creating Free Software is more than that: it includes a unique combination of more familiar practices that range from creating and policing intellectual property to arguing about the meaning of “openness” to organizing and coordinating people and machines across locales and time zones. Taken together, these practices make Free Software distinct, significant, and meaningful both to those who create it and to those who take the time to understand how it comes into being.
@@ -971,7 +954,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 0AA2ABAE563F4AE7BB4E6C426C275C63D27AB6D7BFEF1908C560D208511494E5
.has: notes_reg
@@ -983,7 +965,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 2947DD61D98999403F9968492301719FEB15B92A6690AEA65510E96A595E2931
| The concept of a recursive public is not meant to apply to any and every instance of a public—it is not a replacement for the concept of a “public sphere”—but is intended rather to give readers a specific and detailed sense of the non-obvious, but persistent threads that form the warp and weft of Free Software and to analyze similar and related projects that continue to emerge from it as novel and unprecedented forms of publicity and political action.
@@ -994,7 +975,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: BA45094A975438DFFBA09D3E232AAF1880F9255C586604851B6305FF3A048C38
| At first glance, the thread tying these projects together seems to be the Internet. And indeed, the history and cultural significance of Free Software has been intricately mixed up with that of the Internet over the last thirty years. The Internet is a unique platform—an environment or an infrastructure—for Free Software. But the Internet looks the way it does because of Free Software. Free Software and the Internet are related like figure and ground or like system and environment; neither are stable or unchanging in and of themselves, and there are a number of practical, technical, and historical places where the two are essentially indistinguishable. The Internet is not itself a recursive public, but it is something vitally important to that public, something about which such publics care deeply and act to preserve. Throughout this book, I will return to these three phenomena: the Internet, a heterogeneous and diverse, though singular, infrastructure of technologies and uses; Free Software, a very specific set of technical, legal, and social practices that now require the Internet; and recursive publics, an analytic concept intended to clarify the relation of the first two.
@@ -1005,7 +985,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 0A8EB2CD3ED697D5E46576FC57D08F8A4BD457A181F571C51F322B3A62BC2C2B
.has: notes_reg
@@ -1017,7 +996,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: D01572BB23FB59EF298F7EA96E9F54E8B4109F703C70565F89B99759C75F2538
| Two Bits has three parts. Part I of this book introduces the reader to the concept of recursive publics by exploring the lives, works, and discussions of an international community of geeks brought together by their shared interest in the Internet. Chapter 1 asks, in an ethnographic voice, “Why do geeks associate with one another?” The answer—told via the story of Napster in 2000 and the standards process at the heart of the Internet—is that they are making a recursive public. Chapter 2 explores the words and attitudes of geeks more closely, focusing on the strange stories they tell (about the Protestant Reformation, about their practical everyday polymathy, about progress and enlightenment), stories that make sense of contemporary political economy in sometimes surprising ways. Central to part I is an explication of the ways in which geeks argue about technology but also argue with and through it, by building, modifying, and maintaining the very software, networks, and legal tools within which and by which they associate with one another. It is meant to give the reader a kind of visceral sense of why certain arrangements of technology, organization, and law—specifically that of the Internet and Free Software—are so vitally important to these geeks.
@@ -1028,7 +1006,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: EACFF8D2C20F1ABAB8577ABAE8B7891F53A099D9EC057031C72342102470D80D
| Part II takes a step back from ethnographic engagement to ask, “What is Free Software and why has it emerged at this point in history?” Part II is a historically detailed portrait of the emergence of Free Software beginning in 1998-99 and stretching back in time as far as the late 1950s; it recapitulates part I by examining Free Software as an exemplar of a recursive public. The five chapters in part II tell a coherent historical story, but each is focused on a separate component of Free Software. The stories in these chapters help distinguish the figure of Free Software from the ground of the Internet. The diversity of technical practices, economic concerns, information technologies, and legal and organizational practices is huge, and these five chapters distinguish and describe the specific practices in their historical contexts and settings: practices of ⑆,┨[pg 6]┣, proselytizing and arguing, of sharing, porting, and forking source code, of conceptualizing openness and open systems, of creating Free Software copyright, and of coordinating people and source code.
@@ -1039,7 +1016,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 2E2523B7CF09FF8596C30E3953AFA6205B3CB04C213FA9F5E70FE123E978D5D7
| Part III returns to ethnographic engagement, analyzing two related projects inspired by Free Software which modulate one or more of the five components discussed in part II, that is, which take the practices as developed in Free Software and experiment with making something new and different. The two projects are Creative Commons, a nonprofit organization that creates copyright licenses, and Connexions, a project to develop an online scholarly textbook commons. By tracing the modulations of practices in detail, I ask, “Are these projects still Free Software?” and “Are these projects still recursive publics?” The answer to the first questions reveals how Free Software’s flexible practices are influencing specific forms of practice far from software programming, while the answer to the second question helps explain how Free Software, Creative Commons, Connexions, and projects like them are all related, strategic responses to the reorientation of power and knowledge. The conclusion raises a series of questions intended to help scholars looking at related phenomena.
@@ -1050,7 +1026,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: F2BD756B65FCBA4C36F924F940F44ADFDE24CF72D5CC5F0B8ABD1EF01EFCEBC5
| ⑆!┨Recursive Publics and the Reorientation of Power and Knowledge┣!
@@ -1061,7 +1036,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: C59D9250F42320600244F77BAC34321267728BC44662C8BAB703845ACD21B564
| Governance and control of the creation and dissemination of knowledge have changed considerably in the context of the Internet over the last thirty years. Nearly all kinds of media are easier to produce, publish, circulate, modify, mash-up, remix, or reuse. The number of such creations, circulations, and borrowings has exploded, and the tools of knowledge creation and circulation—software and networks—have also become more and more pervasively available. The results have also been explosive and include anxieties about validity, quality, ownership and control, moral panics galore, and new concerns about the shape and legitimacy of global “intellectual property” systems. All of these concerns amount to a reorientation of knowledge and power that is incomplete and emergent, and whose implications reach directly into the heart of the legitimacy, certainty, reliability and especially the finality and temporality of ⑆,┨[pg 7]┣, the knowledge and infrastructures we collectively create. It is a reorientation at once more specific and more general than the grand diagnostic claims of an “information” or “network” society, or the rise of knowledge work or knowledge-based economies; it is more specific because it concerns precise and detailed technical and legal practices, more general because it is a cultural reorientation, not only an economic or legal one.
@@ -1072,7 +1046,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 267D93B3E6242A42861D31F5A6310A59BF1D6CE902E1090EBAA9BEA1744668DC
.has: notes_reg
@@ -1084,7 +1057,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 952BEC1B301A04C0F11A4F26FD7706A031794B4C5D2F2867F5D62C5BCA9B3923
| By calling Free Software a recursive public, I am doing two things: first, I am drawing attention to the democratic and political significance of Free Software and the Internet; and second, I am suggesting that our current understanding (both academic and colloquial) of what counts as a self-governing public, or even as “the public,” is radically inadequate to understanding the contemporary reorientation of knowledge and power. The first case is easy to make: it is obvious that there is something political about Free Software, but most casual observers assume, erroneously, that it is simply an ideological stance and that it is anti-intellectual property or technolibertarian. I hope to show how geeks do not start with ideologies, but instead come to them through their involvement in the ⑆,┨[pg 8]┣, practices of creating Free Software and its derivatives. To be sure, there are ideologues aplenty, but there are far more people who start out thinking of themselves as libertarians or liberators, but who become something quite different through their participation in Free Software.
@@ -1095,7 +1067,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: D0702DA40932B165E3FB247F46092D4F5DF0EEC6B21DB690DDAC2F627039CDDB
| The second case is more complex: why another contribution to the debate about the public and public spheres? There are two reasons I have found it necessary to invent, and to attempt to make precise, the concept of a recursive public: the first is to signal the need to include within the spectrum of political activity the creation, modification, and maintenance of software, networks, and legal documents. Coding, hacking, patching, sharing, compiling, and modifying of software are forms of political action that now routinely accompany familiar political forms of expression like free speech, assembly, petition, and a free press. Such activities are expressive in ways that conventional political theory and social science do not recognize: they can both express and “implement” ideas about the social and moral order of society. Software and networks can express ideas in the conventional written sense as well as create (express) infrastructures that allow ideas to circulate in novel and unexpected ways. At an analytic level, the concept of a recursive public is a way of insisting on the importance to public debate of the unruly technical materiality of a political order, not just the embodied discourse (however material) about that order. Throughout this book, I raise the question of how Free Software and the Internet are themselves a public, as well as what that public actually makes, builds, and maintains.
@@ -1106,7 +1077,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 4D6A11A1790DE6258E1BCBBA729B6EBEF60C6EB9CEA9FA9D6ABBD2E2EA906BED
.has: notes_reg
@@ -1118,7 +1088,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 1F602B7A4C329A50460EF60BCC1D44966C358D22199C50DCE7A8BDFFE9E490E9
| For instance, a very important aspect of the contemporary Internet, and one that has been fiercely disputed (recently under the banner of “net neutrality”), is its singularity: there is only one Internet. This was not an inevitable or a technically determined outcome, but the result of a contest in which a series of decisions were made about layers ranging from the very basic physical configuration of the Internet (packet-switched networks and routing systems indifferent to data types), to the standards and protocols that make it work (e.g., TCP/IP or DNS), to the applications that run on it (e-mail, www, ssh). The outcome of these decisions has been to privilege the singularity of the Internet and to champion its standardization, rather than to promote its fragmentation into multiple incompatible networks. These same kinds of decisions are routinely discussed, weighed, and programmed in the activity of various Free Software projects, as well as its derivatives. They are, I claim, decisions embedded in imaginations of order that are simultaneously moral and technical.
@@ -1129,7 +1098,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 81750C8C7749B2CA02962B0D341005337D473B8611A5A2D81B318D4210A5BAD5
| By contrast, governments, corporations, nongovernmental organizations (NGOs), and other institutions have plenty of reasons—profit, security, control—to seek to fragment the Internet. But it is the check on this power provided by recursive publics and especially the practices that now make up Free Software that has kept the Internet whole to date. It is a check on power that is by no means absolute, but is nonetheless rigorously and technically concerned with its legitimacy and independence not only from state-based forms of power and control, but from corporate, commercial, and nongovernmental power as well. To the extent that the Internet is public and extensible (including the capability of creating private subnetworks), it is because of the practices discussed herein and their culmination in a recursive public.
@@ -1140,7 +1108,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 3A5CF10B4EA7F9F09756362BDC0A09652B0EC29C99A8788B91A4C9DFACC35D76
| Recursive publics respond to governance by directly engaging in, maintaining, and often modifying the infrastructure they seek, as a ⑆,┨[pg 10]┣, public, to inhabit and extend—and not only by offering opinions or protesting decisions, as conventional publics do (in most theories of the public sphere). Recursive publics seek to create what might be understood, enigmatically, as a constantly “self-leveling” level playing field. And it is in the attempt to make the playing field self-leveling that they confront and resist forms of power and control that seek to level it to the advantage of one or another large constituency: state, government, corporation, profession. It is important to understand that geeks do not simply want to level the playing field to their advantage—they have no affinity or identity as such. Instead, they wish to devise ways to give the playing field a certain kind of agency, effected through the agency of many different humans, but checked by its technical and legal structure and openness. Geeks do not wish to compete qua capitalists or entrepreneurs unless they can assure themselves that (qua public actors) that they can compete fairly. It is an ethic of justice shot through with an aesthetic of technical elegance and legal cleverness.
@@ -1151,7 +1118,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 0266C243ACA3C63435AD818DCE3EE93807A0C038B0ECCF2D4E65548E25920447
.has: notes_reg
@@ -1163,7 +1129,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: B36026D5131F8336933FEC81ACFE38559ADD5EC28D13B102AEE15E07687C1266
.has: notes_reg
@@ -1175,7 +1140,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 34BD8363454DF8E4471F9D657B71AD81C464821928A93EFBC53140634F59153C
| However, it is modifiability that is the most fascinating, and unnerving, aspect of the reorientation of power and knowledge. Modifiability includes the ability not only to access—that is, to reuse in the trivial sense of using something without restrictions—but to transform it for use in new contexts, to different ends, or in order to participate directly in its improvement and to redistribute or recirculate those improvements within the same infrastructures while securing the same rights for everyone else. In fact, the core practice of Free Software is the practice of reuse and modification of software source code. Reuse and modification are also the key ideas that projects modeled on Free Software (such as Connexions and Creative Commons) see as their goal. Creative Commons has as its motto “Culture always builds on the past,” and they intend that to mean “through legal appropriation and modification.” Connexions, which allows authors to create online bits and pieces of textbooks explicitly encourages authors to reuse work by other people, to modify it, and to make it their own. Modifiability therefore raises a very specific and important question about finality. When is something (software, a film, music, culture) finished? How long does it remain finished? Who decides? Or more generally, what does its temporality look like, and how does that temporality restructure political relationships? Such issues are generally familiar only to historians and literary scholars who understand the transformation of canons, the interplay of imitation and originality, and the theoretical questions raised, for instance, in textual scholarship. But the contemporary meaning of modification includes both a vast increase in the speed and scope of modifiability and a certain automation of the practice that was unfamiliar before the advent of sophisticated, distributed forms of software.
@@ -1186,7 +1150,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 83F2A3417865E374BFA71F71AD3614EECA50215A7110D7487305A5E5E674D855
| Modifiability is an oft-claimed advantage of Free Software. It can be updated, modified, extended, or changed to deal with other changing environments: new hardware, new operating systems, unforeseen technologies, or new laws and practices. At an infrastructural level, such modifiability makes sense: it is a response to ⑆,┨[pg 12]┣, and an alternative to technocratic forms of planning. It is a way of planning in the ability to plan out; an effort to continuously secure the ability to deal with surprise and unexpected outcomes; a way of making flexible, modifiable infrastructures like the Internet as safe as permanent, inflexible ones like roads and bridges.
@@ -1197,7 +1160,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 9128CC0215CDED29F300D87FCEF06FC446E66C8F7493A752542AAF8B3335DC64
| But what is the cultural significance of modifiability? What does it mean to plan in modifiability to culture, to music, to education and science? At a clerical level, such a question is obvious whenever a scholar cannot recover a document written in WordPerfect 2.0 or on a disk for which there are no longer disk drives, or when a library archive considers saving both the media and the machines that read that media. Modifiability is an imperative for building infrastructures that can last longer. However, it is not only a solution to a clerical problem: it creates new possibilities and new problems for long-settled practices like publication, or the goals and structure of intellectual-property systems, or the definition of the finality, lifetime, monumentality, and especially, the identity of a work. Long-settled, seemingly unassailable practices—like the authority of published books or the power of governments to control information—are suddenly confounded and denaturalized by the techniques of modifiability.
@@ -1208,7 +1170,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 28CE7319A507F1613B86822EAA387439FAB9238E08BA2ABD61440C22F2CB3D0A
| Over the last ten to fifteen years, as the Internet has spread exponentially and insinuated itself into the most intimate practices of all kinds of people, the issues of availability and modifiability and the reorientation of knowledge and power they signify have become commonplace. As this has happened, the significance and practices associated with Free Software have also spread—and been modulated in the process. These practices provide a material and meaningful starting point for an array of recursive publics who play with, modulate, and transform them as they debate and build new ways to share, create, license, and control their respective productions. They do not all share the same goals, immediate or long-term, but by engaging in the technical, legal, and social practices pioneered in Free Software, they do in fact share a “social imaginary” that defines a particular relationship between technology, organs of governance (whether state, corporate, or nongovernmental), and the Internet. Scientists in a lab or musicians in a band; scholars creating a textbook or social movements contemplating modes of organization and protest; government bureaucrats issuing data or journalists investigating corruption; corporations that manage ⑆,┨[pg 13]┣, personal data or co-ops that monitor community development—all these groups and others may find themselves adopting, modulating, rejecting, or refining the practices that have made up Free Software in the recent past and will do so in the near future.
@@ -1219,7 +1180,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: D7CC593F83342EEF197085D969D6657B3E992ACABF61CCC32AA09F2709E96AEB
| ⑆!┨Experiment and Modulation┣!
@@ -1230,7 +1190,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: CFCDF9920A1AC0001EC0FD30427D1A5E01A1740FACEFA02A21683A4590002E48
| What exactly is Free Software? This question is, perhaps surprisingly, an incredibly common one in geek life. Debates about definition and discussions and denunciations are ubiquitous. As an anthropologist, I have routinely participated in such discussions and debates, and it is through my immediate participation that Two Bits opens. In part I I tell stories about geeks, stories that are meant to give the reader that classic anthropological sense of being thrown into another world. The stories reveal several general aspects of what geeks talk about and how they do so, without getting into what Free Software is in detail. I start in this way because my project started this way. I did not initially intend to study Free Software, but it was impossible to ignore its emergence and manifest centrality to geeks. The debates about the definition of Free Software that I participated in online and in the field eventually led me away from studying geeks per se and turned me toward the central research concern of this book: what is the cultural significance of Free Software?
@@ -1241,7 +1200,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 7C9201174F0577A4217AC146DD9190D45F6D4C2AA0DD76503A20CD0635AEADD3
| In part II what I offer is not a definition of Free Software, but a history of how it came to be. The story begins in 1998, with an important announcement by Netscape that it would give away the source code to its main product, Netscape Navigator, and works backward from this announcement into the stories of the UNIX operating system, “open systems,” copyright law, the Internet, and tools for coordinating people and code. Together, these five stories constitute a description of how Free Software works as a practice. As a cultural analysis, these stories highlight just how experimental the practices are, and how individuals keep track of and modulate the practices along the way.
@@ -1252,7 +1210,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: F6E774609030272E5C5DF19ACC84095516CE7DFCCBDDB7EF943FC75A6ECCEAE7
| Netscape’s decision came at an important point in the life of Free Software. It was at just this moment that Free Software was becoming aware of itself as a coherent movement and not just a diverse amalgamation of projects, tools, or practices. Ironically, this ⑆,┨[pg 14]┣, recognition also betokened a split: certain parties started to insist that the movement be called “Open Source” software instead, to highlight the practical over the ideological commitments of the movement. The proposal itself unleashed an enormous public discussion about what defined Free Software (or Open Source). This enigmatic event, in which a movement became aware of itself at the same time that it began to question its mission, is the subject of chapter 3. I use the term movement to designate one of the five core components of Free Software: the practices of argument and disagreement about the meaning of Free Software. Through these practices of discussion and critique, the other four practices start to come into relief, and participants in both Free Software and Open Source come to realize something surprising: for all the ideological distinctions at the level of discourse, they are doing exactly the same thing at the level of practice. The affect-laden histrionics with which geeks argue about the definition of what makes Free Software free or Open Source open can be matched only by the sober specificity of the detailed practices they share.
@@ -1263,7 +1220,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 793E1AC4025171AF95AE643D119D10504F39BD430680B08CDF1C1DD278A94E6B
| The second component of Free Software is just such a mundane activity: sharing source code (chapter 4). It is an essential and fundamentally routine practice, but one with a history that reveals the goals of software portability, the interactions of commercial and academic software development, and the centrality of source code (and not only of abstract concepts) in pedagogical settings. The details of “sharing” source code also form the story of the rise and proliferation of the UNIX operating system and its myriad derivatives.
@@ -1274,7 +1230,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: CEED6B5C4D582D3B4BF2DB87715BD358DBCE50666636541306713B76887E0C5B
| The third component, conceptualizing openness (chapter 5), is about the specific technical and “moral” meanings of openness, especially as it emerged in the 1980s in the computer industry’s debates over “open systems.” These debates concerned the creation of a particular infrastructure, including both technical standards and protocols (a standard UNIX and protocols for networks), and an ideal market infrastructure that would allow open systems to flourish. Chapter 5 is the story of the failure to achieve a market infrastructure for open systems, in part due to a significant blind spot: the role of intellectual property.
@@ -1285,7 +1240,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 34F3087FAF3775C14F69D6414CF7CDBCC1476AF55BD8CCD01F8B8CD7E9D19B6A
| The fourth component, applying copyright (and copyleft) licenses (chapter 6), involves the problem of intellectual property as it faced programmers and geeks in the late 1970s and early 1980s. In this ⑆,┨[pg 15]┣, chapter I detail the story of the first Free Software license—the GNU General Public License (GPL)—which emerged out of a controversy around a very famous piece of software called EMACS. The controversy is coincident with changing laws (in 1976 and 1980) and changing practices in the software industry—a general drift from trade secret to copyright protection—and it is also a story about the vaunted “hacker ethic” that reveals it in its native practical setting, rather than as a rarefied list of rules.
@@ -1296,7 +1250,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: D6DB52269D77923C81BEF256E94BCDF0EBA4447D98C512B5F78DE3A7A2E5227D
| The fifth component, the practice of coordination and collaboration (chapter 7), is the most talked about: the idea of tens or hundreds of thousands of people volunteering their time to contribute to the creation of complex software. In this chapter I show how novel forms of coordination developed in the 1990s and how they worked in the canonical cases of Apache and Linux; I also highlight how coordination facilitates the commitment to adaptability (or modifiability) over against planning and hierarchy, and how this commitment resolves the tension between individual virtuosity and the need for collective control.
@@ -1307,7 +1260,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: FD7011F0D08AA2037B66AFBB3B19BEBB8D72F8557F39C7997F3FCA0D17B6196C
| Taken together, these five components make up Free Software—but they are not a definition. Within each of these five practices, many similar and dissimilar activities might reasonably be included. The point of such a redescription of the practices of Free Software is to conceptualize them as a kind of collective technical experimental system. Within each component are a range of differences in practice, from conventional to experimental. At the center, so to speak, are the most common and accepted versions of a practice; at the edges are more unusual or controversial versions. Together, the components make up an experimental system whose infrastructure is the Internet and whose “hypotheses” concern the reorientation of knowledge and power.
@@ -1318,7 +1270,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: A6E10171278285A0E4EF3A05EF053DCECB8151FF9ADA897C5BA8D096A06D05B3
| For example, one can hardly have Free Software without source code, but it need not be written in C (though the vast majority of it is); it can be written in Java or perl or TeX. However, if one stretches the meaning of source code to include music (sheet music as source and performance as binary), what happens? Is this still Free Software? What happens when both the sheet and the performance are “born digital”? Or, to take a different example, Free Software requires Free Software licenses, but the terms of these licenses are often changed and often heatedly discussed and vigilantly policed by geeks. What degree of change removes a license ⑆,┨[pg 16]┣, from the realm of Free Software and why? How much flexibility is allowed?
@@ -1329,7 +1280,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 4FC1CF6A60FA4060C8EEC66915E90FD2ECAC9ED61CE55A4EE4BEFE97DD94BB3C
| Conceived this way, Free Software is a system of thresholds, not of classification; the excitement that participants and observers sense comes from the modulation (experimentation) of each of these practices and the subsequent discovery of where the thresholds are. Many, many people have written their own “Free Software” copyright licenses, but only some of them remain within the threshold of the practice as defined by the system. Modulations happen whenever someone learns how some component of Free Software works and asks, “Can I try these practices out in some other domain?”
@@ -1340,7 +1290,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 85FDAE97BFDEC9556ADA6A9A40E41EC46F3BB42A5EC4EB481A7F9623024DD357
.has: notes_reg
@@ -1352,7 +1301,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 762B919851871675818FF9FADD1F22845E005D9637CDFAE5A3DF38C1235E8452
.has: notes_reg
@@ -1364,7 +1312,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: C395A3BF63417789DFD158FB6FA1AB7B02C24CCC5EEDF785914EBE10C6FAE6EE
| In part III, I look in detail at two “commons” understood as modulations of the component practices of Free Software. Rather than treating commons projects simply as metaphorical or inspirational uses of Free Software, I treat them as modulations, which allows me to remain directly connected to the changing practices involved. The goal of part III is to understand how commons projects like Connexions and Creative Commons breach the thresholds of these practices and yet maintain something of the same orientation. What changes, for instance, have made it possible to imagine new forms of free content, free culture, open source music, or a science commons? What happens as new communities of people adopt and modulate the five component practices? Do they also become recursive publics, concerned with the maintenance and expansion of the infrastructures that allow them to come into being in the first place? Are they concerned with the implications of availability and modifiability that continue to unfold, continue to be figured out, in the realms of education, music, film, science, and writing?
@@ -1375,7 +1322,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 2CD8C17880499A633979A168E6444096A42E6418ADA7E45A5F094776D29B40BB
| The answers in part III make clear that, so far, these concerns are alive and well in the modulations of Free Software: Creative Commons and Connexions each struggle to come to terms with new ways of creating, sharing, and reusing content in the contemporary legal environment, with the Internet as infrastructure. Chapters 8 and 9 provide a detailed analysis of a technical and legal experiment: a modulation that begins with source code, but quickly requires modulations in licensing arrangements and forms of coordination. It is here that Two Bits provides the most detailed story of figuring out set against the background of the reorientation of knowledge and power. This story is, in particular, one of reuse, of modifiability and the problems that emerge in the attempt to build it into the everyday practices of pedagogical writing and cultural production of myriad forms. Doing so leads the actors involved directly to the question of the existence and ontology of norms: norms of scholarly production, borrowing, reuse, citation, reputation, and ownership. These last chapters open up questions about the stability of modern knowledge, not as an archival or a legal problem, but as a social and normative one; they raise questions about the invention and control of norms, and the forms of life that may emerge from these ⑆,┨[pg 18]┣, practices. Recursive publics come to exist where it is clear that such invention and control need to be widely shared, openly examined, and carefully monitored.
@@ -1386,7 +1332,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: B4EBE84240D7BD7E885209EC010DCFA54FDDA5B2E90A158A275F741F3CFD332A
| ⑆!┨Three Ways of Looking at Two Bits┣!
@@ -1397,7 +1342,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: E82AAFEF62CEC6B6F0AE3A2F06D1ED420FF572153D60261D26B3525D20AA8858
.has: notes_reg
@@ -1409,7 +1353,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 5D319EE38802E94A725D386061EB28C130564B3A10F43C5D36EFA65A0F374046
.has: notes_reg
@@ -1421,7 +1364,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 01C8156BF178B340259F601AE5B5D5870D409286AF6C63D668CE3DE14BFBC3D7
.has: notes_reg
@@ -1433,7 +1375,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: DD68DB40EB6D51E3A2A02DC47E3D52EEB0445B1773C2F15A46A507EE4B7212A7
.has: links notes_reg
@@ -1446,7 +1387,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: BFD5E172303E7F2212D4921EB47100DA855B565E7C4CA020E1FAC01C941EDAA4
| Methodologically, Two Bits provides an example of how to study distributed phenomena ethnographically. Free Software and the Internet are objects that do not have a single geographic site at which they can be studied. Hence, this work is multisited in the simple sense of having multiple sites at which these objects were investigated: Boston, Bangalore, Berlin, Houston. It was conducted among particular people, projects, and companies and at conferences and online gatherings too numerous to list, but it has not been a study of a single Free Software project distributed around the globe. In all of these places and projects the geeks I worked with were randomly and loosely affiliated people with diverse lives and histories. Some ⑆,┨[pg 20]┣, identified as Free Software hackers, but most did not. Some had never met each other in real life, and some had. They represented multiple corporations and institutions, and came from diverse nations, but they nonetheless shared a certain set of ideas and idioms that made it possible for me to travel from Boston to Berlin to Bangalore and pick up an ongoing conversation with different people, in very different places, without missing a beat.
@@ -1457,7 +1397,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 6E7C3C4625F7A44392F7EED43B713185A4B7A05D3B3DB22397ABAE4C81F14BDA
.has: notes_reg
@@ -1469,7 +1408,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: F054DB317BF0482C32A0DCF04B9FD2E98A0FCBB419712C422074CC475967731C
.has: notes_reg
@@ -1481,7 +1419,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 3DD9362DAA0A4C402C393070921BCB405AA9D80B8A5D909120B84B959236EE8D
| A methodological note about the peculiarity of my subject is also in order. The Attentive Reader will note that there are very few fragments of conventional ethnographic material (i.e., interviews or notes) transcribed herein. Where they do appear, they tend to be “publicly available”—which is to say, accessible via the Internet—and are cited as such, with as much detail as necessary to allow the reader to recover them. Conventional wisdom in both anthropology and history has it that what makes a study interesting, in part, is the work a researcher has put into gathering that which is not already available, that is, primary sources as opposed to secondary sources. In some cases I provide that primary access (specifically in chapters 2, 8, and 9), but in many others it is now literally impossible: nearly everything is archived. Discussions, fights, collaborations, talks, papers, software, articles, news stories, history, old software, old software manuals, reminiscences, notes, and drawings—it is all saved by someone, somewhere, and, more important, often made instantly available by those who collect it. The range of conversations and interactions that count as private (either in the sense of disappearing from written memory or of being accessible only to the parties involved) has shrunk demonstrably since about 1981.
@@ -1492,7 +1429,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: E9DA56A668EE42C29B659AAA5B0C55F7B49A2B8136276C5303356AF439E69BFC
| Such obsessive archiving means that ethnographic research is stratified in time. Questions that would otherwise have required “being there” are much easier to research after the fact, and this is most evident in my reconstruction from sources on USENET and mailing lists in chapters 1, 6, and 7. The overwhelming availability of quasi-archival materials is something I refer to, in a play on the EMACS text editor, as “self-documenting history.” That is to say, one of the activities that geeks love to participate in, and encourage, is the creation, analysis, and archiving of their own roles in the ⑆,┨[pg 22]┣, development of the Internet. No matter how obscure or arcane, it seems most geeks have a well-developed sense of possibility—their contribution could turn out to have been transformative, important, originary. What geeks may lack in social adroitness, they make up for in archival hubris.
@@ -1503,7 +1439,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: ADC3632270183E305C31ECF992EFF68E97D2BE44FE4D9D9EF97EF6E794CB7AB0
| Finally, the theoretical contribution of Two Bits consists of a refinement of debates about publics, public spheres, and social imaginaries that appear troubled in the context of the Internet and Free Software. Terminology such as virtual community, online community, cyberspace, network society, or information society are generally not theoretical constructs, but ways of designating a subgenre of disciplinary research having to do with electronic networks. The need for a more precise analysis of the kinds of association that take place on and through information technology is clear; the first step is to make precise which information technologies and which specific practices make a difference.
@@ -1514,7 +1449,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 449356DD2C4D19AB76C9EF945559A0AAE2A49A41073EBFF93668509DD9DB7725
.has: notes_reg
@@ -1526,7 +1460,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: BE91847B503AC4C92D16D366F78F03924EEC80D6FD7524CF0EF48D9EAB01D1AE
.has: notes_reg
@@ -1538,7 +1471,6 @@
.ancestors: 1 0 0 0 17 0 0 0
.ancestors_collapsed: 1 17 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 8AFC9616D74B9E546D3F46233D2AC0324B033EBA7B8B7EECA69F25D7322CE234
| If recursive public is a useful concept, it is because it helps elaborate the general question of the “reorientation of knowledge and power.” In particular it is meant to bring into relief the ways in which the Internet and Free Software are related to the political economy of modern society through the creation not only of new knowledge, but of new infrastructures for circulating, maintaining, and modifying it. Just as Warner’s book The Letters of the Republic was concerned with the emergence of the discourse of republicanism and the simultaneous development of an American republic of letters, or as Habermas’s analysis was concerned with the relationship of the bourgeois public sphere to the democratic revolutions of the eighteenth century, this book asks a similar series of questions: how are the emergent practices of recursive publics related to emerging relations of political and technical life in a world that submits to the Internet and its forms of circulation? Is there still a role for a republic of letters, much less a species of public that can seriously claim independence and autonomy from other constituted forms of power? Are Habermas’s pessimistic critiques of the bankruptcy of the public sphere in the twentieth century equally applicable to the structures of the twenty-first century? Or is it possible that recursive publics represent a reemergence of strong, authentic publics in a world shot through with cynicism and suspicion about mass media, verifiable knowledge, and enlightenment rationality? [PAGE 24: BLANK]
@@ -1584,10 +1516,10 @@
[75] para
.part: body
+.parent: 0
.ancestors: 1 74 0 0 0 0 0 0
.ancestors_collapsed: 1 74 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: E525E77D1A92ECF712A53A45C76393621B2BE80666AE0EBC3F4B51284C8BF910
.indent: 1 1
@@ -1595,10 +1527,10 @@
[76] para
.part: body
+.parent: 0
.ancestors: 1 74 0 0 0 0 0 0
.ancestors_collapsed: 1 74 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 3298B7C63C764C9AE65CB74B8A136DE9D2025428F9B9389731A7E66C28416465
| - john dewey, ⑆/┨The Public and Its Problems┣/
@@ -1650,7 +1582,6 @@
.ancestors: 1 74 0 0 77 0 0 0
.ancestors_collapsed: 1 74 77 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: CB7AB3FEC1D41F2C55790B2045AD7AD5EEEA8803C4E72C04AFFF5860EBDC8550
| Since about 1997, I have been living with geeks online and off. I have been drawn from Boston to Bangalore to Berlin to Houston to Palo Alto, from conferences and workshops to launch parties, pubs, and Internet Relay Chats (IRCs). All along the way in my research questions of commitment and practice, of ideology and imagination have arisen, even as the exact nature of the connections between these people and ideas remained obscure to me: what binds geeks together? As my fieldwork pulled me from a Boston start-up company that worked with radiological images to media labs in Berlin to young entrepreneurial elites in Bangalore, my logistical question eventually developed into an analytical concept: geeks are bound together as a recursive public.
@@ -1661,7 +1592,6 @@
.ancestors: 1 74 0 0 77 0 0 0
.ancestors_collapsed: 1 74 77 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: FA192AF02CECC6E640ED13556F0EAA1324EC25CA12017CA45EA47BA95136DC47
| How did I come to understand geeks as a public constituted around the technical and moral ideas of order that allow them to associate with one another? Through this question, one can start to understand the larger narrative of Two Bits: that of Free Software ⑆,┨[pg 28]┣, as an exemplary instance of a recursive public and as a set of practices that allow such publics to expand and spread. In this chapter I describe, ethnographically, the diverse, dispersed, and as an exemplary instance of a recursive public and as a set of practices that allow such publics to expand and spread. In this chapter I describe, ethnographically, the diverse, dispersed, and novel forms of entanglements that bind geeks together, and I construct the concept of a recursive public in order to explain these entanglements.
@@ -1672,7 +1602,6 @@
.ancestors: 1 74 0 0 77 0 0 0
.ancestors_collapsed: 1 74 77 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 09C3CA3E8D798EEC8D8B4451D63155A1C751B4DDC01E5CE0BC3A02DF1173EC7D
| A recursive public is a public that is constituted by a shared concern for maintaining the means of association through which they come together as a public. Geeks find affinity with one another because they share an abiding moral imagination of the technical infrastructure, the Internet, that has allowed them to develop and maintain this affinity in the first place. I elaborate the concept of recursive public (which is not a term used by geeks) in relation to theories of ideology, publics, and public spheres and social imaginaries. I illustrate the concept through ethnographic stories and examples that highlight geeks’ imaginations of the technical and moral order of the Internet. These stories include those of the fate of Amicas, a Boston-based healthcare start-up, between 1997 and 2003, of my participation with new media academics and activists in Berlin in 1999-2001, and of the activities of a group of largely Bangalore-based information technology (IT) professionals on and offline, especially concerning the events surrounding the peer-topeer file sharing application Napster in 2000-2001.
@@ -1683,7 +1612,6 @@
.ancestors: 1 74 0 0 77 0 0 0
.ancestors_collapsed: 1 74 77 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 1766DD31A5C6E8844148B13B388BFF57BAB90C054956208E7B902670CD99E943
| The phrase “moral and technical order” signals both technology—principally software, hardware, networks, and protocols—and an imagination of the proper order of collective political and commercial action, that is, how economy and society should be ordered collectively. Recursive publics are just as concerned with the moral order of markets as they are with that of commons; they are not anticommercial or antigovernment. They exist independent of, and as a check on, constituted forms of power, which include markets and corporations. Unlike other concepts of a public or of a public sphere, “recursive public” captures the fact that geeks’ principal mode of associating and acting is through the medium of the Internet, and it is through this medium that a recursive public can come into being in the first place. The Internet is not itself a public sphere, a public, or a recursive public, but a complex, heterogeneous infrastructure that constitutes and constrains geeks’ everyday practical commitments, their ability to “become public” or to compose a common world. As such, their participation qua recursive publics structures their identity as creative and autonomous ⑆,┨[pg 29]┣, individuals. The fact that the geeks described here have been brought together by mailing lists and e-mail, bulletin-board services and Web sites, books and modems, air travel and academia, and cross-talking and cross-posting in ways that were not possible before the Internet is at the core of their own reasoning about why they associate with each other. They are the builders and imaginers of this space, and the space is what allows them to build and imagine it.
@@ -1694,7 +1622,6 @@
.ancestors: 1 74 0 0 77 0 0 0
.ancestors_collapsed: 1 74 77 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 78B5B85B43A843278A40F598893481E7C03AB30F1F38AE2BB2A23742B4CFE917
| Why recursive? I call such publics recursive for two reasons: first, in order to signal that this kind of public includes the activities of making, maintaining, and modifying software and networks, as well as the more conventional discourse that is thereby enabled; and second, in order to suggest the recursive “depth” of the public, the series of technical and legal layers—from applications to protocols to the physical infrastructures of waves and wires—that are the subject of this making, maintaining, and modifying. The first of these characteristics is evident in the fact that geeks use technology as a kind of argument, for a specific kind of order: they argue about technology, but they also argue through it. They express ideas, but they also express infrastructures through which ideas can be expressed (and circulated) in new ways. The second of these characteristics—regarding layers—is reflected in the ability of geeks to immediately see connections between, for example, Napster (a user application) and TCP/IP (a network protocol) and to draw out implications for both of them. By connecting these layers, Napster comes to represent the Internet in miniature. The question of where these layers stop (hardware? laws and regulations? physical constants? etc.) circumscribes the limits of the imagination of technical and moral order shared by geeks.
@@ -1705,7 +1632,6 @@
.ancestors: 1 74 0 0 77 0 0 0
.ancestors_collapsed: 1 74 77 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: DA65FB7486EB4507CB3815BB31765BFA674B33301F617ED40C4BEC85C3ACDD65
| Above all, “recursive public” is a concept—not a thing. It is intended to make distinctions, allow comparison, highlight salient features, and relate two diverse kinds of things (the Internet and Free Software) in a particular historical context of changing relations of power and knowledge. The stories in this chapter (and throughout the book) give some sense of how geeks interact and what they do technically and legally, but the concept of a recursive public provides a way of explaining why geeks (or people involved in Free Software or its derivatives) associate with one another, as well as a way of testing whether other similar cases of contemporary, technologically mediated affinity are similarly structured. ⑆,┨[pg 30]┣,
@@ -1716,7 +1642,6 @@
.ancestors: 1 74 0 0 77 0 0 0
.ancestors_collapsed: 1 74 77 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: D58239D97FE7612BE234D331FD207F24AE31FD01B0DA919A757792E87B377F98
| ⑆!┨Recursion┣!
@@ -1727,7 +1652,6 @@
.ancestors: 1 74 0 0 77 0 0 0
.ancestors_collapsed: 1 74 77 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: AEE3D4D763B7C1392F4C0E87D8B4E37BE46978952F1B6D4E253CD6C6B2A4F1ED
.indent: 1 1
@@ -1739,7 +1663,6 @@
.ancestors: 1 74 0 0 77 0 0 0
.ancestors_collapsed: 1 74 77 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: A947DEE554EC594B5D07884753B189E1A833962908DFE859AC5C688D7054CACD
.indent: 1 1
@@ -1772,7 +1695,6 @@
.ancestors: 1 74 0 0 77 0 0 0
.ancestors_collapsed: 1 74 77 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 14496FB0BF8B2BBD71561377529FFB70A980CF3DD5462F7D4631C3E3AA99515C
.indent: 1 1
@@ -1784,7 +1706,6 @@
.ancestors: 1 74 0 0 77 0 0 0
.ancestors_collapsed: 1 74 77 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 8B8B08BE2D5407E0823DD2537C176C8A1EA793BDE09E57A7E990A1AE55829CFB
.indent: 1 1
@@ -1796,7 +1717,6 @@
.ancestors: 1 74 0 0 77 0 0 0
.ancestors_collapsed: 1 74 77 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 7BB7848F801C8CAD7CF47C166A1BF9B53AD22E26BDC2493BBBEB2231BFE13082
.indent: 1 1
@@ -1808,7 +1728,6 @@
.ancestors: 1 74 0 0 77 0 0 0
.ancestors_collapsed: 1 74 77 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 8856F16263FBACB88B9C7EB946FF75D56F62501186A1CF7E1B2FC52A5A65C64A
.indent: 1 1
@@ -1837,7 +1756,6 @@
.ancestors: 1 74 0 0 77 92 0 0
.ancestors_collapsed: 1 74 77 92 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C956CEEFB49537095357BF0BA878E01BC85E4570A5A4C13F370C3D8C4736312F
| Boston, May 2003. Starbucks. Sean and Adrian are on their way to pick me up for dinner. I’ve already had too much coffee, so I sit at the window reading the paper. Eventually Adrian calls to find out where I am, I tell him, and he promises to show up in fifteen minutes. I get bored and go outside to wait, watch the traffic go by. More or less right on time (only post-dotcom is Adrian ever on time), Sean’s new blue VW Beetle rolls into view. Adrian jumps out of the passenger seat and into the back, and I get in. Sean has been driving for a little over a year. He seems confident, cautious, but meanders through the streets of Cambridge. We are destined for Winchester, a township on the Charles River, in order to go to an Indian restaurant that one of Sean’s friends has recommended. When I ask how they are doing, they say, “Good, good.” Adrian offers, “Well, Sean’s better than he has been in two years.” “Really?” I say, impressed.
@@ -1848,7 +1766,6 @@
.ancestors: 1 74 0 0 77 92 0 0
.ancestors_collapsed: 1 74 77 92 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A5A54B9BE8B9B6429E5BCB7091FA3F59399521F26F435513DD8FF4C355F7159D
| Sean says, “Well, happier than at least the last year. I, well, let me put it this way: forgive me father for I have sinned, I still have unclean thoughts about some of the upper management in the company, I occasionally think they are not doing things in the best interest of the company, and I see them as self-serving and sometimes wish them ill.” In this rolling blue confessional Sean describes some of the people who I am familiar with whom he now tries very hard not to think about. I look at him and say, “Ten Hail Marys and ten Our Fathers, and you will be absolved, my child.” Turning to Adrian, I ask, “And what about you?” Adrian continues the joke: “I, too, have sinned. I have reached the point where I can see absolutely nothing good coming of this company but that I can keep my investments in it long enough to pay for my children’s college tuition.” I say, “You, my son, I cannot help.” Sean says, “Well, funny thing about tainted money . . . there just taint enough of it.”
@@ -1859,7 +1776,6 @@
.ancestors: 1 74 0 0 77 92 0 0
.ancestors_collapsed: 1 74 77 92 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 842C8F2E7574A5DDAB9E25BDA6837BB20AF6B397082E061CE8328B63FF196F0C
| I am awestruck. When I met Sean and Adrian, in 1997, their start-up company, Amicas, was full of spit, with five employees working out of Adrian’s living room and big plans to revolutionize the medical-imaging world. They had connived to get Massachusetts General Hospital to install their rudimentary system and let it compete with the big corporate sloths that normally stalked back offices: General Electric, Agfa, Siemens. It was these behemoths, according to Sean and Adrian, that were bilking hospitals ⑆,┨[pg 32]┣, and healthcare providers with promises of cure-all technologies and horribly designed “silos,” “legacy systems,” and other closed-system monsters of corporate IT harkening back to the days of IBM mainframes. These beasts obviously did not belong to the gleaming future of Internet-enabled scalability. By June of 2000, Amicas had hired new “professional” management, moved to Watertown, and grown to about a hundred employees. They had achieved their goal of creating an alternative Picture Archiving and Communication System (PACS) for use in hospital radiology departments and based on Internet standards.
@@ -1870,7 +1786,6 @@
.ancestors: 1 74 0 0 77 92 0 0
.ancestors_collapsed: 1 74 77 92 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1058F09A913F2C33E2DC0BF8C8C616D9866C9BB150D612DC3CD83F1144F101D8
| At that point, in the spring of 2000, Sean could still cheerfully introduce me to his new boss—the same man he would come to hate, inasmuch as Sean hates anyone. But by 2002 he was frustrated by the extraordinary variety of corner-cutting and, more particularly, by the complacency with which management ignored his recommendations and released software that was almost certainly going to fail later, if not sooner. Sean, who is sort of permanently callow about things corporate, could find no other explanation than that the new management was evil.
@@ -1881,7 +1796,6 @@
.ancestors: 1 74 0 0 77 92 0 0
.ancestors_collapsed: 1 74 77 92 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 65DB91F464453ED79C114FC63B0988B572C38ADDDB18ED3C12309420BDFB35A9
| But by 2003 the company had succeeded, having grown to more than 200 employees and established steady revenue and a stable presence throughout the healthcare world. Both Sean and Adrian were made rich—not wildly rich, but rich enough—by its success. In the process, however, it also morphed into exactly what Sean and Adrian had created it in order to fight: a slothlike corporate purveyor of promises and broken software. Promises Adrian had made and software Sean had built. The failure of Amicas to transform healthcare was a failure too complex and technical for most of America to understand, but it rested atop the success of Amicas in terms more readily comprehensible: a growing company making profit. Adrian and Sean had started the company not to make money, but in order to fix a broken healthcare system; yet the system stayed broken while they made money.
@@ -1892,7 +1806,6 @@
.ancestors: 1 74 0 0 77 92 0 0
.ancestors_collapsed: 1 74 77 92 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 90B2F62C550BA784B0FAB70DA65CAFB6C6071CD52502BDAE3ACF0D75B8EB975A
| In the rolling confessional, Sean and Adrian did in fact see me, however jokingly, as a kind of redeemer, a priest (albeit of an order with no flock) whose judgment of the affairs past was essential to their narration of their venture as a success, a failure, or as an unsatisfying and complicated mixture of both. I thought about this strange moment of confession, of the combination of recognition and denial, of Adrian’s new objectification of the company as an ⑆,┨[pg 33]┣, investment opportunity, and of Sean’s continuing struggle to make his life and his work harmonize in order to produce good in the world. Only the promise of the next project, the next mission (and the ostensible reason for our dinner meeting) could possibly have mitigated the emotional disaster that their enterprise might otherwise be. Sean’s and Adrian’s endless, arcane fervor for the promise of new technologies did not cease, even given the quotidian calamities these technologies leave in their wake. Their faith was strong, and continuously tested.
@@ -1903,7 +1816,6 @@
.ancestors: 1 74 0 0 77 92 0 0
.ancestors_collapsed: 1 74 77 92 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8561D9EDBBBEB176861182C5D873217F4AC7267E23899165D81A56CA36F200AC
| Adrian’s and Sean’s passion was not for money—though money was a powerful drug—it was for the Internet: for the ways in which the Internet could replace the existing infrastructure of hospitals and healthcare providers, deliver on old promises of telemedicine and teleradiology, and, above all, level a playing field systematically distorted and angled by corporate and government institutions that sought secrecy and private control, and stymied progress. In healthcare, as Adrian repeatedly explained to me, this skewed playing field was not only unfair but malicious and irresponsible. It was costing lives. It slowed the creation and deployment of technologies and solutions that could lower costs and thus provide more healthcare for more people. The Internet was not part of the problem; it was part of the solution to the problems that ailed 1990s healthcare.
@@ -1914,7 +1826,6 @@
.ancestors: 1 74 0 0 77 92 0 0
.ancestors_collapsed: 1 74 77 92 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0E890A819F122D2A6621694D90A900C18636D8A9D520790C848012C469CCE264
| At the end of our car trip, at the Indian restaurant in Winchester, I learned about their next scheme, a project called MedCommons, which would build on the ideals of Free Software and give individuals a way to securely control and manage their own healthcare data. The rhetoric of commons and the promise of the Internet as an infrastructure dominated our conversation, but the realities of funding and the question of whether MedCommons could be pursued without starting another company remained unsettled. I tried to imagine what form a future confession might take.
@@ -1942,7 +1853,6 @@
.ancestors: 1 74 0 0 77 101 0 0
.ancestors_collapsed: 1 74 77 101 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9140A0116F7B268CFFBE5F1D0CFF5653DED75CAD1C539BD5F40FA8D4B67CE3E4
| Sean and Adrian are geeks. They are entrepreneurs and idealists in different ways, a sometimes paradoxical combination. They are certainly ⑆,┨[pg 34]┣, obsessed with technology, but especially with the Internet, and they clearly distinguish themselves from others who are obsessed with technology of just any sort. They aren’t quite representative—they do not stand in for all geeks—but the way they think about the Internet and its possibilities might be. Among the rich story of their successes and failures, one might glimpse the outlines of a question: where do their sympathies lie? Who are they with? Who do they recognize as being like them? What might draw them together with other geeks if not a corporation, a nation, a language, or a cause? What binds these two geeks to any others?
@@ -1953,7 +1863,6 @@
.ancestors: 1 74 0 0 77 101 0 0
.ancestors_collapsed: 1 74 77 101 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AAD8223DD592BD32F2E93ED0E5E3005A59A013221FC94FE6A47090B5C12B7DF4
| Sean worked for the Federal Reserve in the 1980s, where he was introduced to UNIX, C programming, EMACS, Usenet, Free Software, and the Free Software Foundation. But he was not a Free Software hacker; indeed, he resisted my attempts to call him a hacker at all. Nevertheless, he started a series of projects and companies with Adrian that drew on the repertoire of practices and ideas familiar from Free Software, including their MedCommons project, which was based more or less explicitly in the ideals of Free Software. Adrian has a degree in medicine and in engineering, and is a serial entrepreneur, with Amicas being his biggest success—and throughout the last ten years has attended all manner of conferences and meetings devoted to Free Software, Open Source, open standards, and so on, almost always as the lone representative from healthcare. Both graduated from the MIT (Sean in economics, Adrian in engineering), one of the more heated cauldrons of the Internet and the storied home of hackerdom, but neither were MIT hackers, nor even computer-science majors.
@@ -1975,7 +1884,6 @@
.ancestors: 1 74 0 0 77 101 0 0
.ancestors_collapsed: 1 74 77 101 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4019B25361F18A6FB6F3762DB49D9502A6F8D794C783D36398EBB8E96BD7B28C
| Their goals in creating a start-up rested on their understanding of the Internet as an infrastructure: as a standardized infrastructure with certain extremely powerful properties, not the least of which was its flexibility. Sean and Adrian talked endlessly about open systems, open standards, and the need for the Internet to remain open and standardized. Adrian spoke in general terms about how it would revolutionize healthcare; Sean spoke in specific terms about how it structured the way Amicas’s software was being designed and written. Both participated in standards committees and in the online and offline discussions that are tantamount to policymaking in the Internet world. The company they created was a “virtual” company, that is, built on tools that depended on the Internet and allowed employees to manage and work from a variety of locations, though not without frustration, of course: Sean waited years for broadband access in his home, and the hospitals they served ⑆,┨[pg 35]┣, hemmed themselves in with virtual private networks, intranets, and security firewalls that betrayed the promises of openness that Sean and Adrian heralded.
@@ -1986,7 +1894,6 @@
.ancestors: 1 74 0 0 77 101 0 0
.ancestors_collapsed: 1 74 77 101 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 07CD33F2BFC1FB21B7380B8857151519E0E22CF91C5EA5D4BB7686A3C4CB3D11
| The Internet was not the object of their work and lives, but it did represent in detail a kind of moral or social order embodied in a technical system and available to everyone to use as a platform whereby they might compete to improve and innovate in any realm. To be sure, although not all Internet entrepreneurs of the 1990s saw the Internet in the same way, Sean and Adrian were hardly alone in their vision. Something about the particular way in which they understood the Internet as representing a moral order—simultaneously a network, a market, a public, and a technology—was shared by a large group of people, those who I now refer to simply as geeks.
@@ -1997,7 +1904,6 @@
.ancestors: 1 74 0 0 77 101 0 0
.ancestors_collapsed: 1 74 77 101 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 73A39AAF90390CF789BF966FB1F41CBD1BC1F36F30DAE1BE805D2877A1DDD826
.has: links notes_reg
@@ -2010,7 +1916,6 @@
.ancestors: 1 74 0 0 77 101 0 0
.ancestors_collapsed: 1 74 77 101 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4A332E35F42232D82D0EA4066F14064C55EE0EC70673C799ABFF83E8048BE448
.has: links notes_reg
@@ -2023,7 +1928,6 @@
.ancestors: 1 74 0 0 77 101 0 0
.ancestors_collapsed: 1 74 77 101 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DB1E669081A8C311616CFBFD383D8AC7E18E58702AD4C635175838E8FD9CBE51
| For the purists like Hayden, geeks were there first, and they understood something, lived in a way, that simply cannot be comprehended by “script kiddies” (i.e., teenagers who perform the hacking equivalent of spray painting or cow tipping), crackers, or AOL users, all of whom are despised by Hayden-style geeks as unskilled users who parade around the Internet as if they own it. While certainly elitist, Hayden captures the distinction between those who are legitimately allowed to call themselves geeks (or hackers) and those who aren’t, a distinction that is often formulated recursively, of course: “You are a hacker when another hacker calls you a hacker.”
@@ -2034,7 +1938,6 @@
.ancestors: 1 74 0 0 77 101 0 0
.ancestors_collapsed: 1 74 77 101 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F109931906A50C74825109860C1DDC07FCD4277E3C082A5935CA219BCD391372
.has: notes_reg
@@ -2063,7 +1966,6 @@
.ancestors: 1 74 0 0 77 110 0 0
.ancestors_collapsed: 1 74 77 110 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9F50762D122225BCE3C61B54271CEEF7B0431AAA0256E7F7CA7B2D66E1263810
| Berlin, November 1999. I am in a very hip club in Mitte called WMF. It’s about eight o’clock—five hours too early for me to be a hipster, but the context is extremely cool. WMF is in a hard-to-find, abandoned building in the former East; it is partially converted, filled with a mixture of new and old furnishings, video projectors, speakers, makeshift bars, and dance-floor lighting. A crowd of around fifty people lingers amid smoke and Beck’s beer bottles, ⑆,┨[pg 37]┣, sitting on stools and chairs and sofas and the floor. We are listening to an academic read a paper about Claude Shannon, the MIT engineer credited with the creation of information theory. The author is smoking and reading in German while the audience politely listens. He speaks for about seventy minutes. There are questions and some perfunctory discussion. As the crowd breaks up, I find myself, in halting German that quickly converts to English, having a series of animated conversations about the GNU General Public License, the Debian Linux Distribution, open standards in net radio, and a variety of things for which Claude Shannon is the perfect ghostly technopaterfamilias, even if his seventy-minute invocation has clashed heavily with the surroundings.
@@ -2074,7 +1976,6 @@
.ancestors: 1 74 0 0 77 110 0 0
.ancestors_collapsed: 1 74 77 110 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9B367E3831DF3C095C24990C39A51B5DAB6FE3FEAD30C31224BE8ED76899FD2A
| Despite my lame German, I still manage to jump deeply into issues that seem extremely familiar: Internet standards and open systems and licensing issues and namespaces and patent law and so on. These are not businesspeople, this is not a start-up company. As I would eventually learn, there was even a certain disdain for die Krawattenfaktor, the suit-and-tie factor, at these occasional, hybrid events hosted by Mikro e.V., a nonprofit collective of journalists, academics, activists, artists, and others interested in new media, the Internet, and related issues. Mikro’s constituency included people from Germany, Holland, Austria, and points eastward. They took some pride in describing Berlin as “the farthest East the West gets” and arranged for a group photo in which, facing West, they stood behind the statue of Marx and Lenin, who face East and look eternally at the iconic East German radio tower (Funkturm) in Alexanderplatz. Mikro’s members are resolutely activist and see the issues around the Internet-as-infrastructure not in terms of its potential for business opportunities, but in urgently political and unrepentantly aesthetic terms—terms that are nonetheless similar to those of Sean and Adrian, from whom I learned the language that allows me to mingle with the Mikro crowd at WMF. I am now a geek.
@@ -2085,7 +1986,6 @@
.ancestors: 1 74 0 0 77 110 0 0
.ancestors_collapsed: 1 74 77 110 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 92F5B9CBE79D5CAB5F1870CCE3D7E776C1FEC9A4C7A78DFC9226D669CA49D39C
| Before long, I am talking with Volker Grassmuck, founding member of Mikro and organizer of the successful “Wizards of OS” conference, held earlier in the year, which had the very intriguing subtitle “Operating Systems and Social Systems.” Grassmuck is inviting me to participate in a planning session for the next WOS, held at the Chaos Computer Congress, a hacker gathering that occurs each year in December in Berlin. In the following months I will meet a huge number of people who seem, uncharacteristically for artists ⑆,┨[pg 38]┣, and activists, strangely obsessed with configuring their Linux distributions or hacking the http protocol or attending German Parliament hearings on copyright reform. The political lives of these folks have indeed mixed up operating systems and social systems in ways that are more than metaphorical.
@@ -2113,7 +2013,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 951B239F06C0FAE7E3A588435B4B164729B6A2E1C0D8AD4A4A86FECC1ED859A8
| If intuition can lead one from geek to geek, from start-up to nightclub, and across countries, languages, and professional orientations, it can only be due to a shared set of ideas of how things fit together in the world. These ideas might be “cultural” in the traditional sense of finding expression among a community of people who share backgrounds, homes, nations, languages, idioms, ethnos, norms, or other designators of belonging and co-presence. But because the Internet—like colonialism, satellite broadcasting, and air travel, among other things—crosses all these lines with abandon that the shared idea of order is better understood as part of a public, or public sphere, a vast republic of letters and media and ideas circulating in and through our thoughts and papers and letters and conversations, at a planetary scope and scale.
@@ -2135,7 +2034,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F02ACD06E35A2B3E23A0B6604FF3C02B13B3C913D2E725B58AE4E712B3F60557
| “Public sphere” is an odd kind of thing, however. It is at once a concept—intended to make sense of a space that is not the here and now, but one made up of writings, ideas, and discussions—and a set of ideas that people have about themselves and their own participation in such a space. I must be able to imagine myself speaking and being spoken to in such a space and to imagine a great number of other people also doing so according to unwritten rules we share. I don’t need a complete theory, and I don’t need to call it a public sphere, but I must somehow share an idea of order with all those other people who also imagine themselves participating in and subjecting themselves to that order. In fact, if the public sphere exists as more than just a theory, then it has no other basis than just such a shared imagination of order, an imagination which provides a guide against which to make judgments and a map for changing or achieving that order. Without such a shared imagination, a public sphere is otherwise nothing more than a cacophony of voices and information, nothing more than a stream of data, structured and formatted by and for machines, whether paper or electronic. ⑆,┨[pg 39]┣,
@@ -2146,7 +2044,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 668ABD7D476D4345779007AB21F76D72AF1EC6D109F71126B8A73C23BB19E40B
.has: notes_reg
@@ -2158,7 +2055,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 25FBC8C280EA919EB3C02B1590DDB79781AC63608F4BB125258687FE73516486
.has: notes_reg
@@ -2170,7 +2066,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AAF80A2869C599ADAB4723903235F691817036646731901D642EBEF9C6353306
.has: notes_reg
@@ -2182,7 +2077,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B58EAA6ED547C9C0E609ED1A5C7EE0AE93AEBA8DFE8F468ECD5540376F193A9E
| The concept of recursive public, like that of Taylor’s public sphere, is understood here as a kind of social imaginary. The primary reason is to bypass the dichotomy between ideas and material practice. Because the creation of software, networks, and legal documents are precisely the kinds of activities that trouble this distinction—they are at once ideas and things that have material effects in the ⑆,┨[pg 40]┣, world, both expressive and performative—it is extremely difficult to identify the properly material materiality (source code? computer chips? semiconductor manufacturing plants?). This is the first of the reasons why a recursive public is to be distinguished from the classic formulae of the public sphere, that is, that it requires a kind of imagination that includes the writing and publishing and speaking and arguing we are familiar with, as well as the making of new kinds of software infrastructures for the circulation, archiving, movement, and modifiability of our enunciations.
@@ -2193,7 +2087,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C7D57EDF7F55432DAEEB3BD32747EB08E7677A0C14BEE190DB1636D31C96E0E1
.has: notes_reg
@@ -2205,7 +2098,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 713503D491B55D690951EA71929F5C860A17B22156AE2041721BE575D3A30D2B
.has: notes_reg
@@ -2217,7 +2109,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CA6DD8447BF0AFD602DBF3BE5E9B91E7879056A3B0FC1FF403F7EA41F56D4788
.has: notes_reg
@@ -2229,7 +2120,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B73853D88551FBA3BC1CF639322216EA6893BDFA094BA53022617115E1391B10
.has: notes_reg
@@ -2241,7 +2131,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2B1B4F4C1DC3108815918754DDF7CB8D9DC734A6B54371D2A13D899F1391A357
| For Ricoeur, the very substance of life begins in the interpretation of reality, and therefore ideologies (as well as utopias—and perhaps conspiracies) could well be treated as systems that integrate those interpretations into the meaningful wholes of political life. Ricoeur’s analysis of the integration of reality though social imagination, however, does not explicitly address how imagination functions: what exactly is the nature of this symbolic action or interpretation, or imagination? Can one know it from the outside, and does it resist the distinction between ideology and material practice? Both Ricoeur and Geertz harbor hope that ideology can be made scientific, that the integration of reality through symbolic action requires only the development of concepts adequate to the job.
@@ -2252,7 +2141,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4D1133EDA07821CB77E04813A54E367E49E64535B8843CB773D219201268CC3C
.has: notes_reg
@@ -2264,7 +2152,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5AE964D22A2CCE271DA40B7F50639885818EC002F1BECE800A7DA90BB11270C9
.has: notes_reg
@@ -2276,7 +2163,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5ADE6E74E431C00BE622341F22616EAF6E7D711E0A08A49C6F10304A91F5D807
| The social imaginary is not simply the norms that structure our actions; it is also a sense of what makes norms achievable or “realizable,” as Taylor says. This is the idea of a “moral order,” one that we expect to exist, and if it doesn’t, one that provides a plan for achieving it. For Taylor, there is such a thing as a “modern idea of order,” which includes, among other things, ideas of what it means to be an individual, ideas of how individual passions and desires are related to collective association, and, most important, ideas about living in time together (he stresses a radically secular conception of time—secular in a sense that means more than simply “outside religion”). He by no means insists that this is the only such definition of modernity (the door is wide open to understanding alternative modernities), but that the modern idea of moral order is ⑆,┨[pg 43]┣, one that dominates and structures a very wide array of institutions and individuals around the world.
@@ -2287,7 +2173,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 081E030694D5A605CDDC68BD34366D9F50E2510A49993A112E1D184B223C9B0B
| The “modern idea of moral order” is a good place to return to the question of geeks and their recursive publics. Are the ideas of order shared by geeks different from those Taylor outlines? Do geeks like Sean and Adrian, or activists in Berlin, possess a distinctive social imaginary? Or do they (despite their planetary dispersal) participate in this common modern idea of moral order? Do the stories and narratives, the tools and technologies, the theories and imaginations they follow and build on have something distinctive about them? Sean’s and Adrian’s commitment to transforming healthcare seems to be, for instance, motivated by a notion of moral order in which the means of allocation of healthcare might become more just, but it is also shot through with technical ideas about the role of standards, the Internet, and the problems with current technical solutions; so while they may seem to be simply advocating for better healthcare, they do so through a technical language and practice that are probably quite alien to policymakers, upper management, and healthcare advocacy groups that might otherwise be in complete sympathy.
@@ -2298,7 +2183,6 @@
.ancestors: 1 74 0 0 77 114 0 0
.ancestors_collapsed: 1 74 77 114 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4BE4AAB2218760A476D98667EA82C32A1C143AAA35221D2BF2AEFDA8EB46CA0A
| The affinity of geeks for each other is processed through and by ideas of order that are both moral and technical—ideas of order that do indeed mix up “operating systems and social systems.” These systems include the technical means (the infrastructure) through which geeks meet, assemble, collaborate, and plan, as well as how they talk and think about those activities. The infrastructure—the Internet—allows for a remarkably wide and diverse array of people to encounter and engage with each other. That is to say, the idea of order shared by geeks is shared because they are geeks, because they “get it,” because the Internet’s structure and software have taken a particular form through which geeks come to understand the moral order that gives the fabric of their political lives warp and weft.
@@ -2326,7 +2210,6 @@
.ancestors: 1 74 0 0 77 131 0 0
.ancestors_collapsed: 1 74 77 131 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 008168FEC4E02D37A254F8CD1FCB87FDC30A7823C5C928EAB1DAF52AFB04F5D9
| Bangalore, March 2000. I am at another bar, this time on one of Bangalore’s trendiest streets. The bar is called Purple Haze, and I have been taken there, the day after my arrival, by Udhay Shankar ⑆,┨[pg 44]┣, N. Inside it is dark and smoky, purple, filled with men between eighteen and thirty, and decorated with posters of Jimi Hendrix, Black Sabbath, Jim Morrison (Udhay: “I hate that band”), Led Zeppelin, and a somewhat out of place Frank Zappa (Udhay: “One of my political and musical heroes”). All of the men, it appears, are singing along with the music, which is almost without exception heavy metal.
@@ -2337,7 +2220,6 @@
.ancestors: 1 74 0 0 77 131 0 0
.ancestors_collapsed: 1 74 77 131 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 869F7AA8788ADC3101E5EC0AC9F24915A98BE56B13BD3215E332ECC61284BF55
| I engage in some stilted conversation with Udhay and his cousin Kirti about the difference between Karnatic music and rock-androll, which seems to boil down to the following: Karnatic music decreases metabolism and heart rate, leading to a relaxed state of mind; rock music does the opposite. Given my aim of focusing on the Internet and questions of openness, I have already decided not to pay attention to this talk of music. In retrospect, I understand this to have been a grave methodological error: I underestimated the extent to which the subject of music has been one of the primary routes into precisely the questions about the “reorientation of knowledge and power” I was interested in. Over the course of the evening and the following days, Udhay introduced me, as promised, to a range of people he either knew or worked with in some capacity. Almost all of the people I met appeared to sincerely love heavy-metal music.
@@ -2348,7 +2230,6 @@
.ancestors: 1 74 0 0 77 131 0 0
.ancestors_collapsed: 1 74 77 131 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 72EBDD56AF0AD74200F43E4BD582888182F8CEE67070EDAAE6BBB0068797F023
| I met Udhay Shankar N. in 1999 through a newsletter, distributed via e-mail, called Tasty Bits from the Technology Front. It was one of a handful of sources I watched closely while in Berlin, looking for such connections to geek culture. The newsletter described a start-up company in Bangalore, one that was devoted to creating a gateway between the Internet and mobile phones, and which was, according to the newsletter, an entirely Indian operation, though presumably with U.S. venture funds. I wanted to find a company to compare to Amicas: a start-up, run by geeks, with a similar approach to the Internet, but halfway around the world and in a “culture” that might be presumed to occupy a very different kind of moral order. Udhay invited me to visit and promised to introduce me to everyone he knew. He described himself as a “random networker”; he was not really a programmer or a designer or a Free Software geek, despite his extensive knowledge of software, devices, operating systems, and so on, including Free and Open Source Software. Neither was he a businessman, but rather described himself as the guy who “translates between the suits and the techs.” ⑆,┨[pg 45]┣,
@@ -2359,7 +2240,6 @@
.ancestors: 1 74 0 0 77 131 0 0
.ancestors_collapsed: 1 74 77 131 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 34012BF5DE233D5B9FB156C73720F31115F21F42ABDAE2762A998B958186BABA
.has: notes_reg
@@ -2371,7 +2251,6 @@
.ancestors: 1 74 0 0 77 131 0 0
.ancestors_collapsed: 1 74 77 131 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 56F1535E6220A47DDDA74205AD58CDFA83E2A81C7023BEFE9E21267C71117B75
| While I was in Bangalore, I was invited to join a mailing list run by Udhay called Silk-list, an irregular, unmoderated list devoted to “intelligent conversation.” The list has no particular focus: long, meandering conversations about Indian politics, religion, economics, and history erupt regularly; topics range from food to science fiction to movie reviews to discussions on Kashmir, Harry Potter, the singularity, or nanotechnology. Udhay started Silk-list in 1997 with Bharath Chari and Ram Sundaram, and the recipients have included hundreds of people around the world, some very well-known ones, programmers, lawyers, a Bombay advertising executive, science-fiction authors, entrepreneurs, one member of the start-up Amicas, at least two transhumanists, one (diagnosed) schizophrenic, and myself. Active participants usually numbered about ten to fifteen, while many more lurked in the background.
@@ -2393,7 +2272,6 @@
.ancestors: 1 74 0 0 77 131 0 0
.ancestors_collapsed: 1 74 77 131 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5BD849867D135358FE71C9DA19873F1A44C0376A8E595B4AA99E82B3B08DFFBD
.has: notes_reg
@@ -2405,7 +2283,6 @@
.ancestors: 1 74 0 0 77 131 0 0
.ancestors_collapsed: 1 74 77 131 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DF88C46403C6CC986B389DC9367E9E475BF4FDD0566702E6AB4A2E0725920166
| Like many similar communities of “digerati” during and after the dot.com boom, Silk-list constituted itself more or less organically around people who “got it,” that is, people who claimed to understand the Internet, its transformative potential, and who had the technical skills to participate in its expansion. Silk-list was not the only list of its kind. Others such as the Tasty Bits newsletter, the FoRK (Friends of Rohit Khare) mailing list (both based in Boston), and the Nettime and Syndicate mailing lists (both based in the Netherlands) ostensibly had different reasons for existence, but many had the same subscribers and overlapping communities of geeks. Subscription was open to anyone, and occasionally someone would stumble on the list and join in, but most were either invited by members or friends of friends, or they were connected by virtue of cross-posting from any number of other mailing lists to which members were subscribed.
@@ -2433,7 +2310,6 @@
.ancestors: 1 74 0 0 77 139 0 0
.ancestors_collapsed: 1 74 77 139 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A818EB14C6F8507C2150B846D05A1C227A2DCD55BE2806E57627A6E1310107B2
| Silk-list is public in many senses of the word. Practically speaking, one need not be invited to join, and the material that passes through the list is publicly archived and can be found easily on the Internet. Udhay does his best to encourage everyone to speak and to participate, and to discourage forms of discourse that he thinks ⑆,┨[pg 47]┣, might silence participants into lurking. Silk-list is not a government, corporate, or nongovernmental list, but is constituted only through the activity of geeks finding each other and speaking to each other on this list (which can happen in all manner of ways: through work, through school, through conferences, through fame, through random association, etc.). Recall Charles Taylor’s distinction between a topical and a metatopical space. Silk-list is not a conventionally topical space: at no point do all of its members meet face-to-face (though there are regular meet-ups in cities around the world), and they are not all online at the same time (though the volume and tempo of messages often reflect who is online “speaking” to each other at any given moment). It is a topical space, however, if one considers it from the perspective of the machine: the list of names on the mailing list are all assembled together in a database, or in a file, on the server that manages the mailing list. It is a stretch to call this an “assembly,” however, because it assembles only the avatars of the mailing-list readers, many of whom probably ignore or delete most of the messages.
@@ -2444,7 +2320,6 @@
.ancestors: 1 74 0 0 77 139 0 0
.ancestors_collapsed: 1 74 77 139 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C24D1ED4C65607A61EB21633A0091289470C97FBFFA278A5960B4FE26EA5CB41
| Silk-list is certainly, on the other hand, a “metatopical” public. It “knits together” a variety of topical spaces: my discussion with friends in Houston, and other members’ discussions with people around the world, as well as the sources of multiple discussions like newspaper and magazine articles, films, events, and so on that are reported and discussed online. But Silk-list is not “The” public—it is far from being the only forum in which the public sphere is knitted together. Many, many such lists exist.
@@ -2455,7 +2330,6 @@
.ancestors: 1 74 0 0 77 139 0 0
.ancestors_collapsed: 1 74 77 139 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 68F1E15999D57037EF20143E744C0724C13398F8E86B96B8E349E727133C4AF4
| In Publics and Counterpublics Michael Warner offers a further distinction. “The” public is a social imaginary, one operative in the terms laid out by Taylor: as a kind of vision of order evidenced through stories, images, narratives, and so on that constitute the imagination of what it means to be part of the public, as well as plans necessary for creating the public, if necessary. Warner distinguishes, however, between a concrete, embodied audience, like that at a play, a demonstration, or a riot (a topical public in Taylor’s terms), and an audience brought into being by discourse and its circulation, an audience that is not metatopical so much as it is a public that is concrete in a different way; it is concrete not in the face-to-face temporality of the speech act, but in the sense of calling a public into being through an address that has a different temporality. It is a public that is concrete in a media-specific ⑆,┨[pg 48]┣, manner: it depends on the structures of creation, circulation, use, performance, and reuse of particular kinds of discourse, particular objects or instances of discourse.
@@ -2477,7 +2351,6 @@
.ancestors: 1 74 0 0 77 139 0 0
.ancestors_collapsed: 1 74 77 139 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3C6E41FBDB77F3487D4915F820F0FA9641DE1FED9C7AF3F3EB74BB3F489D825A
.has: notes_reg
@@ -2489,7 +2362,6 @@
.ancestors: 1 74 0 0 77 139 0 0
.ancestors_collapsed: 1 74 77 139 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 52F5AC5746400274553BC1210E5968AB912DFB7EC80AA42C854B7C24A41FEC22
.has: notes_reg
@@ -2512,7 +2384,6 @@
.ancestors: 1 74 0 0 77 139 0 0
.ancestors_collapsed: 1 74 77 139 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 73BDA9550FA4FEFFB44EF5F2CF10FAF42D35E23FA5978DAC05461A63B1952CAC
| Warner’s description makes no claim that any public or even The Public actually takes this form in the present: it is a description of a social imaginary or a “faith” that allows individuals to make sense of their actions according to a modern idea of social order. As Warner (and Habermas before him) suggests, the existence of such autonomous publics—and certainly the idea of “public opinion”— does not always conform to this idea of order. Often such publics turn out to have been controlled all along by states, corporations, capitalism, and other forms of social totality that determine the nature of discourse in insidious ways. A public whose participants have no faith that it is autotelic and autonomous is little more than a charade meant to assuage opposition to authority, to transform ⑆,┨[pg 49]┣, political power and equality into the negotiation between unequal parties.
@@ -2523,7 +2394,6 @@
.ancestors: 1 74 0 0 77 139 0 0
.ancestors_collapsed: 1 74 77 139 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2353E2B0A3BDC1EE0689D3F36C5F3F9DF0CA2C79ADA3CF318B15A30F17CC3DA2
| Is Silk-list a public? More important, is it a sovereign one? Warner’s distinction between different media-specific forms of assembly is crucial to answering this question. If one wants to know whether a mailing list on the Internet is more or less likely to be a sovereign public than a book-reading public or the nightly-news-hearing one, then one needs to approach it from the specificity of the form of discourse. This specificity not only includes whether the form is text or video and audio, or whether the text is ASCII or Unicode, or the video PAL or NTSC, but it also includes the means of creation, circulation, and reuse of that discourse as well.
@@ -2534,7 +2404,6 @@
.ancestors: 1 74 0 0 77 139 0 0
.ancestors_collapsed: 1 74 77 139 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5211FD5D9D4FF135C7D803A532DCC9A308A39570C76526C999BFD696729B6626
| The on-demand, Internet-mediated book, by contrast, will have a much different temporality of circulation: it might languish in obscurity due to lack of marketing or reputable authority, or it might get mentioned somewhere like the New York Times and suddenly become a sensation. For such a book, copyright law (in the form of a copyleft license) might allow a much wider range of uses and reuses, but it will restrict certain forms of commercialization of the text. The two publics might therefore end up looking quite different, overlapping, to be sure, but varying in terms of their control ⑆,┨[pg 50]┣, and the terms of admittance. What is at stake is the power of one or the other such public to appear as an independent and sovereign entity—free from suspect constraints and control—whose function is to argue with other constituted forms of power.
@@ -2545,7 +2414,6 @@
.ancestors: 1 74 0 0 77 139 0 0
.ancestors_collapsed: 1 74 77 139 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 279E4C1D1CB59C69DA960CA99153FAD28A06D3F78878D2E30F98BEE2D8A41EF4
| The conventionally published book may well satisfy all the criteria of being a public, at least in the colloquial sense of making a set of ideas and a discourse widely available and expecting to influence, or receive a response from, constituted forms of sovereign power. However, it is only the latter “on-demand” scheme for publishing that satisfies the criteria of being a recursive public. The differences in this example offer a crude indication of why the Internet is so crucially important to geeks, so important that it draws them together, in its defense, as an infrastructure that enables the creation of publics that are thought to be autonomous, independent, and autotelic. Geeks share an idea of moral and technical order when it comes to the Internet; not only this, but they share a commitment to maintaining that order because it is what allows them to associate as a recursive public in the first place. They discover, or rediscover, through their association, the power and possibility of occupying the position of independent public—one not controlled by states, corporations, or other organizations, but open (they claim) through and through—and develop a desire to defend it from encroachment, destruction, or refeudalization (to use Habermas’s term for the fragmentation of the public sphere).
@@ -2556,7 +2424,6 @@
.ancestors: 1 74 0 0 77 139 0 0
.ancestors_collapsed: 1 74 77 139 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D19B8C667F119F5FEDF97F2190DFB1A327D064816C190BB8364D6A1FFC95E09D
| The recursive public is thus not only the book and the discourse around the book. It is not even “content” expanded to include all kinds of media. It is also the technical structure of the Internet as well: its software, its protocols and standards, its applications and software, its legal status and the licenses and regulations that govern it. This captures both of the reasons why recursive publics are distinctive: (1) they include not only the discourses of a public, but the ability to make, maintain, and manipulate the infrastructures of those discourses as well; and (2) they are “layered” and include both discourses and infrastructures, to a specific technical extent (i.e., not all the way down). The meaning of which layers are important develops more or less immediately from direct engagement with the medium. In the following example, for instance, Napster represents the potential of the Internet in miniature—as an application—but it also connects immediately to concerns about the core protocols that govern the Internet and the process of standardization ⑆,┨[pg 51]┣, that governs the development of these protocols: hence recursion through the layers of an infrastructure.
@@ -2567,7 +2434,6 @@
.ancestors: 1 74 0 0 77 139 0 0
.ancestors_collapsed: 1 74 77 139 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7304E23B3C680E633195679FF194F5BE6F0202149D80969FEC516A7444D15377
| These two aspects of the recursive public also relate to a concern about the fragmentation or refeudalization of the public sphere: there is only one Internet. Its singularity is not technically determined or by any means necessary, but it is what makes the Internet so valuable to geeks. It is a contest, the goal of which is to maintain the Internet as an infrastructure for autonomous and autotelic publics to emerge as part of The Public, understood as part of an imaginary of moral and technical order: operating systems and social systems.
@@ -2595,7 +2461,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 249D685CA1A8B090446289F541DE69B716717A2408CC759A98062BF8C8F8A416
| On 27 July 2000 Eugen Leitl cross-posted to Silk-list a message with the subject line “Prelude to the Singularity.” The message’s original author, Jeff Bone (not at the time a member of Silk-list), had posted the “op-ed piece” initially to the FoRK mailing list as a response to the Recording Industry Association of America’s (RIAA) actions against Napster. The RIAA had just succeeded in getting U.S. district judge Marilyn Hall Patel, Ninth Circuit Court of Appeals, to issue an injunction to Napster to stop downloads of copyrighted music. Bone’s op-ed said,
@@ -2606,7 +2471,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 299D4D4C820708DF28CFF3F790C97A87788E47C566B1E0C053C56E0F2EDC2E1D
.indent: 1 1
@@ -2622,7 +2486,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1DFBEF0B96234D0103DCE727A3A7D34BE6927B2129862C6B4130F07042E3F317
| Bone’s message is replete with details that illustrate the meaning and value of the Internet to geeks, and that help clarify the concept ⑆,┨[pg 52]┣, of a recursive public. While it is only one message, it nonetheless condenses and expresses a variety of stories, images, folklore, and technical details that I elaborate herein.
@@ -2633,7 +2496,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8754CA3241B69D355D19732B6DAAF5017F544FE534AE283C6BB1037FD0D4E9C4
| The Napster shutdown in 2000 soured music fans and geeks alike, and it didn’t really help the record labels who perpetrated it either. For many geeks, Napster represented the Internet in miniature, an innovation that both demonstrated something on a scope and scale never seen before, and that also connected people around something they cared deeply about—their shared interest in music. Napster raised interesting questions about its own success: Was it successful because it allowed people to develop new musical interests on a scope and scale they had never experienced before? Or was it successful because it gave people with already existing musical interests a way to share music on a scope and scale they had never experienced before? That is to say, was it an innovation in marketing or in distribution? The music industry experienced it as the latter and hence as direct competition with their own means of distribution. Many music fans experienced it as the former, what Cory Doctorow nicely labeled “risk-free grazing,” meaning the ability to try out an almost unimaginable diversity of music before choosing what to invest one’s interests (and money) in. To a large extent, Napster was therefore a recapitulation of what the Internet already meant to geeks.
@@ -2644,7 +2506,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B5A99E127CD940CC871FB6E47400E7892AD99624C59ED6E647B9E0674D689ED9
| Bone’s message, the event of the Napster shutdown, and the various responses to it nicely illustrate the two key aspects of the recursive public: first, the way in which geeks argue not only about rights and ideas (e.g., is it legal to share music?) but also about the infrastructures that allow such arguing and sharing; second, the “layers” of a recursive public are evidenced in the immediate connection of Napster (an application familiar to millions) to the “decentralized routing protocols” (TCP/IP, DNS, and others) that made it possible for Napster to work the way it did.
@@ -2655,7 +2516,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C3FE1461C412E2106D8AA6B58E8F8C126BDCD75C5EA7A9E8534C2AE6EA58EBF9
.has: notes_reg
@@ -2667,7 +2527,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: ECEF08114455A9DDD2FCAB365E59D6A69CC65FC33E53D4B190F8CE5CB21C3678
| Bone’s affinity for transhumanist stories of evolutionary theory, economic theory, and rapid innovation sets the stage for the rest of his message. The crucial rhetorical gambit here is the appeal to inevitability (as in the emphatic “there is no doubt that this will happen”): Bone establishes that he is speaking to an audience that is accustomed to hearing about the inevitability of technical progress and the impossibility of legal maneuvering to change it, but his audience may not necessarily agree with these assumptions. Geeks occupy a spectrum from “polymath” to “transhumanist,” a spectrum that includes their understandings of technological progress and its relation to human intervention. Bone’s message clearly lands on the far transhumanist side.
@@ -2678,7 +2537,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 34943EBB1302050D3171EB74DDF351737C2AA5F23FBB7927994939EE08571FB4
| A second point concerns censorship and the locus of power: according to Bone, power does not primarily reside with the government or the church, but comes instead from the private sector, in this case the coalition of corporations represented by the RIAA. The significance of this has to do with the fact that a “public” is expected to be its own sovereign entity, distinct from church, state, or corporation, and while censorship by the church or the state is a familiar form of aggression against publics, censorship by corporations (or consortia representing them), as it strikes Bone and others, is a novel development. Whether the blocking of file-sharing can legitimately be called censorship is also controversial, and many Silk-list respondents found the accusation of censorship untenable.
@@ -2689,7 +2547,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A0DD597998BEAC45B7A2A190937B6F928A313CB624A9E97E6E8754B9BDB27D63
| Proving Bone’s contention, over the course of the subsequent years and court cases, the RIAA and the Motion Picture Association of America (MPAA) have been given considerably more police authority than even many federal agencies—especially with regard to policing networks themselves (an issue which, given its technical abstruseness, has rarely been mentioned in the mainstream mass media). Both organizations have not only sought to prosecute filesharers but have been granted rights to obtain information from Internet Service Providers about customer activities and have consistently sought the right to secretly disable (hack into, disable, or destroy) private computers suspected of illegal activity. Even if these practices may not be defined as censorship per se, they are nonetheless fine examples of the issues that most exercise geeks: the use of legal means by a few (in this case, private corporations) to ⑆,┨[pg 54]┣, suppress or transform technologies in wide use by the many. They also index the problems of monopoly, antitrust, and technical control that are not obvious and often find expression, for example, in allegories of reformation and the control of the music-sharing laity by papal authorities.
@@ -2700,7 +2557,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 514854EF41BED3260F4DF80BDACAE2558C84C531670FBE4EDE04D8C24939C131
| Third, Bone’s message can itself be understood in terms of the reorientation of knowledge and power. Although what it means to call his message an “op-ed” piece may seem obvious, Bone’s message was not published anywhere in any conventional sense. It doesn’t appear to have been widely cited or linked to. However, for one day at least, it was a heated discussion topic on three mailing lists, including Silk-list. “Publication” in this instance is a different kind of event than getting an op-ed in the New York Times.
@@ -2711,7 +2567,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 47D47595616DC636057CEAFE6BE0F440A808DD84351F8B5680428DFFD0AC4357
| The material on Silk-list rests somewhere between private conversation (in a public place, perhaps) and published opinion. No editor made a decision to “publish” the message—Bone just clicked “send.” However, as with any print publication, his piece was theoretically accessible by anyone, and what’s more, a potentially huge number of copies may be archived in many different places (the computers of all the participants, the server that hosts the list, the Yahoo! Groups servers that archive it, Google’s search databases, etc.). Bone’s message exemplifies the recursive nature of the recursive public: it is a public statement about the openness of the Internet, and it is an example of the new forms of publicness it makes possible through its openness.
@@ -2733,7 +2588,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 207636BC30C58E06DF5678E666DA51D0A25912CAE7128A082D5A414977DDD300
| The constraints on who speaks in a public sphere (such as the power of printers and publishers, the requirements of licensing, or issues of cost and accessibility) are much looser in the Internet era than in any previous one. The Internet gives a previously unknown Jeff Bone the power to dash off a manifesto without so much as a second thought. On the other hand, the ease of distribution belies the difficulty of actually being heard: the multitudes of other Jeff Bones make it much harder to get an audience. In terms of publics, Bone’s message can constitute a public in the same sense that a New York Times op-ed can, but its impact and meaning will be different. His message is openly and freely available for as long as there are geeks and laws and machines that maintain it, but the New York Times piece will have more authority, will be less accessible, and, most important, will not be available to just anyone. Geeks imagine a space where anyone can speak with similar reach and staying ⑆,┨[pg 55]┣, power—even if that does not automatically imply authority—and they imagine that it should remain open at all costs. Bone is therefore interested precisely in a technical infrastructure that ensures his right to speak about that infrastructure and offer critique and guidance concerning it.
@@ -2744,7 +2598,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CD2410DDE2083EE14FF68FF85DE7AF3DD665BCC3E18012C8A53C50AB8FAB4F71
.has: notes_reg
@@ -2756,7 +2609,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6EAC2D7804AED68427B9C7FB0FD7218A06E22707DC43D02DF039C4FEF82F433C
| In the early 1990s this version of the technical order of the Internet was part of a vibrant libertarian dogma asserting that the Internet simply could not be governed by any land-based sovereign and that it was fundamentally a place of liberty and freedom. This was the central message of people such as John Perry Barlow, John Gilmore, Howard Rheingold, Esther Dyson, and a host of others who populated both the pre-1993 Internet (that is, before the World Wide Web became widely available) and the pages of magazines such as Wired and Mondo 2000—the same group of people, incidentally, whose ideas were visible and meaningful to Udhay Shankar and his friends in India even prior to Internet access there, not to mention to Sean and Adrian in Boston, and artists and activists in ⑆,┨[pg 56]┣, Europe, all of whom often reacted more strongly against this libertarian aesthetic.
@@ -2767,7 +2619,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EB32CEFFE05F90AD883774FEB3E60A674507CBED902F7E6BCF753357E0E525E0
| For Jeff Bone (and a great many geeks), the folkloric notion that “the net treats censorship as damage” is a very powerful one: it suggests that censorship is impossible because there is no central point of control. A related and oft-cited sentiment is that “trying to take something off of the Internet is like trying to take pee out of a pool.” This is perceived by geeks as a virtue, not a drawback, of the Internet.
@@ -2778,7 +2629,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EB32CEFFE05F90AD883774FEB3E60A674507CBED902F7E6BCF753357E0E525E0
| For Jeff Bone (and a great many geeks), the folkloric notion that “the net treats censorship as damage” is a very powerful one: it suggests that censorship is impossible because there is no central point of control. A related and oft-cited sentiment is that “trying to take something off of the Internet is like trying to take pee out of a pool.” This is perceived by geeks as a virtue, not a drawback, of the Internet.
@@ -2789,7 +2639,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3496C06C02D15AD0599EA287188471A278E57C69C45441FAE20123F8E4F567C2
.has: notes_reg
@@ -2801,7 +2650,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FE692E1F55B1B206C50263B63DE89CBD9044FBD9AD4B32C94BAC726AAC74E136
| Lessig’s critique is actually at the heart of Bone’s concern, and the concern of recursive publics generally: the Internet is a contest and one that needs to be repeatedly and constantly replayed in order to maintain it as the legitimate infrastructure through which geeks associate with one another. Geeks argue in detail about what distinguishes technical factors from legal or social ones. Openness on the Internet is complexly intertwined with issues of availability, price, legal restriction, usability, elegance of design, censorship, trade secrecy, and so on. ⑆,┨[pg 57]┣,
@@ -2812,7 +2660,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 33E64625EA5C7B962C7EE570CE4F413F901998098B43073BED6B90E3D69A0BAF
| However, even where openness is presented as a natural tendency for technology (in oft-made analogies with reproductive fitness and biodiversity, for example), it is only a partial claim in that it represents only one of the “layers” of a recursive public. For instance, when Bone suggests that the net is “invulnerable to legal attack” because “technology will evolve more quickly than businesses and social institutions can,” he is not only referring to the fact that the Internet’s novel technical configuration has few central points of control, which makes it difficult for a single institution to control it, but also talking about the distributed, loosely connected networks of people who have the right to write and rewrite software and deal regularly with the underlying protocols of the Internet—in other words, of geeks themselves.
@@ -2823,7 +2670,6 @@
.ancestors: 1 74 0 0 77 151 0 0
.ancestors_collapsed: 1 74 77 151 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D71169C783ACC27C2F6F2723D9063F4F6D303C7714102F8E542B538BD75A6A90
| Many geeks, perhaps including Bone, discover the nature of this order by coming to understand how the Internet works—how it works technically, but also who created it and how. Some have come to this understanding through participation in Free Software (an exemplary “recursive public”), others through stories and technologies and projects and histories that illuminate the process of creating, growing, and evolving the Internet. The story of the process by which the Internet is standardized is perhaps the most well known: it is the story of the Internet Engineering Task Force and its Requests for Comments system.
@@ -2851,7 +2697,6 @@
.ancestors: 1 74 0 0 77 172 0 0
.ancestors_collapsed: 1 74 77 172 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 213AD5C90C1556927F915770F8E3C33B3E681290FCD352B4A877A0EFA4C40E56
| For many geeks, the Internet Engineering Task Force (IETF) and its Requests for Comments (RFC) system exemplify key features of the moral and technical order they share, the “stories and practices” that make up a social imaginary, according to Charles Taylor. The IETF is a longstanding association of Internet engineers who try to help disseminate some of the core standards of the Internet through ⑆,┨[pg 58]┣, the RFC process. Membership is open to individuals, and the association has very little real control over the structure or growth of the Internet—only over the key process of Internet standardization. Its standards rarely have the kind of political legitimacy that one associates with international treaties and the standards bodies of Geneva, but they are nonetheless de facto legitimate. The RFC process is an unusual standards process that allows modifications to existing technologies to be made before the standard is finalized. Together Internet standards and the RFC process form the background of the Napster debate and of Jeff Bone’s claims about “internet routing protocols.”
@@ -2862,7 +2707,6 @@
.ancestors: 1 74 0 0 77 172 0 0
.ancestors_collapsed: 1 74 77 172 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 10DBB5550E701FEE9B97639BA5D78E0A49842258FD4DD11E115AE88C70290FBE
.has: links notes_reg
@@ -2875,7 +2719,6 @@
.ancestors: 1 74 0 0 77 172 0 0
.ancestors_collapsed: 1 74 77 172 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B0A11C790B3520B5BA5DB1A777982E7451E3E953992FF73936C98A4187B454D4
.has: links notes_reg
@@ -2887,7 +2730,6 @@
.ancestors: 1 74 0 0 77 172 0 0
.ancestors_collapsed: 1 74 77 172 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 523A80DCFC8E60118AB901D3854AD332DCE524B6779556BF104D17121E951CBB
| Eugen’s flippancy reveals a recognition that there is a political component to coding, even if, in the end, talk disappears and only code remains. Though Eugen and others might like to adopt a rhetoric that suggests “it will just happen,” in practice none of them really act that way. Rather, the activities of coding, writing software, or improving and diversifying the software that exists are not inevitable or automatic but have specific characteristics. They require time and “the proper mental equipment.” The inevitability they refer to consists not in some fantasy of machine intelligence, but in a social imaginary shared by many people in loosely connected networks who spend all their free time building, downloading, hacking, testing, installing, patching, coding, arguing, blogging, and proselytizing—in short, creating a recursive public enabled by the Internet.
@@ -2898,7 +2740,6 @@
.ancestors: 1 74 0 0 77 172 0 0
.ancestors_collapsed: 1 74 77 172 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8A5007FEB64C08597A02EFC13306111A2A1CC03BA8BCDF93B499747C8266ED44
.has: notes_reg
@@ -2921,7 +2762,6 @@
.ancestors: 1 74 0 0 77 172 0 0
.ancestors_collapsed: 1 74 77 172 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B79EA95EDF3809DA60E8A536C27AD0D6E9037F30D7270A4E731E91DA35B23156
| RFCs have developed from an informal system of memos into a formal standardization process over the life of the Internet, as the IETF and the Internet Society (ISOC) have become more bureaucratic entities. The process of writing and maintaining these documents is particular to the Internet, precisely because the Internet ⑆,┨[pg 60]┣, is the kind of network experiment that facilitates the sharing of resources across administratively bounded networks. It is a process that has allowed all the experimenters to both share the network and to propose changes to it, in a common space. RFCs are primarily suggestions, not demands. They are “public domain” documents and thus available to everyone with access to the Internet. As David Clark’s reference to “consensus and running code” demonstrates, the essential component of setting Internet standards is a good, working implementation of the protocols. Someone must write software that behaves in the ways specified by the RFC, which is, after all, only a document, not a piece of software. Different implementations of, for example, the TCP/IP protocol or the File Transfer Protocol (ftp) depend initially on individuals, groups, and/or corporations building them into an operating-system kernel or a piece of user software and subsequently on the existence of a large number of people using the same operating system or application.
@@ -2932,7 +2772,6 @@
.ancestors: 1 74 0 0 77 172 0 0
.ancestors_collapsed: 1 74 77 172 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BDD34A1A46AEBC8B96147EE29546AF5D2275D9920AAA4FBD2505BB60FC6C349D
| In many cases, subsequent to an implementation that has been disseminated and adopted, the RFCs have been amended to reflect these working implementations and to ordain them as standards. So the current standards are actually bootstrapped, through a process of writing RFCs, followed by a process of creating implementations that adhere loosely to the rules in the RFC, then observing the progress of implementations, and then rewriting RFCs so that the process begins all over again. The fact that geeks can have a discussion via e-mail depends on the very existence of both an RFC to define the e-mail protocol and implementations of software to send the e-mails.
@@ -2943,7 +2782,6 @@
.ancestors: 1 74 0 0 77 172 0 0
.ancestors_collapsed: 1 74 77 172 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A18AD16B064D5684266C3798340982ADA2E80EA07A60F2EE0E7CCC78E6717005
| This standardization process essentially inverts the process of planning. Instead of planning a system, which is then standardized, refined, and finally built according to specification, the RFC process allows plans to be proposed, implemented, refined, reproposed, rebuilt, and so on until they are adopted by users and become the standard approved of by the IETF. The implication for most geeks is that this process is permanently and fundamentally open: changes to it can be proposed, implemented, and adopted without end, and the better a technology becomes, the more difficult it becomes to improve on it, and therefore the less reason there is to subvert it or reinvent it. Counterexamples, in which a standard emerges but no one adopts it, are also plentiful, and they suggest that the standardization process extends beyond the proposal-implementation-proposal-standard ⑆,┨[pg 61]┣, circle to include the problem of actually convincing users to switch from one working technology to a better one. However, such failures of adoption are also seen as a kind of confirmation of the quality or ease of use of the current solution, and they are all the more likely to be resisted when some organization or political entity tries to force users to switch to the new standard—something the IETF has refrained from doing for the most part.
@@ -2971,7 +2809,6 @@
.ancestors: 1 74 0 0 77 181 0 0
.ancestors_collapsed: 1 74 77 181 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5469C541FF44226F1D96EB2D88965F34EA92268CD2A7B1EC5DE968BF8E855C36
| Napster was a familiar and widely discussed instance of the “reorientation of power and knowledge” (or in this case, power and music) wrought by the Internet and the practices of geeks. Napster was not, however, a recursive public or a Free Software project, but a dot-com-inspired business plan in which proprietary software was given away for free in the hopes that revenue would flow from the stock market, from advertising, or from enhanced versions of the software. Therefore, geeks did not defend Napster as much as they experienced its legal restriction as a wake-up call: the Internet enables Napster and will enable many other things, but laws, corporations, lobbyists, money, and governments can destroy all of it.
@@ -2982,7 +2819,6 @@
.ancestors: 1 74 0 0 77 181 0 0
.ancestors_collapsed: 1 74 77 181 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4A263757B381F5D6BD9367BBD5831BFD00915C0BCDBCE6F2C251FE8F41AA178D
| I started this chapter by asking what draws geeks together: what constitutes the chain that binds geeks like Sean and Adrian to hipsters in Berlin and to entrepreneurs and programmers in Bangalore? What constitutes their affinity if it is not any of the conventional candidates like culture, nation, corporation, or language? A colloquial answer might be that it is simply the Internet that brings them together: cyberspace, virtual communities, online culture. But this doesn’t answer the question of why? Because they can? Because Community Is Good? If mere association is the goal, why not AOL or a vast private network provided by Microsoft?
@@ -2993,7 +2829,6 @@
.ancestors: 1 74 0 0 77 181 0 0
.ancestors_collapsed: 1 74 77 181 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0A8CFEF3FF760AADC3B254628BA67FA416E91A8D66B6FE4A5E38BE44A896F741
| My answer, by contrast, is that geeks’ affinity with one another is structured by shared moral and technical understandings of order. They are a public, an independent public that has the ability to build, maintain, and modify itself, that is not restricted to the activities of speaking, writing, arguing, or protesting. Recursive publics form through their experience with the Internet precisely because the Internet is the kind of thing they can inhabit and transform. Two ⑆,┨[pg 62]┣, things make recursive publics distinctive: the ability to include the practice of creating this infrastructure as part of the activity of being public or contesting control; and the ability to “recurse” through the layers of that infrastructure, maintaining its publicness at each level without making it into an unchanging, static, unmodifiable thing.
@@ -3004,7 +2839,6 @@
.ancestors: 1 74 0 0 77 181 0 0
.ancestors_collapsed: 1 74 77 181 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6BC815C55EFB8398ABCC93966265FC11E1119B0D0E9F6D4AE987B59FA4EC111C
| The affinity constituted by a recursive public, through the medium of the Internet, creates geeks who understand clearly what association through the Internet means. This affinity structures their imagination of what the Internet is and enables: creation, distribution, modification of knowledge, music, science, software. The infrastructure—this-infrastructure-here, the Internet—must be understood as part of this imaginary (in addition to being a pulsating tangle of computers, wires, waves, and electrons).
@@ -3015,7 +2849,6 @@
.ancestors: 1 74 0 0 77 181 0 0
.ancestors_collapsed: 1 74 77 181 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2AB8D8E26E5019EEF6D232C6EBE7EB920041004ECF1D4BE93B9245E0D06918EF
| The Internet is not the only medium for such association. A corporation, for example, is also based on a shared imaginary of the economy, of how markets, exchanges, and business cycles are supposed to work; it is the creation of a concrete set of relations and practices, one that is generally inflexible—even in this age of socalled flexible capitalism—because it requires a commitment of time, humans, and capital. Even in fast capitalism one needs to rent office space, buy toilet paper, install payroll software, and so on.
@@ -3026,7 +2859,6 @@
.ancestors: 1 74 0 0 77 181 0 0
.ancestors_collapsed: 1 74 77 181 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2AB8D8E26E5019EEF6D232C6EBE7EB920041004ECF1D4BE93B9245E0D06918EF
| The Internet is not the only medium for such association. A corporation, for example, is also based on a shared imaginary of the economy, of how markets, exchanges, and business cycles are supposed to work; it is the creation of a concrete set of relations and practices, one that is generally inflexible—even in this age of socalled flexible capitalism—because it requires a commitment of time, humans, and capital. Even in fast capitalism one needs to rent office space, buy toilet paper, install payroll software, and so on.
@@ -3037,7 +2869,6 @@
.ancestors: 1 74 0 0 77 181 0 0
.ancestors_collapsed: 1 74 77 181 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 99221576B3E5E8956B8FC5CC28CAD55679BDA21946C7E8CD459BACA5E5500F25
| The urgency evidenced in the case of Napster (and repeated in numerous other instances, such as the debate over net neutrality) is linked to a moral idea of order in which there is a shared imaginary⑆,┨[pg 63]┣, of The Public, and not only a vast multiplicity of competing publics. It is an urgency linked directly to the fact that the Internet provides geeks with a platform, an environment, an infrastructure through which they not only associate, but create, and do so in a manner that is widely felt to be autonomous, autotelic, and independent of at least the most conventional forms of power: states and corporations—independent enough, in fact, that both states and corporations can make widespread use of this infrastructure (can become geeks themselves) without necessarily endangering its independence.
@@ -3105,7 +2936,6 @@
.ancestors: 1 74 0 0 189 0 0 0
.ancestors_collapsed: 1 74 189 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: ADC7520E8A6741053F31E4F04357F7B91E359C261E5D84BBB355E4D96D872736
| Geeks talk a lot. They don’t talk about recursive publics. They don’t often talk about imaginations, infrastructures, moral or technical orders. But they do talk a lot. A great deal of time and typing is necessary to create software and networks: learning and talking, teaching and arguing, telling stories and reading polemics, reflecting on the world in and about the infrastructure one inhabits. In this chapter I linger on the stories geeks tell, and especially on stories and reflections that mark out contemporary problems of knowledge and power—stories about grand issues like progress, enlightenment, liberty, and freedom.
@@ -3116,7 +2946,6 @@
.ancestors: 1 74 0 0 189 0 0 0
.ancestors_collapsed: 1 74 189 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 580F46E70F1C614C6F67DC58D5A8E2778173437CFAB579F85B2F686FB03D93B8
| Issues of enlightenment, progress, and freedom are quite obviously still part of a “social imaginary,” especially imaginations of the relationship of knowledge and enlightenment to freedom and autonomy so clearly at stake in the notion of a public or public ⑆,┨[pg 65]┣, sphere. And while the example of Free Software illuminates how issues of enlightenment, progress, and freedom are proposed, contested, and implemented in and through software and networks, this chapter contains stories that are better understood as “usable pasts”—less technical and more accessible narratives that make sense of the contemporary world by reflecting on the past and its difference from today.
@@ -3127,7 +2956,6 @@
.ancestors: 1 74 0 0 189 0 0 0
.ancestors_collapsed: 1 74 189 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 14605CBB7062BC1CD5EE90BBFF9D07B980876F3BF10E8ECF036C948521EDA536
| Usable pasts is a more charitable term for what might be called modern myths among geeks: stories that the tellers know to be a combination of fact and fiction. They are told not in order to remember the past, but in order to make sense of the present and of the future. They make sense of practices that are not questioned in the doing, but which are not easily understood in available intellectual or colloquial terms. The first set of stories I relate are those about the Protestant Reformation: allegories that make use of Catholic and Protestant churches, laity, clergy, high priests, and reformation-era images of control and liberation. It might be surprising that geeks turn to the past (and especially to religious allegory) in order to make sense of the present, but the reason is quite simple: there are no “ready-to-narrate” stories that make sense of the practices of geeks today. Precisely because geeks are “figuring out” things that are not clear or obvious, they are of necessity bereft of effective ways of talking about it. The Protestant Reformation makes for good allegory because it separates power from control; it draws on stories of catechism and ritual, alphabets, pamphlets and liturgies, indulgences and self-help in order to give geeks a way to make sense of the distinction between power and control, and how it relates to the technical and political economy they occupy. The contemporary relationship among states, corporations, small businesses, and geeks is not captured by familiar oppositions like commercial/noncommercial, for/against private property, or capitalist/socialist—it is a relationship of reform and conversion, not revolution or overthrow.
@@ -3138,7 +2966,6 @@
.ancestors: 1 74 0 0 189 0 0 0
.ancestors_collapsed: 1 74 189 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: DEB36EC228AD737CDF62ACE504132332CEEEDEED2230D0338AFA53F7E1D9E66C
.has: notes_reg
@@ -3150,7 +2977,6 @@
.ancestors: 1 74 0 0 189 0 0 0
.ancestors_collapsed: 1 74 189 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: D727499205B27BF527255082815A0EA993A296B1C7568848E9E0B9CC5DE37D95
| The attitudes that geeks take in responding to these questions fall along a spectrum that I have identified as ranging from “polymaths” to “transhumanists.” These monikers are drawn from real discussions with geeks, but they don’t designate a kind of person. They are “subroutines,” perhaps, called from within a larger program of moral and technical imaginations of order. It is possible for the same person to be a polymath at work and a transhumanist at home, but generally speaking they are conflicting and opposite mantles. In polymath routines, technology is an intervention into a complicated, historically unique field of people, customs, organizations, other technologies, and laws; in transhumanist routines, technology is seen as an inevitable force—a product of human action, but not of human design—that is impossible to control or resist through legal or customary means.
@@ -3178,7 +3004,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 79204A29686E9A7629442FBE079696AFF8C581408A1013CFDD7A73E1FCA00909
.has: notes_reg
@@ -3201,7 +3026,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 00ABDA1D184DE38864C0B0B689B1AF1B15A42867BE7195F7B9955BE7043DC546
.has: links notes_reg
@@ -3213,7 +3037,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 572C1CE0EE4709B2D2816E3CFCA6D80A6246F80C6B06483574A23D4B103C0CE2
.has: links notes_reg
@@ -3226,7 +3049,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B02C402C40B4C414B512ADBDF8708D4A849830B8C515E12FE0BFCE9FEA134819
| Often the language of the Reformation creeps playfully into otherwise serious attempts to make aesthetic judgments about technology, as in this analysis of the programming language tcl/tk:
@@ -3237,7 +3059,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F1ECEDBA6D6861D6300A6D4400829B392D3F76761C6B9F093FF0470BB5D6F96F
.indent: 1 1
@@ -3250,7 +3071,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8FDAF886F4DA51779515F3A46F4201A05CD0F314AD72572405B278078DE01159
| In this instance, the “religious war” concerns the difference between academic programming languages and regular programmers made equivalent to a distinction between the insularity of the Catholic Church and the self-help of a protestant laity: the heroes (such as tcl/tk, perl, and python—all Free Software) are the “nasty little languages” of the laity; the High Priests design (presumably) Algol, LISP, and other “academic” languages.
@@ -3261,7 +3081,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 10CA4E9EB5D58A31C7B889895656F6437E9BA983FA9DC7A355DD88F87DE36169
| At a second level, however, the allegory makes precise use of Protestant Reformation details. For example, in a discussion about the various fights over the Gnu C Compiler (gcc), a central component of the various UNIX operating systems, Christopher Browne posted this counter-reformation allegory to a Usenet group.
@@ -3272,7 +3091,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4CD53F41A0CBBFFB32268206E977BED069DBD6313AE435C3909C7327C3A1FB4F
.indent: 1 1
@@ -3284,7 +3102,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 05611B0C50669DA6A840F3814458C8D4C8E5971C74A969EC9EB6EFFE8AF161D8
.indent: 2 2
@@ -3296,7 +3113,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7B453F4463A364F5DB671FDF6AEAA7A54A4ACCA0E3D5F5BFEF77D87EE64C5358
.indent: 2 2
@@ -3308,7 +3124,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E2D0C622B0E97C85AA6CBCDB99AA4D005FFDD78789EB72EE22B89EE200AC51A7
.indent: 2 2
@@ -3320,7 +3135,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5B38E427B9BE85EB2234CBBDBA396E45828D12FA763403441B749FD62788F58F
.indent: 2 2
@@ -3332,7 +3146,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5C3BC0E01100D8B2298E534BC57C69837466C73924A4BF083E689B06542DD53B
.indent: 1 1
@@ -3345,7 +3158,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2601FCDD8CE2B0F50A40E9D04B42700E73FDC9A074BFD0D20749B428C50BF7F5
| In addition to the obvious pleasure with which they deploy the sectarian aspects of the Protestant Reformation, geeks also allow themselves to see their struggles as those of Luther-like adepts, confronted by powerful worldly institutions that are distinct but intertwined: the Catholic Church and absolutist monarchs. Sometimes these comparisons are meant to mock theological argument; sometimes they are more straightforwardly hagiographic. For instance, a 1998 article in Salon compares Martin Luther and Linus Torvalds (originator of the Linux kernel).
@@ -3356,7 +3168,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 71A87D8A729A2B34B4FCC67869529574AA3A312639924BA1B9F36678EDDD7956
.indent: 1 1
@@ -3369,7 +3180,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 351C23A5488DD77FDE33743FC89ADDD2345F0248A445C018AB4AEB3D2BC33C48
.has: links notes_reg
@@ -3383,7 +3193,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 67A2B038B73F82C74D06DF861D5F5D51A2F9267385FA8480F4192A23FF7A9704
| Often the appeal of Reformation-era rhetoric comes from a kind of indictment of the present: despite all this high tech, super-fabulous computronic wonderfulness, we are no less feudal, no less violent, no less arbitrary and undemocratic; which is to say, geeks have progressed, have seen the light and the way, but the rest of society—and especially management and marketing—have not. In this sense, Reformation allegories are stories of how “things never change.”
@@ -3394,7 +3203,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C84B147A9B2A00260FF2D94267A0C2BAB2D957F87153493DBF70DAA9B38220E8
.has: notes_reg
@@ -3406,7 +3214,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1DA002644250A0FB99733B409AA68EA0EF7659189A2A2236B968AE1F9C500B2C
.has: notes_reg
@@ -3418,7 +3225,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: ABA44434CF42A951C21EE63AF9846293CC1D2E67023C01890D08F8363AEE8A27
| Such stories appeal because they bypass the language of modern American politics (liberal, conservative, Democrat, Republican) in which there are only two sides to any issue. They also bypass an ⑆,┨[pg 71]┣, argument between capitalism and socialism, in which if you are not pro-capitalism you must be a communist. They are stories that allow the more pragmatist of the geeks to engage in intervention and reformation, rather than revolution. Though I’ve rarely heard it articulated so bluntly, the allegory often implies that one must “save capitalism from the capitalists,” a sentiment that implies at least some kind of human control over capitalism.
@@ -3429,7 +3235,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8327A4C1E2B08F987DDC2CA283DBACEA758818E1DF3D04A97F7433C363F399D3
| In fact, the allegorical use of the Reformation and the church generates all kinds of clever comparisons. A typical description of such comparisons might go like this: the Catholic Church stands in for large, publicly traded corporations, especially those controlling large amounts of intellectual property (the granting of which might roughly be equated with the ceremonies of communion and confession) for which they depend on the assistance and support of national governments. Naturally, it is the storied excesses of the church—indulgences, liturgical complexity, ritualistic ceremony, and corruption—which make for easy allegory. Modern corporations can be figured as a small, elite papal body with theologians (executives and their lawyers, boards of directors and their lawyers), who command a much larger clergy (employees), who serve a laity (consumers) largely imagined to be sinful (underspending on music and movies—indeed, even “stealing” them) and thus in need of elaborate and ritualistic cleansing (advertising and lawsuits) by the church. Access to grace (the American Dream) is mediated only by the church and is given form through the holy acts of shopping and home improvement. The executives preach messages of damnation to the government, messages most government officials are all too willing to hear: do not tamper with our market share, do not affect our pricing, do not limit our ability to expand these markets. The executives also offer unaccountable promises of salvation in the guise of deregulation and the American version of “reform”—the demolition of state and national social services. Government officials in turn have developed their own “divine right of kings,” which justifies certain forms of manipulation (once called “elections”) of succession. Indulgences are sold left and right by lobbyists or industry associations, and the decrees of the papacy evidence little but full disconnection from the miserable everyday existence of the flock.
@@ -3440,7 +3245,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 256C72F6DA49705C8A6C774C392272098C46E3C7727EA1E19D4678E2E58F3702
| In fact, it is remarkable how easy such comparisons become the more details of the political economy of information one learns. But ⑆,┨[pg 72]┣, allegories of the Reformation and clerical power can lead easily to cynicism, which should perhaps be read in this instance as evidence of political disenfranchisement, rather than a lapse in faith. And yet the usable pasts of these reformation-minded modern monks and priests crop up regularly not only because they provide relief from technical chatter but because they explain a political, technical, legal situation that does not have ready-to-narrate stories. Geeks live in a world finely controlled by corporate organizations, mass media, marketing departments, and lobbyists, yet they share a profound distrust of government regulation—they need another set of just-so stories to make sense of it. The standard unusable pasts of the freeing of markets, the inevitability of capitalism and democracy, or more lately, the necessity of security don’t do justice to their experience.
@@ -3451,7 +3255,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 61D6710F31849E8B7226A5A81A57B74E9DB8C826A550AF54E6729AC43C3261D9
| Allegories of Reformation are stories that make sense of the political economy of information. But they also have a more precise use: to make sense of the distinction between power and control. Because geeks are “closer to the machine” than the rest of the laity, one might reasonably expect them to be the ones in power. This is clearly not the case, however, and it is the frustrations and mysteries by which states, corporations, and individuals manipulate technical details in order to shift power that often earns the deepest ire of geeks. Control, therefore, includes the detailed methods and actual practices by which corporations, government agencies, or individuals attempt to manipulate people (or enroll them to manipulate themselves and others) into making technical choices that serve power, rather than rationality, liberty, elegance, or any other geekly concern.
@@ -3462,7 +3265,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A841CD75169BCC4D79B5DC43C8B791465E7A61F60EF872EB95B0B6D21E35FE3C
| Consider the subject of evil. During my conversations with Sean Doyle in the late 1990s, as well as with a number of other geeks, the term evil was regularly used to refer to some kind of design or technical problem. I asked Sean what he meant.
@@ -3473,7 +3275,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3A2DC43304B62754B25C2756DC221813E5733A0C14D46123A517DDB1C6AD3596
| ⑆!┨SD:┣! [Evil is] just a term I use to say that something’s wrong, but usually it means something is wrong on purpose, there was agency behind it. I can’t remember [the example you gave] but I think it may have been some GE equipment, where it has this default where it likes to send things in its own private format rather than in DICOM [the radiology industry standard for digital images], if you give it a choice. I don’t know why they would have done something like that, ⑆,┨[pg 73]┣, it doesn’t solve any backward compatibility problem, it’s really just an exclusionary sort of thing. So I guess there’s Evil like that. . . .
@@ -3484,7 +3285,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CFFE1785F46FC964C4DE3EB6A7862520D87A0C8025640581DF902B0045578959
| ⑆!┨CK:┣! one of the other examples that you had . . . was something with Internet Explorer 3.0?
@@ -3495,7 +3295,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DFD917EC0F6B897EDF2B2E77F266287F3827F9CDE6460E8736A5A8C3C31D6476
| ⑆!┨SD:┣! Yes, oh yes, there are so many things with IE3 that are completely Evil. Like here’s one of them: in the http protocol there’s a thing called the “user agent field” where a browser announces to the server who it is. If you look at IE, it announces that it is Mozilla, which is the [code-name for] Netscape. Why did they do this? Well because a lot of the web servers were sending out certain code that said, if it were Mozilla they would serve the stuff down, [if not] they would send out something very simple or stupid that would look very ugly. But it turned out that [IE3, or maybe IE2] didn’t support things when it first came out. Like, I don’t think they supported tables, and later on, their versions of Javascript were so different that there was no way it was compatible—it just added tremendous complexity. It was just a way of pissing on the Internet and saying there’s no law that says we have to follow these Internet standards. We can do as we damn well please, and we’re so big that you can’t stop us. So I view it as Evil in that way. I mean they obviously have the talent to do it. They obviously have the resources to do it. They’ve obviously done the work, it’s just that they’ll have this little twitch where they won’t support a certain MIME type or they’ll support some things differently than others.
@@ -3506,7 +3305,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 99D48F4493EBCA55359F2B8221F4DE5866211148F6B9956010BBFB041CF6DFD1
| ⑆!┨CK:┣! But these kinds of incompatibility issues can happen as a result of a lack of communication or coordination, which might involve agency at some level, right?
@@ -3517,7 +3315,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 43B46A6EADBBD2F1BF3EEBABF6E08B2579542E5DC64AE4797E8D73ED263185FD
| ⑆!┨SD:┣! Well, I think of that more as Stupidity than Evil [laughter]. No, Evil is when there is an opportunity to do something, and an understanding that there is an opportunity to, and resources and all that—and then you do something just to spite the other person. You know I’m sure it’s like in messy divorces, where you would rather sell the property at half its value rather than have it go to the other person.
@@ -3528,7 +3325,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B912F3F80278E36EFE3533E438E546AF0E5985350F4AD03100B3FAC53C02A47B
| Sean relates control to power by casting the decisions of a large corporation in a moral light. Although the specific allegory of the Protestant Reformation does not operate here, the details do. Microsoft’s decision to manipulate Internet Explorer’s behavior stems not from a lack of technical sophistication, nor is it an “accident” of ⑆,┨[pg 74]┣, complexity, according to Sean, but is a deliberate assertion of economic and political power to corrupt the very details by which software has been created and standardized and is expected to function. The clear goal of this activity is conversion, the expansion of Microsoft’s flock through a detailed control of the beliefs and practices (browsers and functionality) of computer users. Calling Microsoft “Evil” in this way has much the same meaning as questioning the Catholic Church’s use of ritual, ceremony, literacy, and history—the details of the “implementation” of religion, so to speak.
@@ -3539,7 +3335,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3035A8D6B5CB2246730487F0CD18DFBCA9F3C4DEACBD402B1915423247799A9F
.has: notes_reg
@@ -3551,7 +3346,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E8B3A0A527998D1703BB9D1252E1FF494D3BDB3B7A3E75756D9768E3652A661B
| ✠  ©
@@ -3562,7 +3356,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 18E851599D1FD9E07602983C29362C8C5183DE1EC46CB62BA6AF98B4E9E5755C
.has: notes_reg
@@ -3574,7 +3367,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6D0D9FD2C55C321346E035191FC4911D8414AC3443EC7953120C0942C39620A6
.has: notes_reg
@@ -3597,7 +3389,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5C7CDA1A16EACA2EA7D21FF0C9FF4DC1304F538A55CB08B3EB7B027A70904358
| The © today carries as much if not more power, both ideologically and legally, as the cross of the Catholic church. It is the very symbol of authorship, even though in origin and in function it governs only ownership and rights. Magical thinking about copyright abounds, but one important function of the symbol ©, if not its legal implications, is to achieve the same thing as the Christ’s cross: to associate in the mind of the reader the ownership of a particular text (or in this case, piece of software) with a particular organization or person. Furthermore, even though the symbol is an artifact of national and international law, it creates an association not between a text and the state or government, but between a text and particular corporations, publishers, printers, or authors.
@@ -3608,7 +3399,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0DCA5557542F46AEB50A69C1C7AA1960CDA9748713E7D914587C085939BAA588
| Like the Christ’s cross, the copyright symbol carries both a licensing effect (exclusive, limited or nonexclusive) and an imprimatur on the minds of people: “let it be imprinted in memory” that this is the work of such and such an author and that this is the property of such and such a corporation.
@@ -3630,7 +3420,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5B233740B369314DD1B99C55064DBD93A757CCB38BE4541448C8F100CEC192E5
| Without the allegory of the Protestant Reformation, the only available narrative for such evil—whether it be the behavior of Microsoft or of some other corporation—is that corporations are “competing in the marketplace according to the rules of capitalism” and thus when geeks decry such behavior, it’s just sour grapes. If corporations are not breaking any laws, why shouldn’t they be allowed to achieve control in this manner? In this narrative there is no room for a moral evaluation of competition—anything goes, it would seem. Claiming for Microsoft that it is simply playing by the rules of capitalism puts everyone else into either the competitor box or the noncompetitor box (the state and other noncompetitive organizations). Using the allegory of the Protestant Reformation, on the other hand, gives geeks a way to make sense of an unequal distribution among competing powers—between large and small corporations, and between market power and the details of control. It provides an alternate imagination against which to judge the technically and legally specific actions that corporations and individuals take, and to imagine forms of justified action in return.
@@ -3641,7 +3430,6 @@
.ancestors: 1 74 0 0 189 195 0 0
.ancestors_collapsed: 1 74 189 195 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9DB835DD1B0ECA41B1333C553CE28014B2E55560482364168A2AC9E900ABA20C
| Without such an allegory, geeks who oppose Microsoft are generally forced into the position of being anticapitalist or are forced to adopt the stance that all standards should be publicly generated and controlled, a position few wish to take. Indeed, many geeks would prefer a different kind of imaginary altogether—a recursive public, perhaps. Instead of an infrastructure subject to unequal distributions of power and shot through with “evil” distortions of technical control, there is, as geeks see it, the possibility for a “self-leveling” level playing field, an autotelic system of rules, both technical and legal, by which all participants are expected to compete equally. Even if it remains an imaginary, the allegory of the Protestant Reformation makes sense of (gives order to) the political economy of the contemporary information-technology world and allows geeks to conceive of their interests and actions according to a narrative of reformation, rather than one of revolution or submission. In the Reformation the interpretation or truth of Christian teaching was not primarily in question: it was not a doctrinal revolution, but a bureaucratic one. Likewise, geeks do not question the rightness of networks, software, or protocols and standards, nor are they against capitalism or intellectual property, but they do wish to maintain a space for critique and the moral evaluation of contemporary capitalism and competition.
@@ -3680,7 +3468,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 57545C0F44FF81113C45AD371587132F57472CCE6CAC48770FCB79EFAB73371B
| Usable pasts articulate the conjunction of “operating systems and social systems,” giving narrative form to imaginations of moral and technical order. To say that there are no ready-to-narrate stories about contemporary political economy means only that the standard colloquial explanations of the state of the modern world do not do justice to the kinds of moral and technical imaginations of order that geeks possess by virtue of their practices. Geeks live in, and build, one kind of world—a world of software, networks, and infrastructures—but they are often confronted with stories and explanations that simply don’t match up with their experience, whether in newspapers and on television, or among nongeek friends. To many geeks, proselytization seems an obvious route: why not help friends and neighbors to understand the hidden world of networks and software, since, they are quite certain, it will come to structure their lives as well?
@@ -3691,7 +3478,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FC304F97458E3FEF9287B85F4D677588427A5823BD26CFC452CC383B766C3D6F
.has: links notes_reg
@@ -3704,7 +3490,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 81416DE97F7740C315D5039CB1A9DD62C0DB706033059BA531A810786043987E
| Geeks live in specific ways in time and space. They are not just users of technology, or a “network society,” or a “virtual community,” but embodied and imagining actors whose affinity for one another is enabled in new ways by the tools and technologies they have such deep affective connections to. They live in this-network-here, a historically unique form grounded in particular social, moral, national, and historical specificities which nonetheless relates to generalities such as progress, technology, infrastructure, and liberty. Geeks are by no means of one mind about such generalities though, and they often have highly developed means of thinking about them.
@@ -3715,7 +3500,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BE61D3B9D87ABFE0EF42522CF1C20B660F28F0A7403D63E55868F9A63AB5AA35
| Foucault’s article “What Is Enlightenment?” captures part of this problematic. For Foucault, Kant’s understanding of modernity was an attempt to rethink the relationship between the passage of historical time and the subjective relationship that individuals have toward it.
@@ -3737,7 +3521,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6EF8F45818426700ED71C556B45E2A73196076A3534495F3B46DDF639502EE37
.indent: 1 1
@@ -3750,7 +3533,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 58899BA23FD37371DF9FD382DDAF89B8E7C34C9F6F0C9A75C82D22438FC984C1
.has: notes_reg
@@ -3773,7 +3555,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E95D6F8E0A97346599C41036E9AA7CF023358ED9C35A865BF4ECAF29537120CA
| The questions I raise here are also those of politics in a classical sense: Are the geeks I discuss bound by an attitude toward the present that concerns such things as the relationship of the public to the private and the social (à la Hannah Arendt), the relationship ⑆,┨[pg 79]┣, of economics to liberty (à la John Stuart Mill and John Dewey), or the possibilities for rational organization of society through the application of scientific knowledge (à la Friedrich Hayek or Foucault)? Are geeks “enlightened”? Are they Enlightenment rationalists? What might this mean so long after the Enlightenment and its vigorous, wide-ranging critiques? How is their enlightenment related to the technical and infrastructural commitments they have made? Or, to put it differently, what makes enlightenment newly necessary now, in the milieu of the Internet, Free Software, and recursive publics? What kinds of relationships become apparent when one asks how these geeks relate their own conscious appreciation of the history and politics of their time to their everyday practices and commitments? Do geeks despise the present?
@@ -3784,7 +3565,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1CCFC8A620507EA16295179D9AF140FAE28EC107321E8EE03B9678846F0F878C
| Polymaths and transhumanists speak differently about concepts like technology, infrastructure, networks, and software, and they have different ideas about their temporality and relationship to progress and liberty. Some geeks see technology as one kind of intervention into a constituted field of organizations, money, politics, and people. Some see it as an autonomous force made up of humans and impersonal forces of evolution and complexity. Different geeks speak about the role of technology and its relationship to the present and future in different ways, and how they understand this relationship is related to their own rich understandings of the complex technical and political environment they live and work in.
@@ -3795,7 +3575,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 98A02D71531D4570409253C9A1002615B3C5BE8906F86421D6B875B94B36E5CE
| ⑆!┨Polymaths┣! Polymathy is “avowed dilettantism,” not extreme intelligence. It results from a curiosity that seems to grip a remarkable number of people who spend their time on the Internet and from the basic necessity of being able to evaluate and incorporate sometimes quite disparate fields of knowledge in order to build workable software. Polymathy inevitably emerges in the context of large software and networking projects; it is a creature of constraints, a process bootstrapped by the complex sediment of technologies, businesses, people, money, and plans. It might also be posed in the negative: bad software design is often the result of not enough avowed dilettantism. Polymaths must know a very large and wide range of things in order to intervene in an existing distribution of machines, people, practices, and places. They must have a detailed sense of the present, and the project of the present, in order to imagine how the future might be different.
@@ -3817,7 +3596,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 33EEF2CDB5A9EFE29EF6CFB80997929EA4E2AA56E10A2A23104E45F008967A7D
| My favorite polymath is Sean Doyle. Sean built the first versions of a piece of software that forms the centerpiece of the radiological-image-management company Amicas. In order to build it Sean learned the following: Java, to program it; the mathematics of wavelets, to encode the images; the workflow of hospital radiologists and the manner in which they make diagnoses from images, to make the interface usable; several incompatible databases and the SQL database language, to build the archive and repository; and manual after manual of technical standards, the largest and most frightening of which was the Digital Imaging and Communication (DICOM) standard for radiological images. Sean also read Science and Nature regularly, looking for inspiration about interface design; he read books and articles about imaging very small things (mosquito knees), very large things (galaxies and interstellar dust), very old things (fossils), and very pretty things (butterfly-wing patterns as a function of developmental pathways). Sean also introduced me to Tibetan food, to Jan Svankmeyer films, to Open Source Software, to cladistics and paleoherpetology, to Disney’s scorched-earth policy with respect to culture, and to many other awesome things.
@@ -3828,7 +3606,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BB06C8477EED61CB0BC2B57EA49C51FDBC0DE3685132E98A0B7C172F2CE2F1B7
| Sean is clearly an unusual character, but not that unusual. Over the years I have met many people with a similar range and depth of knowledge (though rarely with Sean’s humility, which does set him apart). Polymathy is an occupational hazard for geeks. There is no sense in which a good programmer, software architect, or information architect simply specializes in code. Specialization is seen not as an end in itself, but rather as a kind of technical prerequisite before other work—the real work—can be accomplished. The real work is the design, the process of inserting usable software into a completely unfamiliar amalgamation of people, organizations, machines, and practices. Design is hard work, whereas the technical stuff—like choosing the right language or adhering to a standard or finding a ready-made piece of code to plug in somewhere—is not.
@@ -3839,7 +3616,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2C1A676A76C16F38137EDE66B2B8970A586FFE0F60FA3767AD77F8852C56201C
| It is possible for Internet geeks and software architects to think this way in part due to the fact that so many of the technical issues they face are both extremely well defined and very easy to address with a quick search and download. It is easy to be an avowed dilettante in the age of mailing lists, newsgroups, and online scientific publishing. I myself have learned whole swaths of technical practices in this manner, but I have designed no technology of note. ⑆,┨[pg 81]┣,
@@ -3850,7 +3626,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B1DC5B04ADB15CD103AFD09A5D0D4220659EE62CE80566B9FF9C5F5E96AA388F
| Sean’s partner in Amicas, Adrian Gropper, also fits the bill of polymath, though he is not a programmer. Adrian, a physician and a graduate of MIT’s engineering program, might be called a “high-functioning polymath.” He scans the horizon of technical and scientific accomplishments, looking for ways to incorporate them into his vision of medical technology qua intervention. Sean mockingly calls these “delusions,” but both agree that Amicas would be nowhere without them. Adrian and Sean exemplify how the meanings of technology, intervention, design, and infrastructure are understood by polymaths as a particular form of pragmatic intervention, a progress achieved through deliberate, piecemeal re-formation of existing systems. As Adrian comments:
@@ -3861,7 +3636,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 96BF2157271ADB052D59426C2B13AAB40F51CDE52E2DCB2579DFD629C89C4B37
.indent: 1 1
@@ -3874,7 +3648,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6885D38DB3D753FFE5F97263B673C29A246FAAB9F4221B2724F2933FBC23CA18
.has: notes_reg
@@ -3886,7 +3659,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2E190B0C67A0553D7F697B4AA0B099A9B248D9CE8ED9F3291B27376DBF63DF58
| Adrian’s self-defined role in this arena is as a nonpracticing physician who is also an engineer and an entrepreneur—hence, his polymathy has emerged from his attempts to translate between doctors, engineers, and businesspeople. His goal is twofold: first, create technologies that save money and improve the allocation of healthcare (and the great dream of telemedicine concerns precisely this goal: the reallocation of the most valuable asset, individuals and their expertise); second, to raise the level of discussion in the business-cum-medical world about the role of technology in managing healthcare resources. Polymathy is essential, since Adrian’s twofold mission requires understanding the language and lives of at least three distinct groups who work elbow-to-elbow in healthcare: engineers and software architects; doctors and nurses; and businessmen.
@@ -3897,7 +3669,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1CC845679AD7B979B2CEEADBA26B8146B4610331273118268AE7331B120DFDD5
| Technology has two different meanings according to Adrian’s two goals: in the first case technology refers to the intervention by means of new technologies (from software, to materials, to electronics, to pharmaceuticals) in specific healthcare situations wherein high costs or limited access to care can be affected. Sometimes technology is allocated, sometimes it does the allocating. Adrian’s goal is to match his knowledge of state-of-the-art technology—in particular, Internet technology—with a specific healthcare situation and thereby effect a reorganization of practices, people, tools, and information. The tool Amicas created was distinguished by its clever use of compression, Internet standards, and cheap storage media to compete with much larger, more expensive, much more entrenched “legacy” and “turnkey” systems. Whether Amicas invented something “new” is less interesting than the nature of this intervention into an existing milieu. This intervention is what Adrian calls “technology.” For Amicas, the relevant technology—the important intervention—was the Internet, which Amicas conceived as a tool for changing the nature of the way healthcare was organized. Their goal was to replace the infrastructure of the hospital radiology department (and potentially the other departments as well) with the Internet. Amicas was able to confront and reform the practices of powerful, entrenched entities, from the administration of large ⑆,┨[pg 83]┣, hospitals to their corporate bedfellows, like HBOC, Agfa, Siemens, and GE.
@@ -3908,7 +3679,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1DF7E6D38E3F930525E77658DE21212CB69E13C9E73CE3581081145E46BA978C
| With regard to raising the level of discussion, however, technology refers to a kind of political-rhetorical argument: technology does not save the world (nor does it destroy it); it only saves lives—and it does this only when one makes particular decisions about its allocation. Or, put differently, the means is technology, but the ends are still where the action is at. Thus, the hype surrounding information technology in healthcare is horrifying to Adrian: promises precede technologies, and the promises suggest that the means can replace the ends. Large corporations that promise “technology,” but offer no real hard interventions (Adrian’s first meaning of technology) that can be concretely demonstrated to reduce costs or improve allocation are simply a waste of resources. Such companies are doubly frustrating because they use “technology” as a blinder that allows people to not think about the hard problems (the ends) of allocation, equity, management, and organization; that is, they treat “technology” (the means) as if it were a solution as such.
@@ -3919,7 +3689,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D760A3DF4EA65041622B874BBE27B2AC0E503EAF930A3CB8FBC66900E4488F8C
| Adrian routinely analyzes the rhetorical and practical uses of technology in healthcare with this kind of subtlety; clearly, such subtlety of thought is rare, and it sets Adrian apart as someone who understands that intervention into, and reform of, modern organizations and styles of thought has to happen through reformation—through the clever use of technology by people who understand it intimately—not through revolution. Reformation through technical innovation is opposed here to control through the consolidation of money and power.
@@ -3930,7 +3699,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8E3C97641BD9A4BF96B9DC773856F83B2ED346924EB72E5B91B4649D482012AC
| In my observations, Adrian always made a point of making the technology—the software tools and picture-archiving system—easily accessible, easily demonstrable to customers. When talking to hospital purchasers, he often said something like “I can show you the software, and I can tell you the price, and I can demonstrate the problem it will solve.” In contrast, however, an array of enormous corporations with salesmen and women (usually called consultants) were probably saying something more like “Your hospital needs more technology, our corporation is big and stable—give us this much money and we will solve your problem.” For Adrian, the decision to “hold hands,” as he put it, with the comfortably large corporation was irrational if the hospital could instead purchase a specific technology that did a specific thing, for a real price. ⑆,┨[pg 84]┣,
@@ -3941,7 +3709,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9A5916A4FBB86F5E3E6328221E2DD571AE1B3202EB8D065F96B623327E4BA1FD
| Adrian’s reflections on technology are also reflections on the nature of progress. Progress is limited intervention structured by goals that are not set by the technology itself, even if entrepreneurial activity is specifically focused on finding new uses and new ideas for new technologies. But discussions about healthcare allocation—which Adrian sees as a problem amenable to certain kinds of technical solutions—are instead structured as if technology did not matter to the nature of the ends. It is a point Adrian resists: “I firmly believe that in the long run the only way you can save money and improve healthcare is to add technology.”
@@ -3952,7 +3719,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E831023DC94E07E004638047AC296D0635A2D42A822923A454EC27C4ADB15D5B
| Sean is similarly frustrated by the homogenization of the concept of technology, especially when it is used to suggest, for instance, that hospitals “lag behind” other industries with regard to computerization, a complaint usually made in order to either instigate investment or explain failures. Sean first objects to such a homogenous notion of “technological.”
@@ -3963,7 +3729,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4FCE10738B926B70204AE459667BBAC1A6F2F55461A48665BECCB944CAA91E8E
.indent: 1 1
@@ -3976,7 +3741,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D46E22908AD039340F20983184A97FA75AC8A9164B2C10D0EDCC063D7523D347
| He also objects to the notion that such a lag results in failures caused by technology, rather than by something like incompetence or bad management. In fact, it might be fair to say that, for the polymath, sometimes technology actually dissolves. Its boundaries are not easily drawn, nor are its uses, nor are its purported “unintended consequences.” On one side there are rules, regulations, protocols, standards, norms, and forms of behavior; on the other there are organizational structures, business plans and logic, human skills, and other machines. This complex milieu requires reform from within: it cannot be replaced wholesale; it cannot leap-frog ⑆,┨[pg 85]┣, other industries in terms of computerization, as intervention is always local and strategic; and it involves a more complex relationship to the project of the present than simply “lagging behind” or “leaping ahead.”
@@ -3987,7 +3751,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A3543B72705AF8FF9D54DA0665FC7F9B166418E554E2BAC6727AC3C703CA3584
.has: notes_reg
@@ -3999,7 +3762,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E341E540920AA47F9B9ADDE612284BFF770F56695145DB3EFDF13492FD7B826B
.has: links notes_reg
@@ -4011,7 +3773,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4CD2824C8CA82386D52BA378B2FB99175EC2B76E0139B8E5BBD313D7F51123B1
.has: notes_reg
@@ -4023,7 +3784,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0C4C57261F5F85B113E96BA4883C36EE9156926EBD7EF657A2CC041857ABAA09
.has: notes_reg
@@ -4035,7 +3795,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D70B4FD50E4B86F89659ECBA1D2D0CDF9F4CD6F014A17693F3859A5755190D0E
.has: links notes_reg
@@ -4049,7 +3808,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 42B8ECE6280E1B3D0D529FA46FEBD91B9076FE909EE48DF405D25DDDD2D32640
| Various groups could be reasonably included under this label. There are the most ardent purveyors of the vision, the Extropians; there are a broad class of people who call themselves transhumanists; there is a French-Canadian subclass, the Raelians, who are more an alien-worshiping cult than a strictly scientific one and are bitterly denounced by the first two; there are also the variety of cosmologists and engineers who do not formally consider themselves ⑆,┨[pg 87]┣, transhumanist, but whose beliefs participate in some way or another: Stephen Hawking, Frank Tipler and John Barrow (famous for their anthropic cosmological principle), Hans Moravic, Ray Kurzweil, Danny Hillis, and down the line through those who embrace the cognitive sciences, the philosophy of artificial intelligence, the philosophy of mind, the philosophy of science, and so forth.
@@ -4060,7 +3818,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FB0260179353D42CE769FB9DE3D6A8C9362E0A501B647614642D87E0FFE63071
.has: links notes_reg
@@ -4072,7 +3829,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F9B0742FDCF4C1A8E73D0B55862F8D854A28FCDEFE6C55EC8A4DE15CBAB8AA38
| For many observers, transhumanists are a lunatic fringe, bounded on either side by alien abductees and Ayn Rand-spouting objectivists. However, like so much of the fringe, it merely represents in crystalline form attitudes that seem to permeate discussions more broadly, whether as beliefs professed or as beliefs attributed. Transhumanism, while probably anathema to most people, actually reveals a very specific attitude toward technical innovation, technical intervention, and political life that is widespread among technically adept individuals. It is a belief that has everything to do also with the timeline of progress and the role of technology in it.
@@ -4083,7 +3839,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E7C2E7EC142BC32BFBE840A8B39D3FD593FAECB60FAB6F2ABAED10480D6ED5AB
.has: notes_reg
@@ -4106,7 +3861,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 10B5A9962ABB77586498268972375F4DF5DC0D4E9CA34DFAFF52CD258E280299
.image: 2bits_02_01-100.png sha256:4170CBD7E3110AFE6869060890199261A0BF077C4F86121E8B5A736FEB11A0F3 bytes:16119 px:1572x1098
@@ -4120,7 +3874,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9EFD0066812380CC7087388EEED08056FC409659636997131549FDCFE46CDEA2
| In figure 1, on the left hand of the timeline, there is history, or rather, there is a string of technological inventions (by which is implied that previous inventions set the stage for later ones) spaced such that they produce a logarithmic curve that can look very much like the doomsday population curves that started to appear in the 1960s. Each invention is associated with a name or sometimes a nation. Beyond the edge of the graph to the right side is the future: history changes here from a series of inventions to an autonomous self-inventing technology associated not with individual inventors but with a complex system of evolutionary adaptation that includes technological as well as biological forms. It is a future in which “humans” are no longer necessary to the progress of science and technology: technology-as-extension-of-humans on the left, a Borg-like autonomous technical intelligence on the right. The fundamental ⑆,┨[pg 89]┣, operation in constructing the “singularity” is the “reasoned extrapolation” familiar to the “hard science fiction” writer or the futurist. One takes present technology as the initial condition for future possibilities and extrapolates based on the (haphazardly handled) evidence of past technical speed-up and change.
@@ -4131,7 +3884,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 521661D4643479E1A729E8DA9123CBCFE650108DAD87F5297B5D027F6DC9B760
| The position of the observer is always a bit uncertain, since he or she is naturally projected at the highest (or lowest, depending on your orientation) point of this curve, but one implication is clear: that the function or necessity of human reflection on the present will disappear at the same time that humans do, rendering enlightenment a quaint, but necessary, step on the route to superrational, transhuman immortality.
@@ -4142,7 +3894,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E4FAF4DCC19AE13EBD6F352E09217BB5093DA6FA0334C682FA5672099F6E0E73
| Strangely, the notion that technical progress has acceleration seems to precede any sense of what the velocity of progress might mean in the first instance; technology is presumed to exist in absolute time—from the Big Bang to the heat death of the universe—and not in any relationship with human life or consciousness. The singularity is always described from the point of view of a god who is not God. The fact of technological speed-up is generally treated as the most obvious thing in the world, reinforced by the constant refrain in the media of the incredible pace of change in contemporary society.
@@ -4153,7 +3904,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D85E2724E81E50C5A87227484188E6C09A4EDB716A5957FFD685CF108C16B325
| Why is the singularity important? Because it always implies that the absolute fact of technical acceleration—this knowing glance into the future—should order the kinds of interventions that occur in the present. It is not mute waiting or eschatological certainty that governs this attitude; rather, it is a mode of historical consciousness that privileges the inevitability of technological progress over the inevitability of human power. Only by looking into the future can one manipulate the present in a way that will be widely meaningful, an attitude that could be expressed as something like “Those who do not learn from the future are condemned to suffer in it.” Since it is a philosophy based on the success of human rationality and ingenuity, rationality and ingenuity are still clearly essential in the future. They lead, however, to a kind of posthuman state of constant technological becoming which is inconceivable to the individual human mind—and can only be comprehended by a transcendental intelligence that is not God.
@@ -4164,7 +3914,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6A5FC16D02365C99C6429016F3F45BEBB4CB1E54A9F575218C4017B9E8866C7D
| Such is a fair description of some strands of transhumanism, and the reason I highlight them is to characterize the kinds of attitudes ⑆,┨[pg 90]┣, toward technology-as-intervention and the ideas of moral and technical order that geeks can evince. On the far side of polymathy, geeks are too close to the machine to see a big picture or to think about imponderable philosophical issues; on the transhuman side, by contrast, one is constantly reassessing the arcane details of everyday technical change with respect to a vision of the whole—a vision of the evolution of technology and its relationship to the humans that (for the time being) must create and attempt to channel it.
@@ -4175,7 +3924,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BC18E609ED1092C98C98E8CFE0C1A39A26FD37E357BE96981E4FADF6F9790E30
| My favorite transhumanist is Eugen Leitl (who is, in fact, an authentic transhumanist and has been vice-chair of the World Transhumanist Association). Eugen is Russian-born, lives in Munich, and once worked in a cryobiology research lab. He is well versed in chemistry, nanotechnology, artificial-intelligence (AI) research, computational- and network-complexity research, artificial organs, cryobiology, materials engineering, and science fiction. He writes, for example,
@@ -4186,7 +3934,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EC790C71E03F9D71BE6AF522D8F236C501A80EA1D8E16936BA324EC64AFB7D9A
.indent: 1 1
@@ -4198,7 +3945,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 15D32BA9178F2D233499D1D51DDAB7E0B25126444AF03E4AFDE34C062EDBD57B
.indent: 1 1
@@ -4211,7 +3957,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6218C51E24A13D60A175930B48E4CDF79199F752E858B0A1566B767FCCF36D3B
| Eugen is also a polymath (and an autodidact to boot), but in the conventional sense. Eugen’s polymathy is an avocational necessity: transhumanists need to keep up with all advances in technology and science in order to better assess what kinds of human-augmenting or human-obsolescing technologies are out there. It is not for work in this world that the transhumanist expands his or her knowledge, nor quite for the next, but for a “this world” yet to arrive.
@@ -4222,7 +3967,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7B5562724E31FFA96D1CE20F09DEE6817D5E01E9B0DC3CF27843FAFC34C61D78
| Eugen and I were introduced during the Napster debates of 2001, which seemed at the time to be a knock-down, drag-out conflagration, but Eugen has been involved in so many online flame wars that he probably experienced it as a mere blip in an otherwise constant struggle with less-evolved intelligences like mine. Nonetheless, ⑆,┨[pg 91]┣, it was one of the more clarifying examples of how geeks think, and think differently, about technology, infrastructure, networks, and software. Transhumanism has no truck with old-fashioned humanism.
@@ -4246,7 +3990,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 74ADAF54EC19FD77402A9255125808D13CE18665BAF2A928866B4E6DA4801C04
.indent: 1 1
@@ -4259,7 +4002,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CDAB4BE4E13D81488D65507259634FBFF5C91C439548C4F74B78F19B887BEFDE
| Eugen’s understanding of what “technological progress” means is sufficiently complex to confound most of his interlocutors. For one surprising thing, it is not exactly inevitable. The manner in which Leitl argues with people is usually a kind of machine-gun prattle of coevolutionary, game-theoretic, cryptographic sorites. Eugen piles on the scientific and transhumanist reasoning, and his interlocutors slowly peel away from the discussion. But it isn’t craziness, hype, or half-digested popular science—Eugen generally knows his stuff—it just fits together in a way that almost no one else can quite grasp. Eugen sees the large-scale adoption and proliferation of technologies (particularly self-replicating molecular devices and evolutionary software algorithms) as a danger that transcends all possibility of control at the individual or state level. Billions of individual decisions do not “average” into one will, but instead produce complex dynamics and hang perilously on initial conditions. In discussing the possibility of the singularity, Eugen suggests, “It could literally be a science-fair project [that causes the singularity].” If Francis Bacon’s understanding of the relation between Man and Nature was that of master and possessor, Eugen’s is its radicalization: Man is a powerful but ultimately arbitrary force in the progress of Life-Intelligence. Man is fully incorporated into Nature in this story, ⑆,┨[pg 92]┣, so much so that he dissolves into it. Eugen writes, when “life crosses over into this petri dish which is getting readied, things will become a lot more lively. . . . I hope we’ll make it.”
@@ -4281,7 +4023,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0C454E567A2BDB28BDBA1002DE0289BA54B62DDD418644DE7D57EBFC96C0D20D
| For Eugen, the arguments about technology that the polymaths involve themselves in couldn’t be more parochial. They are important only insofar as they will set the “initial conditions” for the grand coevolutionary adventure of technology ahead of us. For the transhumanist, technology does not dissolve. Instead, it is the solution within which humans are dissolved. Suffering, allocation, decision making—all these are inessential to the ultimate outcome of technological progress; they are worldly affairs, even if they concern life and death, and as such, they can be either denounced or supported, but only with respect to fine-tuning the acceleration toward the singularity. For the transhumanist, one can’t fight the inevitability of technical evolution, but one certainly can contribute to it. Technical progress is thus both law-like and subject to intelligent manipulation; technical progress is inevitable, but only because of the power of massively parallel human curiosity.
@@ -4303,7 +4044,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BA6E9F1AA73F2D897694282FD128AA183B4E325AA06D0A76689F786EC7AEE03B
| Considered as one of the modes of thought present in this-worldly political discussion, the transhumanist (like the polymath) turns technology into a rhetorical argument. Technology is the more powerful political argument because “it works.” It is pointless to argue “about” technology, but not pointless to argue through and with it. It is pointless to talk about whether stopping technology is good or bad, because someone will simply build a technology that will invalidate your argument.
@@ -4314,7 +4054,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8B14C54B0BACE1F0E60ACA174D10BD447CB22695D7AD9B1973324F9A9D7930CB
| There is still a role for technical invention, but it is strongly distinguished from political, legal, cultural, or social interventions. For most transhumanists, there is no rhetoric here, no sophistry, just the pure truth of “it works”: the pure, undeniable, unstoppable, and undeconstructable reality of technology. For the transhumanist attitude, the reality of “working code” has a reality that other assertions about the world do not. Extreme transhumanism replaces the life-world with the world of the computer, where bad (ethically bad) ideas won’t compile. Less-staunch versions of transhumanism simply allow the confusion to operate opportunistically: the progress of technology is unquestionable (omniscient), and only its effects on humans are worth investigating.
@@ -4325,7 +4064,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3F932851101E688972DEE2A52C15116534BAEAD7027B50F3AAB775A4BE89AF55
| The pure transhumanist, then, is a countermodern. The transhumanist despises the present for its intolerably slow descent into the ⑆,┨[pg 93]┣, future of immortality and superhuman self-improvement, and fears destruction because of too much turbulent (and ignorant) human resistance. One need have no individual conception of the present, no reflection on or synthetic understanding of it. One only need contribute to it correctly. One might even go so far as to suggest that forms of reflection on the present that do not contribute to technical progress endanger the very future of life-intelligence. Curiosity and technical innovation are not historical features of Western science, but natural features of a human animal that has created its own conditions for development. Thus, the transhumanists’ historical consciousness consists largely of a timeline that makes ordered sense of our place on the progress toward the Singularity.
@@ -4336,7 +4074,6 @@
.ancestors: 1 74 0 0 189 234 0 0
.ancestors_collapsed: 1 74 189 234 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 62F47F2821356A41B5435C258C4DF548A66BB3F55DEA61C57B4637B02A9B4DF4
.has: notes_reg
@@ -4365,7 +4102,6 @@
.ancestors: 1 74 0 0 189 287 0 0
.ancestors_collapsed: 1 74 189 287 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FF761482BB7E3EDF7C071739C97F9BBEED8ADFDA857294AFD103C3A9310F86D9
| To many observers, geeks exhibit a perhaps bewildering mix of liberalism, libertarianism, anarchism, idealism, and pragmatism, ⑆,┨[pg 94]┣, yet tend to fall firmly into one or another constituted political category (liberal, conservative, socialist, capitalist, neoliberal, etc.). By showing how geeks make use of the Protestant Reformation as a usable past and how they occupy a spectrum of beliefs about progress, liberty, and intervention, I hope to resist this urge to classify. Geeks are an interesting case precisely because they are involved in the creation of new things that change the meaning of our constituted political categories. Their politics are mixed up and combined with the technical details of the Internet, Free Software, and the various and sundry organizations, laws, people, and practices that they deal with on a regular basis: operating systems and social systems. But such mixing does not make Geeks merely technoliberals or technoconservatives. Rather, it reveals how they think through the specific, historically unique situation of the Internet to the general problems of knowledge and power, liberty and enlightenment, progress and intervention.
@@ -4376,7 +4112,6 @@
.ancestors: 1 74 0 0 189 287 0 0
.ancestors_collapsed: 1 74 189 287 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F226CF87BF0263FC27A69642F34B05E6575056A288232E3373CB46D9F22D7396
| Geeks are not a kind of person: geeks are geeks only insofar as they come together in new, technically mediated forms of their own creation and in ways that are not easy to identify (not language, not culture, not markets, not nations, not telephone books or databases). While their affinity is very clearly constituted through the Internet, the Internet is not the only reason for that affinity. It is this collective affinity that I refer to as a recursive public. Because it is impossible to understand this affinity by trying to identify particular types of people, it is necessary to turn to historically specific sets of practices that form the substance of their affinity. Free Software is an exemplary case—perhaps the exemplar—of a recursive public. To understand Free Software through its changing practices not only gives better access to the life-world of the geek but also reveals how the structure of a recursive public comes into being and manages to persist and transform, how it can become a powerful form of life that extends its affinities beyond technophile geeks into the realms of ordinary life.
@@ -4428,7 +4163,6 @@
.ancestors: 1 290 0 0 291 0 0 0
.ancestors_collapsed: 1 290 291 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: AEF6613E9E87D74DCF5609BC485BFFF5029B5D7164BED294F7320D42DB4FDE45
| Part II of Two Bits describes what Free Software is and where it came from, with each of its five chapters detailing the historical narrative of a particular kind of practice: creating a movement, sharing source code, conceptualizing openness or open systems, writing copyright (and copyleft) licenses, and coordinating collaborations. Taken together, the stories describe Free Software. The stories have their endpoint (or starting point, genealogically speaking) in the years 1998-99, when Free Software burst onto the scene: on the cover of Forbes magazine, as part of the dotcom boom, and in the boardrooms of venture-capital firms and corporations like IBM and Netscape. While the chapters that make up part II can be read discretely to understand the practices that are the sine qua non of Free Software, they can also be read continuously, as a meandering story of the history of software and networks stretching from the late 1950s to the present.
@@ -4450,7 +4184,6 @@
.ancestors: 1 290 0 0 291 0 0 0
.ancestors_collapsed: 1 290 291 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 723B32614D5DF0A419AC0C6AED22D20F776FDB51EE6F769CC703A363654DA2B7
| Rather than define what makes Free Software free or Open Source open, Two Bits treats the five practices as parts of a collective technical experimental system: each component has its own history, development, and temporality, but they come together as a package and emerge as a recognizable thing around 1998-99. As with any experimental system, changing the components changes the operation and outcomes of the whole. Free Software so conceived is a kind of experimental system: its practices can be adopted, adapted, and modulated in new contexts and new places, but it is one whose rules are collectively determined and frequently modified. It is possible to see in each of the five practices where choices about how to do Free Software reached, or surpassed, certain limits, but nonetheless remained part of a system whose identity finally firmed up in the period 1998-99 and after.
@@ -4461,7 +4194,6 @@
.ancestors: 1 290 0 0 291 0 0 0
.ancestors_collapsed: 1 290 291 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: ED7554956B3DA2A3A31485BAFE697DBBD7A32D025DC37C7E530B94205FC633F6
.has: links notes_reg
@@ -4476,7 +4208,6 @@
.ancestors: 1 290 0 0 291 0 0 0
.ancestors_collapsed: 1 290 291 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: A520D0BF5E600161BA4BDA0667B5430AD3F296E92A3AA9614911D3BE2983CC8F
| One way to understand the movement is through the story of Netscape and the Mozilla Web browser (now known as Firefox). Not only does this story provide some context for the stories of geeks presented in part I—and I move here from direct participant observation to historical and archival research on a phenomenon that was occurring at roughly the same time—but it also contains all the elements necessary to understand Free Software. It is full of discussion and argument about the practices that make up Free Software: sharing source code, conceiving of openness, writing licenses, and coordinating collaborations.
@@ -4515,7 +4246,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C263ECC66AB8E0467BECD9EEEB6412587FED827E100101BAB2B4E715D88C548E
| Free Software forked in 1998 when the term Open Source suddenly appeared (a term previously used only by the CIA to refer to unclassified sources of intelligence). The two terms resulted in two separate kinds of narratives: the first, regarding Free Software, stretched back into the 1980s, promoting software freedom and resistance to proprietary software “hoarding,” as Richard Stallman, the head of the Free Software Foundation, refers to it; the second, regarding Open Source, was associated with the dotcom boom and the evangelism of the libertarian pro-business hacker Eric Raymond, who focused on the economic value and cost savings that Open Source Software represented, including the pragmatic (and polymathic) approach that governed the everyday use of Free Software in some of the largest online start-ups (Amazon, Yahoo!, HotWired, and others all “promoted” Free Software by using it to run their shops).
@@ -4526,7 +4256,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D484F74F02026EA19254972446C611337F90E468EDEA003F2E3C7FE5A4751465
| A critical point in the emergence of Free Software occurred in 1998-99: new names, new narratives, but also new wealth and new stakes. “Open Source” was premised on dotcom promises of cost-cutting and “disintermediation” and various other schemes to make money on it (Cygnus Solutions, an early Free Software company, playfully tagged itself as “Making Free Software More Affordable”). VA Linux, for instance, which sold personal-computer systems pre-installed with Open Source operating systems, had the largest single initial public offering (IPO) of the stock-market bubble, seeing a 700 percent share-price increase in one day. “Free Software” by contrast fanned kindling flames of worry over intellectual-property expansionism and hitched itself to a nascent legal resistance to the 1998 Digital Millennium Copyright Act and Sonny Bono Copyright Term Extension Act. Prior to 1998, Free Software referred either to the Free Software Foundation (and the watchful, micromanaging eye of Stallman) or to one of thousands of different commercial, avocational, or university-research projects, processes, licenses, and ideologies that had a variety of names: sourceware, freeware, shareware, open software, public domain software, and so on. The term Open Source, by contrast, sought to encompass them all in one movement.
@@ -4537,7 +4266,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C80CCC0D48CC9E713ED3B8205C96BB37951A62CE7080529A7B5783B525E43AB5
| The event that precipitated this attempted semantic coup d’état was the release of the source code for Netscape’s Communicator ⑆,┨[pg 100]┣, Web browser. It’s tough to overestimate the importance of Netscape to the fortunes of Free Software. Netscape is justly famous for its 1995 IPO and its decision to offer its core product, Netscape Navigator, for free (meaning a compiled, binary version could be downloaded and installed “for zero dollars”). But Netscape is far more famous among geeks for giving away something else, in 1998: the source code to Netscape Communicator (née Navigator). Giving away the Navigator application endeared Netscape to customers and confused investors. Giving away the Communicator source code in 1998 endeared Netscape to geeks and confused investors; it was ignored by customers.
@@ -4548,7 +4276,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8E6DAA82016D06EA3CAA0267DF4700B39AEE8442094EBF5DA4570B43DC5EEC16
| Netscape is important from a number of perspectives. Businesspeople and investors knew Netscape as the pet project of the successful businessman Jim Clarke, who had founded the specialty computer manufacturer, Silicon Graphics Incorporated (SGI). To computer scientists and engineers, especially in the small university town of Champaign-Urbana, Illinois, Netscape was known as the highest bidder for the WWW team at the National Center for Supercomputing Applications (NCSA) at the University of Illinois. That team—Marc Andreessen, Rob McCool, Eric Bina, Jon Mittelhauser, Aleks Totic, and Chris Houck—had created Mosaic, the first and most fondly remembered “graphical browser” for surfing the World Wide Web. Netscape was thus first known as Mosaic Communications Corporation and switched its name only after legal threats from NCSA and a rival firm, Spyglass. Among geeks, Netscape was known as home to a number of Free Software hackers and advocates, most notably Jamie Zawinski, who had rather flamboyantly broken rank with the Free Software Foundation by forking the GNU EMACS code to create what was first known as Lucid Emacs and later as XEmacs. Zawinski would go on to lead the newly free Netscape browser project, now known as Mozilla.
@@ -4559,7 +4286,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E8D2D229CF3BEAED40261525BD182D395FA00E6F2DA3F899380F40FE7BC3B8B2
| Meanwhile, most regular computer users remember Netscape both as an emblem of the dotcom boom’s venture-fed insanity and as yet another of Microsoft’s victims. Although Netscape exploded onto the scene in 1995, offering a feature-rich browser that was an alternative to the bare-bones Mosaic browser, it soon began to lose ground to Microsoft, which relatively quickly adopted the strategy of giving away its browser, Internet Explorer, as if it were part of the Windows operating system; this was a practice that the U.S. Department of Justice eventually found to be in violation of ⑆,┨[pg 101]┣, antitrust laws and for which Microsoft was convicted, but never punished.
@@ -4570,7 +4296,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1E335E053E074AB0765FBA87163E92B44486F7C477AAE6157839D79C0E87E55C
| The nature of Netscape’s decision to release the source code differs based on which perspective it is seen from. It could appear to be a business plan modeled on the original success: give away your product and make money in the stock market. It could appear to be a strategic, last-gasp effort to outcompete Microsoft. It could also appear, and did appear to many geeks, to be an attempt to regain some of that “hacker-cred” it once had acquired by poaching the NCSA team, or even to be an attempt to “do the right thing” by making one of the world’s most useful tools into Free Software. But why would Netscape reach such a conclusion? By what reasoning would such a decision seem to be correct? The reasons for Netscape’s decision to “free the source” recapitulate the five core practices of Free Software—and provided key momentum for the new movement.
@@ -4581,7 +4306,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5DC2015182E5F563E5A07F76924EE2DAEA088AA9841EA4B7B11D542F40B3284D
| ⑆!┨Sharing Source Code┣! Netscape’s decision to share its source code could only seem surprising in the context of the widespread practice of keeping source code secret; secrecy was a practice followed largely in order to prevent competitors from copying a program and competing with it, but also as a means to control the market itself. The World Wide Web that Andreessen’s team at NCSA had cut their teeth on was itself designed to be “platform independent” and accessible by any device on the network. In practice, however, this meant that someone needed to create “browsers” for each different computer or device. Mosaic was initially created for UNIX, using the Motif library of the X11 Window System—in short, a very specific kind of access. Netscape, by contrast, prided itself on “porting” Netscape Navigator to nearly all available computer architectures. Indeed, by 1997, plans were under way to create a version of the browser—written in Java, the programming language created by Sun Microsystems to “write once, run anywhere”—that would be completely platform independent.
@@ -4592,7 +4316,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F1D902AC44767C48A1F7BC0F85ED3615F3815DF09215E5E9C211E2EFAFC4E8B1
| The Java-based Navigator (called Javagator, of course) created a problem, however, with respect to the practice of keeping source code secret. Whenever a program in Java was run, it created a set of “bytecodes” that were easy to reverse-engineer because they had to be transmitted from the server to the machine that ran the program and were thus visible to anyone who might know how and where to look. Netscape engineers flirted with the idea of deliberately ⑆,┨[pg 102]┣, obfuscating these bytecodes to deter competitors from copying them. How can one compete, the logic goes, if anyone can copy your program and make their own ersatz version?
@@ -4603,7 +4326,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 20FE4C1991B8CFF95F7C2B3BB20A8EA0746111C16AA4725017CA1710B12A816C
| Zawinski, among others, suggested that this was a bad idea: why not just share the source code and get people to help make it better? As a longtime participant in Free Software, Zawinski understood the potential benefits of receiving help from a huge pool of potential contributors. He urged his peers at Netscape to see the light. However, although he told them stories and showed them successes, he could never make the case that this was an intelligent business plan, only that it was an efficient software-engineering plan. From the perspective of management and investors, such a move seemed tantamount to simply giving away the intellectual property of the company itself.
@@ -4614,7 +4336,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A0DF52A3153A18DA2470603D7DFACA7EFF8DFC4020A01A97A59364A39505D923
.has: notes_reg
@@ -4626,7 +4347,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 46D0A87D666F23DADE4FF26E57A58845E260AB638C2518216A9FE67D778E05E1
.has: notes_reg
@@ -4638,7 +4358,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F5086ADDA76838D1F24A2CE41EFFC13ED3FB5F5B06FF95224A7A8E4EF6F51D27
| ⑆!┨Conceptualizing Open Systems┣! Releasing the source code was, in a way, an attempt to regain the trust of the people who had first imagined the www. Tim Berners-Lee, the initial architect of the www, was always adamant that the protocol and all its implementations should be freely available (meaning either “in the public domain” or “released as Free Software”). Indeed, Berners-Lee had done just that with his first bare-bones implementations of the www, proudly declaring them to be in the public domain.
@@ -4649,7 +4368,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 155B6F9016295AB26EDF8D4812BEBA2AF44857FBB2A84A08B11EB7A08340DD68
| Over the course of the 1990s, the “browser wars” caused both Netscape and Microsoft to stray far from this vision: each had implemented its own extensions and “features” to the browsers and servers, extensions not present in the protocol that Berners-Lee had created or in the subsequent standards created by the World Wide Web Consortium (W3C). Included in the implementations were various kinds of “evil” that could make browsers fail to work on certain operating systems or with certain kinds of servers. The “browser wars” repeated an open-systems battle from the 1980s, one in which the attempt to standardize a network operating system (UNIX) was stymied by competition and secrecy, at the same time that consortiums devoted to “openness” were forming in order to try to prevent the spread of evil. Despite the fact that both Microsoft and Netscape were members of the W3C, the noncompatibility of their browsers clearly represented the manipulation of the standards process in the name of competitive advantage.
@@ -4660,7 +4378,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D130D6D34E4B5F5BABC43F67E62E3A81AB356A3D65F99C18D338CAAFE11E0B6D
| Releasing the source code for Communicator was thus widely seen as perhaps the only way to bypass the poisoned well of competitively tangled, nonstandard browser implementations. An Open Source browser could be made to comply with the standards—if not by the immediate members involved with its creation, then by creating a “fork” of the program that was standards compliant—because of the rights of redistribution associated with an Open Source license. Open Source would be the solution to an open-systems problem that had never been solved because it had never confronted the issue of intellectual property directly. Free Software, by contrast, had a well-developed solution in the GNU General Public License, ⑆,┨[pg 104]┣, also known as copyleft license, that would allow the software to remain free and revive hope for maintaining open standards.
@@ -4671,7 +4388,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5B739076D5E18492B7A5ADF97336D2B327415C85FB0A8977DB6C02368AC96564
| ⑆!┨Writing Licenses┣! Herein lies the rub, however: Netscape was immediately embroiled in controversy among Free Software hackers because it chose to write its own bespoke licenses for distributing the source code. Rather than rely on one of the existing licenses, such as the GNU GPL or the Berkeley Systems Distribution (BSD) or MIT licenses, they created their own: the Netscape Public License (NPL) and the Mozilla Public License. The immediate concerns of Netscape had to do with their existing network of contracts and agreements with other, third-party developers—both those who had in the past contributed parts of the existing source code that Netscape might not have the rights to redistribute as Free Software, and those who were expecting in the future to buy and redistribute a commercial version. Existing Free Software licenses were either too permissive, giving to third parties rights that Netscape itself might not have, or too restrictive, binding Netscape to make source code freely available (the GPL) when it had already signed contracts with buyers of the nonfree code.
@@ -4682,7 +4398,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2872AFB472FD1767C894D2B165D255DE81DCAF60E45BB966784E502C9104D918
| It was a complex and specific business situation—a network of existing contracts and licensed code—that created the need for Netscape to write its own license. The NPL thus contained a clause that allowed Netscape special permission to relicense any particular contribution to the source code as a proprietary product in order to appease its third-party contracts; it essentially gave Netscape special rights that no other licensee would have. While this did not necessarily undermine the Free Software licenses—and it was certainly Netscape’s prerogative—it was contrary to the spirit of Free Software: it broke the “recursive public” into two halves. In order to appease Free Software geeks, Netscape wrote one license for existing code (the NPL) and a different license for new contributions: the Mozilla Public License.
@@ -4693,7 +4408,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DA7F5A16C323E73E9683B5A81E19E2C59EBC16EBD02AEFE8766268F5F9AFFDAF
.has: notes_reg
@@ -4705,7 +4419,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6E45883148E01A24A964BE455BFB31C8E099867364632D6EB56DB462050523E2
.has: notes_reg
@@ -4717,7 +4430,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A877A6EA0B1513C1271384265F2789026021EDC271B07E291F6046225F823C57
.has: links notes_reg
@@ -4729,7 +4441,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 00D82B8D0EF1413BB8C6B7162B27630B36BD67AF40D764B7A89E96FA623E9632
.has: notes_reg
@@ -4741,7 +4452,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 702A70C44EE957A75BF04386B0D6BC1682E3757C741FCB21A6BBC4BD4E143CC4
| Releasing the Mozilla code, therefore, required a system of coordination that would differ from the normal practice of in-house ⑆,┨[pg 106]┣, software development by paid programmers. It needed to incorporate the contributions of outsiders—developers who didn’t work for Netscape. It also needed to entice people to contribute, since that was the bargain on which the decision to free the source was based, and to allow them to track their contributions, so they could verify that their contributions were included or rejected for legitimate reasons. In short, if any magical Open Source self-organization were to take place, it would require a thoroughly transparent, Internet-based coordination system.
@@ -4763,7 +4473,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 914720E2EF326EAB3EF34290E50006F249A5F7C0FEEBF543AC2A02E6CDFD9987
| At the outset, this meant practical things: obtaining the domain name mozilla.org; setting up (and in turn releasing the source code for) the version-control system (the Free Software standard cvs), the version-control interface (Bonsai), the “build system” that managed and displayed the various trees and (broken) branches of a complex software project (Tinderbox), and a bug-reporting system for tracking bugs submitted by users and developers (Bugzilla). It required an organizational system within the Mozilla project, in which paid developers would be assigned to check submissions from inside and outside, and maintainers or editors would be designated to look at and verify that these contributions should be used.
@@ -4774,7 +4483,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 66EE4A2F7D66847C00CCEC7DDFDCB42EE06E30AC73675FDA9DEFDB9E76D89FCE
.has: links notes_reg
@@ -4798,7 +4506,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6B8596E186C97F4468F654626445E934ABC1F49D82634BE3201A039BC0EA36A7
.has: notes_reg
@@ -4810,7 +4517,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 08C9B8755B98E75AB4701B3060FDB3DB0097932ECE3735B7B019842DD4650390
.has: notes_reg
@@ -4822,7 +4528,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 108FFE6F2F00B52FCC5AE52A1E1ACE7C66203710384C0573592A94BB1FD0A686
| ⑆!┨Fomenting Movements┣! The period from 1 April 1998, when the Mozilla source code was first released, to 1 April 1999, when Zawinski announced its failure, couldn’t have been a headier, more exciting time for participants in Free Software. Netscape’s decision to release the source code was a tremendous opportunity for geeks involved in Free Software. It came in the midst of the rollicking dotcom bubble. It also came in the midst of the widespread adoption of ⑆,┨[pg 108]┣, key Free Software tools: the Linux operating system for servers, the Apache Web server for Web pages, the perl and python scripting languages for building quick Internet applications, and a number of other lower-level tools like Bind (an implementation of the DNS protocol) or sendmail for e-mail.
@@ -4833,7 +4538,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2123250C6293A81A695BCDEAFA1D8C70CEF932081F49387A07EFF60B7D18B956
| Perhaps most important, Netscape’s decision came in a period of fevered and intense self-reflection among people who had been involved in Free Software in some way, stretching back to the mid-1980s. Eric Raymond’s article “The Cathedral and The Bazaar,” delivered at the Linux Kongress in 1997 and the O’Reilly Perl Conference the same year, had started a buzz among Free Software hackers. It was cited by Frank Hecker and Eric Hahn at Netscape as one of the sources for their thinking about the decision to free Mozilla; Raymond and Bruce Perens had both been asked to consult with Netscape on Free Software strategy. In April of the same year Tim O’Reilly, a publisher of handbooks for Free Software, organized a conference called the Freeware Summit.
@@ -4844,7 +4548,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FCB6950EDAA4F2A9697029FC22E7DD66C2DC67B87A94A244E1E7937D8A712E3E
.has: links notes_reg
@@ -4856,7 +4559,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 39B2545B05DCE85D05900E73E0BC24D6A0BEEF6FE6B757BB1CFC7B23F9038D6D
.has: notes_reg
@@ -4868,7 +4570,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9B9D0DEBF225CD9FADABACB0321998818D4C88267BD982C74509D375B2E4322A
| The motivations for these changes came from a variety of sources—ranging from a desire to be included in the dotcom boom to a powerful (ideological) resistance to being ideological. Linus Torvalds loudly proclaimed that the reason to do Free Software was because it was “fun”; others insisted that it made better business ⑆,┨[pg 109]┣, sense or that the stability of infrastructures like the Internet depended on a robust ability to improve them from any direction. But none of them questioned how Free Software got done or proposed to change it.
@@ -4879,7 +4580,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4FAC894112519DE1A3609BD05C5BE0F37435CE7CE9EE003D4B73FF6BF4DE3C47
.has: links notes_reg
@@ -4892,7 +4592,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 18AD930DAF80D0CE4A0381DBCDCA42C6D75980FAE3BCEF685FBFBEA367B597BE
| Raymond was determined to reject the philosophy of liberty that Stallman and the Free Software Foundation represented, but not in order to create a political movement of his own. Rather, Raymond (and the others at the Freeware Summit) sought to cash in on the rising tide of the Internet economy by turning the creation of Free Software into something that made more sense to investors, venture capitalists, and the stock-buying public. To Raymond, Stallman and the Free Software Foundation represented not freedom or liberty, but a kind of dogmatic, impossible communism. As Raymond was a committed libertarian, one might expect his core beliefs in the necessity of strong property rights to conflict with the strange communalism of Free Software—and, indeed, his rhetoric was focused on pragmatic, business-minded, profit-driven, and market-oriented uses of Free Software. For Raymond, the essentially interesting component of Free Software was not its enhancement of human liberty, but the innovation in software production that it represented (the “development model”). It was clear that Free Software achieved something amazing through a clever inversion of strong property rights, an inversion which could be expected to bring massive revenue in some other form, either through cost-cutting or, Netscape-style, through the stock market.
@@ -4903,7 +4602,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0284B20ACB7C770FC86474C9C77AF21D70D9AA9F79179FD9154728590B3F2E5E
| Raymond wanted the business world and the mainstream industry to recognize Free Software’s potential, but he felt that Stallman’s ⑆,┨[pg 110]┣, rhetoric was getting in the way. Stallman’s insistence, for example, on calling corporate intellectual-property protection of software “hoarding” was doing more damage than good in terms of Free Software’s acceptance among businesses, as a practice, if not exactly a product.
@@ -4914,7 +4612,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1FC23C65F44A17D3CB731C224CCD5BE9208B6FF90C38A32A8360600A87FD19F1
| Raymond’s papers channeled the frustration of an entire generation of Free Software hackers who may or may not have shared Stallman’s dogmatic philosophical stance, but who nonetheless wanted to participate in the creation of Free Software. Raymond’s paper, the Netscape announcement, and the Freeware Summit all played into a palpable anxiety: that in the midst of the single largest creation of paper wealth in U.S. history, those being enriched through Free Software and the Internet were not those who built it, who maintained it, or who got it.
@@ -4925,7 +4622,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B3DF0DB306FBDAA93E31BF50F944C9015694D41ED8AD91F24520FDB85AE8E5EE
| The Internet giveaway was a conflict of propriety: hackers and geeks who had built the software that made it work, under the sign of making it free for all, were seeing that software generate untold wealth for people who had not built it (and furthermore, who had no intention of keeping it free for all). Underlying the creation of wealth was a commitment to a kind of permanent technical freedom—a moral order—not shared by those who were reaping the most profit. This anxiety regarding the expropriation of work (even if it had been a labor of love) was ramified by Netscape’s announcement.
@@ -4936,7 +4632,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A7F2A7CEF694F4F4FD22A922863A5ED4B11A9BAC8ABDA5DEE5D584A8A40F7E9D
.has: notes_reg
@@ -4948,7 +4643,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6FA4FA4ECD672391B85AD2E03FB6F17FF3705C6B9725CB8DF35A1DA22C39451E
.image: 2bits_03_02-100.png sha256:268C643F2954DF149EEF6B9DF36900F128F37BFCBCF16B781A9119C906B5888B bytes:317845 px:620x657
@@ -4961,7 +4655,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8F87CAEB640E725BF24CF2E64EC30FA0D32EE34FD7B677476640B4EC91A47BC5
| By early 1999, O’Reilly Press published Open Sources: Voices from the Open Source Revolution, a hastily written but widely read book. It included a number of articles—this time including one by Stallman—that cobbled together the first widely available public history of Free Software, both the practice and the technologies ⑆,┨[pg 111]┣, involved. Kirk McKusick’s article detailed the history of important technologies like the BSD version of UNIX, while an article by Brian Behlendorf, of Apache, detailed the practical challenges of running Free Software projects. Raymond provided a history of hackers and a self-aggrandizing article about his own importance in creating the movement, while Stallman’s contribution told his own version of the rise of Free Software.
@@ -4972,7 +4665,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C165D1E66FD35CAFB369CC86F2F37A05B8DC5106800EDDCF5C8BA855A6857AB1
| By December 1999, the buzz had reached a fever pitch. When VA Linux, a legitimate company which actually made something real—computers with Linux installed on them—went public, its shares’ value gained 700 percent in one day and was the single ⑆,┨[pg 112]┣, most valuable initial public offering of the era. VA Linux took the unconventional step of allowing contributors to the Linux kernel to buy into the stock before the IPO, thus bringing at least a partial set of these contributors into the mainstream Ponzi scheme of the Internet dotcom economy. Those who managed to sell their stock ended up benefiting from the boom, whether or not their contributions to Free Software truly merited it. In a roundabout way, Raymond, O’Reilly, Perens, and others behind the name change had achieved recognition for the central role of Free Software in the success of the Internet—and now its true name could be known: Open Source.
@@ -4983,7 +4675,6 @@
.ancestors: 1 290 0 0 291 296 0 0
.ancestors_collapsed: 1 290 291 296 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BA7E2F79B1575B8B4F999FA6092748F993253CCB5868127DF21DF422FD60B908
| Yet nothing much changed in terms of the way things actually got done. Sharing source code, conceiving openness, writing licenses, coordinating projects—all these continued as before with no significant differences between those flashing the heroic mantle of freedom and those donning the pragmatic tunic of methodology. Now, however, stories proliferated; definitions, distinctions, details, and detractions filled the ether of the Internet, ranging from the philosophical commitments of Free Software to the parables of science as the “original open source” software. Free Software proponents refined their message concerning rights, while Open Source advocates refined their claims of political agnosticism or nonideological commitments to “fun.” All these stories served to create movements, to evangelize and advocate and, as Eugen Leitl would say, to “corrupt young minds” and convert them to the cause. The fact that there are different narratives for identical practices is an advantageous fact: regardless of why people think they are doing what they are doing, they are all nonetheless contributing to the same mysterious thing.
@@ -5011,7 +4702,6 @@
.ancestors: 1 290 0 0 291 337 0 0
.ancestors_collapsed: 1 290 291 337 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B5560C8739985FFC07453D84A078127445F4BC09DCC0DDFD6699143E5C6218A2
| To most onlookers, Free Software and Open Source seem to be overwhelmed with frenzied argument; the flame wars and disputes, online and off, seem to dominate everything. To attend a conference where geeks—especially high-profile geeks like Raymond, Stallman, and Torvalds—are present, one might suspect that the very detailed practices of Free Software are overseen by the brow-beating, histrionic antics of a few charismatic leaders and that ideological commitments result in divergent, incompatible, and affect-laden ⑆,┨[pg 113]┣, opposition which must of necessity take specific and incompatible forms. Strangely, this is far from the case: all this sound and fury doesn’t much change what people do, even if it is a requirement of apprenticeship. It truly is all over but for the shouting.
@@ -5022,7 +4712,6 @@
.ancestors: 1 290 0 0 291 337 0 0
.ancestors_collapsed: 1 290 291 337 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C79278817D0660AAA66D3A27E5F7550C3C2CCB046814FF6646362D89913DBB24
.has: links notes_reg
@@ -5036,7 +4725,6 @@
.ancestors: 1 290 0 0 291 337 0 0
.ancestors_collapsed: 1 290 291 337 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C73326BC7B292EF7731A0E0B0044AF7EC3B011310951B45FD0AE1EC3B7E7904D
| The movement, as a practice of argument and discussion, is thus centered around core agreements about the other four kinds of practices. The discussion and argument have a specific function: to tie together divergent practices according to a wide consensus which tries to capture the why of Free Software. Why is it different from normal software development? Why is it necessary? Why now? ⑆,┨[pg 114]┣, Why do people do it? Why do people use it? Can it be preserved and enhanced? None of these questions address the how: how should source code circulate? How should a license be written? Who should be in charge? All of these “hows” change slowly and experimentally through the careful modulation of the practices, but the “whys” are turbulent and often distracting. Nonetheless, people engaged in Free Software—users, developers, supporters, and observers—could hardly remain silent on this point, despite the frequent demand to just “shut up and show me the code.” “Figuring out” Free Software also requires a practice of reflecting on what is central to it and what is outside of it.
@@ -5047,7 +4735,6 @@
.ancestors: 1 290 0 0 291 337 0 0
.ancestors_collapsed: 1 290 291 337 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 84865C2569C255941997B36822B45008353F018A89835C73E3C65735E72B2D7D
.has: notes_reg
@@ -5059,7 +4746,6 @@
.ancestors: 1 290 0 0 291 337 0 0
.ancestors_collapsed: 1 290 291 337 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0E079A38D167AA3CD09D13D030D95DF3C25E733A6A887E8BE2BFFFF02E9502F6
| Stories of the movement are also stories of a recursive public. The fact that movement isn’t quite the right word is evidence of a kind of grasping, a figuring out of why these practices make sense to all these geeks, in this place and time; it is a practice that is not so different from my own ethnographic engagement with it. Note that both Free Software and Open Source tell stories of movement(s): they are not divided by a commercial-noncommercial line, even if they are divided by ill-defined and hazy notions of their ultimate goals. The problem of a recursive public (or, in an alternate language, a recursive market) as a social imaginary of moral and technical order is common to both of them as part of their practices. Thus, stories about “the movement” are detailed stories about the technical and moral order that geeks inhabit, and they are bound up with the functions and fates of the Internet. Often these stories are themselves practices of inclusion and exclusion (e.g., “this license is not a Free Software license” or “that software is not an open system”); sometimes the stories are normative definitions about how Free Software should look. But they are, always, stories that reveal the shared moral and technical imaginations that make up Free Software as a recursive public.
@@ -5087,7 +4773,6 @@
.ancestors: 1 290 0 0 291 343 0 0
.ancestors_collapsed: 1 290 291 343 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 41343B94AC7966A1722CA71FBCE7465A055DCF76CAAC85438F916E5A6D201D42
| Before 1998, there was no movement. There was the Free Software Foundation, with its peculiar goals, and a very wide array of other projects, people, software, and ideas. Then, all of a sudden, in the heat of the dotcom boom, Free Software was a movement. Suddenly, it was a problem, a danger, a job, a calling, a dogma, a solution, a philosophy, a liberation, a methodology, a business plan, a success, and an alternative. Suddenly, it was Open Source or Free Software, and it became necessary to choose sides. After 1998, debates about definition exploded; denunciations and manifestos and journalistic hagiography proliferated. Ironically, the creation of two names allowed people to identify one thing, for ⑆,┨[pg 116]┣, these two names referred to identical practices, licenses, tools, and organizations. Free Software and Open Source shared everything “material,” but differed vocally and at great length with respect to ideology. Stallman was denounced as a kook, a communist, an idealist, and a dogmatic holding back the successful adoption of Open Source by business; Raymond and users of “open source” were charged with selling out the ideals of freedom and autonomy, with the dilution of the principles and the promise of Free Software, as well as with being stooges of capitalist domination. Meanwhile, both groups proceeded to create objects—principally software—using tools that they agreed on, concepts of openness that they agreed on, licenses that they agreed on, and organizational schemes that they agreed on. Yet never was there fiercer debate about the definition of Free Software.
@@ -5098,7 +4783,6 @@
.ancestors: 1 290 0 0 291 343 0 0
.ancestors_collapsed: 1 290 291 343 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 184D3A8019437FA24F1D6159A3C01745D0BBBF74A8CF6A796CF49684893E1442
| On the one hand, the Free Software Foundation privileges the liberty and creativity of individual geeks, geeks engaged in practices of self-fashioning through the creation of software. It gives precedence to the liberal claim that without freedom of expression, individuals are robbed of their ability to self-determine. On the other hand, Open Source privileges organizations and processes, that is, geeks who are engaged in building businesses, nonprofit organizations, or governmental and public organizations of some form or another. It gives precedence to the pragmatist (or polymathic) view that getting things done requires flexible principles and negotiation, and that the public practice of building and running things should be separate from the private practice of ethical and political beliefs. Both narratives give geeks ways of making sense of a practice that they share in almost all of its details; both narratives give geeks a way to understand how Free Software or Open Source Software is different from the mainstream, proprietary software development that dominates their horizons. The narratives turn the haphazard participation and sharing that existed before 1998 into meaningful, goal-directed practices in the present, turning a class-in-itself into a class-for-itself, to use a terminology for the most part unwelcome among geeks.
@@ -5109,7 +4793,6 @@
.ancestors: 1 290 0 0 291 343 0 0
.ancestors_collapsed: 1 290 291 343 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6243E85CADCD166E16308006BC89274DAEF93859A0F6B0E9569C801275826496
| If two radically opposed ideologies can support people engaged in identical practices, then it seems obvious that the real space of politics and contestation is at the level of these practices and their emergence. These practices emerge as a response to a reorientation of power and knowledge, a reorientation somewhat impervious to ⑆,┨[pg 117]┣, conventional narratives of freedom and liberty, or to pragmatic claims of methodological necessity or market-driven innovation. Were these conventional narratives sufficient, the practices would be merely bureaucratic affairs, rather than the radical transformations they are.
@@ -5158,7 +4841,6 @@
.ancestors: 1 290 0 0 347 0 0 0
.ancestors_collapsed: 1 290 347 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 6C9376ED318713067DA3BCE5041B8A337582AC209F3DE7857A38CA8BB27E35D0
| Free Software would be nothing without shared source code. The idea is built into the very name “Open Source,” and it is a requirement of all Free Software licenses that source code be open to view, not “welded shut.” Perhaps ironically, source code is the most material of the five components of Free Software; it is both an expressive medium, like writing or speech, and a tool that performs concrete actions. It is a mnemonic that translates between the illegible electron-speed doings of our machines and our lingering ability to partially understand and control them as human agents. Many Free Software programmers and advocates suggest that “information wants to be free” and that sharing is a natural condition of human life, but I argue something contrary: sharing produces its own kind of moral and technical order, that is, “information makes people want freedom” and how they want it is related to how that information is created and circulated. In this chapter I explore the ⑆,┨[pg 119]┣, twisted and contingent history of how source code and its sharing have come to take the technical, legal, and pedagogical forms they have today, and how the norms of sharing have come to seem so natural to geeks.
@@ -5169,7 +4851,6 @@
.ancestors: 1 290 0 0 347 0 0 0
.ancestors_collapsed: 1 290 347 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 8205A7AB41A35D3772B1B90A5CCB70292DCB1CF729CBE6061F1F613A31F9F7E4
| Source code is essential to Free Software because of the historically specific ways in which it has come to be shared, “ported,” and “forked.” Nothing about the nature of source code requires that it be shared, either by corporations for whom secrecy and jealous protection are the norm or by academics and geeks for whom source code is usually only one expression, or implementation, of a greater idea worth sharing. However, in the last thirty years, norms of sharing source code—technical, legal, and pedagogical norms—have developed into a seemingly natural practice. They emerged through attempts to make software into a product, such as IBM’s 1968 “unbundling” of software and hardware, through attempts to define and control it legally through trade secret, copyright, and patent law, and through attempts to teach engineers how to understand and to create more software.
@@ -5180,7 +4861,6 @@
.ancestors: 1 290 0 0 347 0 0 0
.ancestors_collapsed: 1 290 347 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: E3267DF23486B204C7046D1D5026BB17E8CA1F98DD95B20A41E3B74C1CBAE704
.has: notes_reg
@@ -5203,7 +4883,6 @@
.ancestors: 1 290 0 0 347 0 0 0
.ancestors_collapsed: 1 290 347 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 6CE2A80BCAF08F928A9DC6EC1C8A270CDF1C7F5CFB6FE26CE5C9C6A702FCB76E
| The proliferation of UNIX was also a hybrid commercial-academic undertaking: it was neither a “public domain” object shared solely among academics, nor was it a conventional commercial product. Proliferation occurred through novel forms of academic sharing as well as through licensing schemes constrained by the peculiar status of AT&T, a regulated monopoly forbidden to enter the computer and software industry before 1984. Thus proliferation was not mere replication: it was not the sale of copies of UNIX, but a complex web of shared and re-shared chunks of source code, and the reimplementation of an elegant and simple conceptual scheme. As UNIX proliferated, it was stabilized in multiple ways: by academics seeking to keep it whole and self-compatible through contributions of source code; by lawyers at AT&T seeking to define boundaries that mapped onto laws, licenses, versions, and regulations; and by professors seeking to define it as an exemplar of the core concepts of operating-system theory. In all these ways, UNIX was a kind of primal recursive public, drawing together people for whom the meaning of their affiliation was the use, modification, and stabilization of UNIX.
@@ -5214,7 +4893,6 @@
.ancestors: 1 290 0 0 347 0 0 0
.ancestors_collapsed: 1 290 347 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: A9A0AEFE2FE2F505FE5DB16C5B022A3B9033ED9E5EC8C4CB2D50EE47BAD4AEA4
| The obverse of proliferation is differentiation: forking. UNIX is admired for its integrity as a conceptual thing and despised (or marveled at) for its truly tangled genealogical tree of ports and forks: new versions of UNIX, some based directly on the source code, some not, some licensed directly from AT&T, some sublicensed or completely independent.
@@ -5225,7 +4903,6 @@
.ancestors: 1 290 0 0 347 0 0 0
.ancestors_collapsed: 1 290 347 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 4B324A5B3E6E2A6BC07996D7388518B7F06D4D0568CB29DB383194A57B640321
.has: notes_reg
@@ -5265,7 +4942,6 @@
.ancestors: 1 290 0 0 347 354 0 0
.ancestors_collapsed: 1 290 347 354 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F85FE620C335CDA7199C0D985CA41266F7391A31FD89DC22BDED5A1A045BAE5E
.has: links notes_reg
@@ -5278,7 +4954,6 @@
.ancestors: 1 290 0 0 347 354 0 0
.ancestors_collapsed: 1 290 347 354 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FEE2201993901CEBE99C22918109817492A0566E12287F987F3A2FACD1159355
.has: notes_reg
@@ -5290,7 +4965,6 @@
.ancestors: 1 290 0 0 347 354 0 0
.ancestors_collapsed: 1 290 347 354 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 216E4AAD42B833C68698B3432A7E6C92DC1E9057765EC51C2639D4294E605FAE
| In the good old days of computers-the-size-of-rooms, the languages that humans used to program computers were mnemonics; they did not exist in the computer, but on a piece of paper or a specially designed code sheet. The code sheet gave humans who were not Alan Turing a way to keep track of, to share with other humans, and to think systematically about the invisible light-speed calculations of a complicated device. Such mnemonics needed to be “coded” on punch cards or tape; if engineers conferred, they conferred over sheets of paper that matched up with wires, relays, and switches—or, later, printouts of the various machine-specific codes that represented program and data.
@@ -5301,7 +4975,6 @@
.ancestors: 1 290 0 0 347 354 0 0
.ancestors_collapsed: 1 290 347 354 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E568BB20821453EADCE803AFD7A31DA0B1589DC1C511CFE39A1F8B5E1F9493CB
| With the introduction of programming languages, the distinction between a “source” language and a “target” language entered the practice: source languages were “translated” into the illegible target language of the machine. Such higher-level source languages were still mnemonics of sorts—they were certainly easier for humans to read and write, mostly on yellowing tablets of paper or special code sheets—but they were also structured enough that a source language could be input into a computer and translated into a target language which the designers of the hardware had specified. Inputting commands and cards and source code required a series of actions specific to each machine: a particular card reader or, later, a keypunch with a particular “editor” for entering the commands. Properly input and translated source code provided the machine with an assembled binary program that would, in fact, run (calculate, operate, control). It was a separation, an abstraction that allowed for a certain division of labor between the ingenious human authors and the fast and mechanical translating machines.
@@ -5312,7 +4985,6 @@
.ancestors: 1 290 0 0 347 354 0 0
.ancestors_collapsed: 1 290 347 354 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 77DB948BA76518B35DAA75B58091D8057F1001993B2C5DE8D27D600D05766E00
.has: notes_reg
@@ -5324,7 +4996,6 @@
.ancestors: 1 290 0 0 347 354 0 0
.ancestors_collapsed: 1 290 347 354 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 58CC33B86DE0F5642F3EEBF9A455AC079E4309DBDC6866217F0E5221214A4B9B
| The proliferation of different machines with different architectures drove a desire, among academics especially, for the standardization of programming languages, not so much because any single language was better than another, but because it seemed necessary to most engineers and computer users to share an emerging corpus of algorithms, solutions, and techniques of all kinds, necessary to avoid reinventing the wheel with each new machine. Algol, a streamlined language suited to algorithmic and algebraic representations, emerged in the early 1960s as a candidate for international standardization. Other languages competed on different strengths: FORTRAN and COBOL for general business use; LISP for symbolic processing. At the same time, the desire for a standard “higher-level” language necessitated a bestiary of translating programs: compilers, parsers, lexical analyzers, and other tools designed to transform the higher-level (human-readable) language into a machine-specific lower-level language, that is, machine language, assembly language, and ultimately the mystical zeroes and ones that course through our machines. The idea of a standard language and the necessity of devising specific tools for translation are the origin of the problem of portability: the ability to move software—not just good ideas, but actual programs, written in a standard language—from one machine to another.
@@ -5335,7 +5006,6 @@
.ancestors: 1 290 0 0 347 354 0 0
.ancestors_collapsed: 1 290 347 354 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4F66308D619C414E6DBB70001D6B0C136FD53A2909ABB0A519535C52E37D6FA7
| A standard source language was seen as a way to counteract the proliferation of different machines with subtly different architectures. Portable source code would allow programmers to imagine their programs as ships, stopping in at ports of call, docking on different platforms, but remaining essentially mobile and unchanged by these port-calls. Portable source code became the Esperanto of humans who had wrought their own Babel of tribal hardware machines.
@@ -5346,7 +5016,6 @@
.ancestors: 1 290 0 0 347 354 0 0
.ancestors_collapsed: 1 290 347 354 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 42E848596DA799D12881E3CBDE9C1F6ED0A1B28E05AF5C849183DE82D56D37AA
| Meanwhile, for the computer industry in the 1960s, portable source code was largely a moot point. Software and hardware were ⑆,┨[pg 124]┣, two sides of single, extremely expensive coin—no one, except engineers, cared what language the code was in, so long as it performed the task at hand for the customer. Each new machine needed to be different, faster, and, at first, bigger, and then smaller, than the last. The urge to differentiate machines from each other was not driven by academic experiment or aesthetic purity, but by a demand for marketability, competitive advantage, and the transformation of machines and software into products. Each machine had to do something really well, and it needed to be developed in secret, in order to beat out the designs and innovations of competitors. In the 1950s and 1960s the software was a core component of this marketable object; it was not something that in itself was differentiated or separately distributed—until IBM’s famous decision in 1968 to “unbundle” software and hardware.
@@ -5357,7 +5026,6 @@
.ancestors: 1 290 0 0 347 354 0 0
.ancestors_collapsed: 1 290 347 354 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 88610131540297DC78062E544DF561979182CDBA89A331F7D858B276A50DE5B0
.has: notes_reg
@@ -5369,7 +5037,6 @@
.ancestors: 1 290 0 0 347 354 0 0
.ancestors_collapsed: 1 290 347 354 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 05C6A0C592EB829F2547162A02A14B5E976199EF09EDFF76481BCDC811D058EE
.has: notes_reg
@@ -5392,7 +5059,6 @@
.ancestors: 1 290 0 0 347 354 0 0
.ancestors_collapsed: 1 290 347 354 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 62EFEBA4F44099158D18B47DB80328DE072A2C41B7A4606D98605A03B9E6BAD8
.has: notes_reg
@@ -5404,7 +5070,6 @@
.ancestors: 1 290 0 0 347 354 0 0
.ancestors_collapsed: 1 290 347 354 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DFA6EBEA2CF2B6BFC1D938E81BCE71CFAC3A45858B0F5A51B6F3DFD273D67C1E
| Portability was thus not simply a technical problem—the problem of running one program on multiple architectures—but also a kind of political-economic problem. The meaning of product was not always the same as the meaning of hardware or software, but was usually some combination of the two. At that early stage, the outlines of a contest over the meaning of portable or shareable source code are visible, both in the technical challenges of creating high-level languages and in the political-economic challenges that corporations faced in creating distinctive proprietary products.
@@ -5432,7 +5097,6 @@
.ancestors: 1 290 0 0 347 367 0 0
.ancestors_collapsed: 1 290 347 367 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3CB5451032CD8790DE8C8B7F1922DF5CABFCB1A7DB7B25B6968EB91BE1EF36C7
| Set against this backdrop, the invention, success, and proliferation of the UNIX operating system seems quite monstrous, an aberration of both academic and commercial practice that should have failed in both realms, instead of becoming the most widely used portable operating system in history and the very paradigm of an “operating system” in general. The story of UNIX demonstrates how portability became a reality and how the particular practice of sharing UNIX source code became a kind of de facto standard in its wake.
@@ -5443,7 +5107,6 @@
.ancestors: 1 290 0 0 347 367 0 0
.ancestors_collapsed: 1 290 347 367 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FA1342F894547BF282F628E7C8B2CFC6236B57220927F779676957C2EC2E83F3
.has: links notes_reg
@@ -5456,7 +5119,6 @@
.ancestors: 1 290 0 0 347 367 0 0
.ancestors_collapsed: 1 290 347 367 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D82E1E64442DAC3A4993AC47A5ADA2C7A4015EA8DD80D45D4611CB33BB6DD147
.has: notes_reg
@@ -5468,7 +5130,6 @@
.ancestors: 1 290 0 0 347 367 0 0
.ancestors_collapsed: 1 290 347 367 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6820C215EDBA9A4E78CFC1B0F665B74A72E5E89F5356713871B2C165DFFA94C9
.has: links notes_reg
@@ -5482,7 +5143,6 @@
.ancestors: 1 290 0 0 347 367 0 0
.ancestors_collapsed: 1 290 347 367 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0EC3F49F5D96BF5C2482EF38F910B099F10FB555688C11793A24F1E1CC40FE91
| Being on the border of business and academia meant that UNIX was, on the one hand, shielded from the demands of management and markets, allowing it to achieve the conceptual integrity that made it so appealing to designers and academics. On the other, it also meant that AT&T treated it as a potential product in the emerging software industry, which included new legal questions from a changing intellectual-property regime, novel forms of marketing and distribution, and new methods of developing, supporting, and distributing software.
@@ -5493,7 +5153,6 @@
.ancestors: 1 290 0 0 347 367 0 0
.ancestors_collapsed: 1 290 347 367 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CEB8D0C3C78BF8217D9B85B501044FF21F188CF30B06961F5A92F8B2ECFD23A7
| Despite this borderline status, UNIX was a phenomenal success. The reasons why UNIX was so popular are manifold; it was widely admired aesthetically, for its size, and for its clever design and tools. But the fact that it spread so widely and quickly is testament also to the existing community of eager computer scientists and engineers (and a few amateurs) onto which it was bootstrapped, users for whom a powerful, flexible, low-cost, modifiable, and fast operating system was a revelation of sorts. It was an obvious alternative to the complex, poorly documented, buggy operating systems that routinely shipped standard with the machines that universities and research organizations purchased. “It worked,” in other words.
@@ -5504,7 +5163,6 @@
.ancestors: 1 290 0 0 347 367 0 0
.ancestors_collapsed: 1 290 347 367 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 869998F2169963FFB59F4F9893C10621CB65DD91FAB1BA52E1CC043D031B6E2E
.has: notes_reg
@@ -5516,7 +5174,6 @@
.ancestors: 1 290 0 0 347 367 0 0
.ancestors_collapsed: 1 290 347 367 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3B41A52C30FC220F0AEAF29F07C29A231816F30487841B57C7F4EEFFFA72F6A2
.has: notes_reg
@@ -5545,7 +5202,6 @@
.ancestors: 1 290 0 0 347 376 0 0
.ancestors_collapsed: 1 290 347 376 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E027AB2BB3B673E829417706588B32405510C775F3EF72A23F7F151FC1D29C0B
.has: notes_reg
@@ -5557,7 +5213,6 @@
.ancestors: 1 290 0 0 347 376 0 0
.ancestors_collapsed: 1 290 347 376 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3ED124C7F391B5982A2144738272C23BE53C31BDBC8267E3F130A76BE868230B
| The manner in which the circulation of and contribution to UNIX occurred is not well documented, but it includes both technical and pedagogical forms of sharing. On the technical side, distribution took a number of forms, both in resistance to AT&T’s attempts to control it and facilitated by its unusually liberal licensing of the software. On the pedagogical side, UNIX quickly became a paradigmatic object for computer-science students precisely because it was a working operating system that included the source code and that was simple enough to explore in a semester or two.
@@ -5568,7 +5223,6 @@
.ancestors: 1 290 0 0 347 376 0 0
.ancestors_collapsed: 1 290 347 376 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BC65B12069FA8F4BF7F41A946C3C71B8BA5AEB49016DBB251518B9D706C07CEE
.has: notes_reg
@@ -5580,7 +5234,6 @@
.ancestors: 1 290 0 0 347 376 0 0
.ancestors_collapsed: 1 290 347 376 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FCE499335033E0E87EED0FAC233AA424575817FA5905B6149863B31D4B9F3821
| The need for a magnetic tape to “get around” marks the difference between the 1970s and the present: the distribution of software involved both the material transport of media and the digital copying of information. The desire to distribute bug fixes (the “diff ” tape) resonates with the future emergence of Free Software: the ⑆,┨[pg 130]┣, fact that others had fixed problems and contributed them back to Thompson and Ritchie produced an obligation to see that the fixes were shared as widely as possible, so that they in turn might be ported to new machines. Bell Labs, on the other hand, would have seen this through the lens of software development, requiring a new release, contract renegotiation, and a new license fee for a new version. Thompson’s notion of a “continuum,” rather than a series of releases also marks the difference between the idea of an evolving common set of objects stewarded by multiple people in far-flung locales and the idea of a shrink-wrapped “productized” software package that was gaining ascendance as an economic commodity at the same time. When Thompson says “the outside world,” he is referring not only to people outside of Bell Labs but to the way the world was seen from within Bell Labs by the lawyers and marketers who would create a new version. For the lawyers, the circulation of source code was a problem because it needed to be stabilized, not so much for commercial reasons as for legal ones—one license for one piece of software. Distributing updates, fixes, and especially new tools and additions written by people who were not employed by Bell Labs scrambled the legal clarity even while it strengthened the technical quality. Lou Katz makes this explicit.
@@ -5591,7 +5244,6 @@
.ancestors: 1 290 0 0 347 376 0 0
.ancestors_collapsed: 1 290 347 376 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F01E796803BE9137ECB3F1E1696E409B741DBD48CF7D35C0FCC7567EA0ED743D
.indent: 1 1
@@ -5604,7 +5256,6 @@
.ancestors: 1 290 0 0 347 376 0 0
.ancestors_collapsed: 1 290 347 376 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 14FC70929BC736E30C85CDE869A0ACB127323C44185396C416239BD54B40C0AD
| Distributing the fixes involved not just a power struggle between the engineers and management, but was in fact clearly motivated by the fact that, as Katz says, “a significant fraction of the fixes were done by non-Bell people.” This meant two things: first, that there was an obvious incentive to return the updated system to these ⑆,┨[pg 131]┣, people and to others; second, that it was not obvious that AT&T actually owned or could claim rights over these fixes—or, if they did, they needed to cover their legal tracks, which perhaps in part explains the stalling and threatening of the lawyers, who may have been buying time to make a “legal” version, with the proper permissions.
@@ -5615,7 +5266,6 @@
.ancestors: 1 290 0 0 347 376 0 0
.ancestors_collapsed: 1 290 347 376 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B9AEEEABE3E34082BAD5467C5948AA217EF834FBD1E69DD0F217F3455B3FDF8A
| The struggle should be seen not as one between the rebel forces of UNIX development and the evil empire of lawyers and managers, but as a struggle between two modes of stabilizing the object known as UNIX. For the lawyers, stability implied finding ways to make UNIX look like a product that would meet the existing legal framework and the peculiar demands of being a regulated monopoly unable to freely compete with other computer manufacturers; the ownership of bits and pieces, ideas and contributions had to be strictly accountable. For the programmers, stability came through redistributing the most up-to-date operating system and sharing all innovations with all users so that new innovations might also be portable. The lawyers saw urgency in making UNIX legally stable; the engineers saw urgency in making UNIX technically stable and compatible with itself, that is, to prevent the forking of UNIX, the death knell for portability. The tension between achieving legal stability of the object and promoting its technical portability and stability is one that has repeated throughout the life of UNIX and its derivatives—and that has ramifications in other areas as well.
@@ -5626,7 +5276,6 @@
.ancestors: 1 290 0 0 347 376 0 0
.ancestors_collapsed: 1 290 347 376 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 28F405BE78ABEDCC01AD869A542EA3514DEEAE91FEA12D6BC2A0C02EB5CA13F7
| The identity and boundaries of UNIX were thus intricately formed through its sharing and distribution. Sharing produced its own form of moral and technical order. Troubling questions emerged immediately: were the versions that had been fixed, extended, and expanded still UNIX, and hence still under the control of AT&T? Or were the differences great enough that something else (not-UNIX) was emerging? If a tape full of fixes, contributed by non-Bell employees, was circulated to people who had licensed UNIX, and those fixes changed the system, was it still UNIX? Was it still UNIX in a legal sense or in a technical sense or both? While these questions might seem relatively scholastic, the history of the development of UNIX suggests something far more interesting: just about every possible modification has been made, legally and technically, but the concept of UNIX has remained remarkably stable.
@@ -5665,7 +5314,6 @@
.ancestors: 1 290 0 0 347 385 0 0
.ancestors_collapsed: 1 290 347 385 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8B6C01CC72F85FA2E4E95370E611D1433FECC78CBACB11EDCEB375B0C26A80FE
| Technical portability accounts for only part of UNIX’s success. As a pedagogical resource, UNIX quickly became an indispensable tool for academics around the world. As it was installed and improved, it was taught and learned. The fact that UNIX spread first to university computer-science departments, and not to businesses, government, or nongovernmental organizations, meant that it also became part of the core pedagogical practice of a generation of programmers and computer scientists; over the course of the 1970s and 1980s, UNIX came to exemplify the very concept of an operating system, especially time-shared, multi-user operating systems. Two stories describe the porting of UNIX from machines to minds and illustrate the practice as it developed and how it intersected with the technical and legal attempts to stabilize UNIX as an object: the story of John Lions’s Commentary on Unix 6th Edition and the story of Andrew Tanenbaum’s Minix.
@@ -5676,7 +5324,6 @@
.ancestors: 1 290 0 0 347 385 0 0
.ancestors_collapsed: 1 290 347 385 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D46FDE6FAD69B38011B151B04C75E23A9620915AD76AD329569B9188E131C87B
| The development of a pedagogical UNIX lent a new stability to the concept of UNIX as opposed to its stability as a body of source code or as a legal entity. The porting of UNIX was so successful that even in cases where a ported version of UNIX shares none of the same source code as the original, it is still considered UNIX. The monstrous and promiscuous nature of UNIX is most clear in the stories of Lions and Tanenbaum, especially when contrasted with the commercial, legal, and technical integrity of something like Microsoft Windows, which generally exists in only a small number of forms (NT, ME, XP, 95, 98, etc.), possessing carefully controlled source code, immured in legal protection, and distributed only through sales and service packs to customers or personal-computer manufacturers. While Windows is much more widely used than UNIX, it is far from having become a paradigmatic pedagogical object; its integrity is predominantly legal, not technical or pedagogical. Or, in pedagogical terms, Windows is to fish as UNIX is to fishing lessons.
@@ -5687,7 +5334,6 @@
.ancestors: 1 290 0 0 347 385 0 0
.ancestors_collapsed: 1 290 347 385 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CEEC3932CEB1F6B4E452924C2CC6778A5DA581782F6FA546E74CF41AED3FECF4
.has: notes_reg
@@ -5699,7 +5345,6 @@
.ancestors: 1 290 0 0 347 385 0 0
.ancestors_collapsed: 1 290 347 385 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BD937440D8DE402D10D65F2FB9CAAE8928AB3B732D852A573B3C7FA1DB74406C
| Lions’s commentary was a unique document in the world of computer science, containing a kind of key to learning about a central component of the computer, one that very few people would have had access to in the 1970s. It shows how UNIX was ported not only to machines (which were scarce) but also to the minds of young researchers and student programmers (which were plentiful). Several generations of both academic computer scientists and students who went on to work for computer or software corporations were trained on photocopies of UNIX source code, with a whiff of toner and illicit circulation: a distributed operating system in the textual sense.
@@ -5710,7 +5355,6 @@
.ancestors: 1 290 0 0 347 385 0 0
.ancestors_collapsed: 1 290 347 385 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2575606B22A455EA65716874C115053E1D6C6DD35EFC0EBC6FD1A07BE5E79E3D
.has: notes_reg
@@ -5722,7 +5366,6 @@
.ancestors: 1 290 0 0 347 385 0 0
.ancestors_collapsed: 1 290 347 385 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5EB7ECCBB6FA177AA17B1D84653FA25F7B8C1F93CEAFF6DC32BCBC59C9543B34
| Thus, these generations of computer-science students and academics shared a secret—a trade secret become open secret. Every student who learned the essentials of the UNIX operating system from a photocopy of Lions’s commentary, also learned about AT&T’s attempt to control its legal distribution on the front cover of their textbook. The parallel development of photocopying has a nice resonance here; together with home cassette taping of music and the introduction of the video-cassette recorder, photocopying helped drive the changes to copyright law adopted in 1976.
@@ -5733,7 +5376,6 @@
.ancestors: 1 290 0 0 347 385 0 0
.ancestors_collapsed: 1 290 347 385 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AB26598F5F6A9EE82F869496F6FD1D836D87169AFDBA42F316F01E8F95B7375B
| Thirty years later, and long after the source code in it had been completely replaced, Lions’s Commentary is still widely admired by geeks. Even though Free Software has come full circle in providing students with an actual operating system that can be legally studied, taught, copied, and implemented, the kind of “literary criticism” that Lions’s work represents is still extremely rare; even reading obsolete code with clear commentary is one of the few ways to truly understand the design elements and clever implementations that made the UNIX operating system so different from its predecessors and even many of its successors, few, if any of which have been so successfully ported to the minds of so many students.
@@ -5744,7 +5386,6 @@
.ancestors: 1 290 0 0 347 385 0 0
.ancestors_collapsed: 1 290 347 385 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DB7B0D9EC047DC0C89023A0FFBFAD25883312D8865AD56BA8EE4460FE6BF7807
| Lions’s Commentary contributed to the creation of a worldwide community of people whose connection to each other was formed by a body of source code, both in its implemented form and in its textual, photocopied form. This nascent recursive public not only understood itself as belonging to a technical elite which was constituted by its creation, understanding, and promotion of a particular ⑆,┨[pg 135]┣, technical tool, but also recognized itself as “breaking the law,” a community constituted in opposition to forms of power that governed the circulation, distribution, modification, and creation of the very tools they were learning to make as part of their vocation. The material connection shared around the world by UNIX-loving geeks to their source code is not a mere technical experience, but a social and legal one as well.
@@ -5755,7 +5396,6 @@
.ancestors: 1 290 0 0 347 385 0 0
.ancestors_collapsed: 1 290 347 385 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5FEF37E70E76F8DB6F2128A11FF6844B4B18D7A108EBC6F327CA946C32BFCF0E
.has: notes_reg
@@ -5767,7 +5407,6 @@
.ancestors: 1 290 0 0 347 385 0 0
.ancestors_collapsed: 1 290 347 385 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EA504D4F09D76C4C3D153BCE6E26191B266A0AC19B650ACE5CB5CBFA5F4C8F2B
| Minix became as widely used in the 1980s as a teaching tool as Lions’s source code had been in the 1970s. According to Tanenbaum, the Usenet group comp.os.minix had reached 40,000 members by the late 1980s, and he was receiving constant suggestions for changes and improvements to the operating system. His own commitment to teaching meant that he incorporated few of these suggestions, an effort to keep the system simple enough to be printed in a textbook and understood by undergraduates. Minix ⑆,┨[pg 136]┣, was freely available as source code, and it was a fully functioning operating system, even a potential alternative to UNIX that would run on a personal computer. Here was a clear example of the conceptual integrity of UNIX being communicated to another generation of computer-science students: Tanenbaum’s textbook is not called “UNIX Operating Systems”—it is called Operating Systems. The clear implication is that UNIX represented the clearest example of the principles that should guide the creation of any operating system: it was, for all intents and purposes, state of the art even twenty years after it was first conceived.
@@ -5778,7 +5417,6 @@
.ancestors: 1 290 0 0 347 385 0 0
.ancestors_collapsed: 1 290 347 385 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5BCB46B299DEEF08745AC13D3128E559A748CDF950517E7C389D413233292F8B
| Minix was not commercial software, but nor was it Free Software. It was copyrighted and controlled by Tanenbaum’s publisher, Prentice Hall. Because it used no AT&T source code, Minix was also legally independent, a legal object of its own. The fact that it was intended to be legally distinct from, yet conceptually true to UNIX is a clear indication of the kinds of tensions that govern the creation and sharing of source code. The ironic apotheosis of Minix as the pedagogical gold standard for studying UNIX came in 1991-92, when a young Linus Torvalds created a “fork” of Minix, also rewritten from scratch, that would go on to become the paradigmatic piece of Free Software: Linux. Tanenbaum’s purpose for Minix was that it remain a pedagogically useful operating system—small, concise, and illustrative—whereas Torvalds wanted to extend and expand his version of Minix to take full advantage of the kinds of hardware being produced in the 1990s. Both, however, were committed to source-code visibility and sharing as the swiftest route to complete comprehension of operating-systems principles.
@@ -5806,7 +5444,6 @@
.ancestors: 1 290 0 0 347 397 0 0
.ancestors_collapsed: 1 290 347 397 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BD7A80DEE879D886ED8117734FEE25D9E257CB149C1910B637AD54E173295D2F
| Tanenbaum’s need to produce Minix was driven by a desire to share the source code of UNIX with students, a desire AT&T was manifestly uncomfortable with and which threatened the trade-secret status of their property. The fact that Minix might be called a fork of UNIX is a key aspect of the political economy of operating systems and social systems. Forking generally refers to the creation of new, modified source code from an original base of source code, resulting in two distinct programs with the same parent. Whereas the modification of an engine results only in a modified engine, the ⑆,┨[pg 137]┣, modification of source code implies differentiation and reproduction, because of the ease with which it can be copied.
@@ -5817,7 +5454,6 @@
.ancestors: 1 290 0 0 347 397 0 0
.ancestors_collapsed: 1 290 347 397 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B4C8CF226CFF876CBAF3923958BF61590E11E37780920034F4C381AEADCF5268
| How could Minix—a complete rewrite—still be considered the same object? Considered solely from the perspective of trade-secret law, the two objects were distinct, though from the perspective of copyright there was perhaps a case for infringement, although AT&T did not rely on copyright as much as on trade secret. From a technical perspective, the functions and processes that the software accomplishes are the same, but the means by which they are coded to do so are different. And from a pedagogical standpoint, the two are identical—they exemplify certain core features of an operating system (file-system structure, memory paging, process management)—all the rest is optimization, or bells and whistles. Understanding the nature of forking requires also that UNIX be understood from a social perspective, that is, from the perspective of an operating system created and modified by user-developers around the world according to particular and partial demands. It forms the basis for the emergence of a robust recursive public.
@@ -5828,7 +5464,6 @@
.ancestors: 1 290 0 0 347 397 0 0
.ancestors_collapsed: 1 290 347 397 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 16E95BEFDB08A8FD23FC2FAD901CCD31A21EC831E7D32E63C9EC20DE19B5647A
| One of the more important instances of the forking of UNIX’s perambulatory source code and the developing community of UNIX co-developers is the story of the Berkeley Software Distribution and its incorporation of the TCP/IP protocols. In 1975 Ken Thompson took a sabbatical in his hometown of Berkeley, California, where he helped members of the computer-science department with their installations of UNIX, arriving with V6 and the “50 bug fixes” diff tape. Ken had begun work on a compiler for the Pascal programming language that would run on UNIX, and this work was taken up by two young graduate students: Bill Joy and Chuck Hartley. (Joy would later co-found Sun Microsystems, one of the most successful UNIX-based workstation companies in the history of the industry.)
@@ -5839,7 +5474,6 @@
.ancestors: 1 290 0 0 347 397 0 0
.ancestors_collapsed: 1 290 347 397 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 807B78A076AD3BC518587D0A215E2BF88CF79F9F72C96DB802A78EC2B2737DE7
.has: notes_reg
@@ -5851,7 +5485,6 @@
.ancestors: 1 290 0 0 347 397 0 0
.ancestors_collapsed: 1 290 347 397 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EF06F2787DF8A26AA5838C0E1B258F187FF6457D01383E0E1EAB3C0C1EDF1DD0
.has: links notes_reg
@@ -5864,7 +5497,6 @@
.ancestors: 1 290 0 0 347 397 0 0
.ancestors_collapsed: 1 290 347 397 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2A7FD0A67D04E3335F27131E3B38CF0AEB28762E76A3088654B8A711FE177128
.has: notes_reg
@@ -5876,7 +5508,6 @@
.ancestors: 1 290 0 0 347 397 0 0
.ancestors_collapsed: 1 290 347 397 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 67FCF4778CAE9188C6B4607307C822468FC311E5002E10DD7479AF6C8C098DDD
| To achieve the benefits of TCP/IP, the resources needed to be implemented in all of the different operating systems that were connected to the Arpanet—whatever operating system and machine happened to be in use at each of the nodes. However, by 1977, the original machines used on the network were outdated and increasingly difficult to maintain and, according to Kirk McKusick, the greatest expense was that of porting the old protocol software to new machines. Hence, IPTO decided to pursue in part a strategy of achieving coordination at the operating-system level, and they chose UNIX as one of the core platforms on which to standardize. In short, they had seen the light of portability. In about 1978 IPTO granted a contract to Bolt, Beranek, and Newman (BBN), one of the original Arpanet contractors, to integrate the TCP/IP protocols into the UNIX operating system.
@@ -5887,7 +5518,6 @@
.ancestors: 1 290 0 0 347 397 0 0
.ancestors_collapsed: 1 290 347 397 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E9C7C35125344A49FEFDD1152A61E06ACA8A561F94186CD6F898776C3FDB5021
.has: notes_reg
@@ -5899,7 +5529,6 @@
.ancestors: 1 290 0 0 347 397 0 0
.ancestors_collapsed: 1 290 347 397 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 01BA5FE85CC335049A86BFADA3BA66621779B0312E6668A57FB47E81537133C4
.has: links notes_reg
@@ -5911,7 +5540,6 @@
.ancestors: 1 290 0 0 347 397 0 0
.ancestors_collapsed: 1 290 347 397 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4B62A08B2524488F36E528C2CA95D7774FA4A957B5FEF6B4E0D9315EFCD4BEC3
| Forking, however, does not imply permanent divergence, and the continual improvement, porting, and sharing of software can have odd consequences when forks occur. On the one hand, there are particular pieces of source code: they must be identifiable and exact, and prepended with a copyright notice, as was the case of the Berkeley code, which was famously and vigorously policed by the University of California regents, who allowed for a very liberal distribution of BSD code on the condition that the copyright notice was retained. On the other hand, there are particular named collections of code that work together (e.g., UNIX™, or DARPA-approved UNIX, or later, Certified Open Source [sm]) and are often identified by a trademark symbol intended, legally speaking, to differentiate products, not to assert ownership of particular instances of a product.
@@ -5922,7 +5550,6 @@
.ancestors: 1 290 0 0 347 397 0 0
.ancestors_collapsed: 1 290 347 397 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6AF2068696EA3CC859B4B71D05DB9E359240EEFFF600C4A6964DB360DD706323
.has: links notes_reg
@@ -5934,7 +5561,6 @@
.ancestors: 1 290 0 0 347 397 0 0
.ancestors_collapsed: 1 290 347 397 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1561154CC9B24CDC501075134D4B0DC3FF53C82B5C135820F33A2A4EA95AC57A
| The BSD fork of UNIX (and the subfork of TCP/IP) was only one of many to come. By the early 1980s, a proliferation of UNIX forks had emerged and would be followed shortly by a very robust commercialization. At the same time, the circulation of source code started to slow, as corporations began to compete by adding features and creating hardware specifically designed to run UNIX (such as the Sun Sparc workstation and the Solaris operating system, the result of Joy’s commercialization of BSD in the 1980s). The question of how to make all of these versions work together eventually became the subject of the open-systems discussions that would dominate the workstation and networking sectors of the computer ⑆,┨[pg 141]┣, market from the early 1980s to 1993, when the dual success of Windows NT and the arrival of the Internet into public consciousness changed the fortunes of the UNIX industry.
@@ -5945,7 +5571,6 @@
.ancestors: 1 290 0 0 347 397 0 0
.ancestors_collapsed: 1 290 347 397 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0D7ED5EEA68B5E4986B2ACDE7D9D0FDC3FDFC0408FBFCBBF0EC7EC460C12D1A6
.has: notes_reg
@@ -5974,7 +5599,6 @@
.ancestors: 1 290 0 0 347 411 0 0
.ancestors_collapsed: 1 290 347 411 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8EA217D959678EA2D417F805C125D45CBB8E19C12F620792AA495DE9A818DFB8
| The UNIX operating system is not just a technical achievement; it is the creation of a set of norms for sharing source code in an unusual environment: quasi-commercial, quasi-academic, networked, and planetwide. Sharing UNIX source code has taken three basic forms: porting source code (transferring it from one machine to another); teaching source code, or “porting” it to students in a pedagogical setting where the use of an actual working operating system vastly facilitates the teaching of theory and concepts; and forking source code (modifying the existing source code to do something new or different). This play of proliferation and differentiation is essential to the remarkably stable identity of UNIX, but that identity exists in multiple forms: technical (as a functioning, self-compatible operating system), legal (as a license-circumscribed version subject to intellectual property and commercial law), and pedagogical (as a conceptual exemplar, the paradigm of an operating system). Source code shared in this manner is essentially unlike any other kind of ⑆,┨[pg 142]┣, source code in the world of computers, whether academic or commercial. It raises troubling questions about standardization, about control and audit, and about legitimacy that haunts not only UNIX but the Internet and its various “open” protocols as well.
@@ -5985,7 +5609,6 @@
.ancestors: 1 290 0 0 347 411 0 0
.ancestors_collapsed: 1 290 347 411 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BB8921AAD61C6D675D458795FCB7BD009BD8F24BE2E5D643A96072A6A5CD6EDE
| Sharing source code in Free Software looks the way it does today because of UNIX. But UNIX looks the way it does not because of the inventive genius of Thompson and Ritchie, or the marketing and management brilliance of AT&T, but because sharing produces its own kind of order: operating systems and social systems. The fact that geeks are wont to speak of “the UNIX philosophy” means that UNIX is not just an operating system but a way of organizing the complex relations of life and work through technical means; a way of charting and breaching the boundaries between the academic, the aesthetic, and the commercial; a way of implementing ideas of a moral and technical order. What’s more, as source code comes to include more and more of the activities of everyday communication and creation—as it comes to replace writing and supplement thinking—the genealogy of its portability and the history of its forking will illuminate the kinds of order emerging in practices and technologies far removed from operating systems—but tied intimately to the UNIX philosophy.
@@ -6036,7 +5659,6 @@
.ancestors: 1 290 0 0 414 0 0 0
.ancestors_collapsed: 1 290 414 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 6351074DCDDEFD125AEC91CDBB93F1E899EA1EB16B0BF1ED7C6A197E667FA97A
.indent: 1 1
@@ -6049,7 +5671,6 @@
.ancestors: 1 290 0 0 414 0 0 0
.ancestors_collapsed: 1 290 414 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 11EB3FE4BB1EFEA71F9C0BC8358D8475D208C15EE56BA7E63BD0790829C0B8A8
| Openness is an unruly concept. While free tends toward ambiguity (free as in speech, or free as in beer?), open tends toward obfuscation. Everyone claims to be open, everyone has something to share, everyone agrees that being open is the obvious thing to do—after all, openness is the other half of “open source”—but for all its obviousness, being “open” is perhaps the most complex component of Free Software. It is never quite clear whether being open is a means or an end. Worse, the opposite of open in this case (specifically, “open systems”) is not closed, but “proprietary”—signaling the complicated imbrication of the technical, the legal, and the commercial.
@@ -6060,7 +5681,6 @@
.ancestors: 1 290 0 0 414 0 0 0
.ancestors_collapsed: 1 290 414 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: EFE22B898F1D2CB6D2AD84EBB0BA453749810114196F7C0DE274E414BBAF62B7
.has: notes_reg
@@ -6072,7 +5692,6 @@
.ancestors: 1 290 0 0 414 0 0 0
.ancestors_collapsed: 1 290 414 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: DFB2C700BB9EA89F07BC5730F97C24FE0CFC46F8421F2F69AF6FB1E33F16A8B0
| The open-systems story is also a story of the blind spot of open systems—in that blind spot is intellectual property. The story reveals a tension between incompatible moral-technical orders: on the one hand, the promise of multiple manufacturers and corporations creating interoperable components and selling them in an open, heterogeneous market; on the other, an intellectual-property system that encouraged jealous guarding and secrecy, and granted monopoly status to source code, designs, and ideas in order to differentiate products and promote competition. The tension proved irresolvable: without shared source code, for instance, interoperable operating systems are impossible. Without interoperable operating systems, internetworking and portable applications are impossible. Without portable applications that can run on any system, open markets are impossible. Without open markets, monopoly power reigns.
@@ -6083,7 +5702,6 @@
.ancestors: 1 290 0 0 414 0 0 0
.ancestors_collapsed: 1 290 414 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 828E7B3BA16ECAB3B27A3CD48483BA2837C5627366D347237CFCFAC79CE52415
| Standardization was at the heart of the contest, but by whom and by what means was never resolved. The dream of open systems, pursued in an entirely unregulated industry, resulted in a complicated experiment in novel forms of standardization and cooperation. The creation of a “standard” operating system based on UNIX is the story of a failure, a kind of “figuring out” gone haywire, which resulted in huge consortia of computer manufacturers attempting to work together and compete with each other at the same time. Meanwhile, the successful creation of a “standard” networking protocol—known as the Open Systems Interconnection Reference Model (OSI)—is a story of failure that hides a larger success; OSI was eclipsed in the same period by the rapid and ad hoc adoption of the Transmission Control Protocol/Internet Protocol (TCP/IP), which used a radically different standardization process and which succeeded for a number of surprising reasons, allowing the Internet ⑆,┨[pg 145]┣, to take the form it did in the 1990s and ultimately exemplifying the moral-technical imaginary of a recursive public—and one at the heart of the practices of Free Software.
@@ -6094,7 +5712,6 @@
.ancestors: 1 290 0 0 414 0 0 0
.ancestors_collapsed: 1 290 414 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: BA6F0DE4DE6D510A3E5FAC44378D247B64CCEAA3B1319C489A1BBC4784D5F34E
| The conceiving of openness, which is the central plot of these two stories, has become an essential component of the contemporary practice and power of Free Software. These early battles created a kind of widespread readiness for Free Software in the 1990s, a recognition of Free Software as a removal of open systems’ blind spot, as much as an exploitation of its power. The geek ideal of openness and a moral-technical order (the one that made Napster so significant an event) was forged in the era of open systems; without this concrete historical conception of how to maintain openness in technical and moral terms, the recursive public of geeks would be just another hierarchical closed organization—a corporation manqué—and not an independent public serving as a check on the kinds of destructive power that dominated the open-systems contest.
@@ -6122,7 +5739,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9455DA5142B3EE7EF84D4D82DDCC04C992F29C1D385C84691D2FE17B8CC8696A
| Big iron, silos, legacy systems, turnkey systems, dinosaurs, mainframes: with the benefit of hindsight, the computer industry of the 1960s to the 1980s appears to be backward and closed, to have literally painted itself into a corner, as an early Intel advertisement suggests (figure 3). Contemporary observers who show disgust and impatience with the form that computers took in this era are without fail supporters of open systems and opponents of proprietary systems that “lock in” customers to specific vendors and create artificial demands for support, integration, and management of resources. Open systems (were it allowed to flourish) would solve all these problems.
@@ -6133,7 +5749,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CBA44844335BF22FBEC972E2EA9C9402F14CEE2EBFAF03D6FFA9703F591D3BFA
| Given the promise of a “general-purpose computer,” it should seem ironic at best that open systems needed to be created. But the general-purpose computer never came into being. We do not live in the world of The Computer, but in a world of computers: myriad, incompatible, specific machines. The design of specialized machines (or “architectures”) was, and still is, key to a competitive industry in computers. It required CPUs and components and associated software that could be clearly qualified and marketed ⑆,┨[pg 146]┣, ⑆,┨[pg 147]┣, as distinct products: the DEC PDP-11 or the IBM 360 or the CDC 6600. On the Fordist model of automobile production, the computer industry’s mission was to render desired functions (scientific calculation, bookkeeping, reservations management) in a large box with a button on it (or a very large number of buttons on increasingly smaller boxes). Despite the theoretical possibility, such computers were not designed to do anything, but, rather, to do specific kinds of calculations exceedingly well. They were objects customized to particular markets.
@@ -6144,7 +5759,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FD4A2EC32299325AC221C4151AFADC6A7C3162E35D3EEC4287D8BD60849EDED6
.image: 2bits_05_03-100.png sha256:71326E711C51CA82B9711DCC81FD0CF43664BDEFB7C56BE69B8D148D28BC7632 bytes:338870 px:619x972
@@ -6168,7 +5782,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E0DC4E3DF97B47D8B3FEC7E1DD161152FFD424FF716153A87A75BD46007F3DCA
| The marketing strategy was therefore extremely stable from about 1955 to about 1980: identify customers with computing needs, build a computer to serve them, provide them with all of the equipment, software, support, or peripherals they need to do the job—and charge a large amount. Organizationally speaking, it was an industry dominated by “IBM and the seven dwarfs”: Hewlett-Packard, Honeywell, Control Data, General Electric, NCR, RCA, Univac, and Burroughs, with a few upstarts like DEC in the wings.
@@ -6179,7 +5792,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5C88C52C8C1338D9C9DF7E018DC02480DB30A5478B9BEF141F1B9390A578EBCD
.has: notes_reg
@@ -6191,7 +5803,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6CD57CA13A4B2DDBDCCBC11CE2F35E082E9432A5BD285D389C604DC19A0895B2
| Open systems emerged in the 1980s as the name of the solution to this problem: an approach to the design of systems that, if all participants were to adopt it, would lead to widely interoperable, integrated machines that could send, store, process, and receive the user’s information. In marketing and public-relations terms, it would provide “seamless integration.”
@@ -6202,7 +5813,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AF0A4AD8F7C2B433CF2AD162436841358391A125B6959B7C14D699ABB5E8160B
| In theory, open systems was simply a question of standards adoption. For instance, if all the manufacturers of UNIX systems could ⑆,┨[pg 148]┣, be convinced to adopt the same basic standard for the operating system, then seamless integration would naturally follow as all the various applications could be written once to run on any variant UNIX system, regardless of which company made it. In reality, such a standard was far from obvious, difficult to create, and even more difficult to enforce. As such, the meaning of open systems was “hopelessly plural,” and the term came to mean an incredibly diverse array of things.
@@ -6213,7 +5823,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 226FAE3AE53FE4A87543545FD19BEECD63EC42EAF621CB5A89BA29EE0A16B38D
| “Openness” is precisely the kind of concept that wavers between end and means. Is openness good in itself, or is openness a means to achieve something else—and if so what? Who wants to achieve openness, and for what purpose? Is openness a goal? Or is it a means by which a different goal—say, “interoperability” or “integration”—is achieved? Whose goals are these, and who sets them? Are the goals of corporations different from or at odds with the goals of university researchers or government officials? Are there large central visions to which the activities of all are ultimately subordinate?
@@ -6224,7 +5833,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 459FC2D5A1F9AE79596AA669558CE0061D91D2A1BA5E9C08761EA280140A26C0
| Between 1980 and 1993, no person or company or computer industry consortium explicitly set openness as the goal that organizations, corporations, or programmers should aim at, but, by the same token, hardly anyone dissented from the demand for openness. As such, it appears clearly as a kind of cultural imperative, reflecting a longstanding social imaginary with roots in liberal democratic notions, versions of a free market and ideals of the free exchange of knowledge, but confronting changed technical conditions that bring the moral ideas of order into relief, and into question.
@@ -6235,7 +5843,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F2F74AB971CE3A7673D5EAAC9D68BF7498074D529F4A9D15521B167F33F12C86
.has: notes_reg
@@ -6247,7 +5854,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6885EAEC8CFF1D536C2E191C1D450ED2B39E6970EB522812CE3C3F60156DD35C
.has: notes_reg
@@ -6259,7 +5865,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 85CF8D1F6D3436B50C7FAAC1BAF39E2600560DB74913BFA49251D4537A768F94
.has: links notes_reg
@@ -6283,7 +5888,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CF857D10BAD905F86F0B97F4A3AB07A9F3BD61D7172571F8DFA4171F24EBF942
.has: notes_reg
@@ -6295,7 +5899,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9D734AE1F1C5323994D867475B43371C4993B8D166055075C84B217CE69777E0
.has: notes_reg
@@ -6307,7 +5910,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E6085F227975165CAFB8701ADF16147C2CEBAD3BFEF1C1D8A201EA61E7CF562C
.has: notes_reg
@@ -6319,7 +5921,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 07B596065C85DA9E78D2E30A0DC5CD0F9568088939DCC56C4BE98F505EDCFD4C
| Openness here is not equated with freedom to copy and modify, but with the freedom to buy access to any aspect of a system without signing a contract, a nondisclosure agreement, or any other legal document besides a check. The ground rules of competition are unchallenged: the existing system of intellectual property—a system that was expanded and strengthened in this period—was a sine qua non of competition.
@@ -6330,7 +5931,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7E5E6E5FAECD8E905555FF059C4574A302D614D563EA08CEE62859FC4EDE05CA
| Openness understood in this manner means an open market in which it is possible to buy standardized things which are neither obscure nor secret, but can be examined and judged—a “commodity” market, where products have functions, where quality is comparable and forms the basis for vigorous competition. What this notion implies is freedom from monopoly control by corporations over products, a freedom that is nearly impossible to maintain when the entire industry is structured around the monopoly control of intellectual property through trade secret, patent, or copyright. The blind spot hides the contradiction between an industry imagined on the model of manufacturing distinct and tangible products, and the reality of an industry that wavers somewhere between service and product, dealing in intangible intellectual property whose boundaries and identity are in fact defined by how they are exchanged, circulated, and shared, as in the case of the proliferation and differentiation of the UNIX operating system.
@@ -6341,7 +5941,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6CA13ECD1F8EE45A79A2DAAB5EECD1B9E12D0897798CD2B1997558C411916069
| There was no disagreement about the necessity of intellectual property in the computer industry of the 1980s, and there was no perceived contradiction in the demands for openness. Indeed, openness could only make sense if it were built on top of a stable system of intellectual property that allowed competitors to maintain clear definitions of the boundaries of their products. But the creation of interoperable components seemed to demand a relaxation of the secrecy and guardedness necessary to “protect” intellectual property. Indeed, for some observers, the problem of openness created the opportunity for the worst kinds of cynical logic, as in this example from Regis McKenna’s Who’s Afraid of Big Blue?
@@ -6352,7 +5951,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DAC40A562E38B46F9AB503D2A7D76FF87A4B6168E7F30E832129810EE215DF1F
.indent: 1 1
@@ -6365,7 +5963,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E03B8A46430F50B75C7578D97F1571E4C17C4C8733348877F1843B4C2972DA26
.has: links notes_reg
@@ -6377,7 +5974,6 @@
.ancestors: 1 290 0 0 414 421 0 0
.ancestors_collapsed: 1 290 414 421 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4D6E8E2E3F654A6B6E01884B08FB59A5B1C13928F9B1B88D187EB5A4D47D82EB
| From the perspective of intellectual property, ideas, designs, and source code are everything—if a company were to release the source code, and allow other vendors to build on it, then what exactly would they be left to sell? Open systems did not mean anything like free, open-source, or public-domain computing. But the fact that competition required some form of collaboration was obvious as well: standard software and network systems were needed; standard markets were needed; standard norms of innovation within the constraints of standards were needed. In short, the challenge was not just the creation of competitive products but the creation of a standard infrastructure, dealing with the technical questions of availability, modifiability, and reusability of components, and the moral questions of the proper organization of competition and collaboration across diverse domains: engineers, academics, the computer industry, and the industries it computerized. What follows is the story of how UNIX entered the open-systems fray, a story in which the tension between the conceiving of openness and the demands of intellectual property is revealed.
@@ -6416,7 +6012,6 @@
.ancestors: 1 290 0 0 414 443 0 0
.ancestors_collapsed: 1 290 414 443 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8729CF118FD965136E483DA959BB7C9ED91F8C46C9C8D2A58F447D8A7D95627A
| In 1980 UNIX was by all accounts the most obvious choice for a standard operating system for a reason that seemed simple at the outset: it ran on more than one kind of hardware. It had been installed on DEC machines and IBM machines and Intel processors and Motorola processors—a fact exciting to many professional programmers, university computer scientists, and system administrators, many of whom also considered UNIX to be the best designed of the available operating systems.
@@ -6427,7 +6022,6 @@
.ancestors: 1 290 0 0 414 443 0 0
.ancestors_collapsed: 1 290 414 443 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 24860043BFEA87A2A027BE646EEF85FA86DDE0F85A72061831F7D8F36CE4C713
.has: notes_reg
@@ -6439,7 +6033,6 @@
.ancestors: 1 290 0 0 414 443 0 0
.ancestors_collapsed: 1 290 414 443 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 375B299C2B2ABA92AB9F4EE30CD8BF7DC29640F5344FE254C183467E18E1C991
.has: notes_reg
@@ -6451,7 +6044,6 @@
.ancestors: 1 290 0 0 414 443 0 0
.ancestors_collapsed: 1 290 414 443 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C41389596ADA8EAE34265D282D4ECD257D33371A5DBD44216E7E78E7E7EE2301
.has: notes_reg
@@ -6463,7 +6055,6 @@
.ancestors: 1 290 0 0 414 443 0 0
.ancestors_collapsed: 1 290 414 443 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DC7A0986D4922BA57828CC6454BF72FCCE10D437427342517083ACBC97577DC8
.has: links notes_reg
@@ -6475,7 +6066,6 @@
.ancestors: 1 290 0 0 414 443 0 0
.ancestors_collapsed: 1 290 414 443 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 28C5BC0AD45BF902A7E1C1DE85A4E3B98C3542B96D5B0EC5F7CEB55FC6D06155
.has: notes_reg
@@ -6487,7 +6077,6 @@
.ancestors: 1 290 0 0 414 443 0 0
.ancestors_collapsed: 1 290 414 443 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7F15A67ECE2714B0F436EF498C3CC1B89B94D4F9B184A67991C75CC5AFF526A3
| The dawning realization that the proliferation of systems was not only spreading UNIX around the world but also spreading it thin and breaking it apart led to a series of increasingly startling and high-profile attempts to “standardize” UNIX. Given that the three major branches (BSD, which would become the industry darling as Sun’s Solaris operating system; Microsoft, and later SCO Xenix; and AT&T’s System V) all emerged from the same AT&T and Berkeley work done largely by Thompson, Ritchie, and Joy, one would think that standardization would be a snap. It was anything but.
@@ -6515,7 +6104,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D0BC4ABA0F05EE2D53B3A50B6E5F34CFAC60C288BD2AEB3D8DB7471E8AA1CA6E
| Figuring out the moral and technical order of open systems went haywire around 1986-88, when there were no fewer than four competing international standards, represented by huge consortia of computer manufacturers (many of whom belonged to multiple consortia): POSIX, the X/Open consortium, the Open Software Foundation, and UNIX International. The blind spot of open systems had much to do with this crazy outcome: academics, industry, and government could not find ways to agree on standardization. One goal of standardization was to afford customers choice; another was to allow competition unconstrained by “artificial” means. A standard body of source code was impossible; a standard “interface definition” was open to too much interpretation; government and academic standards were too complex and expensive; no particular corporation’s standard could be trusted (because they could not be trusted to reveal it in advance of their own innovations); and worst of all, customers kept buying, and vendors kept shipping, and the world was increasingly filled with diversity, not standardization.
@@ -6526,7 +6114,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8624EB782E538932B1113E92E79E6A8365F844EDC3CF8A363391E3A47CFC8651
| UNIX proliferated quickly because of porting, leading to multiple instances of an operating system with substantially similar source code shared by academics and licensed by AT&T. But it differentiated ⑆,┨[pg 156]┣, just as quickly because of forking, as particular features were added to different ports. Some features were reincorporated into the “main” branch—the one Thompson and Ritchie worked on—but the bulk of these mutations spread in a haphazard way, shared through users directly or implemented in newly formed commercial versions. Some features were just that, features, but others could extend the system in ways that might make an application possible on one version, but not on another.
@@ -6537,7 +6124,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7C403609E23360C7C776EFBB67417C146E577AD921E8B3877062D65316A66036
| The proliferation and differentiation of UNIX, the operating system, had peculiar effects on the emerging market for UNIX, the product: technical issues entailed design and organizational issues. The original UNIX looked the way it did because of the very peculiar structure of the organization that created and sustained UNIX: Bell Labs and the worldwide community of users and developers. The newly formed competitors, conceiving of UNIX as a product distinct from the original UNIX, adopted it precisely because of its portability and because of the promise of open systems as an alternative to “big iron” mainframes. But as UNIX was funneled into existing corporations with their own design and organizational structures, it started to become incompatible with itself, and the desire for competition in open systems necessitated efforts at UNIX standardization.
@@ -6548,7 +6134,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 454FED2964CFDFCDB46738F6CE935F679242EF2A990402C93CD9DDB70A48F655
| The first step in the standardization of open systems and UNIX was the creation of what was called an “interface definition,” a standard that enumerated the minimum set of functions that any version of UNIX should support at the interface level, meaning that any programmer who wrote an application could expect to interact with any version of UNIX on any machine in the same way and get the same response from the machine (regardless of the specific implementation of the operating system or the source code that was used). Interface definitions, and extensions to them, were ideally to be published and freely available.
@@ -6559,7 +6144,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 06FEAE8F9E44423253270484680A53C31767F61D92D5845DB68DE9C3171B1120
.has: notes_reg
@@ -6571,7 +6155,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D864830F72745BCA96944072715E48AB18D17E1D0177BF7B27E529317B561445
| The /usr/group standard nevertheless provided a starting point for more traditional standards organizations—the Institute of Electrical and Electronics Engineers (IEEE) and the American National Standards Institute (ANSI)—to take on the task. Both institutions took the /usr/group standard as a basis for what would be called IEEE P1003 Portable Operating System Interface for Computer Environments (POSIX). Over the next three years, from 1984 to 1987, POSIX would work diligently at providing a standard interface definition for UNIX.
@@ -6582,7 +6165,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 30DCD39C2E7D3B4079A9EB798ACED7027212C266930C6A4804467FFC1EC62AF7
.has: notes_reg
@@ -6594,7 +6176,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 17D8F80BFBC24C19F7AE999806F4A5F393CE4F0D8B8710E5BDA511E334635196
| In response to this threat, a third entrant into the standards race emerged: X/Open, which comprised a variety of European computer manufacturers (including AT&T!) and sought to develop a standard that encompassed both SVID and POSIX. The X/Open initiative grew out of European concern about the dominance of IBM and originally included Bull, Ericsson, ICL, Nixdorf, Olivetti, Philips, and Siemens. In keeping with a certain 1980s taste for the integration of European economic activity vis-à-vis the United States and Japan, these manufacturers banded together both to distribute a unified UNIX operating system in Europe (based initially on the BSD and Sun versions of UNIX) and to attempt to standardize it at the same time.
@@ -6605,7 +6186,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 14AD9B778552353409904FCE6F0C4FFEBFEF9FAD3B640F2CF24A5FFA2B35E61A
| X/Open represented a subtle transformation of standardization efforts and of the organizational definition of open systems. While ⑆,┨[pg 158]┣, the /usr/group standard was developed by individuals who used UNIX, and the POSIX standard by an acknowledged professional society (IEEE), the X/Open group was a collective of computer corporations that had banded together to fund an independent entity to help further the cause of a standard UNIX. This paradoxical situation—of a need to share a standard among all the competitors and the need to keep the details of that standardized product secret to maintain an advantage—was one that many manufacturers, especially the Europeans with their long experience of IBM’s monopoly, understood as mutually destructive. Hence, the solution was to engage in a kind of organizational innovation, to create a new form of metacorporate structure that could strategically position itself as at least temporarily interested in collaboration with other firms, rather than in competition. Thus did stories and promises of open systems wend their way from the details of technical design to those of organizational design to the moral order of competition and collaboration, power and strategy. “Standards” became products that corporations sought to “sell” to their own industry through the intermediary of the consortium.
@@ -6616,7 +6196,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 22DF2206D067D20AA5029B5E5EE61167BE59C3176B15661293B5302E3B810585
| In 1985 and 1986 the disarrayed state of UNIX was also frustrating to the major U.S. manufacturers, especially to Sun Microsystems, which had been founded on the creation of a market for UNIX-based “workstations,” high-powered networked computers that could compete with mainframes and personal computers at the same time. Founded by Bill Joy, Vinod Khosla, and Andreas Bechtolsheim, Sun had very quickly become an extraordinarily successful computer company. The business pages and magazines were keen to understand whether workstations were viable competitors to PCs, in particular to those of IBM and Microsoft, and the de facto standard DOS operating system, for which a variety of extremely successful business-, personal-, and home-computer applications were written.
@@ -6627,7 +6206,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2F56397640BFF7A3B2E8990E4C16F51EA532AA0BC3432FB6E4D1C83F70C85236
| Sun seized on the anxiety around open systems, as is evident in the ad it ran during the summer of 1987 (figure 4). The ad plays subtly on two anxieties: the first is directed at the consumer and suggests that only with Sun can one actually achieve interoperability among all of one business’ computers, much less across a network or industry; the second is more subtle and plays to fears within the computer industry itself, the anxiety that Sun might merge with one ⑆,┨[pg 159]┣, of the big corporations, AT&T or Unisys, and corner the market in open systems by producing the de facto standard.
@@ -6638,7 +6216,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 757475A429DA3587AD846348FBE8FB0391F9E53B03FE3CE03CAE299CB3DF6D1C
.image: 2bits_05_04-100.png sha256:D54E58A67DABCA5CBAB6C0D50BB22F2288D464D809DF4F5221DBD517E817E201 bytes:85659 px:619x376
@@ -6651,7 +6228,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 103C9F7D502EC1ECF03269B06977549C3547061AFF368EC60815649A39527969
.has: notes_reg
@@ -6663,7 +6239,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 23AFFB6DFFB31975C3264E003B859834D5C41E197A13E2F3ABE3528102CDE3FB
| In response to this perceived collusion a group of U.S. and European companies banded together to form another rival organization—one that partially overlapped with X/Open but now included IBM—this one called the Open Software Foundation. A nonprofit corporation, the foundation included IBM, Digital Equipment, Hewlett-Packard, Bull, Nixdorf, Siemens, and Apollo Computer (Sun’s most direct competitor in the workstation market). Their goal was explicitly to create a “competing standard” for UNIX that would be available on the hardware they manufactured (and based, according to some newspaper reports, on IBM’s AIX, which was to be called OSF/1). AT&T appeared at first to support the foundation, suggesting that if the Open Software Foundation could come up with a standard, then AT&T would make System V compatible with it. Thus, 1988 was the summer of open love. Every major computer manufacturer in the world was now part of some consortium or another, and some were part of two—each promoting a separate standard.
@@ -6674,7 +6249,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F1E936A408D8A0633ACAD0000B5DCAC71AE4F49C1AB9DC6A49D335C0397E2D2B
| Of all the corporations, Sun did the most to brand itself as the originator of the open-systems concept. They made very broad claims for the success of open-systems standardization, as for instance in an ad from August 1988 (figure 5), which stated in part:
@@ -6685,7 +6259,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 39C75E306EF70C46BB1B177F2E7EDB80556243CE37FAB8AFF73B616709C5B3CF
.indent: 1 1
@@ -6697,7 +6270,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5AB066F28B3DA56C77EF8F1BAC5920103E9F80F267CCC9C2A9754D13B40A2458
.indent: 1 1
@@ -6709,7 +6281,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D8037483EA4A7D61CD1C8CC4611B15D5F55B230F683F56202833ED0C6B40A529
| The ad goes on to suggest that “in a free market, the best products win out,” even as Sun played both sides of every standardization battle, cooperating with both AT&T and with the Open Software Foundation. But by October of that year, it was clear to Sun that ⑆,┨[pg 161]┣, ⑆,┨[pg 162]┣, the idea hadn’t really become “so universal” just yet. In that month AT&T and Sun banded together with seventeen other manufacturers and formed a rival consortium: Unix International, a coalition of the willing that would back the AT&T UNIX System V version as the one true open standard. In a full-page advertisement from Halloween of 1988 (figure 6), run simultaneously in the New York Times, the Washington Post, and the Wall Street Journal, the rhetoric of achieved success remained, but now instead of “the Open Systems idea,” it was “your demand for UNIX System V-based solutions that ushered in the era of open architecture.” Instead of a standard for all open systems, it was a war of all against all, a war to assure customers that they had made, not the right choice of hardware or software, but the right choice of standard.
@@ -6720,7 +6291,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D87727A2E2ABF69EC6B8C461536325D7FD5C2E99236E736F6BED547B4DBD5E85
.image: 2bits_05_05-100.png sha256:236688A3801EF5D12DCFEC855425D765E49C20A0D7AF20BEA244062F05BC827D bytes:149949 px:631x846
@@ -6744,7 +6314,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 26175DD3FFD2A6E245B3AEC4C6B7017F19D163A00716352B59E3A43DB5B04075
.has: notes_reg
@@ -6756,7 +6325,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C182DF94EA016BAD188A5797EB0BA9FEC86AFA2A136C95CE0ACCA57893BD94FB
.image: 2bits_05_06-100.png sha256:97B0ABD89FD3DD16F5FE1763817FED06C51A02E2FA4EBB722FB4F9CB27B40DE4 bytes:257042 px:620x917
@@ -6780,7 +6348,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 708944FCECD17CFC1568C16FBB8365496435EF40F6F0050F56BB2E4543D2C8D2
| The proliferation of these consortia can be understood in various ways. One could argue that they emerged at a time—during the Reagan administration—when antitrust policing had diminished to ⑆,┨[pg 163]┣, ⑆,┨[pg 164]┣, the point where computer corporations did not see such collusion as a risky activity vis-à-vis antitrust policing. One could also argue that these consortia represented a recognition that the focus on hardware control (the meaning of proprietary) had been replaced with a focus on the control of the “open standard” by one or several manufacturers, that is, that competition was no longer based on superior products, but on “owning the standard.” It is significant that the industry consortia quickly overwhelmed national efforts, such as the IEEE POSIX standard, in the media, an indication that no one was looking to government or nonprofits, or to university professional societies, to settle the dispute by declaring a standard, but rather to industry itself to hammer out a standard, de facto or otherwise. Yet another way to understand the emergence of these consortia is as a kind of mutual policing of the market, a kind of paranoid strategy of showing each other just enough to make sure that no one would leapfrog ahead and kill the existing, fragile competition.
@@ -6791,7 +6358,6 @@
.ancestors: 1 290 0 0 414 451 0 0
.ancestors_collapsed: 1 290 414 451 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0A05797477182C465CBFE87CD607FE2CF1E17458FFD456AECE6B0DCB3D2967BF
| What this proliferation of UNIX standards and consortia most clearly represents, however, is the blind spot of open systems: the difficulty of having collaboration and competition at the same time in the context of intellectual-property rules that incompletely capture the specific and unusual characteristics of software. For participants in this market, the structure of intellectual property was unassailable—without it, most participants assumed, innovation would cease and incentives disappear. Despite the fact that secrecy haunted the industry, its customers sought both openness and compatibility. These conflicting demands proved irresolvable.
@@ -6819,7 +6385,6 @@
.ancestors: 1 290 0 0 414 475 0 0
.ancestors_collapsed: 1 290 414 475 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BE7EC22C13FBF63D3452046CC6A874E4BC4B66632CCBE8257AE8F5CFCA8CDCE3
| Ironically, the UNIX wars ended not with the emergence of a winner, but with the reassertion of proprietary computing: Microsoft Windows and Windows NT. Rather than open systems emerging victorious, ushering in the era of seamless integration of diverse components, the reverse occurred: Microsoft managed to grab a huge share of computer markets, both desktop and high-performance, by leveraging its brand, the ubiquity of DOS, and application-software developers’ dependence on the “Wintel” monster (Windows plus Intel chips). Microsoft triumphed, largely for the same reasons the open-systems dream failed: the legal structure of intellectual ⑆,┨[pg 165]┣, property favored a strong corporate monopoly on a single, branded product over a weak array of “open” and competing components. There was no large gain to investors, or to corporations, from an industry of nice guys sharing the source code and making the components work together. Microsoft, on the other hand, had decided to do so internal to itself; it did not necessarily need to form consortia or standardize its operating systems, if it could leverage its dominance in the market to spread the operating system far and wide. It was, as standards observers like to say, the triumph of de facto standardization over de jure. It was a return to the manacled wretches of IBM’s monopoly—but with a new dungeon master.
@@ -6830,7 +6395,6 @@
.ancestors: 1 290 0 0 414 475 0 0
.ancestors_collapsed: 1 290 414 475 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D096742154D04D63BE8A13F8BC5323264F7E0730971B90B79713DC658E73A83E
.has: links notes_reg
@@ -6844,7 +6408,6 @@
.ancestors: 1 290 0 0 414 475 0 0
.ancestors_collapsed: 1 290 414 475 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0EF8B139C85B191C8080C2478949357221E681CB1EBEEE6C7D6F2A7B605269BD
.has: links notes_reg
@@ -6857,7 +6420,6 @@
.ancestors: 1 290 0 0 414 475 0 0
.ancestors_collapsed: 1 290 414 475 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FF1C5A4152041A6239648512BA10AF3183BB734FA2C0EEBC0D016BDD54DB71A8
| This continuity, of course, deliberately disavows the centrality of the legal component, just as Raymond and the Open Source ⑆,┨[pg 166]┣, Initiative had in 1998. The distinction between a robust market in UNIX operating systems and a standard UNIX-based infrastructure on which other markets and other activities can take place still remains unclear to even those closest to the money and machines. It does not yet exist, and may well never come to.
@@ -6868,7 +6430,6 @@
.ancestors: 1 290 0 0 414 475 0 0
.ancestors_collapsed: 1 290 414 475 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AE956FC7633C174C41FFA2044B6C110733DC170758CF13D178ABCEFDC4241B6B
.has: links notes_reg
@@ -6898,7 +6459,6 @@
.ancestors: 1 290 0 0 414 481 0 0
.ancestors_collapsed: 1 290 414 481 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BD5B1CAEBBFB8C409E24972306C85928ECA2BC5D064401B572EAFE83D373F934
.has: notes_reg
@@ -6910,7 +6470,6 @@
.ancestors: 1 290 0 0 414 481 0 0
.ancestors_collapsed: 1 290 414 481 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7CE0E9489AD79DE7E74A6B2FF9E0173A51A8E483B1E74B4A043D3C347583E51F
| OSI and TCP/IP started with different goals: OSI was intended to satisfy everyone, to be the complete and comprehensive model against which all competing implementations would be validated; TCP/IP, by contrast, emphasized the easy and robust interconnection of diverse networks. TCP/IP is a protocol developed by bootstrapping between standard and implementation, a mode exemplified by the Requests for Comments system that developed alongside them as part of the Arpanet project. OSI was a “model” or reference standard developed by internationally respected standards organizations.
@@ -6921,7 +6480,6 @@
.ancestors: 1 290 0 0 414 481 0 0
.ancestors_collapsed: 1 290 414 481 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7A7C47C8AAA809E7E164B3F2E0CF84F8D503F82BBF3AEE58D8F176530C2F5359
| In the mid-1980s OSI was en route to being adopted internationally, but by 1993 it had been almost completely eclipsed by TCP/IP. The success of TCP/IP is significant for three reasons: (1) availability—TCP/IP was itself available via the network and development open to anyone, whereas OSI was a bureaucratically confined and expensive standard and participation was confined to state and corporate representatives, organized through ISO in Geneva; (2) modifiability—TCP/IP could be copied from an existing implementation (such as the BSD version of UNIX) and improved, whereas OSI was a complex standard that had few existing implementations available to copy; and (3) serendipity—new uses that took advantage of availability and modifiability sprouted, including the “killer app” that was the World Wide Web, which was built to function on existing TCP/IP-based networks, convincing many manufacturers to implement that protocol instead of, or in addition to, OSI.
@@ -6932,7 +6490,6 @@
.ancestors: 1 290 0 0 414 481 0 0
.ancestors_collapsed: 1 290 414 481 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D22CAAEE1AB51499E7D5F57FD5D7F110130425533DBC2FDEE79E3A2911591F3A
.has: notes_reg
@@ -6961,7 +6518,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 52906217444AACF1DC6CE759224C80E9BD4EDFACD752E4036832FE79C0B4734F
| The “religious war” between TCP/IP and OSI occurred in the context of intense competition among computer manufacturers and during a period of vibrant experimentation with computer networks worldwide. As with most developments in computing, IBM was one of the first manufacturers to introduce a networking system for its machines in the early 1970s: the System Network Architecture (SNA). DEC followed suit with Digital Network Architecture (DECnet or DNA), as did Univac with Distributed Communications Architecture (DCA), Burroughs with Burroughs Network Architecture (BNA), and others. These architectures were, like the proprietary operating systems of the same era, considered closed networks, networks that interconnected a centrally planned and specified number of machines of the same type or made by the same manufacturer. The goal of such networks was to make connections internal to a firm, even if that involved geographically widespread systems (e.g., from branch to headquarters). Networks were also to be products.
@@ -6972,7 +6528,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7F5ADF208806185BE2294D563A6C03920C09E6E3243C7DF73A6193ABA6EC93FF
.has: links notes_reg
@@ -6985,7 +6540,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D0B8E1FDE176B805854264ECF9BDB1EE846CBBAB6A5DC93BDA820E5EBCEA0D41
.has: links notes_reg
@@ -6998,7 +6552,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 51ACD4A3EFA967274BA45D0137A0AF908EB86808039E7C281FA46EACF843816B
.has: notes_reg
@@ -7010,7 +6563,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 71893A799C936F9295A66AF5D53A377994E09E453EC3AE541741F5A9F9F863AA
.has: notes_reg
@@ -7022,7 +6574,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CEC42901A0BDFEF112D267F78AAFF92C2C2833DD5231F4AD2224CD02A3AC6A71
.has: notes_reg
@@ -7034,7 +6585,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BC7C29F0CA73D7F779A61E900DCA405CC5541BD15E44C1B2F09CF9F4E87F7738
| Opposite ISO is the ad hoc, experimental style of Arpanet and Internet researchers, in which standards are freely available and implementations represent the mode of achieving consensus, rather than the outcome of the consensus. In reality, such a rhetorical ⑆,┨[pg 171]┣, opposition is far from absolute: many ISO standards are used on the Internet, and ISO remains a powerful, legitimate standards organization. But the clash of established (telecommunications) and emergent (computer-networking) industries is an important context for understanding the struggle between OSI and TCP/IP.
@@ -7045,7 +6595,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9717C856659CB5DA90B4D841C28AE6436A9354E8AA5395BB1C06E1B122B3F29C
| The need for standard networking protocols is unquestioned: interoperability is the bread and butter of a network. Nonetheless, the goals of the OSI and the TCP/IP protocols differed in important ways, with profound implications for the shape of that interoperability. OSI’s goals were completeness, control, and comprehensiveness. OSI grew out of the telecommunications industry, which had a long history of confronting the vicissitudes of linking up networks and facilitating communication around the world, a problem that required a strong process of consensus and negotiation among large, powerful, government-run entities, as well as among smaller manufacturers and providers. OSI’s feet were firmly planted in the international standardization organizations like OSI and the ITU (an organization as old as telecommunications itself, dating to the 1860s).
@@ -7056,7 +6605,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 641CA59433B53A21420987CDC22343DAA89D02BE83B088115543B41C6F725F8A
| Even if they were oft-mocked as slow, bureaucratic, or cumbersome, the processes of ISO and ITU—based in consensus, international agreement, and thorough technical specification—are processes of unquestioned legitimacy. The representatives of nations and corporations who attend ISO and ITU standards discussions, and who design, write, and vote on these standards, are usually not bureaucrats, but engineers and managers directly concerned with the needs of their constituency. The consensus-oriented process means that ISO and ITU standards attempt to satisfy all members’ goals, and as such they tend to be very large, complex, and highly specific documents. They are generally sold to corporations and others who need to use them, rather than made freely available, a fact that until recently reflected their legitimacy, rather than lack thereof.
@@ -7067,7 +6615,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4042845EECA9391604BE72E353E45047258BE0FE7B878A07864845BDB8973E28
.has: notes_reg
@@ -7079,7 +6626,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E0D4D666DF77CB284983C07D13C1A89323F9392413A8B40A392F41C00ABC7611
.has: notes_reg
@@ -7091,7 +6637,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3967A1D738B97DDED8D90CAFE50E672DE202593006C2A5BCA682D0B0BF886419
.has: notes_reg
@@ -7103,7 +6648,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C16FE9687DF9CDC162AAD49D7959D0203F93EBC3DD99EFDBF3806FE75F1B08A9
.has: links notes_reg
@@ -7116,7 +6660,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 956505081B6ED17AEE92BA99ED78D499E6BFC662D043FE2DC7C2253A58759C6D
.has: notes_reg
@@ -7128,7 +6671,6 @@
.ancestors: 1 290 0 0 414 486 0 0
.ancestors_collapsed: 1 290 414 486 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B42D4D0857E4B985AFFCA08E573B660657D8248AF59C7A2A8AC6A6092423EEAE
| The OSI protocols were not nearly so freely available. The ironic reversal—the transparency of a military-research program versus the opacity of a Geneva-based international-standards organization—goes a long way toward explaining the reasons why geeks might find the story of TCP/IP’s success to be so appealing. It is not that geeks are secretly militaristic, but that they delight in such surprising reversals, especially when those reversals exemplify the kind of ad hoc, clever solution to problems of coordination that the RFC process does. The RFC process is not the only alternative to a consensus-oriented model of standardization pioneered in the international organizations of Geneva, but it is a specific response to a reorientation of power and knowledge that was perhaps more “intuitively obvious” to the creators of Arpanet and the Internet, with its unusual design goals and context, than it would have been to the purveyors of telecommunications systems with over a hundred years of experience in connecting people in very specific and established ways.
@@ -7156,7 +6698,6 @@
.ancestors: 1 290 0 0 414 502 0 0
.ancestors_collapsed: 1 290 414 502 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 04E028D9088836BAB164E6EEF78FF0ECF4F2C5336F826B078419C50D0F57908B
.has: notes_reg
@@ -7168,7 +6709,6 @@
.ancestors: 1 290 0 0 414 502 0 0
.ancestors_collapsed: 1 290 414 502 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E937700F2A0BD5F4D7715217C931E9C02745F0E2CA86CE3B5EE943C5CE26F169
.has: notes_reg
@@ -7180,7 +6720,6 @@
.ancestors: 1 290 0 0 414 502 0 0
.ancestors_collapsed: 1 290 414 502 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1816735111001ED47314AE7D94E74D06D6C21EBC5D7D0CA49A627425C97773A8
| The more implementations that appeared, the less secure the legitimate standard seemed to be. By many accounts the OSI specifications were difficult to implement, and the yearly networking-industry “Interop” conferences became a regular locale for the religious war between TCP/IP and OSI. The success of TCP/IP over OSI reflects the reorientation of knowledge and power to which Free Software is also a response. The reasons for the success are no doubt complex, but the significance of the success of TCP/IP illustrates three issues: availability, modifiability, and serendipity.
@@ -7191,7 +6730,6 @@
.ancestors: 1 290 0 0 414 502 0 0
.ancestors_collapsed: 1 290 414 502 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F4A6E9BF6A111425553E7BFDF2E90BEF30B8088457DC3EA90425BBD885AAEA71
| ⑆!┨Availability┣! The TCP/IP standards themselves were free to anyone and available over TCP/IP networks, exemplifying one of the aspects of a recursive public: that the only test of participation in a TCP/IP-based internetwork is the fact that one possesses or has created a device that implements TCP/IP. Access to the network is contingent on the interoperability of the networks. The standards were not “published” in a conventional sense, but made available through the network itself, without any explicit intellectual property restrictions, and without any fees or restrictions on who could access them. By contrast, ISO standards are generally not circulated freely, but sold for relatively high prices, as a source of revenue, and under the general theory that only legitimate corporations or government agencies would need access to them.
@@ -7213,7 +6751,6 @@
.ancestors: 1 290 0 0 414 502 0 0
.ancestors_collapsed: 1 290 414 502 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 91DD98E7B713F148245CB10E09D014D6E7D16481FBEB1CE8C73BD4672199A3C5
.has: notes_reg
@@ -7225,7 +6762,6 @@
.ancestors: 1 290 0 0 414 502 0 0
.ancestors_collapsed: 1 290 414 502 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D5144EEF8D7CFAE5CF4427D8F2EBC3939B842F75E06AA896A4A5FECA6FC5EB82
| ⑆!┨Modifiability┣! Implementations of TCP/IP were widely available, bootstrapped from machine to machine along with the UNIX operating system and other tools (e.g., the implementation of TCP/IP in BSD 4.2, the BSD version of UNIX), generally including the source code. An existing implementation is a much more expressive and usable object than a specification for an implementation, and though ISO generally prepares reference implementations for such standards, in the case of OSI there were many fewer implementations to work with or build on. Because multiple implementations of TCP/IP already existed, it was easy to validate: did your (modified) implementation work with the other existing implementations? By contrast, OSI would provide independent validation, but the in situ validation through connection to other OSI networks was much harder to achieve, there being too few of them, or access being restricted. It is far easier to build on an existing implementation and to improve on it piecemeal, or even to rewrite it completely, using its faults as a template (so to speak), than it is to create an implementation based solely on a standard. The existence of the TCP/IP protocols in BSD 4.2 not only meant that people who installed that operating system could connect to the Internet easily, at a time when it was by no means standard to be able to do so, but it also meant that manufacturers or tinkerers could examine the implementation in BSD 4.2 as the basis for a modified, or entirely new, implementation.
@@ -7236,7 +6772,6 @@
.ancestors: 1 290 0 0 414 502 0 0
.ancestors_collapsed: 1 290 414 502 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3331B75BE4268BFE2840FBAC542BCB176C59BD76073EE82DE18F405BE48DF32E
.has: links notes_reg
@@ -7265,7 +6800,6 @@
.ancestors: 1 290 0 0 414 510 0 0
.ancestors_collapsed: 1 290 414 510 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EE570D96C4884C746EFF7377A78584D06C5565EC4EE844759E699717DB323C78
| Openness and open systems are key to understanding the practices of Free Software: the open-systems battles of the 1980s set the context for Free Software, leaving in their wake a partially articulated infrastructure of operating systems, networks, and markets that resulted from figuring out open systems. The failure to create a standard UNIX operating system opened the door for Microsoft Windows NT, but it also set the stage for the emergence of the Linux-operating-system kernel to emerge and spread. The success of the TCP/IP protocols forced multiple competing networking schemes into a single standard—and a singular entity, the Internet—which carried with it a set of built-in goals that mirror the moral-technical order of Free Software.
@@ -7276,7 +6810,6 @@
.ancestors: 1 290 0 0 414 510 0 0
.ancestors_collapsed: 1 290 414 510 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 64574B0507BCF58A18C0CE94CE7B2CE25439C62B550053B917720846F42DE6FE
| This “infrastructure” is at once technical (protocols and standards and implementations) and moral (expressing ideas about the proper order and organization of commercial efforts to provide high-tech software, networks, and computing power). As with the invention of UNIX, the opposition commercial-noncommercial (or its doppelgangers public-private, profit-nonprofit, capitalist-socialist, etc.) ⑆,┨[pg 178]┣, doesn’t capture the context. Constraints on the ability to collaborate, compete, or withdraw are in the making here through the technical and moral imaginations of the actors involved: from the corporate behemoths like IBM to (onetime) startups like Sun to the independent academics and amateurs and geeks with stakes in the new high-tech world of networks and software.
@@ -7287,7 +6820,6 @@
.ancestors: 1 290 0 0 414 510 0 0
.ancestors_collapsed: 1 290 414 510 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 70C3E1B5C01577A4896C641446689F65FE0094B62846C2ED6C03A98C3ACBDF22
| The creation of a UNIX market failed. The creation of a legitimate international networking standard failed. But they were local failures only. They opened the doors to new forms of commercial practice (exemplified by Netscape and the dotcom boom) and new kinds of politicotechnical fractiousness (ICANN, IPv6, and “net neutrality”). But the blind spot of open systems—intellectual property—at the heart of these failures also provided the impetus for some geeks, entrepreneurs, and lawyers to start figuring out the legal and economic aspects of Free Software, and it initiated a vibrant experimentation with copyright licensing and with forms of innovative coordination and collaboration built on top of the rapidly spreading protocols of the Internet.
@@ -7335,7 +6867,6 @@
.ancestors: 1 290 0 0 514 0 0 0
.ancestors_collapsed: 1 290 514 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 3B47BE4B07E450EEC3B3BB9E3399C947513A4726E6A89247049C75804DD5B4EA
.indent: 1 1
@@ -7347,7 +6878,6 @@
.ancestors: 1 290 0 0 514 0 0 0
.ancestors_collapsed: 1 290 514 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: D21CBDCB3960B9A03C70CD815641EB47F333748114426FE7FD0775CC50249C9B
| The use of novel, unconventional copyright licenses is, without a doubt, the most widely recognized and exquisitely refined component of Free Software. The GNU General Public License (GPL), written initially by Richard Stallman, is often referred to as a beautiful, clever, powerful “hack” of intellectual-property law—when it isn’t being denounced as a viral, infectious object threatening the very fabric of economy and society. The very fact that something so boring, so arcane, and so legalistic as a copyright license can become an object of both devotional reverence and bilious scorn means there is much more than fine print at stake. ⑆,┨[pg 180]┣,
@@ -7358,7 +6888,6 @@
.ancestors: 1 290 0 0 514 0 0 0
.ancestors_collapsed: 1 290 514 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 566655AC29411477C0041AAADE96C299F5E9F83C80CECE2AB60C7F1F8C0BF33F
.has: notes_reg
@@ -7370,7 +6899,6 @@
.ancestors: 1 290 0 0 514 0 0 0
.ancestors_collapsed: 1 290 514 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 0A3B3F4471E4547A95C03A9B274407A4D9A57B04660F4EED5D4888E1AC5A31C9
.has: links notes_reg
@@ -7382,7 +6910,6 @@
.ancestors: 1 290 0 0 514 0 0 0
.ancestors_collapsed: 1 290 514 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: FF3D1269E04BE08C7159366424A29A47DB6B29E43B42B8B85202C9630E261131
.has: notes_reg
@@ -7394,7 +6921,6 @@
.ancestors: 1 290 0 0 514 0 0 0
.ancestors_collapsed: 1 290 514 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 16ADF23563953B0C88445CB96876B73A2C8F6121B04E4F223799034040F3C599
.has: notes_reg
@@ -7423,7 +6949,6 @@
.ancestors: 1 290 0 0 514 521 0 0
.ancestors_collapsed: 1 290 514 521 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 39248086D896F78C6A7F78CCA6A71F3F279DF6A6DE82B4DFE1E6DEE76210CE3F
.has: notes_reg
@@ -7435,7 +6960,6 @@
.ancestors: 1 290 0 0 514 521 0 0
.ancestors_collapsed: 1 290 514 521 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A391E936C29678F0F1DE31157260E2C883766FCF2E6A7571B48B0A67AEA9152F
| A similar story might be told of Richard Stallman, hacker hero and founder of the Free Software Foundation, creator of (among many other things) the GNU C Compiler and GNU EMACS, two of the most widely used and tested Free Software tools in the world. Stallman is routinely abused for holding what many perceive to be “dogmatic” or “intractable” ideological positions about freedom and the right of individuals to do what they please with software. While it is no doubt quite true that his speeches and writings clearly betray a certain fervor and fanaticism, it would be a mistake to assume that his speeches, ideas, or belligerent demands concerning word choice constitute the real substance of his reform. In fact, it is the software he has created and the licenses he has written and rewritten which are the key to his Bentham-like inventiveness. Unlike Bentham, however, Stallman is not a creator of law and administrative structure, but a hacker.
@@ -7446,7 +6970,6 @@
.ancestors: 1 290 0 0 514 521 0 0
.ancestors_collapsed: 1 290 514 521 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 26F6F269E1FE27330E450FA9E127FB8FB8867F3A1A06EEDBAF8FE7329C3763F8
| Stallman’s GNU General Public License “hacks” the federal copyright law, as is often pointed out. It does this by taking advantage of the very strong rights granted by federal law to actually loosen the restrictions normally associated with ownership. Because the statutes grant owners strong powers to create restrictions, Stallman’s GPL contains the restriction that anybody can use the licensed material, for any purpose, so long as they subsequently offer the same restriction. Hacks (after which hackers are named) are clever solutions to problems or shortcomings in technology. Hacks are work-arounds, clever, shortest-path solutions that take advantage of characteristics of the system that may or may not have been obvious to the people who designed it. Hacks range from purely utilitarian to mischievously pointless, but they always depend on an existing system or tool through which they achieve their point. To call Free Software a hack is to point out that it would be nothing without the existence of intellectual-property law: it relies on the structure of U.S. copyright law (USC§17) in order to subvert it. Free Software licenses are, in a sense, immanent to copyright laws—there is nothing illegal or even legally arcane about what they accomplish—but there is nonetheless a kind of lingering sense ⑆,┨[pg 183]┣, that this particular use of copyright was not how the law was intended to function.
@@ -7457,7 +6980,6 @@
.ancestors: 1 290 0 0 514 521 0 0
.ancestors_collapsed: 1 290 514 521 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CC3BEB06F42DC175CCE92F6B875B97049C5D16E749749CEE22F1104DA85128DB
.has: links notes_reg
@@ -7469,7 +6991,6 @@
.ancestors: 1 290 0 0 514 521 0 0
.ancestors_collapsed: 1 290 514 521 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AD3A7A10152B8256C401C33D761FB8B9324371A5B8FE3BC92CEA83D1D8E550E2
.has: links notes_reg
@@ -7499,7 +7020,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DEAA0A5C13474ABC5D193C61BEE4EBDAD70D5627D3DED953F7DF5F99AEBA88C4
| EMACS is a text editor; it is also something like a religion. As one of the two most famous text editors, it is frequently lauded by its devoted users and attacked by detractors who prefer its competitor (Bill Joy’s vi, also created in the late 1970s). EMACS is more than just a tool for writing text; for many programmers, it was (and still is) the principal interface to the operating system. For instance, it allows a programmer not only to write a program but also to debug it, to compile it, to run it, and to e-mail it to another user, ⑆,┨[pg 184]┣, all from within the same interface. What’s more, it allows users to quickly and easily write extensions to EMACS itself, extensions that automate frequent tasks and in turn become core features of the software. It can do almost anything, but it can also frustrate almost anyone. The name itself is taken from its much admired extensibility: EMACS stands for “editing macros” because it allows programmers to quickly record a series of commands and bundle them into a macro that can be called with a simple key combination. In fact, it was one of the first editors (if not the first) to take advantage of keys like ctrl and meta, as in the now ubiquitous ctrl-S familiar to users of non-free word processors like Microsoft Word™.
@@ -7510,7 +7030,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: ED00EAB43E29917B41D2037909CD784F73D43EB2B240C8C72E1E27597B6B665F
| Appreciate the innovation represented by EMACS: before the UNIX-dominated minicomputer era, there were very few programs for directly manipulating text on a display. To conceive of source code as independent of a program running on a machine meant first conceiving of it as typed, printed, or hand-scrawled code which programmers would scrutinize in its more tangible, paper-based form. Editors that allowed programmers to display the code in front of them on a screen, to manipulate it directly, and to save changes to those files were an innovation of the mid- to late 1960s and were not widespread until the mid-1970s (and this only for bleeding-edge academics and computer corporations). Along with a few early editors, such as QED (originally created by Butler Lampson and Peter Deutsch, and rewritten for UNIX by Ken Thompson), one of the most famous of these was TECO (text editor and corrector), written by Dan Murphy for DEC’s PDP-1 computer in 1962-63. Over the years, TECO was transformed (ported and extended) to a wide variety of machines, including machines at Berkeley and MIT, and to other DEC hardware and operating systems. By the early 1970s, there was a version of TECO running on the Incompatible Time-sharing System (ITS), the system in use at MIT’s Artificial Intelligence (AI) Lab, and it formed the basis for EMACS. (Thus, EMACS was itself conceived of as a series of macros for a separate editor: Editing MACroS for TECO.)
@@ -7521,7 +7040,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5666C2992F547628A7B45E0CA6A0F7593CACCF6B34E0B81B9FE1F992B68B5507
.has: notes_reg
@@ -7533,7 +7051,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DF7D7A231BB776A37C53E68BD3747ABE6D306BA0095958D83F11B0FF8B04A548
| At this point, in 1978, EMACS lived largely on ITS, but its reputation soon spread, and it was ported to DEC’s TOPS-20 (Twenex) operating system and rewritten for Multics and the MIT’s LISP machine, on which it was called EINE (Eine Is Not EMACS), and which was followed by ZWEI (Zwei Was Eine Initially).
@@ -7544,7 +7061,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6EC44EF35319D15BE0433DDC211E06467F113ED22CBF4FF835BD3184DAA34CF7
.has: notes_reg
@@ -7556,7 +7072,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 02237D9FA7273D36BF6E4117D54F0380569D687DD781C300D63331AFF2745F50
| Thus, while EMACS in its specific form on ITS was a creation of Stallman, the idea of EMACS or of any “real-time display editor” was proliferating in different forms and on different machines. The porting of EMACS, like the porting of UNIX, was facilitated by both its conceptual design integrity and its widespread availability.
@@ -7567,7 +7082,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5C9E2E18BBDD6D971211DA4599C7C4378A141403776A38ED00D6D57245254728
| The phrase “nonextensible imitation” captures the combination of design philosophy and moral philosophy that EMACS represented. Extensibility was not just a useful feature for the individual computer user; it was a way to make the improvements of each new user easily available equally to all by providing a standard way for users to add extensions and to learn how to use new extensions that were added (the “self-documenting” feature of the system). The program had a conceptual integrity that was compromised when it was copied imperfectly. EMACS has a modular, extensible design ⑆,┨[pg 186]┣, that by its very nature invites users to contribute to it, to extend it, and to make it perform all manner of tasks—to literally copy and modify it, instead of imitating it. For Stallman, this was not only a fantastic design for a text editor, but an expression of the way he had always done things in the small-scale setting of the AI Lab. The story of Stallman’s moral commitments stresses his resistance to secrecy in software production, and EMACS is, both in its design and in Stallman’s distribution of it an example of this resistance.
@@ -7578,7 +7092,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A887CF1ED1343B4B800647AD2C3EF12CED76E85F6DE9624BC6C54FD6A6C58FB3
.has: notes_reg
@@ -7590,7 +7103,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2CA2EEA1E4AA33BB374EDEB4CFB767AD88F5D3D12700C995C1D5225A06651EC9
| In another report, intended as a user’s manual for EMACS, Stallman gave more detailed and slightly more colorful instructions:
@@ -7601,7 +7113,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 71E1AFA3CBBE15914FF8A3672AE2E37BFDDD94AA9BC5E2BB7C8E8FDC766820DA
.indent: 1 1
@@ -7614,7 +7125,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F0CEE63A06E54FF35AABF8931EBE6A1577E751ABF11514AB099B1019524CE319
| Because EMACS was so widely admired and respected, Stallman had a certain amount of power over this commune. If it had been an obscure, nonextensible tool, useful for a single purpose, no one would have heeded such demands, but because EMACS was by nature the kind of tool that was both useful for all kinds of tasks and ⑆,┨[pg 187]┣, customizable for specific ones, Stallman was not the only person who benefited from this communal arrangement. Two disparate sites may well have needed the same macro extension, and therefore many could easily see the social benefit in returning extensions for inclusion, as well as in becoming a kind of co-developer of such a powerful system. As a result, the demands of the EMACS commune, while unusual and autocratic, were of obvious value to the flock. In terms of the concept of recursive public, EMACS was itself the tool through which it was possible for users to extend EMACS, the medium of their affinity; users had a natural incentive to share their contributions so that all might receive the maximum benefit.
@@ -7625,7 +7135,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 623714EE5C88C534F2C5242B18A6504E70DDEC05FAF1241CE029073D0FB8E7ED
| The terms of the EMACS distribution agreement were not quite legally binding; nothing compelled participation except Stallman’s reputation, his hectoring, or a user’s desire to reciprocate. On the one hand, Stallman had not yet chosen to, or been forced to, understand the details of the legal system, and so the EMACS commune was the next best thing. On the other hand, the state of intellectual-property law was in great flux at the time, and it was not clear to anyone, whether corporate or academic, exactly what kind of legal arrangements would be legitimate (the 1976 changes to copyright law were some of the most drastic in seventy years, and a 1980 amendment made software copyrightable, but no court cases had yet tested these changes). Stallman’s “agreement” was a set of informal rules that expressed the general sense of mutual aid that was a feature of both the design of the system and Stallman’s own experience at the AI Lab. It was an expression of the way Stallman expected others to behave, and his attempts to punish or shame people amounted to informal enforcement of these expectations. The small scale of the community worked in Stallman’s favor.
@@ -7636,7 +7145,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E6C5E2CFC924BAA3FEB10C96823FADBAC9FFA8B70802AAD029C2EADAA2C7E656
| At its small scale, Stallman’s commune was confronting many of the same issues that haunted the open-systems debates emerging at the same time, issues of interoperability, source-code sharing, standardization, portability, and forking. In particular, Stallman was acutely aware of the blind spot of open systems: the conflict of moral-technical orders represented by intellectual property. While UNIX vendors left intellectual-property rules unchallenged and simply assumed that they were the essential ground rules of debate, Stallman made them the substance of his experiment and, like Bentham, became something of a legal muckraker as a result.
@@ -7658,7 +7166,6 @@
.ancestors: 1 290 0 0 514 527 0 0
.ancestors_collapsed: 1 290 514 527 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C10C59BFDE93B46DD527260F0166CF8C5431874066C49B3B8146712BD3CF3268
| Stallman’s communal model could not completely prevent the porting and forking of software. Despite Stallman’s request that imitators refer to their versions of EMACS as ersatz EMACS, few did. In the absence of legal threats over a trademarked term there was not much to stop people from calling their ports and forks EMACS, a problem of success not unlike that of Kleenex or Xerox. Few people took the core ideas of EMACS, implemented them in an imitation, and then called it something else (EINE and ZWEI were exceptions). In the case of UNIX the proliferation of forked versions of the software did not render them any less UNIX, even when AT&T insisted on ownership of the trademarked name. But as time went on, EMACS was ported, forked, rewritten, copied, or imitated on different operating systems and different computer architectures in universities and corporations around the world; within five or six years, many versions of EMACS were in wide use. It was this situation of successful adoption that would provide the context for the controversy that occurred between 1983 and 1985.
@@ -7686,7 +7193,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D868C71240D977A04D757E790F83F9DEBAC93F4D4C9FCFF9438A96528026F6A8
| In brief the controversy was this: in 1983 James Gosling decided to sell his version of EMACS—a version written in C for UNIX called GOSMACS—to a commercial software vendor called Unipress. GOSMACS, the second most famous implementation of EMACS (after Stallman’s itself ), was written when Gosling was a graduate student at Carnegie Mellon University. For years, Gosling had distributed GOSMACS by himself and had run a mailing list on Usenet, on which he answered queries and discussed extensions. Gosling had explicitly asked people not to redistribute the program, but to come back to him (or send interested parties to him directly) for new versions, making GOSMACS more of a benevolent dictatorship than a commune. Gosling maintained his authority, but graciously accepted revisions and bug-fixes and extensions from users, incorporating them into new releases. Stallman’s system, by contrast, allowed users to distribute their extensions themselves, as well as have them included in the “official” EMACS. By 1983, Gosling had decided he was unable to effectively maintain and support GOSMACS—a task he considered the proper role of a corporation.
@@ -7708,7 +7214,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6AA5D22AAC4266A579A507BABB07CEF9B811687FE490C9771CD79E68EE31E9DC
| For Stallman, Gosling’s decision to sell GOSMACS to Unipress was “software sabotage.” Even though Gosling had been substantially responsible for writing GOSMACS, Stallman felt somewhat proprietorial toward this ersatz version—or, at the very least, was irked that no noncommercial UNIX version of EMACS existed. So Stallman wrote one himself (as part of a project he announced around the same time, called GNU [GNU’s Not UNIX], to create a complete non-AT&T version of UNIX). He called his version GNU EMACS and released it under the same EMACS commune terms. The crux of the debate hinged on the fact that Stallman used, albeit ostensibly with permission, a small piece of Gosling’s code in his new version of EMACS, a fact that led numerous people, including the new commercial suppliers of EMACS, to cry foul. Recriminations and legal threats ensued and the controversy was eventually resolved when Stallman rewrote the offending code, thus creating an entirely “Gosling-free” version that went on to become the standard UNIX version of EMACS.
@@ -7719,7 +7224,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 83427C5D6FC410804DD19DC592F7081B5830A76446489AAD401DBACBAAD4FEDC
| The story raises several questions with respect to the changing legal context. In particular, it raises questions about the difference between “law on the books” and “law in action,” that is, the difference between the actions of hackers and commercial entities, advised by lawyers and legally minded friends, and the text and interpretation of statutes as they are written by legislators and interpreted by courts and lawyers. The legal issues span trade secret, patent, and trademark, but copyright is especially significant. Three issues were undecided at the time: the copyrightability of software, the definition of what counts as software and what doesn’t, and the meaning of copyright infringement. While the controversy did not resolve any of these issues (the first two would be resolved by Congress and the courts, the third remains somewhat murky), it did clarify the legal issues for Stallman sufficiently that he could leave behind the informal EMACS commune and create the first version of a Free Software license, the GNU General Public License, which first started appearing in 1985.
@@ -7730,7 +7234,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4A7444182E1F8CB8218D534CA20974A7DECA82DF0824326C4ABA2BA7CE81B3D1
.has: links notes_reg
@@ -7759,7 +7262,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D37659B76202BDAD7F5D90BA86AB581A7F847EDF2DD982CE346919B8EBEC59DB
| The message is worth paying careful attention to: Gosling’s work of distributing the tapes had become “unmanageable,” and the work of maintenance, upkeep, and porting (making it available on multiple architectures) is something he clearly believes should be done by a commercial enterprise. Gosling, it is clear, did not understand his effort in creating and maintaining EMACS to have emerged from a communal sharing of bits of code—even if he had done a Sisyphean amount of work to incorporate all the changes and suggestions his users had made—but he did long have a commitment ⑆,┨[pg 191]┣, to distributing it for free, a commitment that resulted in many people contributing bits and pieces to GOSMACS.
@@ -7770,7 +7272,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 09BC473517E4FACF7F70DD469AFA429B219A09B717795420276D504D4B9C5660
.has: links notes_reg
@@ -7782,7 +7283,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A225E0D57CAFD9E654A0B5300182E7837FF7A5501808439F0AF67122CFD34A32
| To Stallman, the advancing commercialization of EMACS, both by CCA and by Unipress, was a frustrating state of affairs. The commercialization of CCA had been of little concern so long as GOSMACS remained free, but with Gosling’s announcement, there was no longer a UNIX version of EMACS available. To Stallman, however, “free” meant something more than either “public domain” or “for no cost.” The EMACS commune was designed to keep EMACS alive and growing as well as to provide it for free—it was an image of community stewardship, a community that had included Gosling until April 1983.
@@ -7793,7 +7293,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D833A8E73985005325C7970BBEC7DA79F8103D2F8F8B06599D1594503DD40FAE
.has: links notes_reg
@@ -7828,7 +7327,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AFCABA46028F825D0B8B0CBAE4300257147F4B23DA7B5B013CE0725C2975B2CF
| His justifications were simple.
@@ -7852,7 +7350,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CCFB89FAC20E4A4DF4DA547463153B526EE15CC4E0CFD709F87F3723632521AE
.has: notes_reg
@@ -7864,7 +7361,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1057CD5AB705508084D0CF93DC1B8F8001CAD49F7B7DAB113A1286EE3D98A1FA
.has: links notes_reg
@@ -7876,7 +7372,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 58953701234B70E36F59327F6DDD3926F88E8BCA8EDD98EEA50E1762ADBE1CCF
.has: links notes_reg
@@ -7889,7 +7384,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F6999288929E73514868557DF9AB3E507432EF13952E95AF2D2956E562F0A13F
.has: links notes_reg
@@ -7901,7 +7395,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A3E8C260FEB50F7A1576347BEDC0601599888B271FCB0DD690FE03C08394CE8B
.has: links notes_reg
@@ -7913,7 +7406,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B98469413F41C4B4CBBE6778427558884D58542BC4E24B089A18B2A29E015E33
| The addendum was then followed by an extensive reply from Zimmerman, whose CCA EMACS had been based on Warren Montgomery’s Bell Labs EMACS but rewritten to avoid reusing the code, which may account for why his understanding of the issue seems to have been both deep and troubling for him.
@@ -7924,7 +7416,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A2BF40E2F0894D355B00FC6BB4C73CEF85D31F0DB3649429F1129244F073DACF
.indent: 1 1
@@ -7936,7 +7427,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7D0B9702529ADBDA56B367FADD49CB6FEEE9FA12EAE17E75DA8716EC09E30447
.indent: 1 1
@@ -7949,7 +7439,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7EB1B4DA6ACD8F43CD1D5902B1ADD5FD8FCDB3AE92B8D91D57AD54661C2F6836
| Stallman replied the next day. ⑆,┨[pg 195]┣,
@@ -7960,7 +7449,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BA541E808872B745DB7A3092964768D14B5DDF7BF528BFC71F891042CFC1AC17
.indent: 1 1
@@ -7972,7 +7460,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8406C6D4F75A7F9D47AE68B25002A4F36B9512068CD34EBC7B41032EB156F448
.indent: 1 1
@@ -7985,7 +7472,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 368E9B04E193EA539823D99513892B7BC2C2516CCEACE7AB00D70632F75D2A75
.has: links notes_reg
@@ -7998,7 +7484,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0A0AEFBBD72F017AADE9109B1E02517FE9E9B6DD3B3E4FED01013EB4A5FFAC9B
.has: links notes_reg
@@ -8010,7 +7495,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4E7B586893A399990D52E86BA87D91DCBB92AA3AEAEE297DD8E6A490CE6F6018
| Stallman’s biggest concern was not so much the legality of his own actions as the possibility that people would choose not to use the software because of legal threats (even if such threats were issued only as rumors by former employees of companies that distributed software they had written). Stallman wanted users not only ⑆,┨[pg 196]┣, to feel safe using his software but to adopt his view that software exists to be shared and improved and that anything that hinders this is a loss for everyone, which necessitates an EMACS commune.
@@ -8021,7 +7505,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D6FDD3D23085FFBA621B3BB5F18F495C8BD20051DCD4B00482A3B743494F51BA
.has: links notes_reg
@@ -8033,7 +7516,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3B3E705ECB36FBCE46A508CC42835F0C63827A6096E9832A4EA60BBF082033C6
.has: links notes_reg
@@ -8056,7 +7538,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2F7ACAA10C3C13511AFF458CF2634C01A5D9469FA941C25326B49E71C9C7B7DD
.has: links notes_reg
@@ -8068,7 +7549,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CB305FC75ED10C8D25C535FBA494654FFB1824C3018A44E1B7546BD8DE1DFAEE
| Indeed, the general irony of this complicated situation was certainly not as evident as it might have been given the emotional tone of the debates: Stallman was using code from Gosling based on permission Gosling had given to Labalme, but Labalme had written code for Gosling which Gosling had commercialized without telling Labalme—conceivably, but not likely, the same code. Furthermore, all of them were creating software that had been originally conceived in large part by Stallman (but based on ideas and work on TECO, an editor written twenty years before EMACS), who was now busy rewriting the very software Gosling had rewritten for UNIX. The “once proud hacker ethic” that Labalme mentions would thus amount not so much to an explicit belief in sharing so much as a fast-and-loose practice of making contributions and fixes without documenting them, giving oral permission to use and reuse, and “losing” records that may or may not have existed—hardly a noble enterprise.
@@ -8079,7 +7559,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D1248649208243E5177C204A4508D2F69C47D1736CA899AEE8466E60CB9A0CC1
| But by 27 June 1985, all of the legal discussion was rendered moot when Stallman announced that he would completely rewrite the display code in EMACS.
@@ -8090,7 +7569,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0375E9B7E91C9917E00150FE74DDB2138E5F7F3476CA748F54FFCB884DF15B9A
.indent: 1 1
@@ -8102,7 +7580,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B17CB06A8F64FBCC81A3B113A563DACFDCF840B39F0AB98D15F79B8C0CF42642
.indent: 1 1
@@ -8115,7 +7592,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 46929062749B9E222985DBCEC0EF390132ABED2AF501FC875D1192C3870B97E8
| On 5 July, Stallman sent out a message that said: ⑆,┨[pg 198]┣,
@@ -8126,7 +7602,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 67D9A2E0CF5240795B1F9010F92736EF232AC3E2563CA0E2AD5B2B8E0A3FBC65
.indent: 1 1
@@ -8138,7 +7613,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 87E663E5A7DE9814189D47D567CA71AFA6D8FC43879FEC66DA6C6FBEA78B4A8A
.indent: 1 1
@@ -8151,7 +7625,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E2E7BF5A9842DB0ED76845D44A20027DF4FC809A498C74717DA80667A7E85FDD
| The fact that it only took one week to create the code is a testament to Stallman’s widely recognized skills in creating great software—it doesn’t appear to have indicated any (legal) threat or urgency. Indeed, even though Unipress seems also to have been concerned about their own reputation, and despite the implication made by Stallman that they had forced this issue to happen, they took a month to respond. At that point, the Unipress employee Mike Gallaher wrote to insist, somewhat after the fact, that Unipress had no intention of suing anyone—as long as they were using the Gosling-free EMACS version 16 and higher.
@@ -8162,7 +7635,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C838E0FE095A1DB5A765E7A543F0ACC94EC1B15FA6945AF6922280FF071D9F0D
.indent: 1 1
@@ -8174,7 +7646,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 12E48366D9E5B69909A2398575FF1561AF1E2CFDA8929A24C25DC7F21240102E
.indent: 1 1
@@ -8187,7 +7658,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5A552CC37629A868F7AB3B9B28AD191E44C4D3890CE9654A450F4FF8CB374865
| Both Stallman and Unipress received various attacks and defenses from observers of the controversy. Many people pointed out that Stallman should get credit for “inventing” EMACS and that the issue of him infringing on his own invention was therefore ironic. Others proclaimed the innocence and moral character of Unipress, which, it was claimed, was providing more of a service (support for EMACS) than the program itself.
@@ -8198,7 +7668,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6E34B43424468C1FB66F0823B93AB2BCA5C102A30472934C560F41D203B36461
.has: links notes_reg
@@ -8210,7 +7679,6 @@
.ancestors: 1 290 0 0 514 542 0 0
.ancestors_collapsed: 1 290 514 542 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 97D774C00A64E55A1649F209C88216C9BC40D9418F9E571EEFE27C975EC39E3B
| Gosling’s sale of EMACS is thus of a different order from his participation in the common stewardship of EMACS. The distinction between creating software and maintaining it is a commercial fiction driven in large part by the structure of intellectual property. It mirrors the experience of open systems. Maintaining software can mean improving it, and improving it can mean incorporating the original work and ideas of others. To do so by the rules of a changing intellectual-property structure forces different choices than to do so according to an informal hacker ethic or an experimental “commune.” One programmer’s minor improvement is another programmer’s original contribution.
@@ -8238,7 +7706,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7C992F09C1C98006E488A1F5CC42ACE7B68FF7725FD98F32DFD5EDA4F7BCB50F
| The EMACS controversy occurred in a period just after some of the largest changes to U.S. intellectual-property law in seventy years. Two aspects of this context are worth emphasizing: (1) practices and knowledge about the law change slowly and do not immediately reflect the change in either the law or the strategies of actors; (2) U.S. law creates a structural form of uncertainty in which the interplay between legislation and case law is never entirely certain. In the former aspect, programmers who grew up in the 1970s saw a commercial practice entirely dominated by trade secret and patent protection, and very rarely by copyright; thus, the shift to widespread use of copyright law (facilitated by the 1976 and 1980 changes to the law) to protect software was a shift in thinking that only slowly dawned on many participants, even the most legally astute, since it was a general shift in strategy as well as a statutory change. In the latter aspect, the 1976 and 1980 changes to the copyright law contained a number of uncertainties that would take over a decade to be worked out in case law, issues such as the copyrightability of software, the definition of software, and the meaning ⑆,┨[pg 200]┣, of infringement in software copyright, to say nothing of the impact of the codification of fair use and the removal of the requirement to register (issues that arguably went unnoticed until the turn of the millennium). Both aspects set the stage for the EMACS controversy and Stallman’s creation of the GPL.
@@ -8249,7 +7716,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 18CF720C81B33B845652E145942BAB559F3BA6BFCE34788F7E04AE2E7E7607D2
.has: notes_reg
@@ -8261,7 +7727,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F7C01DE275A1674E4ADC368C2663AA268BFE0C0265ED0C7C7AECA37A89C6C5C5
.has: links notes_reg
@@ -8273,7 +7738,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 50017F8F86916375266C85953A0FD7181F97E5F1C3ABD7EC7323E3B1DFCFB89C
.has: links notes_reg
@@ -8285,7 +7749,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CEC848B4AD7EC325AB8604884BDCE8189FC1B64297FF6F44598CEC084D811352
.has: notes_reg
@@ -8297,7 +7760,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A3E8E0B9D1775A87F56761FDA2C2F9D6F0B2D8909EB7A60BEB0C0FDA1628A786
.has: links notes_reg
@@ -8309,7 +7771,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 732B6DD50DCEA3F3BC571102B911C5DA16A0C0F6E5F0019BF607F701B86E09F9
| The uncertainty over copyright was thus in part a reflection of a changing strategy in the computer-software industry, a kind of uneven development in which copyright slowly and haphazardly came to replace trade secret as the main form of intellectual-property protection. This switch had consequences for how noncommercial programmers, researchers, and amateurs might interpret their own work, as well as for the companies whose lawyers were struggling with the same issues. Of course, copyright and trade-secret protection are not mutually exclusive, but they structure the need for secrecy in different ways, and they make different claims on issues like similarity, reuse, and modification.
@@ -8320,7 +7781,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A855F69CE54A867330CB70BDE3D561B683EDA6B95D19661EEEDE6EBD38CE2E78
| The 1976 changes to copyright law were therefore extremely significant in setting out a new set of boundaries and possibilities for intellectual-property arguments, arguments that created a different kind of uncertainty from that of a changing commercial strategy: a structural uncertainty created by the need for a case law to develop around the statutory changes implemented by Congress.
@@ -8331,7 +7791,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D9002BE14BD436F44F8C921236635CBE0DB13EA447A68FC5973CAD8231E571C8
.has: links notes_reg
@@ -8343,7 +7802,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FC8A93CBC46C2A99C7500FD49F0948130F6757EFEB5B1E543EFF10172E80FF68
.has: notes_reg
@@ -8355,7 +7813,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 338DAD2ED3460C4DE2B9C05ACDB71F58A97A74D596926AB2467B3BBB9B3A1AE2
| The EMACS controversy confronts all three of these questions. Stallman’s initial creation of EMACS was accomplished under conditions in which it was unclear whether copyright would apply (i.e., before 1980). Stallman, of course, did not attempt to copyright the earliest versions of EMACS, but the 1976 amendments removed the requirement to register, thus rendering everything written after 1978 automatically copyrighted. Registration represented only an additional effort to assert ownership in cases of suspected infringement.
@@ -8366,7 +7823,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 23D0F9137CBC7A8AB208502118F9695744925663EBF9C172EDE56549B74BDB31
| Throughout this period, the question of whether software was copyrightable—or copyrighted—was being answered differently in different cases: AT&T was relying on trade-secret status; Gosling, Unipress, and CCA negotiated over copyrighted material; and Stallman was experimenting with his “commune.” Although the uncertainty was answered statutorily by the 1980 amendment, not everyone instantly grasped this new fact or changed practices based on it. There is ample evidence throughout the Usenet archive that the 1976 changes were poorly understood, especially by comparison with the legal sophistication of hackers in the 1990s and 2000s. Although the law changed in 1980, practices changed more slowly, and justifications crystallized in the context of experiments like that of GNU EMACS.
@@ -8377,7 +7833,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A42156FA2C2A6E74D4335EE32E6AB0831A6D67BE7201E6422C883CDD375750FB
| Further, a tension emerged between the meaning of source code and the meaning of software. On the one hand was the question of whether the source code or the binary code was copyrightable, and on the other was the question of defining the boundaries of software in a context wherein all software relies on other software in order to run at all. For instance, EMACS was originally built on top of TECO, which was referred to both as an editor and as a programming language; even seemingly obvious distinctions (e.g., application vs. programming language) were not necessarily always clear. ⑆,┨[pg 204]┣, If EMACS was an application written in TECO qua programming language, then it would seem that EMACS should have its own copyright, distinct from any other program written in TECO. But if EMACS was an extension or modification of TECO qua editor, then it would seem that EMACS was a derivative work and would require the explicit permission of the copyright holder.
@@ -8388,7 +7843,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A5A68A99DD73A34BFFE9578195FE5B45DE8359A5242E0191BEEB0C642B313452
.has: links notes_reg
@@ -8401,7 +7855,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EB9CD9852C35DAC6716927AC4232DD17432552EB315F037BDE0B53FD97110225
.has: notes_reg
@@ -8413,7 +7866,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 683CAE387AFFF27F27D677790EEE88A4A7B6DFE3301ED222F2F823F72510364B
.has: links notes_reg
@@ -8425,7 +7877,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8C15CF7E54D4CE2FCF246D35676B057FBB06BB5852652529E7C0AF0D3383C9C0
| In short, the interplay between new statutes and their settlement in court or in practice was a structural uncertainty that set novel constraints on the meaning of copyright, and especially on the norms and forms of permission and reuse. GNU EMACS 15.34 was the safest option—a completely new version that performed the same tasks, but in a different manner, using different algorithms and code.
@@ -8436,7 +7887,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6570E193A96975EB29625B2F44870542DB55607D6C27166925900B1C773025DE
| Even as it resolved the controversy, however, GNU EMACS posed new problems for Stallman: how would the EMACS commune survive if it wasn’t clear whether one could legally use another person’s code, even if freely contributed? Was Gosling’s action in selling work by others to Unipress legitimate? Would Stallman be able to enforce its opposite, namely, prevent people from commercializing EMACS code they contributed to him? How would Stallman avoid the future possibility of his own volunteers and contributors later asserting that he had infringed on their copyright?
@@ -8447,7 +7897,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2133BFAF9263676F4DEEBAABB22CD85B7399813F0E579F3A8A83ACB828943C4C
.has: links notes_reg
@@ -8459,7 +7908,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 355E71ADABB577FA3CBD3C93F2AA3F5C905DC41BDB18A061E1EDE406EC71704A
| The interplay between technical and legal issues and “ethical” concerns was reflected in the practical issues of fear, intimidation, and common-sense (mis)understandings of intellectual-property ⑆,┨[pg 206]┣, law. Zimmerman’s veiled threats of legal liability were directed not only at Stallman but at anyone who was using the program Stallman had written; breaking the law was, for Zimmerman, an ethical lapse, not a problem of uncertainty and change. Whether or not such an interpretation of the law was correct, it did reveal the mechanisms whereby a low level of detailed knowledge about the law—and a law in flux, at that (not to mention the litigious reputation of the U.S. legal system worldwide)—often seemed to justify a sense that buying software was simply a less risky option than acquiring it for free. Businesses, not customers, it was assumed, would be liable for such infringements. By the same token, the sudden concern of software programmers (rather than lawyers) with the detailed mechanics of copyright law meant that a very large number of people found themselves asserting common-sense notions, only to be involved in a flame war over what the copyright law “actually says.”
@@ -8470,7 +7918,6 @@
.ancestors: 1 290 0 0 514 585 0 0
.ancestors_collapsed: 1 290 514 585 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1E894CECB136128BC173F57E94AA9A4551121C7B336C5DA0AEED9C513DCA8C78
.has: notes_reg
@@ -8499,7 +7946,6 @@
.ancestors: 1 290 0 0 514 607 0 0
.ancestors_collapsed: 1 290 514 607 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4BBA4DBC267CE416FA63187F048148A84EA36BDF546B7B0497F352BDFEF95AF5
| The rest of the story is quickly told: Stallman resigned from the AI Lab at MIT and started the Free Software Foundation in 1985; he created a raft of new tools, but ultimately no full UNIX operating system, and issued General Public License 1.0 in 1989. In 1990 he was awarded a MacArthur “genius grant.” During the 1990s, he was involved in various high-profile battles among a new generation of hackers; those controversies included the debate around Linus Torvalds’s creation of Linux (which Stallman insisted be referred to as GNU/Linux), the forking of EMACS into Xemacs, and Stallman’s own participation in—and exclusion from—conferences and events devoted to Free Software. ⑆,┨[pg 207]┣,
@@ -8510,7 +7956,6 @@
.ancestors: 1 290 0 0 514 607 0 0
.ancestors_collapsed: 1 290 514 607 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D6D87FB8E6E9652993408C6BB8CC1D41266273FABA65AFC6C996738A39B0AB32
| Between 1986 and 1990, the Free Software Foundation and its software became extremely well known among geeks. Much of this had to do with the wealth of software that they produced and distributed via Usenet and Arpanet. And as the software circulated and was refined, so were the new legal constraints and the process of teaching users to understand what they could and could not do with the software—and why it was not in the public domain.
@@ -8521,7 +7966,6 @@
.ancestors: 1 290 0 0 514 607 0 0
.ancestors_collapsed: 1 290 514 607 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B755AD5DC1368A00058B68925992DCEE6B83975B100D7171A4ABA094FC24C000
.has: links notes_reg
@@ -8533,7 +7977,6 @@
.ancestors: 1 290 0 0 514 607 0 0
.ancestors_collapsed: 1 290 514 607 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5C8E76690C1F9FF0B086591526ED134469FA790709F6ED68CF38D66801B68989
.has: links notes_reg
@@ -8545,7 +7988,6 @@
.ancestors: 1 290 0 0 514 607 0 0
.ancestors_collapsed: 1 290 514 607 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8AB066A82AD15FD1C8A691FEF0C716E9807BE7E289DFBFA5F6E8AB74DC953526
| The creation of the GPL and the Free Software Foundation are often understood as expressions of the hacker ethic, or of Stallman’s ideological commitment to freedom. But the story of EMACS and the complex technical and legal details that structure it illustrate how the GPL is more than just a hack: it was a novel, privately ordered legal “commune.” It was a space thoroughly independent of, but insinuated into the existing bedrock of rules and practices of the world of corporate and university software, and carved out of the slippery, changing substance of intellectual-property statutes. At a time when the giants of the software industry were fighting to create a different kind of openness—one that preserved and would even strengthen existing relations of intellectual property—this ⑆,┨[pg 208]┣, hack was a radical alternative that emphasized the sovereignty not of a national or corporate status quo, but of self-fashioning individuals who sought to opt out of that national-corporate unity. The creation of the GNU GPL was not a return to a golden age of small-scale communities freed from the dominating structures of bureaucratic modernity, but the creation of something new out of those structures. It relied on and emphasized, not their destruction, but their stability—at least until they are no longer necessary.
@@ -8556,7 +7998,6 @@
.ancestors: 1 290 0 0 514 607 0 0
.ancestors_collapsed: 1 290 514 607 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0E6FFE1A73B239A0042EB932C1DF475C077C4C1A8BDE510C98A685A3C0B5E394
| The significance of the GPL is due to its embedding within and emergence from the legal and technical infrastructure. Such a practice of situated reworking is what gives Free Software—and perhaps all forms of engineering and creative practice—its warp and weft. Stallman’s decision to resign from the AI Lab and start the Free Software Foundation is a good example; it allowed Stallman no only to devote energy to Free Software but also to formally differentiate the organizations, to forestall at least the potential threat that MIT (which still provided him with office space, equipment, and network connection) might decide to claim ownership over his work. One might think that the hacker ethic and the image of self-determining free individuals would demand the total absence of organizations, but it requires instead their proliferation and modulation. Stallman himself was never so purely free: he relied on the largesse of MIT’s AI Lab, without which he would have had no office, no computer, no connection to the network, and indeed, for a while, no home.
@@ -8567,7 +8008,6 @@
.ancestors: 1 290 0 0 514 607 0 0
.ancestors_collapsed: 1 290 514 607 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 99B6F474A2968E80C0A51E69A68F872CE7EB38D79B183B2E73D9DD0A3327DEEC
| The Free Software Foundation represents a recognition on his part that individual and communal independence would come at the price of a legally and bureaucratically recognizable entity, set apart from MIT and responsible only to itself. The Free Software Foundation took a classic form: a nonprofit organization with a hierarchy. But by the early 1990s, a new set of experiments would begin that questioned the look of such an entity. The stories of Linux and Apache reveal how these ventures both depended on the work of the Free Software Foundation and departed from the hierarchical tradition it represented, in order to innovate new similarly embedded sociotechnical forms of coordination.
@@ -8578,7 +8018,6 @@
.ancestors: 1 290 0 0 514 607 0 0
.ancestors_collapsed: 1 290 514 607 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1195C1D0D9B62A94A6191D6034924BAF2AC6D68B4BCE088B582E1F64CA6BB1CE
| The EMACS text editor is still widely used, in version 22.1 as of 2007, and ported to just about every conceivable operating system. The controversy with Unipress has faded into the distance, as newer and more intense controversies have faced Stallman and Free Software, ⑆,┨[pg 209]┣, but the GPL has become the most widely used and most finely scrutinized of the legal licenses. More important, the EMACS controversy was by no means the only one to have erupted in the lives of software programmers; indeed, it has become virtually a rite of passage for young geeks to be involved in such debates, because it is the only way in which the technical details and the legal details that confront geeks can be explored in the requisite detail. Not all such arguments end in the complete rewriting of source code, and today many of them concern the attempt to convince or evangelize for the release of source code under a Free Software license. The EMACS controversy was in some ways a primal scene—a traumatic one, for sure—that determined the outcome of many subsequent fights by giving form to the Free Software license and its uses.
@@ -8627,7 +8066,6 @@
.ancestors: 1 290 0 0 616 0 0 0
.ancestors_collapsed: 1 290 616 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 9CC4F1CAC51334B3112AA1085B069010FD5D79AA5D6F025BCAA4E62E715C7A56
.has: notes_reg
@@ -8639,7 +8077,6 @@
.ancestors: 1 290 0 0 616 0 0 0
.ancestors_collapsed: 1 290 616 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: B50E16CB6DFD138EB053639A04769B21164804C4E16A3A5E8D13A0AEF9293DFB
.has: links notes_reg
@@ -8651,7 +8088,6 @@
.ancestors: 1 290 0 0 616 0 0 0
.ancestors_collapsed: 1 290 616 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 674A8F84382A6FE6474308210D1A8B443CCEAED3C1EDF8B0861CA568B882B7BC
| Adaptability does not mean randomness or anarchy, however; it is a very specific way of resolving the tension between the individual curiosity and virtuosity of hackers, and the collective coordination necessary to create and use complex software and networks. No man is an island, but no archipelago is a nation, so to speak. Adaptability preserves the “joy” and “fun” of programming without sacrificing the careful engineering of a stable product. Linux and Apache should be understood as the results of this kind of coordination: experiments with adaptability that have worked, to the surprise of many who have insisted that complexity requires planning and hierarchy. Goals and planning are the province of governance—the practice of goal-setting, orientation, and definition of control—but adaptability is the province of critique, and this is why Free Software is a recursive public: it stands outside power and offers powerful criticism in the form of working alternatives. It is not the domain of the new—after all Linux is just a rewrite of UNIX—but the domain of critical and responsive public direction of a collective undertaking.
@@ -8662,7 +8098,6 @@
.ancestors: 1 290 0 0 616 0 0 0
.ancestors_collapsed: 1 290 616 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 6959ECB6D70C307FB71A9DB215B2C12E1A59D0B5319143EA2545BDED8E413A7E
| Linux and Apache are more than pieces of software; they are organizations of an unfamiliar kind. My claim that they are “recursive publics” is useful insofar as it gives a name to a practice that is neither corporate nor academic, neither profit nor nonprofit, neither governmental nor nongovernmental. The concept of recursive public includes, within the spectrum of political activity, the creation, modification, and maintenance of software, networks, and legal documents. While a “public” in most theories is a body of ⑆,┨[pg 212]┣, people and a discourse that give expressive form to some concern, “recursive public” is meant to suggest that geeks not only give expressive form to some set of concerns (e.g., that software should be free or that intellectual property rights are too expansive) but also give concrete infrastructural form to the means of expression itself. Linux and Apache are tools for creating networks by which expression of new kinds can be guaranteed and by which further infrastructural experimentation can be pursued. For geeks, hacking and programming are variants of free speech and freedom of assembly.
@@ -8690,7 +8125,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 15AE3C9474E5BD63764DDDB7D6039D217593B90764C7576DB4F9A65D0E4275AB
.has: notes_reg
@@ -8702,7 +8136,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 483CA3608FD8C9DCAF727FC09393B4F54712791C63B0FB35CE97F1FADFFC45A5
| Linux and Apache are both experiments in coordination. Both projects evolved decision-making systems through experiment: a voting system in Apache’s case and a structured hierarchy of decision-makers, with Linus Torvalds as benevolent dictator, in Linux’s case. Both projects also explored novel technical tools for coordination, especially Source Code Management (SCM) tools such as Concurrent Versioning System (cvs). Both are also cited as exemplars of how “fun,” “joy,” or interest determine individual participation and of how it is possible to maintain and encourage that participation and mutual aid instead of narrowing the focus or eliminating possible routes for participation.
@@ -8713,7 +8146,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FAC7A57332090A2F8E3332400F3A79D17127B00CC356429EF1E1B50AA3D02B6D
| Beyond these specific experiments, the stories of Linux and Apache are detailed here because both projects were actively central to the construction and expansion of the Internet of the 1990s by allowing a massive number of both corporate and noncorporate sites to cheaply install and run servers on the Internet. Were Linux and Apache nothing more than hobbyist projects with a few thousand ⑆,┨[pg 213]┣, interested tinkerers, rather than the core technical components of an emerging planetary network, they would probably not represent the same kind of revolutionary transformation ultimately branded a “movement” in 1998-99.
@@ -8724,7 +8156,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 480FD716839BF7CEA40F5C9C61B33545CBEBAF0238A13129A1C2F6F2AE8A16B8
.has: links notes_reg
@@ -8739,7 +8170,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AC69D903ED0A7AFA7E6EE8E600C27AEFCCCF3C7EDE15025169AEEC1364FE1F32
| When Torvalds started, he was blessed with an eager audience of hackers keen on seeing a UNIX system run on desktop computers and a personal style of encouragement that produced enormous positive feedback. Torvalds is often given credit for creating, through his “management style,” a “new generation” of Free Software—a younger generation than that of Stallman and Raymond. Linus and Linux are not in fact the causes of this change, but the results of being at the right place at the right time and joining together a number of existing components. Indeed, the title of Torvalds’s semi-autobiographical reflection on Linux—Just for Fun: The Story of an Accidental Revolutionary—captures some of the character of its genesis.
@@ -8750,7 +8180,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1F0E2E16CF3678D7FD0AB12A64C7D9465E1D803ACA7EEE94C50549C6D69F7B56
.has: notes_reg
@@ -8762,7 +8191,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 273AB1F252E6A2854AA71ED723255D106EE71710296E6C067F12E5103CC9327B
.has: notes_reg
@@ -8774,7 +8202,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 34FDA5D9E96118E51052A06BFA705CD70CD97BC9BA1B01369E7142278055DCBD
| During this period (roughly 1987 to 1993), the Free Software Foundation attained a mythic cult status—primarily among UNIX and EMACS users. Part of this status was due to the superiority of the tools Stallman and his collaborators had already created: the GNU C Compiler (gcc), GNU EMACS, the GNU Debugger (gdb), GNU Bison, and loads of smaller utilities that replaced the original AT&T UNIX versions. The GNU GPL had also acquired a life of its own by this time, having reached maturity as a license and become the de facto choice for those committed to Free Software and the Free Software Foundation. By 1991, however, the rumors of the imminent appearance of Stallman’s replacement UNIX operating system had started to sound empty—it had been six years since his public announcement of his intention. Most hackers were skeptical of Stallman’s operating-system project, even if they acknowledged the success of all the other tools necessary to create a full-fledged operating system, and Stallman himself was stymied by the development ⑆,┨[pg 215]┣, of one particular component: the kernel itself, called GNU Hurd.
@@ -8796,7 +8223,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3E75A27CB7424A2FBE8679B3251A3F4B2F606E0D2C02DF990D6BA10CCE2B509D
.has: links notes_reg
@@ -8809,7 +8235,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D3DA593C0D84137769A73DFED32F548BCFD73D5747481A80EB14F1ACA01B8F83
| The fact of Linus Torvalds’s pedagogical embedding in the world of UNIX, Minix, the Free Software Foundation, and the Usenet should not be underestimated, as it often is in hagiographical accounts of the Linux operating system. Without this relatively robust moral-technical order or infrastructure within which it was possible to be at the right place at the right time, Torvalds’s late-night dorm-room project would have amounted to little more than that—but the pieces were all in place for his modest goals to be transformed into something much more significant.
@@ -8820,7 +8245,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C8FFEF96816332095A94B730886FAFE5F79136FEF9F5337054C3DD00B780F5C0
| Consider his announcement on 25 August 1991:
@@ -8831,7 +8255,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 78FB5E17F96C5A6AD942451CF52B1361357DB0AF99F2647D7241F21A2316E24B
.indent: 1 1
@@ -8843,7 +8266,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 05842809E003A6F7ACE8996063BB4D2F71C3318D26001FC485DD98920249C744
.indent: 1 1
@@ -8855,7 +8277,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AA5663612BFECAF662ED11A84BF206C6B367DC8C5BD09E44C94587F0BE7AD0A6
.indent: 1 1
@@ -8879,7 +8300,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 46EBE213866D2CE4ADAA20E8F0F07D4D2756A4AC5F5A73D3978CE81E8EEB0DFD
| Torvalds’s announcement is telling as to where his project fit into the existing context: “just a hobby,” not “big and professional like gnu” (a comment that suggests the stature that Stallman and the Free Software Foundation had achieved, especially since they were in reality anything but “big and professional”). The announcement was posted to the Minix list and thus was essentially directed at Minix users; but Torvalds also makes a point of insisting that the system would be free of cost, and his postscript furthermore indicates that it would be free of Minix code, just as Minix had been free of AT&T code.
@@ -8890,7 +8310,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 766E509D4AB9DA6BAE541500A59FC72CDC9B41B476105F223310241B2A876EC0
| Torvalds also mentions that he has ported “bash” and “gcc,” software created and distributed by the Free Software Foundation and tools essential for interacting with the computer and compiling new versions of the kernel. Torvalds’s decision to use these utilities, rather than write his own, reflects both the boundaries of his project (an operating-system kernel) and his satisfaction with the availability and reusability of software licensed under the GPL.
@@ -8901,7 +8320,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C3485F6BA5468E258111EAAC123EADBA9F401ED81E33B8C15D4B0A6E4FA95153
| So the system is based on Minix, just as Minix had been based on UNIX—piggy-backed or bootstrapped, rather than rewritten in an entirely different fashion, that is, rather than becoming a different kind of operating system. And yet there are clearly concerns about the need to create something that is not Minix, rather than simply extending or “debugging” Minix. This concern is key to understanding what happened to Linux in 1991.
@@ -8912,7 +8330,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DD3BF2D926B5A96207F1BCD8B4C9CA1A9260C729B9E769B5DD9D32F8F3510524
.has: links notes_reg
@@ -8935,7 +8352,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 492C6975A1A565BD68F665E2A1A0C6C304FD9D274898A6BB25417BCCEF8B2E58
.has: links notes_reg
@@ -8947,7 +8363,6 @@
.ancestors: 1 290 0 0 616 621 0 0
.ancestors_collapsed: 1 290 616 621 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F9FEF6FFFE122ADC02421EB2F9BD62A26A86BC08FD805CC0AD24783DFD7DDD0B
| The most significant aspect of Torvalds’s initial message, however, is his request: “I’d like to know what features most people would want. Any suggestions are welcome, but I won’t promise I’ll implement them.” Torvalds’s announcement and the subsequent interest it generated clearly reveal the issues of coordination and organization that would come to be a feature of Linux. The reason Torvalds had so many eager contributors to Linux, from the very start, was because he enthusiastically took them off of Tanenbaum’s hands.
@@ -8975,7 +8390,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AFDDB8C483C7A57D5EE3E7229F5855C0699541B924F890E923A5972DC89E499A
.has: links notes_reg
@@ -8987,7 +8401,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0CBCADC5A22BC00C96D9979010BA20C70CF0569BBECB4E9803B2F2BA72AE58DE
| So while Tanenbaum was in sympathy with the Free Software Foundation’s goals (insofar as he clearly wanted people to be able to use, update, enhance, and learn from software), he was not in sympathy with the idea of having 40,000 strangers make his software “better.” Or, to put it differently, the goals of Minix remained those of a researcher and a textbook author: to be useful in classrooms and cheap enough to be widely available and usable on the largest number of cheap computers.
@@ -8998,7 +8411,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0B94F13BE63886FAF6EC859D31CEC9D1A4B23C1A39A3F0D14474D46D2DEE4A1A
| By contrast, Torvalds’s “fun” project had no goals. Being a cocky nineteen-year-old student with little better to do (no textbooks to write, no students, grants, research projects, or committee meetings), Torvalds was keen to accept all the ready-made help he could find to make his project better. And with 40,000 Minix users, he had a more or less instant set of contributors. Stallman’s audience for EMACS in the early 1980s, by contrast, was limited to about a hundred distinct computers, which may have translated into thousands, but certainly not tens of thousands of users. Tanenbaum’s work in creating a generation of students who not only understood the internals of an operating system but, more specifically, understood the internals of the UNIX operating system created a huge pool of competent and eager UNIX hackers. It was the work of porting UNIX not only to various machines but to a generation of minds as well that set the stage for this event—and this is an essential, though often overlooked component of the success of Linux.
@@ -9009,7 +8421,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FBF6A5CDC4D9B97CDE87227D00AF555A2789F64ED8BFEE73AE974664A23B087E
.has: links notes_reg
@@ -9021,7 +8432,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CFD3D01F9ABA8B5D83B2264D45C03852DB0F6149AA28AD0519EFCF6614E91A52
| Both Tanenbaum and Torvalds operated under a model of coordination in which one person was ultimately responsible for the entire project: Tanenbaum oversaw Minix and ensured that it remained true to its goals of serving a pedagogical audience; Torvalds would oversee Linux, but he would incorporate as many different features as users wanted or could contribute. Very quickly—with a pool of 40,000 potential contributors—Torvalds would be in the same position Tanenbaum was in, that is, forced to make decisions about the goals of Linux and about which enhancements would go into it and which would not. What makes the story of Linux so interesting to observers is that it appears that Torvalds made no decision: he accepted almost everything.
@@ -9032,7 +8442,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6521F65E5A158EBD57CD91AEE828F1FB5DD1D2CD89C160E7C768F4A200F478F6
| Tanenbaum’s goals and plans for Minix were clear and autocratically formed. Control, hierarchy, and restriction are after all appropriate in the classroom. But Torvalds wanted to do more. He wanted to go on learning and to try out alternatives, and with Minix as the only widely available way to do so, his decision to part ways starts to make sense; clearly he was not alone in his desire to explore and extend what he had learned. Nonetheless, Torvalds faced the problem of coordinating a new project and making similar decisions about its direction. On this point, Linux has been the subject of much reflection by both insiders and outsiders. Despite images of Linux as either an anarchic bazaar or an autocratic dictatorship, the reality is more subtle: it includes a hierarchy of contributors, maintainers, and “trusted lieutenants” and a sophisticated, informal, and intuitive sense of “good taste” gained through reading and incorporating the work of co-developers.
@@ -9043,7 +8452,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C39E3DBC76C493D899992D305724AF8888A21D814E40F2BF99A1BF28F1E0A371
.has: notes_reg
@@ -9055,7 +8463,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2C1EE47C3F92AFF3DC01099E0755D0D649622943FB28FE7C64952A6671723296
| Almost all of the decisions made by Torvalds and lieutenants were of a single kind: whether or not to incorporate a piece of code submitted by a volunteer. Each such decision was technically complex: insert the code, recompile the kernel, test to see if it works or if it produces any bugs, decide whether it is worth keeping, issue a new version with a log of the changes that were made. Although the various official leaders were given the authority to make such changes, coordination was still technically informal. Since they were all working on the same complex technical object, one person (Torvalds) ultimately needed to verify a final version, containing all the subparts, in order to make sure that it worked without breaking.
@@ -9066,7 +8473,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DCA9994CE5055C9DC383D149D1FFA57ECDFF00B7BFC0390ACEA7F16225241AD2
| Such decisions had very little to do with any kind of design goals or plans, only with whether the submitted patch “worked,” a term that reflects at once technical, aesthetic, legal, and design criteria that are not explicitly recorded anywhere in the project—hence, the privileging of adaptability over planning. At no point were the patches assigned or solicited, although Torvalds is justly famous for encouraging people to work on particular problems, but only if they wanted to. As a result, the system morphed in subtle, unexpected ways, diverging from its original, supposedly backwards “monolithic” design and into a novel configuration that reflected the interests of the volunteers and the implicit criteria of the leaders.
@@ -9077,7 +8483,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 81A491AC4880DFE5CD2E8F09D245216D8BBCE3D21D1D53D9C6EF8C3A7AB836FA
| By 1995-96, Torvalds and lieutenants faced considerable challenges with regard to hierarchy and decision-making, as the project had grown in size and complexity. The first widely remembered response to the ongoing crisis of benevolent dictatorship in Linux was the creation of “loadable kernel modules,” conceived as a way to release some of the constant pressure to decide which patches would be incorporated into the kernel. The decision to modularize ⑆,┨[pg 221]┣, Linux was simultaneously technical and social: the software-code base would be rewritten to allow for external loadable modules to be inserted “on the fly,” rather than all being compiled into one large binary chunk; at the same time, it meant that the responsibility to ensure that the modules worked devolved from Torvalds to the creator of the module. The decision repudiated Torvalds’s early opposition to Tanenbaum in the “monolithic vs. microkernel” debate by inviting contributors to separate core from peripheral functions of an operating system (though the Linux kernel remains monolithic compared to classic microkernels). It also allowed for a significant proliferation of new ideas and related projects. It both contracted and distributed the hierarchy; now Linus was in charge of a tighter project, but more people could work with him according to structured technical and social rules of responsibility.
@@ -9088,7 +8493,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2F190E47B44165AB1B414C7BCB5EDE3D5D7344CC7B28B7EA8F9D282F1FBF0009
| Creating loadable modules changed the look of Linux, but not because of any planning or design decisions set out in advance. The choice is an example of the privileged adaptability of the Linux, resolving the tension between the curiosity and virtuosity of individual contributors to the project and the need for hierarchical control in order to manage complexity. The commitment to adaptability dissolves the distinction between the technical means of coordination and the social means of management. It is about producing a meaningful whole by which both people and code can be coordinated—an achievement vigorously defended by kernel hackers.
@@ -9099,7 +8503,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 042923E283AEEC639C1B320C1EF7BAD7F28388F44819D988F8BE3D2B8FA89E5A
| The adaptable organization and structure of Linux is often described in evolutionary terms, as something without teleological purpose, but responding to an environment. Indeed, Torvalds himself has a weakness for this kind of explanation.
@@ -9110,7 +8513,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 87868D209CDE87BC633B454934821CBCCDF581326916B815FED0F2FC12DC5801
.indent: 1 1
@@ -9122,7 +8524,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9CFC6B7631825FBFEC606B559CE4CEC6E5ECB047E9D188F31A2BF646E78BB4DF
.indent: 1 1
@@ -9134,7 +8535,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E187A4246975AC55CBD471B064D68BBD9E27D3D5067EAA19A4C381BBBA291FE8
.indent: 1 1
@@ -9146,7 +8546,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 20542B084680256D857D0918721ACD146AAF8930EF8410A062C254E290EE69EE
.indent: 1 1
@@ -9170,7 +8569,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 870352381E1D53010B442CE95A694C99FE5EEF441A3AD9DE6BB4555C6083FE26
| Adaptability does not answer the questions of intelligent design. Why, for example, does a car have four wheels and two headlights? Often these discussions are polarized: either technical objects are designed, or they are the result of random mutations. What this opposition overlooks is the fact that design and the coordination of collaboration go hand in hand; one reveals the limits and possibilities of the other. Linux represents a particular example of such a problematic—one that has become the paradigmatic case of Free Software—but there have been many others, including UNIX, for which the engineers created a system that reflected the distributed collaboration of users around the world even as the lawyers tried to make it conform to legal rules about licensing and practical concerns about bookkeeping and support.
@@ -9181,7 +8579,6 @@
.ancestors: 1 290 0 0 616 642 0 0
.ancestors_collapsed: 1 290 616 642 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9D292A38928B5B1FB71CA2694D18F638261684C65F42058DEE82B6EDD2A9F607
| Because it privileges adaptability over planning, Linux is a recursive public: operating systems and social systems. It privileges openness to new directions, at every level. It privileges the right to propose changes by actually creating them and trying to convince others to use and incorporate them. It privileges the right to fork the software into new and different kinds of systems. Given what it privileges, Linux ends up evolving differently than do systems whose life and design are constrained by corporate organization, or by strict engineering design principles, or by legal or marketing definitions of products—in short, by clear goals. What makes this distinction between the goal-oriented design principle and the principle of adaptability important is its relationship to politics. Goals and planning are the subject of negotiation and consensus, or of autocratic decision-making; adaptability is the province of critique. It should be remembered that Linux is by no means an attempt to create something radically new; it is a rewrite of a UNIX operating system, as Torvalds points out, but one that through adaptation can end up becoming something new.
@@ -9209,7 +8606,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4893B9F68DF0D2F533E8C0862BBE1A5B8CA203E4F588C576424B24AE3EE8FBFC
| The Apache Web server and the Apache Group (now called the Apache Software Foundation) provide a second illuminating example of the how and why of coordination in Free Software of the 1990s. As with the case of Linux, the development of the Apache project illustrates how adaptability is privileged over planning ⑆,┨[pg 223]┣, and, in particular, how this privileging is intended to resolve the tensions between individual curiosity and virtuosity and collective control and decision-making. It is also the story of the progressive evolution of coordination, the simultaneously technical and social mechanisms of coordinating people and code, patches and votes.
@@ -9220,7 +8616,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 64825D5C2C82237438B54D76FBB4BD2CDDF92C7B7718184464C8BD8D884539D0
.has: links notes_reg
@@ -9232,7 +8627,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CC8CD31C0C6BBC9AC2DF7E454CC18E1C01282868360D5241CD014D0C59485AAC
| The NCSA, at the University of Illinois, Urbana-Champaign, picked up both www projects, subsequently creating both the first widely used browser, Mosaic, directed by Marc Andreessen, and httpd. Httpd was public domain up until version 1.3. Development slowed when McCool was lured to Netscape, along with the team that created Mosaic. By early 1994, when the World Wide Web had started to spread, many individuals and groups ran Web servers that used httpd; some of them had created extensions and fixed bugs. They ranged from university researchers to corporations like Wired Ventures, which launched the online version of its magazine (HotWired.com) in 1994. Most users communicated primarily through Usenet, on the comp.infosystems.www.* newsgroups, sharing experiences, instructions, and updates in the same manner as other software projects stretching back to the beginning of the Usenet and Arpanet newsgroups.
@@ -9243,7 +8637,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EE42E07722E29D0833D76C001B8FB7B3543C466E16B86A170EB2D635BA46662F
.has: links notes_reg
@@ -9256,7 +8649,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A6A6F798470DB200AB599246D89EFE75D135C7A5F8EB33900E8FF6ED8EC2C4F3
.has: notes_reg
@@ -9268,7 +8660,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 28E71DDE31BB5356C0D9354929364B3D76C7FE1ACE48D738E9370591EDBC4C6F
.has: notes_reg
@@ -9280,7 +8671,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E96340A75D4C2BDEC5E66182046F6801A46190B5C78A344AABEC4CA833887525
| The need for process arose more or less organically, as the group developed mechanisms for managing the various patches: assigning them IDs, testing them, and incorporating them “by hand” into the main source-code base. As this happened, members of the list would occasionally find themselves lost, confused by the process or the efficiency of other members, as in this message from Andrew Wilson concerning Cliff Skolnick’s management of the list of bugs:
@@ -9291,7 +8681,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5D13E563996019BEA3B47A5E81B415C8418BA846A2706F917DB53B060086DB1C
.indent: 1 1
@@ -9303,7 +8692,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EE4DC2A5401250366C8F03B2739EB34EBF83FA2CC3006A8D3B49E93D01C8679F
.indent: 1 1
@@ -9316,7 +8704,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9F080D15347A9DD551F50944D7727358BEFFEFE35BD3A612279E05685221DFDE
.has: notes_reg
@@ -9328,7 +8715,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A4F7B23D7A6B6584D8FFF5EF1B79E9FA5F866103C39369FA03FC5C26550D13A4
.has: notes_reg
@@ -9358,7 +8744,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7253AF52D84616B0BBB5A0A812DDB61A89EF8D83EAF31877116246114EB45DB2
.has: notes_reg
@@ -9370,7 +8755,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EF3DEE897EC348F1F6382E1BBC46763348635E4FADA74499301BD47CA7139B02
| The significance of the patch-and-vote system was that it clearly represented the tension between the virtuosity of individual developers and a group process aimed at creating and maintaining a common piece of software. It was a way of balancing the ability of each separate individual’s expertise against a common desire to ship and promote a stable, bug-free, public-domain Web server. As Roy Fielding and others would describe it in hindsight, this tension was part of Apache’s advantage.
@@ -9381,7 +8765,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3B9837F0DB31C52DC8DD1DD73C93B410E33088D5F6911F3FCBC6D0C339CF47F2
.indent: 1 1
@@ -9394,7 +8777,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 22AE4C6A6CCAAAB8361343CA0BABAC1578E52C1A8591A54B38662A16A657F31C
| Although openness is widely touted as the key to the innovations of Apache, the claim is somewhat disingenuous: patches are just that, patches. Any large-scale changes to the code could not be accomplished by applying patches, especially if each patch must be subjected to a relatively harsh vote to be included. The only way to make sweeping changes—especially changes that require iteration and testing to get right—is to engage in separate “branches” of a project or to differentiate between internal and external releases—in short, to fork the project temporarily in hopes that it would soon rejoin its stable parent. Apache encountered this problem very early on with the “Shambhala” rewrite of httpd by Robert Thau. ⑆,┨[pg 227]┣,
@@ -9405,7 +8787,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5AAE03E22CC5BC94361F0A58E7D46EBBEB2B9033CEC0BA1BC321BBCE44FF853F
.has: notes_reg
@@ -9417,7 +8798,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8241438EACB5A6FE3DDBE23757DB95A5326D283E119D56E842E8A105CDF4E1F6
.has: notes_reg
@@ -9429,7 +8809,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6F1512BBCE94A148093551CAB627E7C67D91D34AC58C623E9A6B74F35995295B
.indent: 1 1
@@ -9442,7 +8821,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5DBCA705291515F53E72F5F7074669D9948F9DEDE6BF76D22A268327D9699623
.has: notes_reg
@@ -9454,7 +8832,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 282A8CA109C7B9C2CA0FB20D9376C4518DC46E9FC0B02A52E5B46ABEED7E93E4
.has: notes_reg
@@ -9466,7 +8843,6 @@
.ancestors: 1 290 0 0 616 661 0 0
.ancestors_collapsed: 1 290 616 661 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 626BEE784DA4C8B0B4B1EE2682A59737403489A0542D445475E797540D4713A3
| In the case of Apache one can see how coordination in Free Software is not just an afterthought or a necessary feature of distributed work, but is in fact at the core of software production itself, governing the norms and forms of life that determine what will count as good software, how it will progress with respect to a context and ⑆,┨[pg 229]┣, background, and how people will be expected to interact around the topic of design decisions. The privileging of adaptability brings with it a choice in the mode of collaboration: it resolves the tension between the agonistic competitive creation of software, such as Robert Thau’s creation of Shambhala, and the need for collective coordination of complexity, such as Harthill’s plea for collaboration to reduce duplicated or unnecessary work.
@@ -9494,7 +8870,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1F28B464C6370318FD4BFE91E8ADD48085EF189C151860E97509FD6DC45EE7A5
| The technical and social forms that Linux and Apache take are enabled by the tools they build and use, from bug-tracking tools and mailing lists to the Web servers and kernels themselves. One such tool plays a very special role in the emergence of these organizations: Source Code Management systems (SCMs). SCMs are tools for coordinating people and code; they allow multiple people in dispersed locales to work simultaneously on the same object, the same source code, without the need for a central coordinating overseer and without the risk of stepping on each other’s toes. The history of SCMs—especially in the case of Linux—also illustrates the recursive-depth problem: namely, is Free Software still free if it is created with non-free tools?
@@ -9505,7 +8880,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F922F87DD384401C39B74286FC1DA97902A1540228179753F56D08A07D355F31
| SCM tools, like the Concurrent Versioning System (cvs) and Subversion, have become extremely common tools for Free Software programmers; indeed, it is rare to find a project, even a project conducted by only one individual, which does not make use of these tools. Their basic function is to allow two or more programmers to work on the same files at the same time and to provide feedback on where their edits conflict. When the number of programmers grows large, an SCM can become a tool for managing complexity. It keeps track of who has “checked out” files; it enables users to lock files if they want to ensure that no one else makes changes at the same time; it can keep track of and display the conflicting changes made by two users to the same file; it can be used to create “internal” forks or “branches” that may be incompatible with each other, but still allows programmers to try out new things and, if all goes well, merge the branches into the trunk later on. In sophisticated forms it can be used to “animate” successive changes to a piece of code, in order to visualize its evolution. ⑆,┨[pg 230]┣,
@@ -9516,7 +8890,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F69E5897575FC7DE59970671084D517E1C8939EC06F1CFB9DFE896FF569BCDCC
| Beyond mere coordination functions, SCMs are also used as a form of distribution; generally SCMs allow anyone to check out the code, but restrict those who can check in or “commit” the code. The result is that users can get instant access to the most up-to-date version of a piece of software, and programmers can differentiate between stable releases, which have few bugs, and “unstable” or experimental versions that are under construction and will need the help of users willing to test and debug the latest versions. SCM tools automate certain aspects of coordination, not only reducing the labor involved but opening up new possibilities for coordination.
@@ -9527,7 +8900,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 908EB4E6DE27D3A8FE29C3D1D5C57EB33D44EEEA78AC27606B28F2F68E709753
| The genealogy of SCMs can be seen in the example of Ken Thompson’s creation of a diff tape, which he used to distribute changes that had been contributed to UNIX. Where Thompson saw UNIX as a spectrum of changes and the legal department at Bell Labs saw a series of versions, SCM tools combine these two approaches by minutely managing the revisions, assigning each change (each diff) a new version number, and storing the history of all of those changes so that software changes might be precisely undone in order to discover which changes cause problems. Written by Douglas McIlroy, “diff” is itself a piece of software, one of the famed small UNIX tools that do one thing well. The program diff compares two files, line by line, and prints out the differences between them in a structured format (showing a series of lines with codes that indicate changes, additions, or removals). Given two versions of a text, one could run diff to find the differences and make the appropriate changes to synchronize them, a task that is otherwise tedious and, given the exactitude of source code, prone to human error. A useful side-effect of diff (when combined with an editor like ed or EMACS) is that when someone makes a set of changes to a file and runs diff on both the original and the changed file, the output (i.e., the changes only) can be used to reconstruct the original file from the changed file. Diff thus allows for a clever, space-saving way to save all the changes ever made to a file, rather than retaining full copies of every new version, one saves only the changes. Ergo, version control. diff—and programs like it—became the basis for managing the complexity of large numbers of programmers working on the same text at the same time.
@@ -9538,7 +8910,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E85DF57AF512C1EE152E2F4023B3997EAB49960AB4D4A44234304B4F2E959924
.has: notes_reg
@@ -9550,7 +8921,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F15F79579F202B05C55803FCF823DC1B9E5D9ED1667562B588067427F3F7F91E
| In order to add sophistication to RCS, Dick Grune, at the Vrije Universiteit, Amsterdam, began writing scripts that used RCS as a multi-user, Internet-accessible version-control system, a system that eventually became the Concurrent Versioning System. cvs allowed multiple users to check out a copy, make changes, and then commit those changes, and it would check for and either prevent or flag conflicting changes. Ultimately, cvs became most useful when programmers could use it remotely to check out source code from anywhere on the Internet. It allowed people to work at different speeds, different times, and in different places, without needing a central person in charge of checking and comparing the changes. cvs created a form of decentralized version control for very-large-scale collaboration; developers could work offline on software, and always on the most updated version, yet still be working on the same object.
@@ -9561,7 +8931,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8B78EEFBAE5272DB79E60F79CAD59B3D0B941233B64EE0F5143C74D3D1606221
| Both the Apache project and the Linux kernel project use SCMs. In the case of Apache the original patch-and-vote system quickly began to strain the patience, time, and energy of participants as the number of contributors and patches began to grow. From the very beginning of the project, the contributor Paul Richards had urged the group to make use of cvs. He had extensive experience with the system in the Free-BSD project and was convinced that it provided a superior alternative to the patch-and-vote system. Few other contributors had much experience with it, however, so it wasn’t until over a year after Richards began his admonitions that cvs was eventually adopted. However, cvs is not a simple replacement for a patch-and-vote system; it necessitates a different kind of organization. Richards recognized the trade-off. The patch-and-vote system created a very high level of quality assurance and peer review of the patches that people submitted, while the cvs system allowed individuals to make more changes that might not meet the same level of quality assurance. The cvs system allowed branches—stable, testing, experimental—with different levels of quality assurance, while the patch-and-vote system was inherently directed at one final and stable version. As the case of Shambhala ⑆,┨[pg 232]┣, exhibited, under the patch-and-vote system experimental versions would remain unofficial garage projects, rather than serve as official branches with people responsible for committing changes.
@@ -9572,7 +8941,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2E98916FA93CDEF3F16D79F06E57EB1C15B86E1E21E98B56436585874BB53FEC
| While SCMs are in general good for managing conflicting changes, they can do so only up to a point. To allow anyone to commit a change, however, could result in a chaotic mess, just as difficult to disentangle as it would be without an SCM. In practice, therefore, most projects designate a handful of people as having the right to “commit” changes. The Apache project retained its voting scheme, for instance, but it became a way of voting for “committers” instead for patches themselves. Trusted committers—those with the mysterious “good taste,” or technical intuition—became the core members of the group.
@@ -9583,7 +8951,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 650F51CC1D07E6EB4FA5BA261BA5FA97D7F1A82E3C91F6075450242FA91205CD
.has: notes_reg
@@ -9595,7 +8962,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2EB32AFE3CA9A2DF2959B3BECB5201F356F89C965BE6B33EFAFAA904EC13DF58
| A great deal of yelling ensued, as nicely captured in Moody’s Rebel Code, culminating in the famous phrase, uttered by Larry McVoy: “Linus does not scale.” The meaning of this phrase is that the ability of Linux to grow into an ever larger project with increasing complexity, one which can handle myriad uses and functions (to “scale” up), is constrained by the fact that there is only one Linus Torvalds. By all accounts, Linus was and is excellent at what he does—but there is only one Linus. The danger of this situation is the danger of a fork. A fork would mean one or more new versions would proliferate under new leadership, a situation much like ⑆,┨[pg 233]┣, the spread of UNIX. Both the licenses and the SCMs are designed to facilitate this, but only as a last resort. Forking also implies dilution and confusion—competing versions of the same thing and potentially unmanageable incompatibilities.
@@ -9606,7 +8972,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D8F728D9E47682B4A43DF8846D176986DD9842D0AA64C819FD64585B60E2B33F
| The fork never happened, however, but only because Linus went on vacation, returning renewed and ready to continue and to be more responsive. But the crisis had been real, and it drove developers into considering new modes of coordination. Larry McVoy offered to create a new form of SCM, one that would allow a much more flexible response to the problem that the VGER tree represented. However, his proposed solution, called Bitkeeper, would create far more controversy than the one that precipitated it.
@@ -9617,7 +8982,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 96C7751F2DB9BFF00C8ACDE4CE4E327AF9CA14DA5A1D6BE85F84DD46E7E8F1F5
| McVoy was well-known in geek circles before Linux. In the late stages of the open-systems era, as an employee of Sun, he had penned an important document called “The Sourceware Operating System Proposal.” It was an internal Sun Microsystems document that argued for the company to make its version of UNIX freely available. It was a last-ditch effort to save the dream of open systems. It was also the first such proposition within a company to “go open source,” much like the documents that would urge Netscape to Open Source its software in 1998. Despite this early commitment, McVoy chose not to create Bitkeeper as a Free Software project, but to make it quasi-proprietary, a decision that raised a very central question in ideological terms: can one, or should one, create Free Software using non-free tools?
@@ -9628,7 +8992,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8A34C46BE72FB7E07B55F825A767E8CFD1A67B58497EA3CF995D836191846862
.has: links notes_reg
@@ -9640,7 +9003,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1D768549B247A9823632CA0006188A859E94F8BB763256F06B8F414C5C207FF8
| Torvalds emphasizes pragmatism in terms of coordination: the right tool for the job is the right tool for the job. In terms of licenses, ⑆,┨[pg 234]┣, however, such pragmatism does not play, and Torvalds has always been strongly committed to the GPL, refusing to let non-GPL software into the kernel. This strategic pragmatism is in fact a recognition of where experimental changes might be proposed, and where practices are settled. The GPL was a stable document, sharing source code widely was a stable practice, but coordinating a project using SCMs was, during this period, still in flux, and thus Bitkeeper was a tool well worth using so long as it remained suitable to Linux development. Torvalds was experimenting with the meaning of coordination: could a non-free tool be used to create Free Software?
@@ -9651,7 +9013,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A7924BF3F4D97356C994282B730510FAA520DA725ACDE98F339BB6B02BD84325
| McVoy, on the other hand, was on thin ice. He was experimenting with the meaning of Free Software licenses. He created three separate licenses for Bitkeeper in an attempt to play both sides: a commercial license for paying customers, a license for people who sell Bitkeeper, and a license for “free users.” The free-user license allowed Linux developers to use the software for free—though it required them to use the latest version—and prohibited them from working on a competing project at the same time. McVoy’s attempt to have his cake and eat it, too, created enormous tension in the developer community, a tension that built from 2002, when Torvalds began using Bitkeeper in earnest, to 2005, when he announced he would stop.
@@ -9662,7 +9023,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A3E157179D84D056C6A236305608CDB93262899DB02A4B64B5B1B51FD270C9C0
| The tension came from two sources: the first was debates among developers addressing the moral question of using non-free software to create Free Software. The moral question, as ever, was also a technical one, as the second source of tension, the license restrictions, would reveal.
@@ -9673,7 +9033,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 02DFED33A547223356F7AE25E5CDFB893DCC3E740449DA6ABB7D2D01E242C5FA
.has: links notes_reg
@@ -9685,7 +9044,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9320984609BF0EFF773335DFE99A15D2B6108912E969E5793788B6958C05F095
| The story of the VGER tree and Bitkeeper illustrate common tensions within recursive publics, specifically, the depth of the meaning of free. On the one hand, there is Linux itself, an exemplary Free Software project made freely available; on the other hand, however, there is the ability to contribute to this process, a process that is potentially constrained by the use of Bitkeeper. So long as the function of Bitkeeper is completely circumscribed—that is, completely planned—there can be no problem. However, the moment one user sees a way to change or improve the process, and not just the kernel itself, then the restrictions and constraints of Bitkeeper can come into play. While it is not clear that Bitkeeper actually prevented anything, it is also clear that developers clearly recognized it as a potential drag on a generalized commitment to adaptability. Or to put it in terms of recursive publics, only one layer is properly open, that of the kernel itself; the layer beneath it, the process of its construction, is not free in the same sense. It is ironic that Torvalds—otherwise the spokesperson for antiplanning and adaptability—willingly adopted this form of constraint, but not at all surprising that it was collectively rejected.
@@ -9696,7 +9054,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0AC7B1A1A9ACBD2898B590528CB87ACA86C07816FA53302CB181A4CD1B508B14
.has: notes_reg
@@ -9708,7 +9065,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F19C18C2CAB411DE687BE39A301F0727FF6DE530F286273E8CADE88E51777915
.has: links notes_reg
@@ -9720,7 +9076,6 @@
.ancestors: 1 290 0 0 616 684 0 0
.ancestors_collapsed: 1 290 616 684 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 34F7722B668853E735D9142D90C2C2A011B3C8C80EB759FE7C58DA8936E741BB
| Novelty, both in the case of Linux and in intellectual property law more generally, is directly related to the interplay of social and technical coordination: goal direction vs. adaptability. The ideal of adaptability promoted by Torvalds suggests a radical alternative to the dominant ideology of creation embedded in contemporary intellectual-property systems. If Linux is “new,” it is new through adaptation and the coordination of large numbers of creative contributors who challenge the “design” of an operating system from the bottom up, not from the top down. By contrast, McVoy represents a moral imagination of design in which it is impossible to achieve novelty without extremely expensive investment in top-down, goal-directed, unpolitical design—and it is this activity that the intellectual-property system is designed to reward. Both are engaged, however, in an experiment; both are engaged in “figuring out” what the limits of Free Software are.
@@ -9748,7 +9103,6 @@
.ancestors: 1 290 0 0 616 706 0 0
.ancestors_collapsed: 1 290 616 706 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E3AA6507248AE6C17144464DC15E8943A1CE49EA8BAB05F7BF26591F4524B681
.has: notes_reg
@@ -9760,7 +9114,6 @@
.ancestors: 1 290 0 0 616 706 0 0
.ancestors_collapsed: 1 290 616 706 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F3EAF40241A743DAE58FF4D197B5AA3C684F6C203ADFA297CE675054275E56BF
.has: notes_reg
@@ -9772,7 +9125,6 @@
.ancestors: 1 290 0 0 616 706 0 0
.ancestors_collapsed: 1 290 616 706 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 483EED52FC16117B7015E0AD9E892F89511F4CCD78E9C0E798BE7B5F98B4103F
.has: notes_reg
@@ -9784,7 +9136,6 @@
.ancestors: 1 290 0 0 616 706 0 0
.ancestors_collapsed: 1 290 616 706 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8A440CD29319878FAB68C171248D456D11109432CB2A95DA1A562F2527EFF122
.has: notes_reg
@@ -9796,7 +9147,6 @@
.ancestors: 1 290 0 0 616 706 0 0
.ancestors_collapsed: 1 290 616 706 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AFF8B126FB653F18C9D56E840B52C2BD6421AF944C06162D2D4511BDAAEC8273
| UNIX was initially ported and shared through mixed academic and commercial means, through the active participation of computer scientists who both received updates and contributed fixes back to Thompson and Ritchie. No formal system existed to manage this process. When Thompson speaks of his understanding of UNIX as a “spectrum” and not as a series of releases (V1, V2, etc.), the implication is that work on UNIX was continuous, both within Bell Labs and among its widespread users. Thompson’s use of the diff tape encapsulates the core problem of coordination: how to collect and redistribute the changes made to the system by its users.
@@ -9807,7 +9157,6 @@
.ancestors: 1 290 0 0 616 706 0 0
.ancestors_collapsed: 1 290 616 706 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 74926298BBE69F0C105934C6B0DB6C783AE575D5225548C13467C5AA671564B5
| Similarly, Bill Joy’s distribution of BSD and James Gosling’s distribution of GOSMACS were both ad hoc, noncorporate experiments in “releasing early and often.” These distribution schemes had a purpose (beyond satisfying demand for the software). The frequent distribution of patches, fixes, and extensions eased the pain of debugging software and satisfied users’ demands for new features and extensions (by allowing them to do both themselves). Had Thompson and Ritchie followed the conventional corporate model of software production, they would have been held responsible for thoroughly debugging and testing the software they distributed, and AT&T or Bell Labs would have been responsible for coming up with all innovations and extensions as well, based on marketing and product research. Such an approach would have sacrificed adaptability in favor of planning. But Thompson’s and Ritchie’s model was different: both the extension and the debugging of software became shared responsibilities of the users and the developers. Stallman’s creation of EMACS followed a similar pattern; since EMACS was by design extensible and intended to satisfy myriad unforeseen needs, the responsibility rested on the users to address those needs, and sharing their extensions and fixes had obvious social benefit.
@@ -9818,7 +9167,6 @@
.ancestors: 1 290 0 0 616 706 0 0
.ancestors_collapsed: 1 290 616 706 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1A0D7A05649D628673FC726435457500749BD11617D99DCA91937D1DB2D19548
| The ability to see development of software as a spectrum implies more than just continuous work on a product; it means seeing the ⑆,┨[pg 239]┣, product itself as something fluid, built out of previous ideas and products and transforming, differentiating into new ones. Debugging, from this perspective, is not separate from design. Both are part of a spectrum of changes and improvements whose goals and direction are governed by the users and developers themselves, and the patterns of coordination they adopt. It is in the space between debugging and design that Free Software finds its niche.
@@ -9857,7 +9205,6 @@
.ancestors: 1 290 0 0 616 714 0 0
.ancestors_collapsed: 1 290 616 714 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D8B4B2FDCFF811AAA2C1FB89F2E632B4DF776D5C2A3AF5CDEA6DEE7FE67C2A97
| Coordination is a key component of Free Software, and is frequently identified as the central component. Free Software is the result of a complicated story of experimentation and construction, and the forms that coordination takes in Free Software are specific outcomes of this longer story. Apache and Linux are both experiments—not scientific experiments per se but collective social experiments in which there are complex technologies and legal tools, systems of coordination and governance, and moral and technical orders already present.
@@ -9868,7 +9215,6 @@
.ancestors: 1 290 0 0 616 714 0 0
.ancestors_collapsed: 1 290 616 714 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 15B7FFF230B71E8892DD17AD89BE6C1371E1C9420CCE3261C8B4B6E081930C19
| Free Software is an experimental system, a practice that changes with the results of new experiments. The privileging of adaptability makes it a peculiar kind of experiment, however, one not directed by goals, plans, or hierarchical control, but more like what John Dewey suggested throughout his work: the experimental praxis of science extended to the social organization of governance in the service of improving the conditions of freedom. What gives this experimentation significance is the centrality of Free Software—and specifically of Linux and Apache—to the experimental expansion of the Internet. As an infrastructure or a milieu, the Internet is changing the conditions of social organization, changing the relationship of knowledge to power, and changing the orientation of collective life toward governance. Free Software is, arguably, the best example of an attempt to make this transformation public, to ensure that it uses the advantages of adaptability as critique to counter the power of planning as control. Free Software, as a recursive public, proceeds by proposing and providing alternatives. It is a bit like Kant’s version of enlightenment: insofar as geeks speak (or hack) as scholars, in a public realm, they have a right to propose criticisms and changes of any sort; as soon as they relinquish ⑆,┨[pg 240]┣, that commitment, they become private employees or servants of the sovereign, bound by conscience and power to carry out the duties of their given office. The constitution of a public realm is not a universal activity, however, but a historically specific one: Free Software confronts the specific contemporary technical and legal infrastructure by which it is possible to propose criticisms and offer alternatives. What results is a recursive public filled not only with individuals who govern their own actions but also with code and concepts and licenses and forms of coordination that turn these actions into viable, concrete technical forms of life useful to inhabitants of the present.
@@ -9913,10 +9259,10 @@
[718] para
.part: body
+.parent: 0
.ancestors: 1 717 0 0 0 0 0 0
.ancestors_collapsed: 1 717 0 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 0BF93B5315785E154BB846A519B4EF325F5A35F4A3D3B0E7B5BC0FB0B130BDE7
.indent: 1 1
@@ -9965,7 +9311,6 @@
.ancestors: 1 717 0 0 719 0 0 0
.ancestors_collapsed: 1 717 719 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 6D73D25F7C7BF2662D8BBFC9D8B023E8540096782B08F2E5CA45AF8DC6D3726C
| In early 2002, after years of reading and learning about Open Source and Free Software, I finally had a chance to have dinner with famed libertarian, gun-toting, Open Source-founding impresario Eric Raymond, author of The Cathedral and the Bazaar and other amateur anthropological musings on the subject of Free Software. He had come to Houston, to Rice University, to give a talk at the behest of the Computer and Information Technology Institute (CITI). Visions of a mortal confrontation between two anthropologists-manqué filled my head. I imagined explaining point by point why his references to self-organization and evolutionary psychology were misguided, and how the long tradition of economic anthropology contradicted basically everything he had to say about gift-exchange. Alas, two things conspired against this epic, if bathetic, showdown.
@@ -9987,7 +9332,6 @@
.ancestors: 1 717 0 0 719 0 0 0
.ancestors_collapsed: 1 717 719 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 64189C6419EB5ED901EEE3C5B7903DB58019E32026C0BA16A67AB4D1A5AC3446
| First, there was the fact that (as so often happens in meetings among geeks) there was only one woman present at dinner; she was ⑆,┨[pg 244]┣, young, perhaps unmarried, but not a student—an interested female hacker. Raymond seated himself beside this woman, turned toward her, and with a few one-minute-long exceptions proceeded to lavish her with all of his available attention. The second reason was that I was seated next to Richard Baraniuk and Brent Hendricks. All at once, Raymond looked like the past of Free Software, arguing the same arguments, using the same rhetoric of his online publications, while Baraniuk and Hendricks looked like its future, posing questions about the transformation—the modulation—of Free Software into something surprising and new.
@@ -9998,7 +9342,6 @@
.ancestors: 1 717 0 0 719 0 0 0
.ancestors_collapsed: 1 717 719 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 70D1E40821E54B797B0E0CFF1B76823A232A18165E9443AE2D379F670946749B
| Baraniuk, a professor of electrical engineering and a specialist in digital signal processing, and Hendricks, an accomplished programmer, had started a project called Connexions, an “open content repository of educational materials.” Far more interesting to me than Raymond’s amateur philosophizing was this extant project to extend the ideas of Free Software to the creation of educational materials—textbooks, in particular.
@@ -10009,7 +9352,6 @@
.ancestors: 1 717 0 0 719 0 0 0
.ancestors_collapsed: 1 717 719 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: A80F46D13CA93A6D7C62D25B968529FA51A6C6FFBD18D66D0CD87D7146B4CA36
| Rich and Brent were, by the looks of it, equally excited to be seated next to me, perhaps because I was answering their questions, whereas Raymond was not, or perhaps because I was a new hire at Rice University, which meant we could talk seriously about collaboration. Rich and Brent (and Jan Odegard, who, as director of CITI, had organized the dinner) were keen to know what I could add to help them understand the “social” aspects of what they wanted to do with Connexions, and I, in return, was equally eager to learn how they conceptualized their Free Software-like project: what had they kept the same and what had they changed in their own experiment? Whatever they meant by “social” (and sometimes it meant ethical, sometimes legal, sometimes cultural, and so on), they were clear that there were domains of expertise in which they felt comfortable (programming, project management, teaching, and a particular kind of research in computer science and electrical engineering) and domains in which they did not (the “norms” of academic life outside their disciplines, intellectual-property law, “culture”). Although I tried to explain the nature of my own expertise in social theory, philosophy, history, and ethnographic research, the academic distinctions were far less important than the fact that I could ask detailed and pointed questions about the project, questions that indicated to them that I must have some kind of stake in the domains that they needed filled—in particular, ⑆,┨[pg 245]┣, around the question of whether Connexions was the same thing as Free Software, and what the implications of that might be.
@@ -10020,7 +9362,6 @@
.ancestors: 1 717 0 0 719 0 0 0
.ancestors_collapsed: 1 717 719 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: D904773048A3D4CB965D388D1CF5D985E7662B188E5F3E5D3C6DADE0117689DF
| Raymond courted and chattered on, then left, the event of his talk and dinner of fading significance, but over the following weeks, as I caught up with Brent and Rich, I became (surprisingly quickly) part of their novel experiment.
@@ -10048,7 +9389,6 @@
.ancestors: 1 717 0 0 719 725 0 0
.ancestors_collapsed: 1 717 719 725 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 277E935EC28F115EF9B627E6BA077C7A43202FBE34B87897C4E2D9A0DDFFFCAF
| My nonmeeting with Raymond is an allegory of sorts: an allegory of what comes after Free Software. The excitement around that table was not so much about Free Software or Open Source, but about a certain possibility, a kind of genotypic urge of which Free Software seemed a fossil phenotype and Connexions a live one. Rich and Brent were people in the midst of figuring something out. They were engaged in modulating the practices of Free Software. By modulation I mean exploring in detail the concrete practices—the how—of Free Software in order to ask what can be changed, and what cannot, in order to maintain something (openness?) that no one can quite put his finger on. What drew me immediately to Connexions was that it was related to Free Software, not metaphorically or ideologically, but concretely, practically, and experimentally, a relationship that was more about emergence out of than it was about the reproduction of forms. But the opposition between emergence and reproduction immediately poses a question, not unlike that of the identity of species in evolution: if Free Software is no longer software, what exactly is it?
@@ -10059,7 +9399,6 @@
.ancestors: 1 717 0 0 719 725 0 0
.ancestors_collapsed: 1 717 719 725 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C64B7E27A7856AB78F4921EEF7AB21E86B86B2D93BB6F9A17BB27E27AC6C6B9C
| In part III I confront this question directly. Indeed, it was this question that necessitated part II, the analytic decomposition of the practices and histories of Free Software. In order to answer the question “Is Connexions Free Software?” (or vice versa) it was necessary to rethink Free Software as itself a collective, technical experiment, rather than as an expression of any ideology or culture. To answer yes, or no, however, merely begs the question “What is Free Software?” What is the cultural significance of these practices? The concept of a recursive public is meant to reveal in part the significance of both Free Software and emergent projects like Connexions; it is meant to help chart when these emergent projects branch off absolutely (cease to be public) and when they do not, by ⑆,┨[pg 246]┣, focusing on how they modulate the five components that give Free Software its contemporary identity.
@@ -10070,7 +9409,6 @@
.ancestors: 1 717 0 0 719 725 0 0
.ancestors_collapsed: 1 717 719 725 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2BD76EF862A4DCDFD882E1D8C25862141D7A89ED75AB7EBFD3380E946931DE69
.has: notes_reg
@@ -10082,7 +9420,6 @@
.ancestors: 1 717 0 0 719 725 0 0
.ancestors_collapsed: 1 717 719 725 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 51019A9F751ED743742AE6CB235D54B3E8B02293625AF63BCD46A5334E5F0E62
| Connexions emerged out of Free Software, and not, as one might expect, out of education, textbook writing, distance education, or any of those areas that are topically connected to pedagogy. That is to say, the people involved did not come to their project by attempting to deal with a problem salient to education and teaching as much as they did so through the problems raised by Free Software and the question of how those problems apply to university textbooks. Similarly, a second project, Creative Commons, also emerged out of a direct engagement with and exploration of Free Software, and not out of any legal movement or scholarly commitment to the critique of intellectual-property law or, more important, out of any desire to transform the entertainment industry. Both projects are resolutely committed to experimenting with the given practices of Free Software—to testing their limits and changing them where they can—and this is what makes them vibrant, risky, and potentially illuminating as cases of a recursive public.
@@ -10093,7 +9430,6 @@
.ancestors: 1 717 0 0 719 725 0 0
.ancestors_collapsed: 1 717 719 725 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9ADB6E96532B69C0D844CD7A7656801446548E72CBFFBD957A7B0221772854DD
| While both initiatives are concerned with conventional subject areas (educational materials and cultural productions), they enter the fray orthogonally, armed with anxiety about the social and moral order in which they live, and an urge to transform it by modulating Free Software. This binds such projects across substantive domains, in that they are forced to be oppositional, not because they want to be (the movement comes last), but because they enter the domains of education and the culture industry as outsiders. They are in many ways intuitively troubled by the existing state of affairs, and their organizations, tools, legal licenses, and movements are seen as alternative imaginations of social order, especially concerning creative freedom and the continued existence of a commons of scholarly knowledge. To the extent that these projects ⑆,┨[pg 247]┣, remain in an orthogonal relationship, they are making a recursive public appear—something the textbook industry and the entertainment industry are, by contrast, not at all interested in doing, for obvious financial and political reasons.
@@ -10121,7 +9457,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 789DA4DF0AB874846C5748183EAB19E3E057CF06C39E91908BD177BDCDBF9875
| I’m at dinner again. This time, a windowless hotel conference room in the basement maybe, or perhaps high up in the air. Lawyers, academics, activists, policy experts, and foundation people are semi-excitedly working their way through the hotel’s steam-table fare. I’m trying to tell a story to the assembled group—a story that I have heard Rich Baraniuk tell a hundred times—but I’m screwing it up. Rich always gets enthusiastic stares of wonder, light-bulbs going off everywhere, a subvocalized “Aha!” or a vigorous nod. I, on the other hand, am clearly making it too complicated. Faces and foreheads are squirmed up into lines of failed comprehension, people stare at the gravy-sodden food they’re soldiering through, weighing the option of taking another bite against listening to me complicate an already complicated world. I wouldn’t be doing this, except that Rich is on a plane, or in a taxi, delayed by snow or engineers or perhaps at an eponymous hotel in another city. Meanwhile, our co-organizer Laurie Racine, has somehow convinced herself that I have the childlike enthusiasm necessary to channel Rich. I’m flattered, but unconvinced. After about twenty minutes, so is she, and as I try to answer a question, she stops me and interjects, “Rich really needs to be here. He should really be telling this story.”
@@ -10132,7 +9467,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 97C4401DADA05FA49B81B2EE0861E577C12A57F01268E655FA06A0BC34597CC0
| Miraculously, he shows up and, before he can even say hello, is conscripted into telling his story properly. I sigh in relief and pray that I’ve not done any irreparable damage and that I can go back to my role as straight man. I can let the superaltern speak for himself. The downside of participant observation is being asked to participate in what one had hoped first of all to observe. I do know the story—I have heard it a hundred times. But somehow what I hear, ears tuned to academic questions and marveling at some of the stranger claims he makes, somehow this is not the ear for enlightenment that his practiced and boyish charm delivers to those hearing it for the first time; it is instead an ear tuned to questions ⑆,┨[pg 248]┣, of why: why this project? Why now? And even, somewhat convolutedly, why are people so fascinated when he tells the story? How could I tell it like Rich?
@@ -10143,7 +9477,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 07D22B9B101A30467A5311AF2858D10EB3F08F134A4E739DB3364153CB8E700A
| Rich is an engineer, in particular, a specialist in Digital Signal Processing (DSP). DSP is the science of signals. It is in everything, says Rich: your cell phones, your cars, your CD players, all those devices. It is a mathematical discipline, but it is also an intensely practical one, and it’s connected to all kinds of neighboring fields of knowledge. It is the kind of discipline that can connect calculus, bioinformatics, physics, and music. The statistical and analytical techniques come from all sorts of research and end up in all kinds of interesting devices. So Rich often finds himself trying to teach students to make these kinds of connections—to understand that a Fourier transform is not just another chapter in calculus but a tool for manipulating signals, whether in bioinformatics or in music.
@@ -10154,7 +9487,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A1C971DC08E1C4ED15E4DD1F199C3F7BC03501DA2D0F4D9FD60A80A0D0FAD929
| Around 1998 or 1999, Rich decided that it was time for him to write a textbook on DSP, and he went to the dean of engineering, Sidney Burris, to tell him about the idea. Burris, who is also a DSP man and longtime member of the Rice University community, said something like, “Rich, why don’t you do something useful?” By which he meant: there are a hundred DSP textbooks out there, so why do you want to write the hundred and first? Burris encouraged Rich to do something bigger, something ambitious enough to put Rice on the map. I mention this because it is important to note that even a university like Rice, with a faculty and graduate students on par with the major engineering universities of the country, perceives that it gets no respect. Burris was, and remains, an inveterate supporter of Connexions, precisely because it might put Rice “in the history books” for having invented something truly novel.
@@ -10165,7 +9497,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4BBFB4B7BC8641D13D5C8C434FB012DBCAE67EC6A29A03A5823D13D22BDCF229
| At about the same time as his idea for a textbook, Rich’s research group was switching over to Linux, and Rich was first learning about Open Source and the emergence of a fully free operating system created entirely by volunteers. It isn’t clear what Rich’s aha! moment was, other than simply when he came to an understanding that such a thing as Linux was actually possible. Nonetheless, at some point, Rich had the idea that his textbook could be an Open Source textbook, that is, a textbook created not just by him, but by DSP researchers all over the world, and made available to everyone to make use of and modify and improve as they saw fit, just like Linux. Together with Brent Hendricks, Yan David Erlich, ⑆,┨[pg 249]┣, and Ross Reedstrom, all of whom, as geeks, had a deep familiarity with the history and practices of Free and Open Source Software, Rich started to conceptualize a system; they started to think about modulations of different components of Free and Open Source Software. The idea of a Free Software textbook repository slowly took shape.
@@ -10176,7 +9507,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3186CDD9D62AA3E0BF11027AB8AA9155C7ED8BAE0CA6F2ED5967E0E183B7FEEC
| Thus, Connexions: an “open content repository of high-quality educational materials.” These “textbooks” very quickly evolved into something else: “modules” of content, something that has never been sharply defined, but which corresponds more or less to a small chunk of teachable information, like two or three pages in a textbook. Such modules are much easier to conceive of in sciences like mathematics or biology, in which textbooks are often multiauthored collections, finely divided into short chapters with diagrams, exercises, theorems, or programs. Modules lend themselves much less well to a model of humanities or social-science scholarship based in reading texts, discussion, critique, and comparison—and this bias is a clear reflection of what Brent, Ross, and Rich knew best in terms of teaching and writing. Indeed, the project’s frequent recourse to the image of an assembly-line model of knowledge production often confirms the worst fears of humanists and educators when they first encounter Connexions. The image suggests that knowledge comes in prepackaged and colorfully branded tidbits for the delectation of undergrads, rather than characterizing knowledge as a state of being or as a process.
@@ -10187,7 +9517,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 748475A7F76AD69FE35A912DA58F05594A14F7DC39BEEDAB1FB6C02A1FEFAE3F
| The factory image (figure 7) is a bit misleading. Rich’s and Brent’s imaginations are in fact much broader, which shows whenever they demo the project, or give a talk, or chat at a party about it. Part of my failure to communicate excitement when I tell the story of Connexions is that I skip the examples, which is where Rich starts: what if, he says, you are a student taking Calculus 101 and, at the same time, Intro to Signals and Systems—no one is going to explain to you how Fourier transforms form a bridge, or connection, between them. “Our brains aren’t organized in linear, chapter-by-chapter ways,” Rich always says, “so why are our textbooks?” How can we give students a way to see the connection between statistics and genetics, between architecture and biology, between intellectual-property law and chemical engineering? Rich is always looking for new examples: a music class for kids that uses information from physics, or vice versa, for instance. Rich’s great hope is that the ⑆,┨[pg 250]┣, ⑆,┨[pg 251]┣, more modules there are in the Connexions commons, the more fantastic and fascinating might be the possibilities for such novel—and natural—connections.
@@ -10209,7 +9538,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D6B91235472D0A529729E7B4693B309F589FF18ECB41F896E49B8F41312B9010
.image: 2bits_08_07-100.png sha256:090BD98CB932ABFEE63247422B2E5A3A0B6C484B0AABBA5E25710F11CD265BC6 bytes:72418 px:530x827
@@ -10222,7 +9550,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4BA96CE5A61C785722F9D4488ABADF3B2AFBE7CCB5588F027A1D634FD1B34698
.has: links notes_reg
@@ -10235,7 +9562,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 08C76021E18993A8A730B1E2B587E2AA6105A3896C7720B80241FD160808A1B4
.has: links notes_reg
@@ -10247,7 +9573,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C24A5FB49826D5224B464420040E45F34A72064003D2B8954976FFE31AB98BEC
| OCW, Connexions, and distance learning, therefore, while all ostensibly interested in combining education with the networks and software, emerged out of different demands and different places. While the profit-driven demand of distance learning fueled many attempts around the country, it stalled in the case of OCW, largely because the final MIT Council on Educational Technology report that recommended OCW was issued at the same time as the first plunge in the stock market (April 2000). Such issues were not a core factor in the development of Connexions, which is not to say that the problems of funding and sustainability have not always been important concerns, only that genesis of the project was not at the administrative level or due to concerns about distance education. For Rich, Brent, and Ross the core commitment was to openness and to the success of Open Source as an experiment with massive, distributed, Internet-based, collaborative production of software—their commitment to this has been, from the beginning, completely and adamantly unwavering. Neverthless, the project has involved modulations of the core features of Free Software. Such modulations depend, to a certain extent, on being a project that emerges out of the ideas and practices of Free Software, rather than, as in the case of OCW, one founded as a result of conflicting goals (profit and academic freedom) and resulting in a strategic use of public relations to increase the symbolic power of the university over its fiscal growth.
@@ -10269,7 +9594,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C3BC570BB9350329BE98669BCD78FAEC5736F2C2748BAB74E86EB5FFB999A217
| When Rich recounts the story of Connexions, though, he doesn’t mention any of this background. Instead, like a good storyteller, he waits for the questions to pose themselves and lets his demonstration answer them. Usually someone asks, “How is Connexions different from OCW?” And, every time, Rich says something similar: Connexions is about “communities,” about changing the way scholars collaborate and create knowledge, whereas OCW is simply ⑆,┨[pg 253]┣, an attempt to transfer existing courses to a Web format in order to make the content of those courses widely available. Connexions is a radical experiment in the collaborative creation of educational materials, one that builds on the insights of Open Source and that actually encompasses the OCW project. In retrospective terms, it is clear that OCW was interested only in modulating the meaning of source code and the legal license, whereas Connexions seeks also to modulate the practice of coordination, with respect to academic textbooks.
@@ -10280,7 +9604,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4B9BF686E1FDAF1271BC02BBBB3EA65AFBEA03BFD8D3D663012C46DA7987390E
| Rich’s story of the origin of Connexions usually segues into a demonstration of the system, in which he outlines the various technical, legal, and educational concepts that distinguish it. Connexions uses a standardized document format, the eXtensible Mark-up Language (XML), and a Creative Commons copyright license on every module; the Creative Commons license allows people not only to copy and distribute the information but to modify it and even to use it for commercial gain (an issue that causes repeated discussion among the team members). The material ranges from detailed explanations of DSP concepts (naturally) to K-12 music education (the most popular set of modules). Some contributors have added entire courses; others have created a few modules here and there. Contributors can set up workgroups to manage the creation of modules, and they can invite other users to join. Connexions uses a version-control system so that all of the changes are recorded; thus, if a module used in one class is changed, the person using it for another class can continue to use the older version if they wish. The number of detailed and clever solutions embodied in the system never ceases to thoroughly impress anyone who takes the time to look at it.
@@ -10291,7 +9614,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 04ADE7FB65A64E0A3A4E549D91406B44EA28D7A8D6A45DB6D97120A507AFED53
| But what always animates people is the idea of random and flexible connection, the idea that a textbook author might be able to build on the work of hundreds of others who have already contributed, to create new classes, new modules, and creative connections between them, or surprising juxtapositions—from the biologist teaching a class on bioinformatics who needs to remind students of certain parts of calculus without requiring a whole course; to the architect who wants a studio to study biological form, not necessarily in order to do experiments in biology, but to understand buildings differently; to the music teacher who wants students to understand just enough physics to get the concepts of pitch and ⑆,┨[pg 254]┣, timbre; to or the physicist who needs a concrete example for the explanation of waves and oscillation.
@@ -10302,7 +9624,6 @@
.ancestors: 1 717 0 0 719 731 0 0
.ancestors_collapsed: 1 717 719 731 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2E8EFE44743428626EADEA1BDA3C59BF74E82281F1147A1F5D9594AC21DA5081
| The idea of such radical recombinations is shocking for some (more often for humanities and social-science scholars, rather than scientists or engineers, for reasons that clearly have to do with an ideology of authentic and individualized creative ability). The questions that result—regarding copyright, plagiarism, control, unauthorized use, misuse, misconstrual, misreading, defamation, and so on—generally emerge with surprising force and speed. If Rich were trying to sell a version of “distance learning,” skepticism and suspicion would quickly overwhelm the project; but as it is, Connexions inverts almost all of the expectations people have developed about textbooks, classroom practice, collaboration, and copyright. More often than not people leave the discussion converted—no doubt helped along by Rich’s storytelling gift.
@@ -10330,7 +9651,6 @@
.ancestors: 1 717 0 0 719 747 0 0
.ancestors_collapsed: 1 717 719 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: ED08B1CD5DEDDEE43C0C8D54CC3A93958CBDD61EEF02EEDD75D77A95BF3AC478
| Connexions surprises people for some of the same reasons as Free Software surprises people, emerging, as it does, directly out of the same practices and the same components. Free Software provides a template made up of the five components: shared source code, a concept of openness, copyleft licenses, forms of coordination, and a movement or ideology. Connexions starts with the idea of modulating a shared “source code,” one that is not software, but educational textbook modules that academics will share, port, and fork. The experiment that results has implications for the other four components as well. The implications lead to new questions, new constraints, and new ideas.
@@ -10352,7 +9672,6 @@
.ancestors: 1 717 0 0 719 747 0 0
.ancestors_collapsed: 1 717 719 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4379DC0064E2EE78635E49A9F139EE64D13F713D4D039C47BD8BED8B167B7079
.has: notes_reg
@@ -10364,7 +9683,6 @@
.ancestors: 1 717 0 0 719 747 0 0
.ancestors_collapsed: 1 717 719 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3AF76921D7301FAF04045DDF763B6845E5C699819193E67362485E5619AC8708
| At the same time, there is “content,” the ubiquitous term for digital creations that are not software. The creation of content modules, on the other hand (which the software system makes technically possible), is intended to function like a Free Software project, in which, for instance, a group of engineering professors might get together to collaborate on pieces of a textbook on DSP. The Connexions project does not encompass or initiate such collaborations, but, rather, proceeds from the assumption that such activity is already happening and that Connexions can provide a kind of alternative platform—an alternative infrastructure even—which textbook-writing academics can make use of instead of the current infrastructure of publishing. The current infrastructure and technical model of textbook writing, this implies, is one that both prevents people from taking advantage of the Open Source model of collaborative development and makes academic work “non-free.” The shared objects of content are not source code that can be compiled, like source code in C, but documents marked up with XML and filled with “educational” content, then “displayed” either on paper or onscreen.
@@ -10375,7 +9693,6 @@
.ancestors: 1 717 0 0 719 747 0 0
.ancestors_collapsed: 1 717 719 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 52B4A9A1E2F7E9F4CE18811A42F5ACA2D7877A329CD8217E76DEFD720B9B788E
.has: notes_reg
@@ -10387,7 +9704,6 @@
.ancestors: 1 717 0 0 719 747 0 0
.ancestors_collapsed: 1 717 719 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1315C4BE0546E9186574C8FC583F17DD86F9B60F222823E46FBA17C988FAC07E
| With respect to content, the devotion to openness is nearly identical, because conventional textbook publishers “lock in” customers (students) through the creation of new editions and useless “enhanced” content, which jacks up prices and makes it difficult for educators to customize their own courses. “Openness” in this sense trades on the same reasoning as it did in the 1980s: the most important aspect of the project is the information people create, and any proprietary system locks up content and prevents people from taking it elsewhere or using it in a different context.
@@ -10398,7 +9714,6 @@
.ancestors: 1 717 0 0 719 747 0 0
.ancestors_collapsed: 1 717 719 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 03A04455EA61A1846B1102A74C5785D826A3B5AF6C8B5ED25EF6D47BF5A6CFCD
| Indeed, so firm is the commitment to openness that Rich and Brent often say something like, “If we are successful, we will disappear.” They do not want to become a famous online textbook publisher; they want to become a famous publishing infrastructure. Being radically open means that any other competitor can use your system—but it means they are using your system, and this is the goal. Being open means not only sharing the “source code” (content and modules), but devising ways to ensure the perpetual openness of that content, that is, to create a recursive public devoted to the maintenance and modifiability of the medium or infrastructure by which it communicates. Openness trumps “sustainability” (i.e., the self-perpetuation of the financial feasibility of a particular organization), and where it fails to, the commitment to openness has been compromised.
@@ -10409,7 +9724,6 @@
.ancestors: 1 717 0 0 719 747 0 0
.ancestors_collapsed: 1 717 719 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0578F97E200F0DE93666DA835BD1984454D90826F08BE4584835959C98C75C3E
| The commitment to openness and the modulation of the meaning of source code thus create implications for the meaning of Free Software licenses: do such licenses cover this kind of content? Are new licenses necessary? What should they look like? Connexions was by no means the first project to stimulate questions about the applicability of Free Software licenses to texts and documents. In the case of EMACS and the GPL, for example, Richard Stallman had faced the problem of licensing the manual at the same time as the source code for the editor. Indeed, such issues would ultimately result in a GNU Free Documentation License intended narrowly to ⑆,┨[pg 257]┣, cover software manuals. Stallman, due to his concern, had clashed during the 1990s with Tim O’Reilly, publisher and head of O’Reilly Press, which had long produced books and manuals for Free Software programs. O’Reilly argued that the principles reflected in Free Software licenses should not be applied to instructional books, because such books provided a service, a way for more people to learn how to use Free Software, and in turn created a larger audience. Stallman argued the opposite: manuals, just like the software they served, needed to be freely modifiable to remain useful.
@@ -10420,7 +9734,6 @@
.ancestors: 1 717 0 0 719 747 0 0
.ancestors_collapsed: 1 717 719 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B5ADC932DE8D790E2DEB5B305585F30D934F7F0D4313BA990655802BBB0E780F
| By the late 1990s, after Free Software and Open Source had been splashed across the headlines of the mainstream media, a number of attempts to create licenses modeled on Free Software, but applicable to other things, were under way. One of the earliest and most general was the Open Content License, written by the educational-technology researcher David Wiley. Wiley’s license was intended for use on any kind of content. Content could include text, digital photos, movies, music, and so on. Such a license raises new issues. For example, can one designate some parts of a text as “invariant” in order to prevent them from being changed, while allowing other parts of the text to be changed (the model eventually adopted by the GNU Free Documentation License)? What might the relationship between the “original” and the modified version be? Can one expect the original author to simply incorporate suggested changes? What kinds of forking are possible? Where do the “moral rights” of an author come into play (regarding the “integrity” of a work)?
@@ -10431,7 +9744,6 @@
.ancestors: 1 717 0 0 719 747 0 0
.ancestors_collapsed: 1 717 719 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 71414D96A14D4B426295E17C39184C9AF53AF1E20A5D438868D33BDE5EB713B1
| At the same time, the modulation of source code to include academic textbooks has extremely complex implications for the meaning and context of coordination: scholars do not write textbooks like programmers write code, so should they coordinate in the same ways? Coordination of a textbook or a course in Connexions requires novel experiments in textbook writing. Does it lend itself to academic styles of work, and in which disciplines, for what kinds of projects? In order to cash in on the promise of distributed, collaborative creation, it would be necessary to find ways to coordinate scholars.
@@ -10442,7 +9754,6 @@
.ancestors: 1 717 0 0 719 747 0 0
.ancestors_collapsed: 1 717 719 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0C1E83F31329CCFF05518A8E3C39A9E689C9013D12686E89831C5D1AAEE40DCC
.has: notes_reg
@@ -10471,7 +9782,6 @@
.ancestors: 1 717 0 0 719 758 0 0
.ancestors_collapsed: 1 717 719 758 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D6FEAB7C9BC9298116EC92CD22B00F56D5E58B1ACF7FBBB6CE41DEC8F9BC014D
| I’m standing in a parking lot in 100 degree heat and 90 percent humidity. It is spring in Houston. I am looking for my car, and I cannot find it. James Boyle, author of Shamans, Software, and Spleens and distinguished professor of law at Duke University, is standing near me, staring at me, wearing a wool suit, sweating and watching me search for my car under the blazing sun. His look says simply, “If I don’t disembowel you with my Palm Pilot stylus, I am going to relish telling this humiliating story to your friends at every opportunity I can.” Boyle is a patient man, with the kind of arch Scottish humor that can make you feel like his best friend, even as his stories of the folly of man unfold with perfect comic pitch and turn out to be about you. Having laughed my way through many an uproarious tale of the foibles of my fellow creatures, I am aware that I have just taken a seat among them in Boyle’s theater of human weakness. I repeatedly press the panic button on my key chain, in the hopes that I am near enough to my car that it will erupt in a frenzy of honking and flashing that will end the humiliation.
@@ -10482,7 +9792,6 @@
.ancestors: 1 717 0 0 719 758 0 0
.ancestors_collapsed: 1 717 719 758 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2D7C9BCF50B2882958EF42B0D9F7B3B35A7FE2358527BB1F95C87BF6B638140D
| The day had started well. Boyle had folded himself into my Volkswagen (he is tall), and we had driven to campus, parked the car in what no doubt felt like a memorable space at 9 A.M., and happily gone to the scheduled meeting—only to find that it had been mistakenly scheduled for the following day. Not my fault, though now, certainly, my problem. The ostensible purpose of Boyle’s visit was to meet the Connexions team and learn about what they were doing. Boyle had proposed the visit himself, as he was planning to pass through Houston anyway. I had intended to pester him with questions about the politics and possibilities of licensing the content in Connexions and with comparisons to MIT’s OCW and other such commons projects that Boyle knew of.
@@ -10493,7 +9802,6 @@
.ancestors: 1 717 0 0 719 758 0 0
.ancestors_collapsed: 1 717 719 758 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E4F334CAAA1FB94685E520021C6D49678EE12C77A1F44AEDBBFC9BE713EBC2DA
| Instead of attending the meeting, I took him back to my office, where I learned more about why he was interested in Connexions. Boyle’s interest was not entirely altruistic (nor was it designed to spend valuable quarter hours standing in a scorched parking lot as I looked for my subcompact car). What interested Boyle was finding ⑆,┨[pg 259]┣, a constituency of potential users for Creative Commons, the nonprofit organization he was establishing with Larry Lessig, Hal Abelson, Michael Carroll, Eric Eldred, and others—largely because he recognized the need for a ready constituency in order to make Creative Commons work. The constituency was needed both to give the project legitimacy and to allow its founders to understand what exactly was needed, legally speaking, for the creation of a whole new set of Free Software-like licenses.
@@ -10504,7 +9812,6 @@
.ancestors: 1 717 0 0 719 758 0 0
.ancestors_collapsed: 1 717 719 758 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 35B76283066E779F76EB00104FECBC91120AC328AACAE175B836C69C4E4160A5
| Creative Commons, as an organization and as a movement, had been building for several years. In some ways, Creative Commons represented a simple modulation of the Free Software license: a broadening of the license’s concept to cover other types of content. But the impetus behind it was not simply a desire to copy and extend Free Software. Rather, all of the people involved in Creative Commons were those who had been troubling issues of intellectual property, information technology, and notions of commons, public domains, and freedom of information for many years. Boyle had made his name with a book on the construction of the information society by its legal (especially intellectual property) structures. Eldred was a publisher of public-domain works and the lead plaintiff in a court case that went to the Supreme Court in 2002 to determine whether the recent extension of copyright term limits was constitutional. Abelson was a computer scientist with an active interest in issues of privacy, freedom, and law “on the electronic frontier.” And Larry Lessig was originally interested in constitutional law, a clerk for Judge Richard Posner, and a self-styled cyberlaw scholar, who was, during the 1990s, a driving force for the explosion of interest in cyberlaw, much of it carried out at the Berkman Center for Internet and Society at Harvard University.
@@ -10515,7 +9822,6 @@
.ancestors: 1 717 0 0 719 758 0 0
.ancestors_collapsed: 1 717 719 758 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C2098F26240441507C12895F340D1942F2BC84DF7AEF1DD43D731E6DE817749C
| With the exception of Abelson—who, in addition to being a famous computer scientist, worked for years in the same building that Richard Stallman camped out in and chaired the committee that wrote the report recommending OCW—none of the members of Creative Commons cut their teeth on Free Software projects (they were lawyers and activists, primarily) and yet the emergence of Open Source into the public limelight in 1998 was an event that made more or less instant and intuitive sense to all of them. During this time, Lessig and members of the Berkman Center began an “open law” project designed to mimic the Internet-based collaboration of the Open Source project among lawyers who might want to ⑆,┨[pg 260]┣, contribute to the Eldred case. Creative Commons was thus built as much on a commitment to a notion of collaborative creation—the use of the Internet especially—but more generally on the ability of individuals to work together to create new things, and especially to coordinate the creation of these things by the use of novel licensing agreements.
@@ -10526,7 +9832,6 @@
.ancestors: 1 717 0 0 719 758 0 0
.ancestors_collapsed: 1 717 719 758 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B0A79990AE4FA95D670E33ED1F349EB5CD834F24F669D8760CF9343FC930467D
.has: notes_reg
@@ -10538,7 +9843,6 @@
.ancestors: 1 717 0 0 719 758 0 0
.ancestors_collapsed: 1 717 719 758 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8E9EEAF92901531FCA8B18449914CFD050E7655AEA62DCF5AC2ACD5ABCA83B3E
| Creative Commons was thus a back-door approach: if the laws could not be changed, then people should be given the tools they needed to work around those laws. Understanding how Creative Commons was conceived requires seeing it as a modulation of both the notion of “source code” and the modulation of “copyright licenses.” But the modulations take place in that context of a changing legal system that was so unfamiliar to Stallman and his EMACS users, a legal system responding to new forms of software, networks, and devices. For instance, the changes to the Copyright Act of 1976 created an unintended effect that Creative Commons would ultimately seize on. By eliminating the requirement to register copyrighted works (essentially granting copyright as soon as the ⑆,┨[pg 261]┣, work is “fixed in a tangible medium”), the copyright law created a situation wherein there was no explicit way in which a work could be intentionally placed in the public domain. Practically speaking an author could declare that a work was in the public domain, but legally speaking the risk would be borne entirely by the person who sought to make use of that work: to copy it, transform it, sell it, and so on. With the explosion of interest in the Internet, the problem ramified exponentially; it became impossible to know whether someone who had placed a text, an image, a song, or a video online intended for others to make use of it—even if the author explicitly declared it “in the public domain.” Creative Commons licenses were thus conceived and rhetorically positioned as tools for making explicit exactly what uses could be made of a specific work. They protected the rights of people who sought to make use of “culture” (i.e., materials and ideas and works they had not authored), an approach that Lessig often summed up by saying, “Culture always builds on the past.”
@@ -10549,7 +9853,6 @@
.ancestors: 1 717 0 0 719 758 0 0
.ancestors_collapsed: 1 717 719 758 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D48FC58407470CC86754ACAB479331B9530D62468B14E439F19ECE6E0FEA1DF3
| The background to and context of the emergence of Creative Commons was of course much more complicated and fraught. Concerns ranged from the plights of university libraries with regard to high-priced journals, to the problem of documentary filmmakers unable to afford, or even find the owners of, rights to use images or snippets in films, to the high-profile fights over online music trading, Napster, and the RIAA. Over the course of four years, Lessig and the other founders of Creative Commons would address all of these issues in books, in countless talks and presentations and conferences around the world, online and off, among audiences ranging from software developers to entrepreneurs to musicians to bloggers to scientists.
@@ -10560,7 +9863,6 @@
.ancestors: 1 717 0 0 719 758 0 0
.ancestors_collapsed: 1 717 719 758 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 33BD98880972A1135CBBE32871C36043C097799AEFEF8DC8FC81227221B031ED
| Often, the argument for Creative Commons draws heavily on the concept of culture besieged by the content industries. A story which Lessig enjoys telling—one that I heard on several occasions when I saw him speak at conferences—was that of Mickey Mouse. An interesting, quasi-conspiratorial feature of the twentieth-century expansion of intellectual-property law is that term limits seem to have been extended right around the time Mickey Mouse was about to become public property. True or not, the point Lessig likes to make is that the Mouse is not the de novo creation of the mind of Walt Disney that intellectual-property law likes to pretend it is, but built on the past of culture, in particular, on Steamboat Willie, ⑆,┨[pg 262]┣, Charlie Chaplin, Krazy Kat, and other such characters, some as inspiration, some as explicit material. The greatness in Disney’s creation comes not from the mind of Disney, but from the culture from which it emerged. Lessig will often illustrate this in videos and images interspersed with black-typewriter-font-bestrewn slides and a machine-gun style that makes you think he’s either a beat-poet manqué or running for office, or maybe both.
@@ -10571,7 +9873,6 @@
.ancestors: 1 717 0 0 719 758 0 0
.ancestors_collapsed: 1 717 719 758 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E40683864FF8918F38D122411D3DA3EDAAD1CE11E3E8E0AB80A37400C56A0EE3
.has: links notes_reg
@@ -10584,7 +9885,6 @@
.ancestors: 1 717 0 0 719 758 0 0
.ancestors_collapsed: 1 717 719 758 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DADC60BC196D68469723DADCFAE211AD842FFDDB32053C578F54A430575301E5
.has: notes_reg
@@ -10613,7 +9913,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F59742BE209CEB54E8CF41B932DC7232E770EE8A2193CD3DA417DE109CDAB0E5
| The workshop I organized in August 2002 was intended to allow Creative Commons, Connexions, and MIT’s OCW project to try to articulate what each might want from the other. It was clear what Creative Commons wanted: to convince as many people as possible to use their licenses. But what Connexions and OCW might have wanted, from each other as well as from Creative Commons, was less clear. Given the different goals and trajectories of the two projects, their needs for the licenses differed in substantial ways—enough so that the very idea of using the same license was, at least temporarily, rendered impossible by MIT. While OCW was primarily concerned about obtaining permissions to place existing copyrighted work on the Web, Connexions was more concerned about ensuring that new work remain available and modifiable.
@@ -10624,7 +9923,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4C8AA005933EDBB7858605AB5721ECA916D1DB27A7A5F973EA4C0F4147D19F02
| In retrospect, this workshop clarified the novel questions and problems that emerged from the process of modulating the components of Free Software for different domains, different kinds of content, and different practices of collaboration and sharing. Since then, my own involvement in this activity has been aimed at resolving some of these issues in accordance with an imagination of openness, an imagination of social order, that I had learned from my long experience with geeks, and not from my putative expertise as an anthropologist or a science-studies scholar. The fiction that I had at first adopted—that I was bringing scholarly knowledge to the table—became harder and harder to maintain the more I realized that it was my understanding of Free Software, gained through ongoing years of ethnographic apprenticeship, that was driving my involvement.
@@ -10635,7 +9933,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 932BEEE75ED56E564B01761B2B58D0F8E2939EF0A1ABCC8B486DFB425FA5E88C
.has: notes_reg
@@ -10647,7 +9944,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 32AA72EA22E12FCAB2D317122EFA3A7886308B63C394EAC773F6FC99DBBA3405
| My experience—my participant-observation—with Creative Commons was therefore primarily done as an intermediary between the Connexions project (and, by implication, similar projects under way elsewhere) and Creative Commons with respect to the writing of licenses. In many ways this detailed, specific practice was the most challenging and illuminating aspect of my participation, but in retrospect it was something of a red herring. It was not only the modulation of the meaning of source code and of legal licenses that differentiated these projects, but, more important, the meaning of collaboration, reuse, coordination, and the cultural practice of sharing and building on knowledge that posed the trickiest of the problems.
@@ -10658,7 +9954,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CECAAE98D1DDDEF7B172E3C45A657028516887546FCB58BC7216293D8AE06292
| My contact at Creative Commons was not James Boyle or Larry Lessig, but Glenn Otis Brown, the executive director of that organization (as of summer 2002). I first met Glenn over the phone, as I tried to explain to him what Connexions was about and why he should join us in Houston in August to discuss licensing issues related to scholarly material. Convincing him to come to Texas was an easier sell than explaining Connexions (given my penchant for complicating it unnecessarily), as Glenn was an Austin native who had been educated at the University of Texas before heading off to Harvard Law School and its corrupting influence at the hands of Lessig, Charlie Nesson, and John Perry Barlow.
@@ -10669,7 +9964,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9AFF19F3283205AEEC4AF98EF4BBD3A77D830B2CA6E20B793D39D1494514A6AA
.has: notes_reg
@@ -10681,7 +9975,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6E5A08FF388B8C2FD925CF357B1A3FA8D7D23DAC488B8D18A694F29612B5A0D4
.has: notes_reg
@@ -10693,7 +9986,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FE69C93953D77C1D7589448AA00E931BE932DC04E5202B315144D83F61F8711B
.has: notes_reg
@@ -10705,7 +9997,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AC12496D999FA69572E85C18A48E1AEE601E2C2121C10A9FD1EAF3E957A68FA6
| At the workshop, participants had a chance to hash out a number of different issues related to the creation of licenses that would be appropriate to scholarly content: questions of attribution and commercial use, modification and warranty; differences between federal copyright law concerning licenses and state law concerning commercial contracts. The starting point for most people was Free Software, but this was not the only starting point. There were at least two other broad threads that fed into the discussion and into the general understanding of the state of affairs facing projects like ⑆,┨[pg 266]┣, Connexions or OCW. The first thread was that of digital libraries, hypertext, human-computer interaction research, and educational technology. These disciplines and projects often make common reference to two pioneers, Douglas Englebart and Theodore Nelson, and more proximately to things like Apple’s HyperCard program and a variety of experiments in personal academic computing. The debates and history that lead up to the possibility of Connexions are complex and detailed, but they generally lack attention to legal detail. With the exception of a handful of people in library and information science who have made “digital” copyright into a subspecialty, few such projects, over the last twenty-five years, have made the effort to understand, much less incorporate, issues of intellectual property into their purview.
@@ -10716,7 +10007,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 67E50B597B7173EF70ADEDD1B8B72DE52E5CED1AE57695E6406581580E5E3A52
| The other thread combines a number of more scholarly interests that come out of the disciplines of economics and legal theory: institutional economics, critical legal realism, law and economics—these are the scholastic designations. Boyle and Lessig, for example, are both academics; Boyle does not practice law, and Lessig has tried few cases. Nonetheless, they are both inheritors of a legal and philosophical pragmatism in which value is measured by the transformation of policy and politics, not by the mere extension or specification of conceptual issues. Although both have penned a large number of complicated theoretical articles (and Boyle is well known in several academic fields for his book Shamans, Software, and Spleens and his work on authorship and the law), neither, I suspect, would ever sacrifice the chance to make a set of concrete changes in legal or political practice given the choice. This point was driven home for me in a conversation I had with Boyle and others at dinner on the night of the launch of Creative Commons, in December 2002. During that conversation, Boyle said something to the effect of, “We actually made something; we didn’t just sit around writing articles and talking about the dangers that face us—we made something.” He was referring as much to the organization as to the legal licenses they had created, and in this sense Boyle qualifies very much as a polymathic geek whose understanding of technology is that it is an intervention into an already constituted state of affairs, one that demonstrates its value by being created and installed, not by being assessed in the court of scholarly opinions. ⑆,┨[pg 267]┣,
@@ -10727,7 +10017,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 638645294A09776E3E32C3D1CB4805B39D2D8C3EE12B3BFFC8120AB5A700C113
.has: notes_reg
@@ -10739,7 +10028,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D325D614391C5BBC6C47D666475D61952D2F3485D43AA6BD4C54AD9D2406CEC0
.has: notes_reg
@@ -10751,7 +10039,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8D339519711CE8F9FD93F10134A2B908FCD29E1BF41E170E8C5D7DB5210461A1
.has: notes_reg
@@ -10763,7 +10050,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C464E7A5B4895932FFA6E4A52D2733B5B0827C2F1B0A154FA4BF851176434B05
| In my years with Connexions I eventually came to see it as something in between a natural experiment and a thought experiment: it was conducted in the open, and it invited participation from working scholars and teachers (a natural experiment, in that it was not a closed, scholarly endeavor aimed at establishing specific results, but an essentially unbounded, functioning system that people could and would come to depend on), and yet it proceeded by making a series of strategic guesses (a thought experiment) about three related things: (1) what it is (and will be) possible to do technically; (2) what it is (and will be) possible to do legally; and (3) what scholars and educators have done and now do in the normal course of their activities.
@@ -10774,7 +10060,6 @@
.ancestors: 1 717 0 0 719 770 0 0
.ancestors_collapsed: 1 717 719 770 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 80F5270B706520B45CF67D8E4C540D16ED08D8E881CD150D14C720CF7087FEE3
.has: notes_reg
@@ -10824,7 +10109,6 @@
.ancestors: 1 717 0 0 786 0 0 0
.ancestors_collapsed: 1 717 786 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 6EDCA359B7B69F9CB91FFC2E662AE811AACC4BB9DB8C5BDFAE31320B19901E18
| The Connexions project was an experiment in modulating the practices of Free Software. It was not inspired by so much as it was based on a kind of template drawn from the experience of people who had some experience with Free Software, including myself. But how exactly do such templates get used? What is traced and what is changed? In terms of the cultural significance of Free Software, what are the implications of these changes? Do they maintain the orientation of a recursive public, or are they attempts to apply Free Software for other private concerns? And if they are successful, what are the implications for the domains they affect: education, scholarship, scientific knowledge, and cultural production? What effects do these changes have on the norms of work and the meaning and shape of knowledge in these domains? ⑆,┨[pg 270]┣,
@@ -10835,7 +10119,6 @@
.ancestors: 1 717 0 0 786 0 0 0
.ancestors_collapsed: 1 717 786 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: BB1FEC95F8D2AEAEB19FD7FA1D65CFA3717B8AC741CE6A742DEF20FF601FB6F1
| In this chapter I explore in ethnographic detail how the modulations of Free Software undertaken by Connexions and Creative Commons are related to the problems of reuse, modification, and the norms of scholarly production. I present these two projects as responses to the contemporary reorientation of knowledge and power; they are recursive publics just as Free Software is, but they expand the domain of practice in new directions, that is, into the scholarly world of textbooks and research and into the legal domains of cultural production more generally.
@@ -10846,7 +10129,6 @@
.ancestors: 1 717 0 0 786 0 0 0
.ancestors_collapsed: 1 717 786 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 010AEB26B85D91EBDB24A96908A4A8F2019F3B63F92DA33F9123632F69D25581
.has: notes_reg
@@ -10858,7 +10140,6 @@
.ancestors: 1 717 0 0 786 0 0 0
.ancestors_collapsed: 1 717 786 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: AFACE76B27D7AB7B94D2135113230B5ADDA16FF67ED3DCAC2A4234FCCF25C938
| The modulations of Free Software performed by Connexions and Creative Commons reveal two significant issues. The first is the troublesome matter of the meaning of reuse, as in the reuse of concepts, ideas, writings, articles, papers, books, and so on for the creation of new objects of knowledge. Just as software source code can be shared, ported, and forked to create new versions with new functions, and just as software and people can be coordinated in new ways using the Internet, so too can scholarly and scientific content. I explore the implications of this comparison in this chapter. The central gambit of both Connexions and Creative Commons (and much of scientific practice generally) is that new work builds on ⑆,┨[pg 271]┣, previous work. In the sciences the notion that science is cumulative is not at issue, but exactly how scientific knowledge accumulates is far from clear. Even if “standing on the shoulders of giants” can be revealed to hide machinations, secret dealings, and Machiavellian maneuvering of the most craven sort, the very concept of cumulative knowledge is sound. Building a fact, a result, a machine, or a theory out of other, previous works—this kind of reuse as progress is not in question. But the actual material practice of writing, publication, and the reuse of other results and works is something that, until very recently, has been hidden from view, or has been so naturalized that the norms of practice are nearly invisible to practitioners themselves.
@@ -10869,7 +10150,6 @@
.ancestors: 1 717 0 0 786 0 0 0
.ancestors_collapsed: 1 717 786 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 09D94D64FBFB156A6FF727CA1FDFEC7F9788DE5D7E537B79E1F47234EDB2EEBB
.has: notes_reg
@@ -10898,7 +10178,6 @@
.ancestors: 1 717 0 0 786 792 0 0
.ancestors_collapsed: 1 717 786 792 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5A20DEA6F89CBD14FE6369FF8A389DE4C2BA939611AF74392BB845308FD0E666
| More than once, I have found myself in a room with Rich Baraniuk and Brent Hendricks and any number of other employees of the ⑆,┨[pg 272]┣, Connexions project, staring at a whiteboard on which a number of issues and notes have been scrawled. Usually, the notes have a kind of palimpsestic quality, on account of the array of previous conversations that are already there, rewritten in tiny precise script in a corner, or just barely erased beneath our discussion. These conversations are often precipitated by a series of questions that Brent, Ross Reedstrom, and the development team have encountered as they build and refine the system. They are never simple questions. A visitor staring at the whiteboard might catch a glimpse of the peculiar madness that afflicts the project: a mixture of legal terms, technical terms, and terms like scholarly culture or DSP communities. I’m consulted whenever this mixture of terms starts to worry the developers in terms of legality, culture, or the relationship between the two. I’m generally put in the position of speaking either as a lawyer (which, legally speaking, I am not supposed to do) or as an anthropologist (which I do mainly by virtue of holding a position in an anthropology department). Rarely are the things I say met with assent: Brent and Ross, like most hackers, are insanely well versed in the details of intellectual-property law, and they routinely correct me when I make bold but not-quite-true assertions about it. Nonetheless, they rarely feel well versed enough to make decisions about legal issues on their own, and often I have been called—on again as a thoughtful sounding board, and off again as intermediary with Creative Commons.
@@ -10909,7 +10188,6 @@
.ancestors: 1 717 0 0 786 792 0 0
.ancestors_collapsed: 1 717 786 792 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C7E4172677906E694494C5DAD301EB551C77ABA5984174E35FE1DD99475BD634
| This process, I have come to realize, is about figuring something out. It is not just a question of solving technical problems to which I might have some specific domain knowledge. Figuring out is modulation; it is template-work. When Free Software functions as a template for projects like Connexions, it does so literally, by allowing us to trace a known form of practice (Free Software) onto a less well known, seemingly chaotic background and to see where the forms match up and where they do not. One very good way to understand what this means in a particular case—that is, to see more clearly the modulations that Connexions has performed—is to consider the practice and institution of scholarly publication through the template of Free Software.
@@ -10920,7 +10198,6 @@
.ancestors: 1 717 0 0 786 792 0 0
.ancestors_collapsed: 1 717 786 792 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2C7E112604A8319CCE7F796708516252F24070BE241219744628629BF969144B
.has: notes_reg
@@ -10932,7 +10209,6 @@
.ancestors: 1 717 0 0 786 792 0 0
.ancestors_collapsed: 1 717 786 792 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5806E7323113B6F3DD0401CD8F058899874394DBAE132C00E97351CC5487D888
.has: notes_reg
@@ -10944,7 +10220,6 @@
.ancestors: 1 717 0 0 786 792 0 0
.ancestors_collapsed: 1 717 786 792 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D401967B27EF990FCD741AEE6BE947A87E8BB54A10C72EF959A7222BB936A464
| Johns’s work focuses on the elaborate and difficult cultural, social, and economic work involved, in the sixteenth and seventeenth centuries, in transforming the European book into the kind of authority it is taken to be across the globe today. The creation and standardization not just of books but of a publishing infrastructure involved the kind of careful social engineering, reputation management, and skills of distinction, exclusion, and consensus that science studies has effectively explored in science and engineering. Hence, Johns focuses on “print-in-the-making” and the relationship of the print culture of that period to the reliability of knowledge. Instead of making broad claims for the transformation of knowledge by print (eerily similar in many respects to the broad claims made for the Internet), Johns explores the clash of representations and practices necessary to create the sense, in the twentieth century, that there really is or was only one print culture.
@@ -10955,7 +10230,6 @@
.ancestors: 1 717 0 0 786 792 0 0
.ancestors_collapsed: 1 717 786 792 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DA2646AF58CCD4C43634BA35C7726A5A5293DF2DE68C210C195B3B48BA6669C3
| The problem of publication that Connexions confronts is thus not simply caused by the invention or spread of the Internet, much less that of Free Software. Rather, it is a confrontation with the problems of producing stability and finality under very different technical, legal, and social conditions—a problem more complex even than the “different print cultures in particular historical circumstances” that Johns speaks of in regard to the book. Connexions faces two challenges: that of figuring out the difference that today introduces with respect to yesterday, and that of creating or modifying an infrastructure in order to satisfy the demands of a properly authoritative knowledge. Connexions textbooks of necessity look different from conventional textbooks; they consist of digital documents, or “modules,” that are strung together and made available through the Web, under a Creative Commons license that allows for free use, reuse, and modification. This version of “publication” clearly has implications for the meaning of authorship, ownership, stewardship, editing, validation, collaboration, and verification.
@@ -10966,7 +10240,6 @@
.ancestors: 1 717 0 0 786 792 0 0
.ancestors_collapsed: 1 717 786 792 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AC62947F397ADA76BD76D2F5D7BD962DD20BFE0A885EE2F644045324B2BBCB00
| The conventional appearance of a book—in bookstores, through mail-order, in book clubs, libraries, or universities—was an event that signified, as the name suggests, its official public appearance ⑆,┨[pg 275]┣, in the world. Prior to this event, the text circulated only privately, which is to say only among the relatively small network of people who could make copies of it or who were involved in its writing, editing, proofreading, reviewing, typesetting, and so on. With the Internet, the same text can be made instantly available at each of these stages to just as many or more potential readers. It effectively turns the event of publication into a notional event—the click of a button—rather than a highly organized, material event. Although it is clear that the practice of publication has become denaturalized or destabilized by the appearance of new information technologies, this hardly implies that the work of stabilizing the meaning of publication—and producing authoritative knowledge as a result—has ceased. The tricky part comes in understanding how Free Software is used as a template by which the authority of publication in the Gutenberg Galaxy is being transformed into the authority of publication in the Turing Universe.
@@ -10994,7 +10267,6 @@
.ancestors: 1 717 0 0 786 800 0 0
.ancestors_collapsed: 1 717 786 800 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 552949CD451D6E08A592F330BDC1FA6F0809721B8D3F67C9B360F7F8C4247575
| In the case of Connexions there are roughly three stages to the creation of content. The first, temporally speaking, is whatever happens before Connexions is involved, that is, the familiar practices of what I would call composition, rather than simply writing. Some project must be already under way, perhaps started under the constraints of and in the era of the book, perhaps conceived as a digital textbook or an online textbook, but still, as of yet, written on paper or saved in a Word document or in LaTeX, on a scholar’s desktop. It could be an individual project, as in the case of Rich’s initial plan to write a DSP textbook, or it could be a large collaborative project to write a textbook.
@@ -11005,7 +10277,6 @@
.ancestors: 1 717 0 0 786 800 0 0
.ancestors_collapsed: 1 717 786 800 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BF506F3AF28ABA1A33A95D492DA03A3F947339C611C514D9FDCD739FF45482C2
| The second stage is the one in which the document or set of documents is translated (“Connexified”) into the mark-up system used by Connexions. Connexions uses the eXtensible Mark-up Language (XML), in particular a subset of tags that are appropriate to textbooks. These “semantic” tags (e.g., <term>) refer only to the meaning of the text they enclose, not to the “presentation” or syntactic look of what they enclose; they give the document the necessary structure it needs to be transformed in a number of creative ways. Because XML is related only to content, and not to ⑆,┨[pg 276]┣, presentation (it is sometimes referred to as “agnostic”), the same document in Connexions can be automatically made to look a number of different ways, as an onscreen presentation in a browser, as a pdf document, or as an on-demand published work that can be printed out as a book, complete with continuous page numbering, footnotes (instead of links), front and back matter, and an index. Therein lies much of Connexions’s technical wizardry.
@@ -11016,7 +10287,6 @@
.ancestors: 1 717 0 0 786 800 0 0
.ancestors_collapsed: 1 717 786 800 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 55FCCA4CE323168EC91F3A0ECCB21EBA5B83712C2CC5655B6E17C49394ECAE60
| During the second stage, that of being marked up in XML, the document is not quite public, although it is on the Internet; it is in what is called a workgroup, where only those people with access to the particular workgroup (and those have been invited to collaborate) can see the document. It is only when the document is finished, ready to be distributed, that it will enter the third, “published” stage—the stage at which anyone on the Internet can ask for the XML document and the software will display it, using style sheets or software converters, as an HTML page, a pdf document for printing, or as a section of a larger course. However, publication does not here signify finality; indeed, one of the core advantages of Connexions is that the document is rendered less stable than the book-object it mimics: it can be updated, changed, corrected, deleted, copied, and so on, all without any of the rigmarole associated with changing a published book or article. Indeed, the very powerful notion of fixity theorized by McLuhan and Eisenstein is rendered moot here. The fact that a document has been printed (and printed as a book) no longer means that all copies will be the same; indeed, it may well change from hour to hour, depending on how many people contribute (as in the case of Free Software, which can go through revisions and updates as fast, or faster, than one can download and install new versions). With Wikipedia entries that are extremely politicized or active, for example, a “final” text is impossible, although the dynamics of revision and counter-revision do suggest outlines for the emergence of some kinds of stability. But Connexions differs from Wikipedia with respect to this finality as well, because of the insertion of the second stage, during which a self-defined group of people can work on a nonpublic text before committing changes that a public can see.
@@ -11027,7 +10297,6 @@
.ancestors: 1 717 0 0 786 800 0 0
.ancestors_collapsed: 1 717 786 800 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A5E0B337CC6274F9F6297DA0992B4CCF9720A7EEA0FDE506EFB34DE2CA197A58
.has: notes_reg
@@ -11039,7 +10308,6 @@
.ancestors: 1 717 0 0 786 800 0 0
.ancestors_collapsed: 1 717 786 800 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DCDB2DBE9BD108EB971905D617283DB208C1EA25F2B96A3859205DED411639C9
.has: notes_reg
@@ -11051,7 +10319,6 @@
.ancestors: 1 717 0 0 786 800 0 0
.ancestors_collapsed: 1 717 786 800 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5D0BF5A317CC2FADE1E26DD247966825158A7FEA6136FEE4706D6E7DFF3C1344
| In the Connexions repository all changes to a text are tracked and noted, but the identity of the module does not change. “Editions” have thus become “versions,” whereas a substantially revised or changed module might require not reissuance but a forking of that module to create one with a new identity. Editions in publishing are not a feature of the medium per se; they are necessitated by the temporal and spatial practices of publication as an event, though this process is obviously made visible only in the book itself. In the same way, versioning is now used to manage a process, but it results in a very different configuration of the medium and the material available in that medium. Connexions traces the template of software production (sharing, porting, and forking and the norms and forms of coordination in Free Software) directly onto older forms of publication. Where the practices match, no change occurs, and where they don’t, it is the reorientation of knowledge and power and the emergence of recursive publics that serves as a guide to the development of the system.
@@ -11062,7 +10329,6 @@
.ancestors: 1 717 0 0 786 800 0 0
.ancestors_collapsed: 1 717 786 800 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6731486AB9CDC007034F0A81B9A7DEF5D9D1D625F84889EC6C480B487A2E0C50
| Legally speaking, the change from editions to versions and forks raises troubling questions about the boundaries and status of a copyrighted work. It is a peculiar feature of copyright law that it needs to be updated regularly each time the media change, in order to bring certain old practices into line with new possibilities. Scattered throughout the copyright statutes is evidence of old new media: gramophones, jukeboxes, cable TV, photocopiers, peer-to-peer file-sharing programs, and so on. Each new form of communication shifts the assumptions of past media enough that they require a reevaluation of the putative underlying balance of the constitutional mandate that gives (U.S.) intellectual-property law its inertia. Each new device needs to be understood in terms of creation, storage, distribution, production, consumption, and tangibility, in order to assess the dangers it poses to the rights of inventors and artists.
@@ -11073,7 +10339,6 @@
.ancestors: 1 717 0 0 786 800 0 0
.ancestors_collapsed: 1 717 786 800 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 13ED6F3EFA2195056E2FCBD505BBEBBA9A3E565CBAE8BA5F78938EC48A5C7401
| Because copyright law “hard codes” the particular media into the statutes, copyright law is comfortable with, for example, book editions or musical recordings. But in Connexions, new questions arise: how much change constitutes a new work, and thus demands a new copyright license? If a licensee receives one copy of a work, to which versions will he or she retain rights after changes? Because ⑆,┨[pg 279]┣, of the complexity of the software involved, there are also questions that the law simply cannot deal with (just as it had not been able to do in the late 1970s with respect to the definition of software): is the XML document equivalent to the viewable document, or must the style sheet also be included? Where does the “content” begin and the “software” end? Until the statutes either incorporate these new technologies or are changed to govern a more general process, rather than a particular medium, these questions will continue to emerge as part of the practice of writing.
@@ -11084,7 +10349,6 @@
.ancestors: 1 717 0 0 786 800 0 0
.ancestors_collapsed: 1 717 786 800 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DE953355DDA99B6A9981DF1FB0455D57CBF08F8F3AFE132CDD5D66755FB4AA59
.has: notes_reg
@@ -11096,7 +10360,6 @@
.ancestors: 1 717 0 0 786 800 0 0
.ancestors_collapsed: 1 717 786 800 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 76CCF01B53325AE9C673C858D8748441C59C6CE5088E820546ECA36725BA5F40
.has: links notes_reg
@@ -11108,7 +10371,6 @@
.ancestors: 1 717 0 0 786 800 0 0
.ancestors_collapsed: 1 717 786 800 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 36DFFF8DE08ACF1BB7147925ABCFCFC7215A7E5FB82D7ACF7F220AAD8BCD5D58
| These implications are not lost on the Connexions team, but neither are they understood as goals or as having simple solutions. There is a certain immodest, perhaps even reckless, enthusiasm surrounding these implications, an enthusiasm that can take both polymath and transhumanist forms. For instance, the destabilization of the contemporary textbook-publishing system that Connexions represents is (according to Rich) a more accurate way to represent the connections between concepts than a linear textbook format. Connexions thus represents a use of technology as an intervention into an existing context of practice. The fact that Connexions could also render the reliability or trustworthiness of scholarly knowledge unstable is sometimes discussed as an inevitable outcome of technical change—something that the world at large, not Connexions, must learn to deal with.
@@ -11119,7 +10381,6 @@
.ancestors: 1 717 0 0 786 800 0 0
.ancestors_collapsed: 1 717 786 800 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: ADC138B4AC38E8FCF6034D750EA40BE56028F954F54C4BB504983CA433A04F07
| To put it differently, the “goal” of Connexions was never to destroy publishing, but it has been structured by the same kind of imaginations of moral and technical order that pervade Free Software and the construction of the Internet. In this sense Rich, Brent, and others are geeks in the same sense as Free Software geeks: they ⑆,┨[pg 281]┣, share a recursive public devoted to achieving a moral and technical order in which openness and modifiability are core values (“If we are successful, we will disappear”). The implication is that the existing model and infrastructure for the publication of textbooks is of a different moral and technical order, and thus that Connexions needs to innovate not only the technology (the source code or the openness of the system) or the legal arrangements (licenses) but also the very norms and forms of textbook writing itself (coordination and, eventually, a movement). If publication once implied the appearance of reliable, final texts—even if the knowledge therein could be routinely contested by writing more texts and reviews and critiques—Connexions implies the denaturalization of not knowledge per se, but of the process whereby that knowledge is stabilized and rendered reliable, trustworthy.
@@ -11130,7 +10391,6 @@
.ancestors: 1 717 0 0 786 800 0 0
.ancestors_collapsed: 1 717 786 800 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CABA592174A13920537F30E7BB26072269C6BB8558E32407B091064ED75D93ED
| A keyword for the transformation of textbook writing is community, as in the tagline of the Connexions project: “Sharing Knowledge and Building Communities.” Building implies that such communities do not yet exist and that the technology will enable them; however, Connexions began with the assumption that there exist standard academic practices and norms of creating teaching materials. As a result, Connexions both enables these practices and norms, by facilitating a digital version of the textbook, and intervenes in them, by creating a different process for creating a textbook. Communities are both assumed and desired. Sometimes they are real (a group of DSP engineers, networked around Rich and others who work in his subspecialty), and sometimes they are imagined (as when in the process of grant writing we claim that the most important component of the success of the project is the “seeding” of scholarly communities). Communities, furthermore, are not audiences or consumers, and sometimes not even students or learners. They are imagined to be active, creative producers and users of teaching materials, whether for teaching or for the further creation of such materials. The structure of the community has little to do with issues of governance, solidarity, or pedagogy, and much more to do with a set of relationships that might obtain with respect to the creation of teaching materials—a community of collaborative production or collaborative debugging, as in the modulation of forms of coordination, modulated to include the activity of creating teaching materials. ⑆,┨[pg 282]┣,
@@ -11158,7 +10418,6 @@
.ancestors: 1 717 0 0 786 814 0 0
.ancestors_collapsed: 1 717 786 814 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4C59B117C91FF7BB0255BCE1C19308F467B2136AEB3F1751B63F7DDAF57E7714
| One of the most animated whiteboard conversations I remember having with Brent and Ross concerned difference between the possible “roles” that a Connexions user might occupy and the implications this could have for both the technical features of the system and the social norms that Connexions attempts to maintain and replicate. Most software systems are content to designate only “users,” a generic name-and-password account that can be given a set of permissions (and which has behind it a long and robust tradition in computer-operating-system and security research). Users are users, even if they may have access to different programs and files. What Connexions needed was a way to designate that the same person might have two different exogenous roles: a user might be the author, but not the owner of the content, and vice versa. For instance, perhaps Rice University maintains the copyright for a work, but the author is credited for its creation. Such a situation—known, in legal terms, as “work for hire”—is routine in some universities and most corporations. So while the author is generally given the freedom and authority to create and modify the text as he or she sees fit, the university asserts copyright ownership in order to retain the right to commercially exploit the work. Such a situation is far from settled and is, of course, politically fraught, but the Connexions system, in order to be useful at all to anyone, needed to accommodate this fact. Taking an oppositional political stand would render the system useless in too many cases or cause it to become precisely the kind of authorless, creditless system as Wikipedia—a route not desired by many academics. In a perfectly open world all Connexions modules might each have identical authors and owners, but pragmatism demands that the two roles be kept separate.
@@ -11169,7 +10428,6 @@
.ancestors: 1 717 0 0 786 814 0 0
.ancestors_collapsed: 1 717 786 814 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C394A7404F9D1186611326F72E4D738C2282544CF7E1AED326E6AB5B6A7E716A
.has: notes_reg
@@ -11181,7 +10439,6 @@
.ancestors: 1 717 0 0 786 814 0 0
.ancestors_collapsed: 1 717 786 814 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 94FF5A38C09794F82DC928E2126602A561A3FE49F2928811154106F62A752BA8
| As Brent, Ross, and I stared at the whiteboard, the discovery of the need for multiple exogenous roles hit all of us in a kind of slow-motion shockwave. It was not simply that the content needed to have different labels attached to it to keep track of these people in a database—something deeper was at work: the law and the practice of authorship actually dictated, to a certain extent, what the software itself should look like. All of sudden, the questions were preformatted, so to speak, by the law and by certain kinds of practices that had been normalized and thus were nearly invisible: who should have permission to change what? Who will have permission to add or drop authors? Who will be allowed to make what changes, and who will have the legal right to do so and who the moral or customary right? What implications follow from the choices the designers make and the choices we present to authors or maintainers?
@@ -11192,7 +10449,6 @@
.ancestors: 1 717 0 0 786 814 0 0
.ancestors_collapsed: 1 717 786 814 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 247AC1F6A6BC03CE3A1A7128B551872052F15D88E1D0A53F45B34BD22ABA01A1
| The Creative Commons licenses were key to revealing many of these questions. The licenses were in themselves modulations of Free Software licenses, but created with people like artists, musicians, scholars, and filmmakers in mind. Without them, the content in Connexions would be unlicensed, perhaps intended to be in the public domain, but ultimately governed by copyright statutes that provided no clear answers to any of these questions, as those statutes were designed to deal with older media and a different publication process. Using the Creative Commons licenses, on the other hand, meant that the situation of the content in Connexions became well-defined enough, in a legal sense, to be used as a constraint in defining the structure of the software system. The license itself provided the map of the territory by setting parameters for things such as distribution, modification, attribution, and even display, reading, or copying.
@@ -11203,7 +10459,6 @@
.ancestors: 1 717 0 0 786 814 0 0
.ancestors_collapsed: 1 717 786 814 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 608BF6155661ED5B69428BEDEA9B636A1DB2DBD10A0B7B3C72FF6D3A7ADE79BA
| For instance, when the author and owner are different, it is not at all obvious who should be given credit. Authors, especially academic authors, expect to be given credit (which is often all they get) for an article or a textbook they have written, yet universities often retain ownership of those textbooks, and ownership would seem to imply a legal right to be identified as both owner and author (e.g., Forrester Research reports or UNESCO reports, which hide the ⑆,┨[pg 284]┣, identity of authors). In the absence of any licenses, such a scenario has no obvious solution or depends entirely on the specific context. However, the Creative Commons licenses specified the meaning of attribution and the requirement to maintain the copyright notice, thus outlining a procedure that gave the Connexions designers fixed constraints against which to measure how they would implement their system.
@@ -11214,7 +10469,6 @@
.ancestors: 1 717 0 0 786 814 0 0
.ancestors_collapsed: 1 717 786 814 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7C9CAD0FBF601C5CDA095E8458A0B654725D4BA27C8DD5E6AF8F760B890A386F
| A positive result of such constraints is that they allow for a kind of institutional flexibility that would not otherwise be possible. Whether a university insists on expropriating copyright or allows scholars to keep their copyrights, both can use Connexions. Connexions is more “open” than traditional textbook publishing because it allows a greater number of heterogeneous contributors to participate, but it is also more “open” than something like Wikipedia, which is ideologically committed to a single definition of authorship and ownership (anonymous, reciprocally licensed collaborative creation by authors who are also the owners of their work). While Wikipedia makes such an ideological commitment, it cannot be used by institutions that have made the decision to operate as expropriators of content, or even in cases wherein authors willingly allow someone else to take credit. If authors and owners must be identical, then either the author is identified as the owner, which is illegal in some cases, or the owner is identified as the author, a situation no academic is willing to submit to.
@@ -11225,7 +10479,6 @@
.ancestors: 1 717 0 0 786 814 0 0
.ancestors_collapsed: 1 717 786 814 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A7AF67A00599719754C92F8B33CF4758007B5DF3863454851A68A449455AA0D8
.has: notes_reg
@@ -11237,7 +10490,6 @@
.ancestors: 1 717 0 0 786 814 0 0
.ancestors_collapsed: 1 717 786 814 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C5D1712C0847223CF0536210A7AEECBE5F8DB2FD37B0900E889B3CB527601B5B
| The discussion of roles circulated fluidly across concepts like law (and legal licenses), norms, community, and identity. Brent and Ross and others involved had developed sophisticated imaginations of how Connexions would fit into the existing ecology of academia, constrained all the while by both standard goals, like usability and efficiency, and by novel legal licenses and concerns about the changing practices of authors and scholars. The question, for instance, of how a module can be used (technically, legally) is often confused with, or difficult to disentangle from, how a module should be used (technically, legally, or, more generally, “socially”—with usage shaped by the community who uses it). In order to make sense of this, Connexions programmers and participants like myself are prone to using the language of custom and norm, and the figure of community, as in “the customary norms of a scholarly community.”
@@ -11265,7 +10517,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 88E128393961EDECE1487E2AABD82E4170734723670BECD479D758419CB23937
| The meaning of publication in Connexions and the questions about roles and their proper legal status emerged from the core concern with reuse, which is the primary modulation of Free Software that Connexions carries out: the modulation of the meaning of source code to include textbook writing. What makes source code such a central component of Free Software is the manner in which it is shared and transformed, not the technical features of any particular language or program. So the modulation of source code to include textbooks is not just an attempt to make textbooks exact, algorithmic, or digital, but an experiment in sharing textbook writing in a similar fashion.
@@ -11276,7 +10527,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B2C6B4F26E5AEB98E1871D0021E0924579C8CA1E231B1631AEB5AA1566464208
| This modulation also affects the other components: it creates a demand for openness in textbook creation and circulation; it demands new kinds of copyright licenses (the Creative Commons licenses); and it affects the meaning of coordination among scholars, ranging from explicit forms of collaboration and co-creation to the entire spectrum of uses and reuses that scholars normally make of their ⑆,┨[pg 286]┣, peers’ works. It is this modulation of coordination that leads to the second core concern of Connexions: that of the existence of “norms” of scholarly creation, use, reuse, publication, and circulation.
@@ -11287,7 +10537,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5CD151FE80539983371A60A798FEE5F3DB015E1B035C39D8F3FEFB21B6496904
| Since software programmers and engineers are prone to thinking about things in concrete, practical, and detailed ways, discussions of creation, use, and circulation are rarely conducted at the level of philosophical abstraction. They are carried out on whiteboards, using diagrams.
@@ -11298,7 +10547,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 092121E072642339A21508EF079DEEF5E76B7A6989B3C9B3E513907F78B90614
| The whiteboard diagram transcribed in figure 8 was precipitated by a fairly precise question: “When is the reuse of something in a module (or of an entire module) governed by ‘academic norms’ and when is it subject to the legal constraints of the licenses?” For someone to quote a piece of text from one module in another is considered normal practice and thus shouldn’t involve concerns about legal rights and duties to fork the module (create a new modified version, perhaps containing only the section cited, which is something legal licenses explicitly allow). But what if someone borrows, say, all of the equations in a module about information theory and uses them to illustrate a very different point in a different module. Does he or she have either a normal or a legal right to do so? Should the equations be cited? What should that citation look like? What if the equations are particularly hard to mark-up in the MathML language and therefore represent a significant investment in time on the part of the original author? Should the law govern this activity, or should norms?
@@ -11309,7 +10557,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 869ECBDD027F51B30EF5A35EA0F3F8A22F27B04540E28ABBE419240407F05A86
.image: 2bits_09_08-100.png sha256:E6580C137883B81D2180EDAFBEBE6AD091928702D4D1EB90541053E54605F812 bytes:267023 px:788x658
@@ -11322,7 +10569,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E360C88786DE46E53D1D9DF359BF3BF31F2308D1EE548DECE54B80FDA14325A2
| There is a natural tendency among geeks to answer these questions solely with respect to the law; it is, after all, highly codified and seemingly authoritative on such issues. However, there is often no need to engage the law, because of the presumed consensus (“academic norms”) about how to proceed, even if those norms conflict with the law. But these norms are nowhere codified, and this makes geeks (and, increasingly, academics themselves) uneasy. As in the case of a requirement of attribution, the constraints of a written license are perceived to be much more stable and reliable than those of culture, precisely because culture is what remains contested and contestable. So the idea of creating a new “version” of a text is easier to understand when it is clearly circumscribed as a legally defined “derivative work.” The Connexions software was therefore implemented in such a way that the legal right to create a derived work (to fork a module) could be done with the press of ⑆,┨[pg 287]┣, a button: a distinct module is automatically created, and it retains the name of the original author and the original owner, but now also includes the new author’s name as author and maintainer. That new author can proceed to make any number of changes.
@@ -11333,7 +10579,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 565059635C5BA3FA01273CC39C1D66F57ED9197C53BB3691A650B5DB8C61AEE3
| But is forking always necessary? What if the derivative work contains only a few spelling corrections and slightly updated information? Why not change the existing module (where such changes would be more akin to issuing a new edition), rather than create a legally defined derivative work? Why not simply suggest the changes to the original author? Why not collaborate? While a legal license gives people the right to do all of these things without ever consulting the person who licensed it, there may well be occasions ⑆,┨[pg 288]┣, when it makes much more sense to ignore those rights in favor of other norms. The answers to these questions depend a great deal on the kind and the intent of the reuse. A refined version of the whiteboard diagram, depicted in figure 9, attempts to capture the various kinds of reuse and their intersection with laws, norms, and technologies.
@@ -11344,7 +10589,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1B09489E7EA84F5989FF04AB1E4732472B4FE36BD4D84BCF7F2B4038AA4D1CC4
.image: 2bits_09_09-100.png sha256:3F61BEC183DC80713C10A54C93D0C719ED3E174152D2601AACF35DEC456D37F6 bytes:20367 px:811x492
@@ -11357,7 +10601,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1D44446713E45BE8F99953122A52850A39FD97068854AB24DC89CA749EE2AD76
| The center of the diagram contains a list of different kinds of imaginable reuses, arrayed from least interventionist at the top to most interventionist at the bottom, and it implies that as the intended transformations become more drastic, the likelihood of collaboration with the original author decreases. The arrow on the left indicates the legal path from cultural norms to protected fair uses; the arrow on the right indicates the technical path from built-in legal constraints based on the licenses to software tools that make collaboration (according to presumed scholarly norms) easier than the alternative (exercising the legal right to make a derivative work). With the benefit of hindsight, it seems that the arrows on either side should actually be a circle that connect laws, technologies, and norms in a chain of influence and constraint, since it is clear in retrospect that the norms of authorial practice have actually changed (or at least have been made explicit) based on the existence of licenses and the types of tools available (such as blogs and Wikipedia).
@@ -11368,7 +10611,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5DC5601155F37586DBB88B67CA1B51480880A8A4C21278EFAAE757E98A74199A
| The diagram can best be understood as a way of representing, to Connexions itself (and its funders), the experiment under way with the components of Free Software. By modulating source code to include the writing of scholarly textbooks, Connexions made visible the need for new copyright licenses appropriate to this content; by making the system Internet-based and relying on open standards such as XML and Open Source components, Connexions also modulated the concept of openness to include textbook publication; and by making the system possible as an open repository of freely licensed textbook modules, Connexions made visible the changed conditions of coordination, not just between two collaborating authors, but within the entire system of publication, citation, use, reuse, borrowing, building on, plagiarizing, copying, emulating, and so on. Such changes to coordination may or may not take hold. For many scholars, they pose an immodest challenge to a working system that has developed over centuries, but for others they represent the removal of arbitrary constraints that prevent ⑆,┨[pg 289]┣, novel and innovative forms of knowledge creation and association rendered possible in the last thirty to forty years (and especially in the last ten). For some, these modulations might form the basis for a final modulation—a Free Textbooks movement—but as yet no such movement exists.
@@ -11379,7 +10621,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9FC547E25E2001385288D5A654779ED7B2F294CECC74074E3C7F0647348F9181
| In the case of shared software source code, one of the principal reasons for sharing it was to reuse it: to build on it, to link to it, to employ it in ways that made building more complex objects into an easier task. The very design philosophy of UNIX well articulates the necessity of modularity and reuse, and the idea is no less powerful in other areas, such as textbooks. But just as the reuse of software is not simply a feature of software’s technical characteristics, the idea of “reusing” scholarly materials implies all kinds of questions that are not simply questions of recombining texts. The ability to share source code—and the ability to create complex software based on it—requires modulations of both the legal meaning of software, as in the case of EMACS, and the organizational form, as in the ⑆,┨[pg 290]┣, emergence of Free Software projects other than the Free Software Foundation (the Linux kernel, Perl, Apache, etc.).
@@ -11390,7 +10631,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 05A755AE06ED059FFD7CE423986A490B63600D81C1A93C01FE4D998D1E09A6CC
.has: notes_reg
@@ -11402,7 +10642,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5B7981BDB538CD5BBC25F2C58E7E088B59822ED30736FD55137E13CDD7A23C6A
.has: notes_reg
@@ -11414,7 +10653,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4515F8F7B915A7B785B8C21D5634FCFAFCD0C4C13FBDBB111FEC07D025B10E11
| The Connexions software does not, however, enforce disciplinary differences. If anything it makes very strong and troubling claims that knowledge is knowledge and that disciplinary constraints are arbitrary. Thus, for instance, if a biologist wishes to transform a literary scholar’s article on Darwin’s tropes to make it reflect current evolutionary theory, he or she could do so; it is entirely possible, both legally and technically. The literary scholar could react in a number of ways, including outrage that the biologist has misread or misunderstood the work or pleasure in seeing the work refined. Connexions adheres rigorously to its ideas of openness in this regard; it neither encourages nor censures such behavior.
@@ -11425,7 +10663,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 67510F0B0C0B8FB5DCB8F1FAECAD07C19DD760D415420AA0218BD7E837826007
| By contrast, as figure 9 suggests, the relationship between these two scholars can be governed either by the legal specification of rights contained in the licenses (a privately ordered legal regime dependent on a national-cum-global statutory regime) or by the customary means of collaboration enabled, perhaps enhanced, by software tools. The former is the domain of the state, the legal profession, and a moral and technical order that, for lack of a better word, might be called modernity. The latter, however, is the domain of the cultural, the informal, the practical, the interpersonal; it is the domain of ethics (prior to its modernization, perhaps) and of tradition.
@@ -11436,7 +10673,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 412D4EA77113E263044BB3316D0E59581B7F18E33F11A33603E0F091D4689DA6
| If figure 9 is a recapitulation of modernity and tradition (what better role for an anthropologist to play!), then the presumptive boundaries around “communities” define which groups possess which norms. But the very design of Connexions—its technical and legal exactitude—immediately brings a potentially huge variety of traditions into conflict with one another. Can the biologist and the literary scholar be expected to occupy the same universe of norms? Does the fact of being academics, employees of a university, ⑆,┨[pg 292]┣, or readers of Darwin ensure this sharing of norms? How are the boundaries policed and the norms communicated and reinforced?
@@ -11447,7 +10683,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4E1C84273EC30B6C6DE43B8937B3AF534451B64DBF826FB81CBEDF6067C4B4C9
.has: notes_reg
@@ -11459,7 +10694,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CFC97AE8E927E8239DB807420507246C969CB6DFFFA44DFFC3176DB1EBFABA68
.has: notes_reg
@@ -11471,7 +10705,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 98BF7FD92D7005B3A592E91260E4DB2B858CAB31B7B8C53C59AE83DF0A66A863
| The answer that my informants give, in practice, concerning the mode of existence of cultural norms is neither. On the one hand, in the Connexions project the question of the mode of existence of academic norms is unanswered; the basic assumption is that certain actions are captured and constrained neither by legal constraints nor technical barriers, and that it takes people who know or study “communities” (i.e., nonlegal and nontechnical constraints) to figure out what those actions may be. On some days, the project is modestly understood to enable academics to do what they do faster and better, but without fundamentally changing anything about the practice, institutions, or legal relations; on other days, however, it is a radically transformative project, changing how people think about creating scholarly work, a project that requires educating people and potentially “changing the culture” of scholarly work, including its technology, its legal relations, and its practices.
@@ -11482,7 +10715,6 @@
.ancestors: 1 717 0 0 786 823 0 0
.ancestors_collapsed: 1 717 786 823 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 60A855518917C680713EA03C1661242C87774C35EB699D8E104D41692C56B220
| In stark contrast (despite the very large degree of simpatico), the principal members of Creative Commons answer the question of the existence of norms quite differently than do those in Connexions: ⑆,┨[pg 293]┣, they assert that norms not only change but are manipulated and/or channeled by the modulation of technical and legal practices (this is the novel version of law and economics that Creative Commons is founded on). Such an assertion leaves very little for norms or for culture; there may be a deep evolutionary role for rule following or for choosing socially sanctioned behavior over socially unacceptable behavior, but the real action happens in the legal and technical domains. In Creative Commons the question of the existence of norms is answered firmly in the phrase coined by Glenn Brown: “punt to culture.” For Creative Commons, norms are a prelegal and pretechnical substrate upon which the licenses they create operate. Norms must exist for the strategy employed in the licenses to make sense—as the following story illustrates.
@@ -11510,7 +10742,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9039BE2C693BD467A9738EAB81D8EC6A8BA54EAAECE1D18C61CBF8D5AC54CC48
| More than once, I have found myself on the telephone with Glenn Brown, staring at notes, a diagram, or some inscrutable collection of legalese. Usually, the conversations wander from fine legal points to music and Texas politics to Glenn’s travels around the globe. They are often precipitated by some previous conversation and by Glenn’s need to remind himself (and me) what we are in the middle of creating. Or destroying. His are never simple questions. While the Connexions project started with a repository of scholarly content in need of a license, Creative Commons started with licenses in need of particular kinds of content. But both projects required participants to delve into the details of both licenses and the structure of digital content, which qualified me, for both projects, as the intermediary who could help explore these intersections. My phone conversations with Glenn, then, were much like the whiteboard conversations at Connexions: filled with a mix of technical and legal terminology, and conducted largely in order to give Glenn the sense that he had cross-checked his plans with someone presumed to know better. I can’t count the number of times I have hung up the phone or left the conference room wondering, “Have I just sanctioned something mad?” Yet rarely have I felt that my interventions served to do more than confirm suspicions or derail already unstable arguments. ⑆,┨[pg 294]┣,
@@ -11521,7 +10752,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 87B991FFED1FF253DC78B6D4FD3238267A46A392095BF866864878270DA61648
| In one particular conversation—the “punt to culture” conversation—I found myself bewildered by a sudden understanding of the process of writing legal licenses and of the particular assumptions about human behavior that need to be present in order to imagine creating these licenses or ensuring that they will be beneficial to the people who will use them.
@@ -11532,7 +10762,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 297A24564402284F755E4427309914FAFB3F92051C95F37E5E7CCDEA330348EB
.has: notes_reg
@@ -11544,7 +10773,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 72832271185A60131E494A389DCCD4F0CA87C7CBE34362958866B94A1D81CB62
| I helped write, read, and think about the first of the Creative Commons licenses, and it was through this experience that I came to understand how the crafting of legal language works, and in particular how the mode of existence of cultural or social norms relates to the crafting of legal language. Creative Commons licenses are not a familiar legal entity, however. They are modulations of the Free Software license, but they differ in important ways.
@@ -11555,7 +10783,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EC2C47CB35CE6519B6ECD226C468EEC2457371DFC61B16D38EB2D106DAC57903
.has: notes_reg
@@ -11567,7 +10794,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 24F2A15FC4897971F892459B5FF35724075B6DAB27950D4DBE15BE4FED4B12B6
| But what if Sahlins had chosen a license that allowed modification of his work. This would mean that I, Christopher Kelty, whether in agreement with or in objection to his work, could download the paper, rewrite large sections of it, add in my own baroque and idiosyncratic scholarship, and write a section that purports to debunk (or, what could amount to the same, augment) Sahlins’s arguments. I would then be legally entitled to re-release the paper as “© 2004 Marshall Sahlins, with modifications © 2007 Christopher Kelty,” so long as Sahlins is identified as the author of the paper. The nature or extent of the modifications is not legally restricted, but both the original and the modified version would be legally attributed to Sahlins (even though he would own only the first paper).
@@ -11578,7 +10804,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E5BC7ECDEBB0A4FAACE6E6D77D5BC574ACED3CA47D533300054CD03AE15B69EE
| In the course of a number of e-mails, chat sessions, and phone conversations with Glenn, I raised this example and proposed that the licenses needed a way to account for it, since it seemed to me entirely possible that were I to produce a modified work that so distorted Sahlins’s original argument that he did not want to be associated with the modified paper, then he should have the right also to repudiate his identification as author. Sahlins should, legally speaking, be able to ask me to remove his name from all subsequent versions of my misrepresentation, thus clearing his good name and providing me the freedom to continue sullying mine into obscurity. After hashing it out with the expensive Palo Alto legal firm that was officially drafting the licenses, we came up with text that said: ⑆,┨[pg 296]┣, “If You create a Derivative Work, upon notice from any Licensor You must, to the extent practicable, remove from the Derivative Work any reference to such Licensor or the Original Author, as requested.”
@@ -11589,7 +10814,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5E2E14ED6FD672DD3E4FABA7D61EC6ACFE1481DB4D8295333734462E2F440E95
| The bulk of our discussion centered around the need for the phrase, “to the extent practicable.” Glenn asked me, “How is the original author supposed to monitor all the possible uses of her name? How will she enforce this clause? Isn’t it going to be difficult to remove the name from every copy?” Glenn was imagining a situation of strict adherence, one in which the presence of the name on the paper was the same as the reputation of the individual, regardless of who actually read it. On this theory, until all traces of the author’s name were expunged from each of these teratomata circulating in the world, there could be no peace, and no rest for the wronged.
@@ -11600,7 +10824,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DFE566E95F946D4E5A54549A72D2E91D2870B230AF6339FD1DBEB37A09F7FC7A
| I paused, then gave the kind of sigh meant to imply that I had come to my hard-won understandings of culture through arduous dissertation research: “It probably won’t need to be strictly enforced in all cases—only in the significant ones. Scholars tend to respond to each other only in very circumscribed cases, by writing letters to the editor or by sending responses or rebuttals to the journal that published the work. It takes a lot of work to really police a reputation, and it differs from discipline to discipline. Sometimes, drastic action might be needed, usually not. There is so much misuse and abuse of people’s arguments and work going on all the time that people only react when they are directly confronted with serious abuses. And even so, it is only in cases of negative criticism or misuse that people need respond. When a scholar uses someone’s work approvingly, but incorrectly, it is usually considered petulant (at best) to correct them publicly.”
@@ -11611,7 +10834,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1BF47A950CB985C3E250AFFF14A942B9AED73C0E7A36F74B37ECA364A6F93912
| “In short,” I said, leaning back in my chair and acting the part of expert, “it’s like, you know, c’mon—it isn’t all law, there are a bunch of, you know, informal rules of civility and stuff that govern that sort of thing.”
@@ -11622,7 +10844,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D0DBBB452834656A8FC379D9806FCAAEAA34ECB9E2CFDAC29C683786AB40EA9F
| Then Glenn said., “Oh, okay, well that’s when we punt to culture.”
@@ -11633,7 +10854,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9E4FC884B15613053F73405A6DFADF06406331891FB4BD6E68D0F1E27474DD17
| When I heard this phrase, I leaned too far back and fell over, joyfully stunned. Glenn had managed to capture what no amount of fieldwork, with however many subjects, could have. Some combination of American football, a twist of Hobbes or Holmes, and a lived understanding of what exactly these copyright licenses are ⑆,┨[pg 297]┣, meant to achieve gave this phrase a luminosity I usually associate only with Balinese cock-fights. It encapsulated, almost as a slogan, a very precise explanation of what Creative Commons had undertaken. It was not a theory Glenn proposed with this phrase, but a strategy in which a particular, if vague, theory of culture played a role.
@@ -11644,7 +10864,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FA55BE8F3ECF33D5E7A5CBD83C300688641F1F7E2B81AA892B434D8DC3DEB5D4
| For those unfamiliar, a bit of background on U.S. football may help. When two teams square off on the football field, the offensive team gets four attempts, called “downs,” to move the ball either ten yards forward or into the end zone for a score. The first three downs usually involve one of two strategies: run or pass, run or pass. On the fourth down, however, the offensive team must either “go for it” (run or pass), kick a field goal (if close enough to the end zone), or “punt” the ball to the other team. Punting is a somewhat disappointing option, because it means giving up possession of the ball to the other team, but it has the advantage of putting the other team as far back on the playing field as possible, thus decreasing its likelihood of scoring.
@@ -11655,7 +10874,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2F3B6106B26680F90DA05AD4F3F03C2C2151F7C5D4AC1C839A1A50943392F366
| To “punt to culture,” then, suggests that copyright licenses try three times to legally restrict what a user or consumer of a work can make of it. By using the existing federal intellectual-property laws and the rules of license and contract writing, copyright licenses articulate to people what they can and cannot do with that work according to law. While the licenses do not (they cannot) force people, in any tangible sense, to do one thing or another, they can use the language of law and contract to warn people, and perhaps obliquely, to threaten them. If the licenses end up silent on a point—if there is no “score,” to continue the analogy—then it’s time to punt to culture. Rather than make more law, or call in the police, the license strategy relies on culture to fill in the gaps with people’s own understandings of what is right and wrong, beyond the law. It operationalizes a theory of culture, a theory that emphasizes the sovereignty of nonstate customs and the diversity of systems of cultural norms. Creative Commons would prefer that its licenses remain legally minimalist. It would much prefer to assume—indeed, the licenses implicitly require—the robust, powerful existence of this multifarious, hetero-physiognomic, and formidable opponent to the law with neither uniform nor mascot, hunched at the far end of the field, preparing to, so to speak, clean law’s clock. ⑆,┨[pg 298]┣,
@@ -11666,7 +10884,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EB779D32193C0852504FE227ED17A89A06D3F0FDC510DCAD28A0E37E41FAE94D
| Creative Commons’s “culture” thus seems to be a somewhat vague mixture of many familiar theories. Culture is an unspecified but finely articulated set of given, evolved, designed, informal, practiced, habitual, local, social, civil, or historical norms that are expected to govern the behavior of individuals in the absence of a state, a court, a king, or a police force, at one of any number of scales. It is not monolithic (indeed, my self-assured explanation concerned only the norms of “academia”), but assumes a diversity beyond enumeration. It employs elements of relativism—any culture should be able to trump the legal rules. It is not a hereditary biological theory, but one that assumes historical contingency and arbitrary structures.
@@ -11677,7 +10894,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F2841AB34DC153ECA144C315ECDFEB1C87F6D36EED26ADA5582BEB7DEF4A4D47
| Certainly, whatever culture is, it is separate from law. Law is, to borrow Sharon Traweek’s famous phrase, “a culture of no culture” in this sense. It is not the cultural and normative practices of legal scholars, judges, lawyers, legislators, and lobbyists that determine what laws will look like, but their careful, expert, noncultural ratiocination. In this sense, punting to culture implies that laws are the result of human design, whereas culture is the result of human action, but not of human design. Law is systematic and tractable; culture may have a deep structure, but it is intractable to human design. It can, however, be channeled and tracked, nudged or guided, by law.
@@ -11688,7 +10904,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D76D72F6C1BC2597423FD63430948AB27D0FE99EDF94370B67D210D1B1127E79
| Thus, Lawrence Lessig, one of the founders of Creative Commons has written extensively about the “regulation of social meaning,” using cases such as those involving the use or nonuse of seatbelts or whether or not to allow smoking in public places. The decision not to wear a seatbelt, for instance, may have much more to do with the contextual meaning of putting on a seatbelt (don’t you trust the cab driver?) than with either the existence of the seatbelt (or automatic seatbelts, for that matter) or with laws demanding their use. According to Lessig, the best law can do in the face of custom is to change the meaning of wearing the seatbelt: to give the refusal a dishonorable rather than an honorable meaning. Creative Commons licenses are based on a similar assumption: the law is relatively powerless in the face of entrenched academic or artistic customs, and so the best the licenses can do is channel the meaning of sharing and reuse, of copyright control or infringement. As Glenn explained in the context of a discussion about a license that would allow music sampling. ⑆,┨[pg 299]┣,
@@ -11699,7 +10914,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 85D6851E9DB1CF533B6AA60132B80FF1E57D17ECCDCB48EE7EB9942FFD192B61
.indent: 1 1
@@ -11711,7 +10925,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F5E53ECEDA42E5094C1E69EC9F9D220A00CD55DBF1998D5B005C2B50AAA87E11
.indent: 1 1
@@ -11724,7 +10937,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 70108552EB0DFECD917EF5D82A7A8F574762444486FA7612E19701611C60DAFE
.has: notes_reg
@@ -11736,7 +10948,6 @@
.ancestors: 1 717 0 0 786 844 0 0
.ancestors_collapsed: 1 717 786 844 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B769F63BE92D878F7CC984CD839024087EE964CCC57B3C9EDEB8FC6228BE802A
| At stake, then, is the construction of both technologies and legal licenses that, as Brent and Rich would assert, “make it easy for users to do the right thing.” The “right thing,” however, is precisely what goes unstated: the moral and technical order that guides the design of both licenses and tools. Connexions users are given tools that facilitate citation, acknowledgment, attribution, and certain kinds of reuse instead of tools that privilege anonymity or facilitate proliferation or encourage nonreciprocal collaborations. By the same token, Creative Commons licenses, while legally binding, are created with the aim of changing norms: they promote attribution and citation; they promote fair use and clearly designated uses; they are written to give users flexibility to decide what kinds of things should be allowed and what kinds shouldn’t. Without a doubt, the “right thing” is right for some people and not for others—and it is thus political. But the criteria for what is right are not ⑆,┨[pg 300]┣, merely political; the criteria are what constitute the affinity of these geeks in the first place, what makes them a recursive public. They see in these instruments the possibility for the creation of authentic publics whose role is to stand outside power, outside markets, and to participate in sovereignty, and through this participation to produce liberty without sacrificing stability.
@@ -11764,7 +10975,6 @@
.ancestors: 1 717 0 0 786 866 0 0
.ancestors_collapsed: 1 717 786 866 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AA226EB04C972F8EB457F172377012072F95511FC7E9B8986350C1DF18D777FA
| What happens when geeks modulate the practices that make up Free Software? What is the intuition or the cultural significance of Free Software that makes people want to emulate and modulate it? Creative Commons and Connexions modulate the practices of Free Software and extend them in new ways. They change the meaning of shared source code to include shared nonsoftware, and they try to apply the practices of license writing, coordination, and openness to new domains. At one level, such an activity is fascinating simply because of what it reveals: in the case of Connexions, it reveals the problem of determining the finality of a work. How should the authority, stability, and reliability of knowledge be assessed when work can be rendered permanently modifiable? It is an activity that reveals the complexity of the system of authorization and evaluation that has been built in the past.
@@ -11775,7 +10985,6 @@
.ancestors: 1 717 0 0 786 866 0 0
.ancestors_collapsed: 1 717 786 866 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 58FE81D19AB902AAB95FD25F2DE3354D74CE324252185563AD53C0728FBA7D2D
| The intuition that Connexions and Creative Commons draw from Free Software is an intuition about the authority of knowledge, about a reorientation of knowledge and power that demands a response. That response needs to be technical and legal, to be sure, but it also needs to be public—a response that defines the meaning of finality publicly and openly and makes modifiability an irreversible aspect of the process of stabilizing knowledge. Such a commitment is incompatible with the provision of stable knowledge by unaccountable private parties, whether individuals or corporations or governments, or by technical fiat. There must always remain the possibility that someone can question, change, reuse, and modify according to their needs.
@@ -11836,7 +11045,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DF5F2A3728E7D9EF3366120BE0200A1D8EA8B697FF6519927D3663433E6CF7F3
| Free Software is changing. In all aspects it looks very different from when I started, and in many ways the Free Software described herein is not the Free Software readers will encounter if they turn to the Internet to find it. But how could it be otherwise? If the argument I make in Two Bits is at all correct, then modulation must constantly be occurring, for experimentation never seeks its own conclusion. A question remains, though: in changing, does Free Software and its kin preserve the imagination of moral and technical order that created it? Is the recursive public something that survives, orders, or makes sense of these changes? Does Free Software exist for more than its own sake?
@@ -11847,7 +11055,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 52D8C11F6263743AD7DD2F636DBB235DF2D5BB681BC74B1992407F000CB3958C
.has: links notes_reg
@@ -11873,7 +11080,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FAC72164E604AA3ABFD9FB8B8B497974F0AD103A7877C6F1DA3D3BF1D5C90CB0
.has: notes_reg
@@ -11885,7 +11091,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 93C1713E1F07184010FFDFDDB213BF2CCC4FB6276D1137C4D59572CBC9FC8FB1
| But what questions should one ask? Where should scholars or curious onlookers focus their attention in order to see whether or not a recursive public is at work? Many of these questions are simple, ⑆,┨[pg 303]┣, practical ones: are software and networks involved at any level? Do the participants claim to understand Free Software or Open Source, either in their details or as an inspiration? Is intellectual-property law a key problem? Are participants trying to coordinate each other through the Internet, and are they trying to take advantage of voluntary, self-directed contributions of some kind? More specifically, are participants modulating one of these practices? Are they thinking about something in terms of source code, or source and binary? Are they changing or creating new forms of licenses, contracts, or privately ordered legal arrangements? Are they experimenting with forms of coordinating the voluntary actions of large numbers of unevenly distributed people? Are the people who are contributing aware of or actively pursuing questions of ideology, distinction, movement, or opposition? Are these practices recognized as something that creates the possibility for affinity, rather than simply arcane “technical” practices that are too complex to understand or appreciate?
@@ -11896,7 +11101,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1FF2A2162E44382232DA6125871EC325E3E4BB4B23C805206FEF90B671D5F75D
| In the last few years, talk of “social software” or “Web 2.0” has dominated the circuit of geek and entrepreneur conferences and discussions: Wikipedia, MySpace, Flickr, and YouTube, for example. For instance, there are scores and scores of “social” music sites, with collaborative rating, music sharing, music discovery, and so forth. Many of these directly use or take inspiration from Free Software. For all of them, intellectual property is a central and dominating concern. Key to their novelty is the leveraging and coordinating of massive numbers of people along restricted lines (i.e., music preferences that guide music discovery). Some even advocate or lobby for free(er) access to digital music. But they are not (yet) what I would identify as recursive publics: most of them are commercial entities whose structure and technical specifications are closely guarded and not open to modification. While some such entities may deal in freely licensed content (for instance, Creative Commons-licensed music), few are interested in allowing strangers to participate in, modulate, or modify the system as such; they are interested in allowing users to become consumers in more and more sophisticated ways, and not necessarily in facilitating a public culture of music. They want information and knowledge to be free, to be sure, but not necessarily the infrastructure that makes that information available and knowledge possible. Such entities lack the “recursive” commitment. ⑆,┨[pg 304]┣,
@@ -11907,7 +11111,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F257143F8985979E50F297CBC619229FA93EFA69CA1EB796D0B8B2B331AA3ABA
| By contrast, some corners of the open-access movement are more likely to meet this criteria. As the appellation suggests, participants see it as a movement, not a corporate or state entity, a movement founded on practices of copyleft and the modulation of Free Software licensing ideas. The use of scientific data and the tools for making sense of open access are very often at the heart of controversy in science (a point often reiterated by science and technology studies), and so there is often an argument about not only the availability of data but its reuse, modification, and modulation as well. Projects like the BioBricks Foundation (biobricks.org) and new organizations like the Public Library of Science (plos.org) are committed to both availability and certain forms of collective modification. The commitment to becoming a recursive public, however, raises unprecedented issues about the nature of quality, reliability, and finality of scientific data and results—questions that will reverberate throughout the sciences as a result.
@@ -11918,7 +11121,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0E5E9D6710E985A783F0BCF0FA5845BD7B0E985FF6A92BD99BE83D47C10A0383
.has: notes_reg
@@ -11930,7 +11132,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AD4891E041E28EC6306E5B754809D2248D548FA88B36B0F305F1BA558CDD1F45
| Such examples should indicate the degree to which Two Bits is focused on a much longer time span than simply the last couple of years and on much broader issues of political legitimacy and cultural change. Rather than offer immediate policy prescriptions or seek to change the way people think about an issue, I have approached ⑆,┨[pg 305]┣, Two Bits as a work of history and anthropology, making it less immediately applicable in the hopes that it is more lastingly usable. The stories I have told reach back at least forty years, if not longer. While it is clear that the Internet as most people know it is only ten to fifteen years old, it has been “in preparation” since at least the late 1950s. Students in my classes—especially hip geeks deep in Free Software apprenticeship—are bewildered to learn that the arguments and usable pasts they are rehearsing are refinements and riffs on stories that are as old or older than their parents. This deeper stability is where the cultural significance of Free Software lies: what difference does Free Software today introduce with respect to knowledge and power yesterday?
@@ -11941,7 +11142,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E018EDFF90AE0141B3D878D67B106861273BA6E5F6D8A8F81B53A53749B590E6
| Free Software is a response to a problem, in much the same way that the Royal Society in the sixteenth century, the emergence of a publishing industry in the eighteenth century, and the institutions of the public sphere in the eighteenth and nineteenth centuries were responses. They responded to the collective challenge of creating regimes of governance that required—and encouraged—reliable empirical knowledge as a basis for their political legitimacy. Such political legitimacy is not an eternal or theoretical problem; it is a problem of constant real-world practice in creating the infrastructures by which individuals come to inhabit and understand their own governance, whether by states, corporations, or machines. If power seeks consent of the governed—and especially the consent of the democratic, self-governing kind that has become the global dominant ideal since the seventeenth century—it must also seek to ensure the stability and reliability of the knowledge on which that consent is propped.
@@ -11952,7 +11152,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1E8F4FFF40AF9EAA23DCBCBD7A163DCF55C8083A8D6B20B0E93BC9DF8563652C
| Debates about the nature and history of publics and public spheres have served as one of the main arenas for this kind of questioning, but, as I hope I have shown here, it is a question not only of public spheres but of practices, technologies, laws, and movements, of going concerns which undergo modulation and experimentation in accord with a social imagination of order both moral and technical. “Recursive public” as a concept is not meant to replace that of public sphere. I intend neither for actors nor really for many scholars to find it generally applicable. I would not want to see it suddenly discovered everywhere, but principally in tracking the transformation, proliferation, and differentiation of Free Software and its derivatives. ⑆,┨[pg 306]┣,
@@ -11963,7 +11162,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0EABC618E86E88C0722E74BA4F6736D353AF43F9B3912BE5F74AB18C961CA507
| Several threads from the three parts of Two Bits can now be tied together. The detailed descriptions of Free Software and its modulations should make clear that (1) the reason the Internet looks the way it does is due to the work of figuring out Free Software, both before and after it was recognized as such; (2) neither the Internet nor the computer is the cause of a reorientation of knowledge and power, but both are tools that render possible modulations of settled practices, modulations that reveal a much older problem regarding the legitimacy of the means of circulation and production of knowledge; (3) Free Software is not an ethical stance, but a practical response to the revelation of these older problems; and (4) the best way to understand this response is to see it as a kind of public sphere, a recursive public that is specific to the technical and moral imaginations of order in the contemporary world of geeks.
@@ -11974,7 +11172,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3FFA6358DA21281FEBAA3AB91EE178F9F266D18020287F998396D8928CEFE00C
| It is possible now to return to the practical and political meaning of the “singularity” of the Internet, that is, to the fact that there is only one Internet. This does not mean that there are no other networks, but only that the Internet is a singular entity and not an instance of a general type. How is it that the Internet is open in the same way to everyone, whether an individual or a corporate or a national entity? How has it become extensible (and, by extension, defensible) by and to everyone, regardless of their identity, locale, context, or degree of power?
@@ -11985,7 +11182,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9BF40DB3C2054B1ED9159BB67B0F15D97ABAB43ABC8392B9F0C29935D8E3FF28
| The singularity of the Internet is both an ontological and an epistemological fact; it is a feature of the Internet’s technical configurations and modes of ordering the actions of humans and machines by protocols and software. But it is also a feature of the technical and moral imaginations of the people who build, manage, inhabit, and expand the Internet. Ontologically, the creation and dissemination of standardized protocols, and novel standard-setting processes are at the heart of the story. In the case of the Internet, differences in standards-setting processes are revealed clearly in the form of the famous Request for Comments system of creating, distributing, and modifying Internet protocols. The RFC system, just as much as the Geneva-based International Organization for Standards, reveal the fault lines of international legitimacy in complex societies dependent on networks, software, and other high-tech forms of knowledge production, organization, and governance. The legitimacy of standards has massive significance for the abilities of individual actors to participate in their own recursive publics, whether they ⑆,┨[pg 307]┣, be publics that address software and networks or those that address education and development. But like the relationship between “law on the books” and “law in action,” standards depend on the coordinated action and order of human practices.
@@ -11996,7 +11192,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0A7C7EAF0134824C68D2A18A9EAD595858ACA28E23AFF60F3F894B730C38F7A6
| What’s more, the seemingly obvious line between a legitimate standard and a marketable product based on these standards causes nothing but trouble. The case of open systems in the 1980s high-end computer industry demonstrates how the logic of standardization is not at all clearly distinguished from the logic of the market. The open-systems battles resulted in novel forms of cooperation-within-competition that sought both standardization and competitive advantage at the same time. Open systems was an attempt to achieve a kind of “singularity,” not only for a network but for a market infrastructure as well. Open systems sought ways to reform technologies and markets in tandem. What it ignored was the legal structure of intellectual property. The failure of open systems reveals the centrality of the moral and technical order of intellectual property—to both technology and markets—and shows how a reliance on this imagination of order literally renders impossible the standardization of singular market infrastructure. By contrast, the success of the Internet as a market infrastructure and as a singular entity comes in part because of the recognition of the limitations of the intellectual-property system—and Free Software in the 1990s was the main experimental arena for trying out alternatives.
@@ -12007,7 +11202,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8612A9C9E38D252C4999E495AF7D829DB741A63E1EED1CB845064F4B4938F558
| The singularity of the Internet rests in turn on a counterintuitive multiplicity: the multiplicity of the UNIX operating system and its thousands of versions and imitations and reimplementations. UNIX is a great example of how novel, unexpected kinds of order can emerge from high-tech practices. UNIX is neither an academic (gift) nor a market phenomenon; it is a hybrid model of sharing that emerged from a very unusual technical and legal context. UNIX demonstrates how structured practices of sharing produce their own kind of order. Contrary to the current scholarly consensus that Free Software and its derivatives are a kind of “shadow economy” (a “sharing” economy, a “peer production” economy, a “noncommercial” economy), UNIX was never entirely outside of the mainstream market. The meanings of sharing, distribution, and profitability are related to the specific technical, legal, and organizational context. Because AT&T was prevented from commercializing UNIX, because UNIX users were keen to expand and ⑆,┨[pg 308]┣, adapt it for their own uses, and because its developers were keen to encourage and assist in such adaptations, UNIX proliferated and differentiated in ways that few commercial products could have. But it was never “free” in any sense. Rather, in combination with open systems, it set the stage for what “free” could come to mean in the 1980s and 1990s. It was a nascent recursive public, confronting the technical and legal challenges that would come to define the practices of Free Software. To suggest that it represents some kind of “outside” to a functioning economic market based in money is to misperceive how transformative of markets UNIX and the Internet (and Free Software) have been. They have initiated an imagination of moral and technical order that is not at all opposed to ideologies of market-based governance. Indeed, if anything, what UNIX and Free Software represent is an imagination of how to change an entire market-based governance structure—not just specific markets in things—to include a form of public sphere, a check on the power of existing authority.
@@ -12018,7 +11212,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F34CEC82E6DD03DB4447CC98261E01482A49AEF1851EAB45227FD2D30DE8AEE1
| UNIX and Open Systems should thus be seen as early stages of a collective technical experiment in transforming our imaginations of order, especially of the moral order of publics, markets, and self-governing peoples. The continuities and the gradualness of the change are more apparent in these events than any sudden rupture or discontinuity that the “invention of the Internet” or the passing of new intellectual-property laws might suggest. The “reorientation of knowledge and power” is more dance than earthquake; it is stratified in time, complex in its movements, and takes an experimental form whose concrete traces are the networks, infrastructures, machines, laws, and standards left in the wake of the experiments.
@@ -12029,7 +11222,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D0E011B227364460DC63A3818476A8238569598AD0673C49155C5DBD21CBC32B
| Availability, reusability, and modifiability are at the heart of this reorientation. The experiments of UNIX and open systems would have come to nothing if they had not also prompted a concurrent experimentation with intellectual-property law, of which the copyleft license is the central and key variable. Richard Stallman’s creation of GNU EMACS and the controversy over propriety that it engendered was in many ways an attempt to deal with exactly the same problem that UNIX vendors and open-systems advocates faced: how to build extensibility into the software market—except that Stallman never saw it as a market. For him, software was and is part of the human itself, constitutive of our very freedom and, hence, inalienable. Extending software, through collective mutual ⑆,┨[pg 309]┣, aid, is thus tantamount to vitality, progress, and self-actualization. But even for those who insist on seeing software as mere product, the problem of extensibility remains. Standardization, standards processes, and market entry all appear as political problems as soon as extensibility is denied—and thus the legal solution represented by copyleft appears as an option, even though it raises new and troubling questions about the nature of competition and profitability.
@@ -12040,7 +11232,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 841241B55D3821FB41E6DFE912011ED30180CEFE076C67128DF3C7C6D4B16C15
| New questions about competition and profitability have emerged from the massive proliferation of hybrid commercial and academic forms, forms that bring with them different traditions of sharing, credit, reputation, control, creation, and dissemination of knowledge and products that require it. The new economic demands on the university—all too easily labeled neoliberalization or corporatization—mirror changing demands on industry that it come to look more like universities, that is, that it give away more, circulate more, and cooperate more. The development of UNIX, in its details, is a symptom of these changes, and the success of Free Software is an unambiguous witness to them.
@@ -12051,7 +11242,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7CDF5CD052E6F38CAE50C5FB980D3B2536AD721A2809B59B29AD60B3178DED0D
| The proliferation of hybrid commercial-academic forms in an era of modifiability and reusability, among the debris of standards, standards processes, and new experiments in intellectual property, results in a playing field with a thousand different games, all of which revolve around renewed experimentation with coordination, collaboration, adaptability, design, evolution, gaming, playing, worlds, and worlding. These games are indicative of the triumph of the American love of entrepreneurialism and experimentalism; they relinquish the ideals of planning and hierarchy almost absolutely in favor of a kind of embedded, technically and legally complex anarchism. It is here that the idea of a public reemerges: the ambivalence between relinquishing control absolutely and absolute distrust of government by the few. A powerful public is a response, and a solution, so long as it remains fundamentally independent of control by the few. Hence, a commitment, widespread and growing, to a recursive public, an attempt to maintain and extend the kinds of independent, authentic, autotelic public spheres that people encounter when they come to an understanding of how Free Software and the Internet have evolved.
@@ -12062,7 +11252,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A9A81BE63BB3E3F5605D7C378F8C0B6244F1549B77A695F7C079DB05035366BA
| The open-access movement, and examples like Connexions, are attempts at maintaining such publics. Some are conceived as bulwarks ⑆,┨[pg 310]┣, against encroaching corporatization, while others see themselves as novel and innovative, but most share some of the practices hashed out in the evolution of Free Software and the Internet. In terms of scholarly publishing and open access, the movement has reignited discussions of ethics, norms, and method. The Mertonian ideals are in place once more, this time less as facts of scientific method than as goals. The problem of stabilizing collective knowledge has moved from being an inherent feature of science to being a problem that needs our attention. The reorientation of knowledge and power and the proliferation of hybrid commercial-academic entities in an era of massive dependence on scientific knowledge and information leads to a question about the stabilization of that knowledge.
@@ -12073,7 +11262,6 @@
.ancestors: 1 717 0 0 869 870 0 0
.ancestors_collapsed: 1 717 869 870 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BFC102F853B044268B2ADA1D654CB745DB5E152BEF0FF591BEB058D8DECC4F0B
| Understanding how Free Software works and how it has developed along with the Internet and certain practices of legal and cultural critique may be essential to understanding the reliable foundation of knowledge production and circulation on which we still seek to ground legitimate forms of governance. Without Free Software, the only response to the continuing forms of excess we associate with illegitimate, unaccountable, unjust forms of governance might just be mute cynicism. With it, we are in possession of a range of practical tools, structured responses and clever ways of working through our complexity toward the promises of a shared imagination of legitimate and just governance. There is no doubt room for critique—and many scholars will demand it—but scholarly critique will have to learn how to sit, easily or uneasily, with Free Software as critique. Free Software can also exclude, just as any public or public sphere can, but this is not, I think, cause for resistance, but cause for joining. The alternative would be to create no new rules, no new practices, no new procedures—that is, to have what we already have. Free Software does not belong to geeks, and it is not the only form of becoming public, but it is one that will have a profound structuring effect on any forms that follow.
@@ -12385,7 +11573,6 @@
.ancestors: 1 892 0 0 893 0 0 0
.ancestors_collapsed: 1 892 893 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 10EAE3AA93A80CF618606F8E4C92CC566C0D3B710D831B43F33DE46AADDF3BC9
| Parts of this book have been published elsewhere. A much earlier version of chapter 1 was published as “Geeks, Social Imaginaries and Recursive Publics,” Cultural Anthropology 20.2 (summer 2005); chapter 6 as “The EMACS Controversy,” in Mario Biagioli, Martha Woodmansee, and Peter Jaszi, eds., Contexts of Invention (forthcoming); and parts of chapter 9 as “Punt to Culture,” Anthropological Quarterly 77.3.
@@ -16497,6 +15684,7 @@
[900] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16509,6 +15697,7 @@
[901] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16521,6 +15710,7 @@
[902] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16533,6 +15723,7 @@
[903] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16545,6 +15736,7 @@
[904] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16557,6 +15749,7 @@
[905] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16569,6 +15762,7 @@
[906] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16581,6 +15775,7 @@
[907] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16593,6 +15788,7 @@
[908] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16605,6 +15801,7 @@
[909] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16617,6 +15814,7 @@
[910] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16629,6 +15827,7 @@
[911] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16641,6 +15840,7 @@
[912] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16653,6 +15853,7 @@
[913] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16665,6 +15866,7 @@
[914] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16677,6 +15879,7 @@
[915] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16689,6 +15892,7 @@
[916] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16701,6 +15905,7 @@
[917] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16713,6 +15918,7 @@
[918] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16725,6 +15931,7 @@
[919] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16737,6 +15944,7 @@
[920] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16749,6 +15957,7 @@
[921] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16761,6 +15970,7 @@
[922] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16773,6 +15983,7 @@
[923] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16785,6 +15996,7 @@
[924] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16797,6 +16009,7 @@
[925] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16809,6 +16022,7 @@
[926] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16821,6 +16035,7 @@
[927] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16833,6 +16048,7 @@
[928] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16845,6 +16061,7 @@
[929] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16857,6 +16074,7 @@
[930] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16869,6 +16087,7 @@
[931] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16881,6 +16100,7 @@
[932] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16893,6 +16113,7 @@
[933] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16905,6 +16126,7 @@
[934] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16917,6 +16139,7 @@
[935] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16929,6 +16152,7 @@
[936] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16941,6 +16165,7 @@
[937] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16953,6 +16178,7 @@
[938] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16965,6 +16191,7 @@
[939] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16977,6 +16204,7 @@
[940] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -16989,6 +16217,7 @@
[941] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17001,6 +16230,7 @@
[942] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17013,6 +16243,7 @@
[943] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17025,6 +16256,7 @@
[944] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17037,6 +16269,7 @@
[945] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17049,6 +16282,7 @@
[946] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17061,6 +16295,7 @@
[947] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17073,6 +16308,7 @@
[948] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17085,6 +16321,7 @@
[949] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17097,6 +16334,7 @@
[950] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17109,6 +16347,7 @@
[951] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17121,6 +16360,7 @@
[952] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17133,6 +16373,7 @@
[953] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17145,6 +16386,7 @@
[954] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17157,6 +16399,7 @@
[955] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17169,6 +16412,7 @@
[956] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17181,6 +16425,7 @@
[957] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17193,6 +16438,7 @@
[958] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17205,6 +16451,7 @@
[959] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17217,6 +16464,7 @@
[960] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17229,6 +16477,7 @@
[961] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17241,6 +16490,7 @@
[962] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17253,6 +16503,7 @@
[963] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17265,6 +16516,7 @@
[964] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17277,6 +16529,7 @@
[965] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17289,6 +16542,7 @@
[966] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17301,6 +16555,7 @@
[967] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17313,6 +16568,7 @@
[968] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17325,6 +16581,7 @@
[969] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17337,6 +16594,7 @@
[970] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17349,6 +16607,7 @@
[971] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17361,6 +16620,7 @@
[972] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17373,6 +16633,7 @@
[973] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17385,6 +16646,7 @@
[974] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17397,6 +16659,7 @@
[975] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17409,6 +16672,7 @@
[976] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17421,6 +16685,7 @@
[977] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17433,6 +16698,7 @@
[978] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17445,6 +16711,7 @@
[979] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17457,6 +16724,7 @@
[980] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17469,6 +16737,7 @@
[981] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17481,6 +16750,7 @@
[982] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17493,6 +16763,7 @@
[983] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17505,6 +16776,7 @@
[984] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17517,6 +16789,7 @@
[985] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17529,6 +16802,7 @@
[986] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17541,6 +16815,7 @@
[987] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17553,6 +16828,7 @@
[988] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17565,6 +16841,7 @@
[989] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17577,6 +16854,7 @@
[990] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17589,6 +16867,7 @@
[991] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17601,6 +16880,7 @@
[992] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17613,6 +16893,7 @@
[993] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17625,6 +16906,7 @@
[994] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17637,6 +16919,7 @@
[995] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17649,6 +16932,7 @@
[996] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17661,6 +16945,7 @@
[997] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17673,6 +16958,7 @@
[998] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17685,6 +16971,7 @@
[999] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17697,6 +16984,7 @@
[1000] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17709,6 +16997,7 @@
[1001] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17721,6 +17010,7 @@
[1002] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17733,6 +17023,7 @@
[1003] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17745,6 +17036,7 @@
[1004] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17757,6 +17049,7 @@
[1005] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17769,6 +17062,7 @@
[1006] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17781,6 +17075,7 @@
[1007] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17793,6 +17088,7 @@
[1008] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17805,6 +17101,7 @@
[1009] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17817,6 +17114,7 @@
[1010] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17829,6 +17127,7 @@
[1011] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17841,6 +17140,7 @@
[1012] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17853,6 +17153,7 @@
[1013] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17865,6 +17166,7 @@
[1014] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17877,6 +17179,7 @@
[1015] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17889,6 +17192,7 @@
[1016] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17901,6 +17205,7 @@
[1017] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17913,6 +17218,7 @@
[1018] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17925,6 +17231,7 @@
[1019] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17937,6 +17244,7 @@
[1020] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17949,6 +17257,7 @@
[1021] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17961,6 +17270,7 @@
[1022] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17973,6 +17283,7 @@
[1023] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17985,6 +17296,7 @@
[1024] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -17997,6 +17309,7 @@
[1025] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18009,6 +17322,7 @@
[1026] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18021,6 +17335,7 @@
[1027] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18033,6 +17348,7 @@
[1028] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18045,6 +17361,7 @@
[1029] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18057,6 +17374,7 @@
[1030] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18069,6 +17387,7 @@
[1031] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18081,6 +17400,7 @@
[1032] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18093,6 +17413,7 @@
[1033] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18105,6 +17426,7 @@
[1034] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18117,6 +17439,7 @@
[1035] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18129,6 +17452,7 @@
[1036] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18141,6 +17465,7 @@
[1037] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18153,6 +17478,7 @@
[1038] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18165,6 +17491,7 @@
[1039] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18177,6 +17504,7 @@
[1040] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18189,6 +17517,7 @@
[1041] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18201,6 +17530,7 @@
[1042] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18213,6 +17543,7 @@
[1043] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18225,6 +17556,7 @@
[1044] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18237,6 +17569,7 @@
[1045] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18249,6 +17582,7 @@
[1046] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18261,6 +17595,7 @@
[1047] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18273,6 +17608,7 @@
[1048] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18285,6 +17621,7 @@
[1049] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18297,6 +17634,7 @@
[1050] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18309,6 +17647,7 @@
[1051] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18321,6 +17660,7 @@
[1052] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18333,6 +17673,7 @@
[1053] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18345,6 +17686,7 @@
[1054] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18357,6 +17699,7 @@
[1055] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18369,6 +17712,7 @@
[1056] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18381,6 +17725,7 @@
[1057] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18393,6 +17738,7 @@
[1058] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18405,6 +17751,7 @@
[1059] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18417,6 +17764,7 @@
[1060] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18429,6 +17777,7 @@
[1061] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18441,6 +17790,7 @@
[1062] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18453,6 +17803,7 @@
[1063] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18465,6 +17816,7 @@
[1064] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18477,6 +17829,7 @@
[1065] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18489,6 +17842,7 @@
[1066] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18501,6 +17855,7 @@
[1067] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18513,6 +17868,7 @@
[1068] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18525,6 +17881,7 @@
[1069] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18537,6 +17894,7 @@
[1070] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18549,6 +17907,7 @@
[1071] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18561,6 +17920,7 @@
[1072] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18573,6 +17933,7 @@
[1073] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18585,6 +17946,7 @@
[1074] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18597,6 +17959,7 @@
[1075] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18609,6 +17972,7 @@
[1076] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18621,6 +17985,7 @@
[1077] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18633,6 +17998,7 @@
[1078] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18645,6 +18011,7 @@
[1079] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18657,6 +18024,7 @@
[1080] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18669,6 +18037,7 @@
[1081] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18681,6 +18050,7 @@
[1082] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18693,6 +18063,7 @@
[1083] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18705,6 +18076,7 @@
[1084] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18717,6 +18089,7 @@
[1085] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18729,6 +18102,7 @@
[1086] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18741,6 +18115,7 @@
[1087] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18753,6 +18128,7 @@
[1088] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18765,6 +18141,7 @@
[1089] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18777,6 +18154,7 @@
[1090] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18789,6 +18167,7 @@
[1091] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18801,6 +18180,7 @@
[1092] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18813,6 +18193,7 @@
[1093] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18825,6 +18206,7 @@
[1094] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18837,6 +18219,7 @@
[1095] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18849,6 +18232,7 @@
[1096] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18861,6 +18245,7 @@
[1097] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18873,6 +18258,7 @@
[1098] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18885,6 +18271,7 @@
[1099] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18897,6 +18284,7 @@
[1100] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18909,6 +18297,7 @@
[1101] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18921,6 +18310,7 @@
[1102] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18933,6 +18323,7 @@
[1103] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18945,6 +18336,7 @@
[1104] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18957,6 +18349,7 @@
[1105] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18969,6 +18362,7 @@
[1106] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18981,6 +18375,7 @@
[1107] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -18993,6 +18388,7 @@
[1108] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19005,6 +18401,7 @@
[1109] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19017,6 +18414,7 @@
[1110] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19029,6 +18427,7 @@
[1111] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19041,6 +18440,7 @@
[1112] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19053,6 +18453,7 @@
[1113] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19065,6 +18466,7 @@
[1114] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19077,6 +18479,7 @@
[1115] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19089,6 +18492,7 @@
[1116] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19101,6 +18505,7 @@
[1117] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19113,6 +18518,7 @@
[1118] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19125,6 +18531,7 @@
[1119] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19137,6 +18544,7 @@
[1120] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19149,6 +18557,7 @@
[1121] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19161,6 +18570,7 @@
[1122] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19173,6 +18583,7 @@
[1123] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19185,6 +18596,7 @@
[1124] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19197,6 +18609,7 @@
[1125] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19209,6 +18622,7 @@
[1126] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19221,6 +18635,7 @@
[1127] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19233,6 +18648,7 @@
[1128] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19245,6 +18661,7 @@
[1129] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19257,6 +18674,7 @@
[1130] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19269,6 +18687,7 @@
[1131] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19281,6 +18700,7 @@
[1132] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19293,6 +18713,7 @@
[1133] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19305,6 +18726,7 @@
[1134] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19317,6 +18739,7 @@
[1135] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19329,6 +18752,7 @@
[1136] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19341,6 +18765,7 @@
[1137] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19353,6 +18778,7 @@
[1138] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19365,6 +18791,7 @@
[1139] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19377,6 +18804,7 @@
[1140] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19389,6 +18817,7 @@
[1141] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19401,6 +18830,7 @@
[1142] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19413,6 +18843,7 @@
[1143] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19425,6 +18856,7 @@
[1144] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19437,6 +18869,7 @@
[1145] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19449,6 +18882,7 @@
[1146] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19461,6 +18895,7 @@
[1147] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19473,6 +18908,7 @@
[1148] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19485,6 +18921,7 @@
[1149] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19497,6 +18934,7 @@
[1150] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19509,6 +18947,7 @@
[1151] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19521,6 +18960,7 @@
[1152] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19533,6 +18973,7 @@
[1153] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19545,6 +18986,7 @@
[1154] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19557,6 +18999,7 @@
[1155] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19569,6 +19012,7 @@
[1156] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19581,6 +19025,7 @@
[1157] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19593,6 +19038,7 @@
[1158] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19605,6 +19051,7 @@
[1159] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19617,6 +19064,7 @@
[1160] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19629,6 +19077,7 @@
[1161] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19641,6 +19090,7 @@
[1162] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19653,6 +19103,7 @@
[1163] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19665,6 +19116,7 @@
[1164] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19677,6 +19129,7 @@
[1165] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19689,6 +19142,7 @@
[1166] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19701,6 +19155,7 @@
[1167] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19713,6 +19168,7 @@
[1168] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19725,6 +19181,7 @@
[1169] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19737,6 +19194,7 @@
[1170] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19749,6 +19207,7 @@
[1171] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19761,6 +19220,7 @@
[1172] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19773,6 +19233,7 @@
[1173] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19785,6 +19246,7 @@
[1174] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19797,6 +19259,7 @@
[1175] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19809,6 +19272,7 @@
[1176] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19821,6 +19285,7 @@
[1177] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19833,6 +19298,7 @@
[1178] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19845,6 +19311,7 @@
[1179] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19857,6 +19324,7 @@
[1180] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19869,6 +19337,7 @@
[1181] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19881,6 +19350,7 @@
[1182] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19893,6 +19363,7 @@
[1183] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19905,6 +19376,7 @@
[1184] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19917,6 +19389,7 @@
[1185] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19929,6 +19402,7 @@
[1186] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19941,6 +19415,7 @@
[1187] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19953,6 +19428,7 @@
[1188] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19965,6 +19441,7 @@
[1189] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19977,6 +19454,7 @@
[1190] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -19989,6 +19467,7 @@
[1191] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -20001,6 +19480,7 @@
[1192] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -20013,6 +19493,7 @@
[1193] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -20025,6 +19506,7 @@
[1194] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -20037,6 +19519,7 @@
[1195] bibliography
.part: backmatter
+.parent: 0
.ancestors: 1 899 0 0 0 0 0 0
.ancestors_collapsed: 1 0 0 0 0 0 0 0
.parent_lev: 4
@@ -20092,6 +19575,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20105,6 +19589,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20118,6 +19603,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20137,6 +19623,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20152,6 +19639,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20165,6 +19653,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20178,6 +19667,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20191,6 +19681,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20204,6 +19695,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20217,6 +19709,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20230,6 +19723,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20243,6 +19737,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20258,6 +19753,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20271,6 +19767,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20284,6 +19781,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20297,6 +19795,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20310,6 +19809,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20323,6 +19823,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20336,6 +19837,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20359,6 +19861,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20378,6 +19881,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20391,6 +19895,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20408,6 +19913,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20425,6 +19931,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20438,6 +19945,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20451,6 +19959,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20464,6 +19973,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20479,6 +19989,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20492,6 +20003,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20507,6 +20019,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20520,6 +20033,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20533,6 +20047,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20546,6 +20061,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20559,6 +20075,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20572,6 +20089,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20585,6 +20103,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20598,6 +20117,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20611,6 +20131,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20624,6 +20145,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20637,6 +20159,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20650,6 +20173,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20663,6 +20187,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20676,6 +20201,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20689,6 +20215,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20702,6 +20229,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20715,6 +20243,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20728,6 +20257,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20741,6 +20271,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20754,6 +20285,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20767,6 +20299,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20780,6 +20313,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20793,6 +20327,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20806,6 +20341,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20819,6 +20355,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20838,6 +20375,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20851,6 +20389,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20864,6 +20403,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20879,6 +20419,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20894,6 +20435,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20907,6 +20449,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20924,6 +20467,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20967,6 +20511,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20980,6 +20525,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -20993,6 +20539,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21006,6 +20553,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21025,6 +20573,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21042,6 +20591,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21069,6 +20619,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21096,6 +20647,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21119,6 +20671,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21136,6 +20689,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21157,6 +20711,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21170,6 +20725,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21193,6 +20749,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21208,6 +20765,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21221,6 +20779,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21234,6 +20793,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21255,6 +20815,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21268,6 +20829,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21283,6 +20845,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21296,6 +20859,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21309,6 +20873,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21322,6 +20887,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21337,6 +20903,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21350,6 +20917,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21365,6 +20933,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21382,6 +20951,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21397,6 +20967,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21410,6 +20981,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21423,6 +20995,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21436,6 +21009,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21449,6 +21023,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21462,6 +21037,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21475,6 +21051,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21488,6 +21065,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21501,6 +21079,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21514,6 +21093,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21529,6 +21109,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21542,6 +21123,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21555,6 +21137,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21578,6 +21161,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21591,6 +21175,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21604,6 +21189,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21617,6 +21203,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21630,6 +21217,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21647,6 +21235,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21660,6 +21249,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21673,6 +21263,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21686,6 +21277,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21699,6 +21291,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21716,6 +21309,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21729,6 +21323,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21742,6 +21337,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21755,6 +21351,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21768,6 +21365,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21781,6 +21379,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21794,6 +21393,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21813,6 +21413,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21828,6 +21429,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21841,6 +21443,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21856,6 +21459,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21875,6 +21479,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21888,6 +21493,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21901,6 +21507,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21914,6 +21521,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21929,6 +21537,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21958,6 +21567,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21975,6 +21585,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -21988,6 +21599,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22001,6 +21613,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22014,6 +21627,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22027,6 +21641,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22040,6 +21655,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22053,6 +21669,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22072,6 +21689,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22085,6 +21703,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22098,6 +21717,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22111,6 +21731,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22124,6 +21745,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22141,6 +21763,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22154,6 +21777,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22167,6 +21791,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22180,6 +21805,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22193,6 +21819,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22206,6 +21833,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22219,6 +21847,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22234,6 +21863,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22247,6 +21877,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22260,6 +21891,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22273,6 +21905,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22286,6 +21919,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22299,6 +21933,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22312,6 +21947,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22325,6 +21961,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22338,6 +21975,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22351,6 +21989,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22364,6 +22003,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22381,6 +22021,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22394,6 +22035,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22407,6 +22049,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22420,6 +22063,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22433,6 +22077,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22450,6 +22095,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22463,6 +22109,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22476,6 +22123,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22489,6 +22137,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22502,6 +22151,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22515,6 +22165,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22528,6 +22179,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22541,6 +22193,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22554,6 +22207,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22567,6 +22221,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22580,6 +22235,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22593,6 +22249,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22606,6 +22263,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22619,6 +22277,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22634,6 +22293,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22647,6 +22307,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22662,6 +22323,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22675,6 +22337,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22688,6 +22351,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22701,6 +22365,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22716,6 +22381,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22729,6 +22395,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22742,6 +22409,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22755,6 +22423,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22768,6 +22437,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22797,6 +22467,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22810,6 +22481,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22823,6 +22495,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22836,6 +22509,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22849,6 +22523,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22862,6 +22537,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22875,6 +22551,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22888,6 +22565,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22901,6 +22579,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22914,6 +22593,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22927,6 +22607,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22940,6 +22621,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22953,6 +22635,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22966,6 +22649,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22979,6 +22663,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -22992,6 +22677,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23005,6 +22691,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23020,6 +22707,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23033,6 +22721,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23046,6 +22735,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23063,6 +22753,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23076,6 +22767,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23089,6 +22781,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23102,6 +22795,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23115,6 +22809,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23138,6 +22833,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23151,6 +22847,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23166,6 +22863,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23179,6 +22877,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23192,6 +22891,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23205,6 +22905,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23218,6 +22919,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23231,6 +22933,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23246,6 +22949,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23259,6 +22963,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23272,6 +22977,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23285,6 +22991,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23298,6 +23005,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23311,6 +23019,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23324,6 +23033,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23337,6 +23047,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23350,6 +23061,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23363,6 +23075,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23378,6 +23091,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23391,6 +23105,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23404,6 +23119,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23417,6 +23133,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23438,6 +23155,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23451,6 +23169,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23464,6 +23183,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23477,6 +23197,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23492,6 +23213,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23505,6 +23227,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23520,6 +23243,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23541,6 +23265,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23558,6 +23283,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23571,6 +23297,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23584,6 +23311,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23597,6 +23325,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23610,6 +23339,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23623,6 +23353,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23636,6 +23367,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23649,6 +23381,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23662,6 +23395,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23679,6 +23413,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23692,6 +23427,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23705,6 +23441,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23718,6 +23455,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23731,6 +23469,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23748,6 +23487,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23761,6 +23501,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23774,6 +23515,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23787,6 +23529,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23800,6 +23543,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23813,6 +23557,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23826,6 +23571,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23839,6 +23585,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23852,6 +23599,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23865,6 +23613,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23884,6 +23633,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23897,6 +23647,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23924,6 +23675,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23937,6 +23689,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23950,6 +23703,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23963,6 +23717,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23980,6 +23735,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -23993,6 +23749,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24008,6 +23765,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24021,6 +23779,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24034,6 +23793,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24047,6 +23807,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24066,6 +23827,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24079,6 +23841,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24092,6 +23855,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24111,6 +23875,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24128,6 +23893,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24141,6 +23907,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24158,6 +23925,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24187,6 +23955,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24200,6 +23969,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24213,6 +23983,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24226,6 +23997,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24239,6 +24011,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24254,6 +24027,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24267,6 +24041,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24284,6 +24059,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24297,6 +24073,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24316,6 +24093,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24329,6 +24107,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24342,6 +24121,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24355,6 +24135,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24368,6 +24149,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24381,6 +24163,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24394,6 +24177,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24409,6 +24193,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24422,6 +24207,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24435,6 +24221,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24450,6 +24237,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24473,6 +24261,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24488,6 +24277,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24501,6 +24291,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24514,6 +24305,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24527,6 +24319,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24540,6 +24333,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24553,6 +24347,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24566,6 +24361,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24579,6 +24375,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24592,6 +24389,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24611,6 +24409,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24624,6 +24423,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24639,6 +24439,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24658,6 +24459,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24677,6 +24479,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24692,6 +24495,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24713,6 +24517,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24730,6 +24535,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24747,6 +24553,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24760,6 +24567,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24773,6 +24581,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24786,6 +24595,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24799,6 +24609,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24812,6 +24623,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24827,6 +24639,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24840,6 +24653,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24853,6 +24667,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24874,6 +24689,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24887,6 +24703,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24900,6 +24717,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24913,6 +24731,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24926,6 +24745,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24939,6 +24759,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24952,6 +24773,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24969,6 +24791,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24982,6 +24805,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -24995,6 +24819,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25008,6 +24833,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25021,6 +24847,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25034,6 +24861,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25047,6 +24875,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25060,6 +24889,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25075,6 +24905,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25088,6 +24919,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25101,6 +24933,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25114,6 +24947,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25127,6 +24961,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25140,6 +24975,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25153,6 +24989,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25166,6 +25003,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25179,6 +25017,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25192,6 +25031,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25205,6 +25045,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25218,6 +25059,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25231,6 +25073,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25244,6 +25087,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25257,6 +25101,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25272,6 +25117,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25285,6 +25131,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25308,6 +25155,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25323,6 +25171,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25336,6 +25185,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25349,6 +25199,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25364,6 +25215,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25377,6 +25229,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25396,6 +25249,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25413,6 +25267,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25426,6 +25281,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25447,6 +25303,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25460,6 +25317,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25473,6 +25331,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25486,6 +25345,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25499,6 +25359,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25518,6 +25379,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25541,6 +25403,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25554,6 +25417,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25567,6 +25431,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25580,6 +25445,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25607,6 +25473,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25622,6 +25489,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25635,6 +25503,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25648,6 +25517,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25661,6 +25531,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25674,6 +25545,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25687,6 +25559,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25702,6 +25575,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25715,6 +25589,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25728,6 +25603,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25745,6 +25621,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25760,6 +25637,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25779,6 +25657,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25792,6 +25671,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25805,6 +25685,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25818,6 +25699,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25831,6 +25713,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25844,6 +25727,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25857,6 +25741,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25874,6 +25759,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25887,6 +25773,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25900,6 +25787,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25919,6 +25807,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25932,6 +25821,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25949,6 +25839,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25964,6 +25855,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25977,6 +25869,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -25990,6 +25883,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26005,6 +25899,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26022,6 +25917,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26035,6 +25931,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26048,6 +25945,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26061,6 +25959,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26074,6 +25973,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26087,6 +25987,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26100,6 +26001,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26113,6 +26015,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26126,6 +26029,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26139,6 +26043,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26170,6 +26075,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26183,6 +26089,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26196,6 +26103,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26209,6 +26117,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26222,6 +26131,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26235,6 +26145,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26250,6 +26161,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26263,6 +26175,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26278,6 +26191,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26291,6 +26205,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26304,6 +26219,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26317,6 +26233,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26330,6 +26247,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26343,6 +26261,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26356,6 +26275,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26369,6 +26289,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26382,6 +26303,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26395,6 +26317,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26408,6 +26331,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26421,6 +26345,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26434,6 +26359,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26447,6 +26373,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26462,6 +26389,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26475,6 +26403,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26488,6 +26417,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26501,6 +26431,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26514,6 +26445,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26527,6 +26459,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26540,6 +26473,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4
@@ -26553,6 +26487,7 @@
[0] bookindex
.part: backmatter
+.parent: 0
.ancestors: 1 1196 0 0 0 0 0 0
.ancestors_collapsed: 1 1196 0 0 0 0 0 0
.parent_lev: 4