Tenen & Foxman
Book Piracy as Peer Preservation
2014
Book Piracy as Peer Preservation {#book-piracy-as-peer-preservation .entry-title}
**Abstract**
In describing the people, books, and technologies behind one of the
largest "shadow libraries" in the world, we find a tension between the
dynamics of sharing and preservation. The paper proceeds to
contextualize contemporary book piracy historically, challenging
accepted theories of peer production. Through a close analysis of one
digital library's system architecture, software and community, we assert
that the activities cultivated by its members are closer to that of
conservationists of the public libraries movement, with the goal of
preserving rather than mass distributing their collected material.
Unlike common peer production models emphasis is placed on the expertise
of its members as digital preservations, as well as the absorption of
digital repositories. Additionally, we highlight issues that arise from
their particular form of distributed architecture and community.
>
>
> *Literature is the secretion of civilization, poetry of the ideal.
> That is why literature is one of the wants of societies. That is why
> poetry is a hunger of the soul. That is why poets are the first
> instructors of the people. That is why Shakespeare must be translated
> in France. That is why Molière must be translated in England. That is
> why comments must be made on them. That is why there must be a vast
> public literary domain. That is why all poets, all philosophers, all
> thinkers, all the producers of the greatness of the mind must be
> translated, commented on, published, printed, reprinted, stereotyped,
> distributed, explained, recited, spread abroad, given to all, given
> cheaply, given at cost price, given for nothing.*
> ^[1](#fn-2025-1){#fnref-2025-1}^
**Introduction**
The big money (and the bandwidth) in online media is in film, music, and
software. Text is less profitable for copyright holders; it is cheaper
to duplicate and easier to share. Consequently, issues surrounding the
unsanctioned sharing of print material receive less press and scant
academic attention. The very words, "book piracy," fail to capture the
spirit of what is essentially an Enlightenment-era project, openly
embodied in many contemporary "shadow libraries":^[2](#fn-2025-2){#fnref-2025-2}^
in the words of Victor Hugo, to establish a "vast public
literary domain." Writers, librarians, and political activists from Hugo
to Leo Tolstoy and Andrew Carnegie have long argued for unrestricted
access to information as a form of a public good essential to civic
engagement. In that sense, people participating in online book exchanges
enact a role closer to that of a librarian than that of a bootlegger or
a plagiarist. Whatever the reader's stance on the ethics of copyright
and copyleft, book piracy should not be dismissed as mere search for
free entertainment. Under the conditions of "digital
disruption,"^[3](#fn-2025-3){#fnref-2025-3}^ when the traditional
institutions of knowledge dissemination---the library, the university,
the newspaper, and the publishing house---feel themselves challenged and
transformed by the internet, we can look to online book sharing
communities for lessons in participatory governance, technological
innovation, and economic sustainability.
The primary aims of this paper are ethnographic and descriptive: to
study and to learn from a library that constitutes one of the world's
largest digital archives, rivaling *Google Books*, *Hathi Trust*, and
*Europeana*. In approaching a "thick description" of this archive we
begin to broach questions of scope and impact. We would like to ask:
Who? Where? and Why? What kind of people distribute books online? What
motivates their activity? What technologies enable the sharing of print
media? And what lessons can we draw from them? Our secondary aim is to
continue the work of exploring the phenomenon of book sharing more
widely, placing it in the context of other commons-based peer production
communities like Project Gutenberg and Wikipedia. The archetypal model
of peer production is one motivated by altruistic participation. But the
very history of public libraries is one that combines the impulse to
share and to protect. To paraphrase Jacques Derrida
^[4](#fn-2025-4){#fnref-2025-4}^ writing in "Archive Fever," the archive
shelters memory just as it shelters itself from memory. We encompass
this dual dynamic under the term "peer preservation," where the
logistics of "peers" and of "preservation" can sometimes work at odds to
one another.
Academic literature tends to view piracy on the continuum between free
culture and intellectual property rights. On the one side, an argument
is made for unrestricted access to information as a prerequisite to
properly deliberative democracy.^[5](#fn-2025-5){#fnref-2025-5}^ On this
view, access to knowledge is a form of political power, which must be
equitably distributed, redressing regional and social imbalances of
access.^[6](#fn-2025-6){#fnref-2025-6}^ The other side offers pragmatic
reasoning related to the long-term sustainability of the cultural
sphere, which, in order to prosper, must provide proper economic
incentives to content creators.^[7](#fn-2025-7){#fnref-2025-7}^
It is our contention that grassroots file sharing practices cannot be
understood solely in terms of access or intellectual property. Our field
work shows that while some members of the book sharing community
participate for activist or ideological reasons, others do so as
collectors, preservationists, curators, or simply readers. Despite
romantic notions to the contrary, reading is a social and mediated
activity. The reader encounters texts in conversation, through a variety
of physical interfaces and within an ecosystem of overlapping
communities, each projecting their own material contexts, social norms,
and ideologies. A technician who works in a biology laboratory, for
example, might publish closed-access peer-review articles by day, as
part of his work collective, and release terabytes of published material
by night, in the role of a moderator for an online digital library. Our
approach then, is to capture some of the complexity of such an
ecosystem, particularly in the liminal areas where people, texts, and
technology converge.
**Ethics disclaimer**
Research for this paper was conducted under the aegis of piracyLab, an
academic collective exploring the impact of technology on the spread of
knowledge globally.^[8](#fn-2025-8){#fnref-2025-8}^ One of the lab's
first tasks was to discuss the ethical challenges of collaborative
research in this space. The conversation involved students, faculty,
librarians, and informal legal council. Neutrality, to the extent that
it is possible, emerged as one of our foundational principles. To keep
all channels of communication open, we wanted to avoid bias and to give
voice to a diversity of stakeholders: from authors, to publishers, to
distributors, whether sanctioned or not. Following a frank discussion
and after several iterations, we drafted an ethics charter that
continues to inform our work today. The charter contains the following
provisions:
-- We neither condone nor condemn any forms of information exchange.\
-- We strive to protect our sources and do not retain any identifying
personal information.\
-- We seek transparency in sharing our methods, data, and findings with
the widest possible audience.\
-- Credit where credit is due. We believe in documenting attribution
thoroughly.\
-- We limit our usage of licensed material to the analysis of metadata,
with results used for non-commercial, nonprofit, educational purposes.\
-- Lab participants commit to abiding by these principles as long as
they remain active members of the research group.
In accordance with these principles and following the practice of
scholars like Balazs Bodo ^[9](#fn-2025-9){#fnref-2025-9}^, Eric Priest
^[10](#fn-2025-10){#fnref-2025-10}^, and Ramon Lobato and Leah Tang
^[11](#fn-2025-11){#fnref-2025-11}^, we redact the names of file sharing
services and user names, where such names are not made explicitly public
elsewhere.
**Centralization**
We begin with the intuition that all infrastructure is social to an
extent. Even private library collections cannot be said to reflect the
work of a single individual. Collective forces shape furniture, books,
and the very cognitive scaffolding that enables reading and
interpretation. Yet, there are significant qualitative differences in
the systems underpinning private collections, public libraries, and
unsanctioned peer-to-peer information exchanges like *The Pirate Bay*,
for example. Given these differences, the recent history of online book
sharing can be divided roughly into two periods. The first is
characterized by local, ad-hoc peer-to-peer document exchanges and the
subsequent growth of centralized content aggregators. Following trends
in the development of the web as a whole, shadow libraries of the second
period are characterized by communal governance and distributed
infrastructure.
Shadow libraries of the first period resemble a private library in that
they often emanate from a single authoritative source--a site of
collection and distribution associated with an individual collector,
sometimes explicitly. The library of Maxim Moshkov, for example,
established in 1994 and still thriving at *lib.ru*, is one of the most
visible collections of this kind. Despite their success, such libraries
are limited in scale by the means and efforts of a few individuals. Due
to their centralized architecture they are also susceptible to legal
challenges from copyright owners and to state intervention.
Shadow libraries responded to these problems by distributing labor,
responsibility, and infrastructure, resulting in a system that is more
robust, more redundant, and more resistant to any single point of
failure or control.
The case of *Gigapedia* (later *library.nu*) and its related file
hosting service *ifile.it* demonstrates the successes and the
deficiencies of the centralized digital library model. Arguably among
the largest and most popular virtual libraries online in the period of
2009-2011, the sites were operated by Irish
nationals^[12](#fn-2025-12){#fnref-2025-12}^ on domains registered in
Italy and on the island state of Niue, with servers on the territory of
Germany and Ukraine. At its peak, *library.nu* (LNU) hosted more than
400,000 books and was purported to make an "estimated turnover of EUR 8
million (USD 10,602,400) from advertising revenues, donations and sales
of premium-level accounts," at least according to a press release made
by the International Publishers Association
(IPA).^[13](#fn-2025-13){#fnref-2025-13}^\
*Archived version of library.nu, circa 12/10/2010*
Its apparent popularity notwithstanding, *LNU/Gigapedia* was supported
by relatively simple architecture, likely maintained by a lone
developer-administrator. The site itself consisted of a catalog of
digital books and related metadata, including title, author, year of
publication, number of pages, description, category classification, and
a number of boolean parameters (whether the file is bookmarked,
paginated, vectorized, is searchable, and has a cover). Although the
books could be hosted anywhere, many in the catalog resided on the
servers of a "cyberlocker" service *ifile.it*, affiliated with the main
site. Not strictly a single-source archive, *LNU/Gigapedia* was
nevertheless a federated entity, tied to a single site and to a single
individual. On February 15, 2012, in a Munich court, the IPA, in
conjunction with a consortium of international publishing houses and the
help of the German law firm Lausen
Rechtsanwalte,^[14](#fn-2025-14){#fnref-2025-14}^ served judicial
cease-and-desist orders naming both sites (*Gigapedia* and *ifile.it*).
Seventeen injunctions were sought in Ireland, with the consequent
voluntary shut-down of both domains, which for a brief time redirected
visitors first to *Google Books* and then to *Blue Latitudes*, a *New
York Times* bestseller about pirates, for sale on *Amazon*.
Figure 1: Archived version of library.nu, circa 12/10/2010
:::
The relatively brief, by library standards, existence of *LNU/Gigapedia*
underscores a weakness in the federated library model. The site
flourished as long as it did not attract the ire of the publishing
industry. A lack of redundancy in the site's administrative structure
paralleled its lack on the server level. Once the authorities were able
to establish the identity of the site's operators (via *Paypal*
receipts, according to a partner at Lausen Rechtsanwalte), the project
was forced to shut down irrevocably.^[15](#fn-2025-15){#fnref-2025-15}^
The system's single point of origin proved also to be its single point
of failure.
Jens Bammel, Secretary General of the IPA, called the action "an
important step towards a more transparent, honest and fair trade of
digital content on the Internet."^[16](#fn-2025-16){#fnref-2025-16}^ The
rest of the internet mourned the passage of "the greatest, largest and
the best website for downloading
eBooks,"^[17](#fn-2025-17){#fnref-2025-17}^ comparing the demise of
*LNU/Gigapedia* to the burning of the ancient Library of
Alexandria.^[18](#fn-2025-18){#fnref-2025-18}^ Readers from around the
world flocked to sites like *Reddit* and *TorrentFreak* to express their
support and anger. For example, one reader wrote on *TorrentFreak*:
> I live in Macedonia (the Balkans), a country where the average salary
> is somewhere around 200eu, and I'm a student, attending a MA degree in
> communication sci. \[...\] where I come from the public library is not
> an option. \[...\] Our libraries are so poor, mostly containing 30year
> or older editions of books that almost never refer to the field of
> communication or any other contemporary science. My professors never
> hide that they use sites like library.nu \[...\] Original textbooks
> \[...\] are copy-printed handouts of some god knows how obtained
> original \[...\] For a country like Macedonia and the Balkans region
> generally THIS IS A APOCALYPTIC SCALE DISASTER! I really feel like the
> dark age is just around the corner these
> days.^[19](#fn-2025-19){#fnref-2025-19}^
A similar comment on *Reddit* reads:
> This is the saddest news of the year...heart-breaking...shocking...I
> was so attached to this site...I am from a third world country where
> buying original books is way too expensive if we see currency exchange
> rates...library.nu was a sea of knowledge for me and I learnt a lot
> from it \[...\] RIP library.nu...you have ignited several minds with
> free knowledge.^[20](#fn-2025-20){#fnref-2025-20}^
Another redditor wrote:
> This was an invaluable resource for international academics. The
> catalog of libraries overseas often cannot meet the needs of
> researchers in fields not specific to the country in which they are
> located. My doctoral research has taken a significant blow due to this
> recent shutdown \[...\] Please publishers, if you take away such a
> valuable resource, realize that you have created a gap that will be
> filled. This gap can either be filled by you or by
> us.^[21](#fn-2025-21){#fnref-2025-21}^
Another concludes:
> This just makes me want to start archiving everything I can get my
> hands on.^[22](#fn-2025-22){#fnref-2025-22}^
These anecdotal reports confirm our own experiences of studying and
teaching at universities with a diverse audience of international
students, who often recount a similar personal narrative. *Gigapedia*
and analogous sites fulfilled an unmet need in the international market,
redressing global inequities of access to
information.^[23](#fn-2025-23){#fnref-2025-23}^
But, being a cyberlocker-based service, *Gigapedia* did not succeed in
cultivating a meaningful sense of a community (even though it supported
a forum for brief periods of its existence). As Lobato and Tang
^[24](#fn-2025-24){#fnref-2025-24}^ write in their paper on
cyberlocker-based media distribution systems, cyberlockers in general
"do not foster collaboration and co-creation," taking an "instrumental
view of content hosted on their
sites."^[25](#fn-2025-25){#fnref-2025-25}^ Although not strictly a
cyberlocker, *LNU/Gigapedia* fit the profile of a passive,
non-transformative site by these criteria. For Lobato and Tang, the
rapid disappearance of many prominent cyberlocker sites underscores the
"structural instability" of "fragile file-hosting
ecology."^[26](#fn-2025-26){#fnref-2025-26}^ In our case, it would be
more precise to say that cyberlocker architecture highlights rather the
structural instability of centralized media archives, and not of file
sharing communities in general. Although bereaved readers were concerned
about the irrevocable loss of a valuable resource, digital libraries
that followed built a model of file sharing that is more resilient, more
transparent, and more participatory than their *LNU/Gigapedia*
predecessors.
**Distribution**
In parallel with the development of *LNU/Gigapedia*, a group of Russian
enthusiasts were working on a meta-library of sorts, under the name of
*Aleph*. Records of *Aleph's* activity go back at least as far as 2009.
Colloquially known as "prospectors," the volunteer members of *Aleph*
compiled library collections widely available on the gray market, with
an emphasis on academic and technical literature in Russian and
English.\
*DVD case cover of "Traum's library" advertising "more than 167,000
books" in fb2 format. Similar DVDs sell for around 1,000 RUB (\$25-30
US) on the streets of Moscow.*
At its inception, *Aleph* aggregated several "home-grown" archives,
already in wide circulation in universities and on the gray market.
These included:
-- *KoLXo3*, a collection of scientific texts that was at one time
distributed on 20 DVDs, overlapping with early Gigapedia efforts;\
-- *mexmat*, a library collected by the members of Moscow State
University's Department of Mechanics and Mathematics for internal use,
originally distributed through private FTP servers;\
-- *Homelab*, *Ihtik*, and *Ingsat* libraries;\
-- the Foreign Fiction archive collected from IRC \#\*\*\*
2003.09-2011.07.09 and the Internet Library;\
-- the *Great Science Textbooks* collection and, later, over 20 smaller
miscellaneous archives.^[27](#fn-2025-27){#fnref-2025-27}^
In retrospect, we can categorize the founding efforts along three
parallel tracks: 1) as the development of "front-end" server software
for searching and downloading books, 2) as the organization of an online
forum for enthusiasts willing to contribute to the project, and 3) the
collection effort required to expand and maintain the "back-end" archive
of documents, primarily in .pdf and .djvu
formats.^[28](#fn-2025-28){#fnref-2025-28}^ "What do we do?" writes one
of the early volunteers (in 2009) on the topic of "Outcomes, Goals, and
Scope of the Project." He answers: "we loot sites with ready-made
collections," "sort the indices in arbitrary normalized formats," "for
uncatalogued books we build a 'technical index': name of file, size,
hashcode," "write scripts for database sorting after the initial catalog
process," "search the database," "use the database for the construction
of an accessible catalog," "build torrents for the distribution of files
in the collection."^[29](#fn-2025-29){#fnref-2025-29}^ But, "everything
begins with the forum," in the words of another founding
member.^[30](#fn-2025-30){#fnref-2025-30}^ *Aleph*, the very name of the
group, reflects the aspiration to develop a "platform for the inception
of subsequent and more user-friendly" libraries--a platform "useful for
the developer, the reader, and the
librarian."^[31](#fn-2025-31){#fnref-2025-31}^\
Aleph's *anatomy*
Figure 2: DVD case cover of "Traum's library" advertising "more than
167,000 books
:::
What is *Aleph*? Is it a collection of books? A community? A piece of
software? What makes a library? When attempting to visualize Aleph's
constituents (Figure 3), it seems insufficient to point to books alone,
or to social structure, or to technology in the absence of people and
content. Taking a systems approach to description, we understand a
library to comprise an assemblage of books, people, and infrastructure,
along with their corresponding words and texts, rules and institutions,
and shelves and servers.^[32](#fn-2025-32){#fnref-2025-32}^ In this
light, *Aleph*'s iteration on *LNU/Gigapedia* lies not in technological
advancement alone, but in system architecture, on all levels of
analysis.
Where the latter relied on proprietary server applications, *Aleph*
built software that enabled others to mirror and to serve the site in
its entirety. The server was written by d\* from www.l\*.com (Bet),
utilizing a codebase common to several similar large book-sharing
communities. The initial organizational efforts happened on a sub-forum
of a popular torrent tracker (*RR*). Fifteen founding members reached
early consensus to start hashing document filenames (using the MD5
message-digest algorithm), rather than to store files as is, with their
appropriate .pdf or .mobi extensions.^[33](#fn-2025-33){#fnref-2025-33}^
Bit-wise hashing was likely chosen as a (computationally) cheap way to
de-duplicate documents, since two identical files would hash into an
identical string. Hashing the filenames was hoped to have the
side-effect of discouraging direct (file system-level) browsing of the
archive.^[34](#fn-2025-34){#fnref-2025-34}^ Instead, the books were
meant to be accessed through the front-end "librarian" interface, which
added a layer of meta-data and search tools. In other words, the group
went out of its way to distribute *Aleph* as a library and not merely as
a large aggregation of raw files.
Site volunteers coordinate their efforts asynchronously, by means of a
simple online forum (using *phpBB* software), open to all interested
participants. Important issues related to the governance of the
project--decisions about new hardware upgrades, software design, and
book acquisition--receive public airing. For example, at one point, the
site experienced increased traffic from *Google* searches. Some senior
members welcomed the attention, hoping to attract new volunteers. Others
worried increased visibility would bring unwanted scrutiny. To resolve
the issue, a member suggested delisting the website by altering the
robots.txt configuration file and thereby blocking *Google*
crawlers.^[35](#fn-2025-35){#fnref-2025-35}^ Consequently, the site
would become invisible to *Google*, while remaining freely accessible
via a direct link. Early conversations on *RR*, reflect a consistent
concern about the archive's longevity and its vulnerability to official
sanctions. Rather than following the cyber-locker model of distribution,
the prospectors decided to release canonical versions of the library in
chunks, via *BitTorrent*--a distributed protocol for file sharing.
Another decision was made to "store" the library on open trackers (like
*The Pirate Bay*), rather than tying it to a closed, by-invitation-only
community. Although *LN/Gigapedia* was already decentralized to an
extent, the archeology of the community discussion reveals a multitude
of concious choices that work to further atomize *Aleph* and to
decentralize it along the axes of the collection, governance, and
engineering.
By March of 2009 these efforts resulted in approximately 79k volumes or
around 180gb of data.^[36](#fn-2025-36){#fnref-2025-36}^ By December of
the same year, the moderators began talking about a terabyte, 2tb in
2010, and around 7tb by 2011.^[37](#fn-2025-37){#fnref-2025-37}^ By
2012, the core group of "prospectors" grew to 1,000 registered users.
*Aleph*'s main mirror received over a million page views per month and
about 40,000 unique visits per day.^[38](#fn-2025-38){#fnref-2025-38}^
An online eBook piracy report estimates a combined total of a million
unique visitors per day for *Aleph* and its
mirrors.^[39](#fn-2025-39){#fnref-2025-39}^
As of January 2014, the *Aleph* catalog contains over a million books
(1,021,000) and over 15 million academic articles, "weighing in" at just
under 10tb. Most remarkably, one of the world's largest digital
libraries operates on an annual budget of \$1,900
US.^[40](#fn-2025-40){#fnref-2025-40}^
\#\#\# Vulnerability\
Distributed architecture gives *Aleph* significant advantages over its
federated predecessors. Were *Aleph* servers to go offline the archive
would survive "in the cloud" of the *BitTorrent* network. Should the
forum (*Bet*) close, another online forum could easily take its place.
And were *Aleph* library portal itself go dark, other mirrors would (and
usually do) quickly take its place.
But the decentralized model of content distribution is not without its
challenges. To understand them, we need to review some of the
fundamentals behind the *BitTorrent* protocol. At its bare minimum (as
it was described in the original specification by Bram Cohen) the
protocol involves a "seeder," someone willing to share something it its
entirety; a "leecher," someone downloading shared data; and a torrent
"tracker" that coordinates activity between seeders and
leechers.^[41](#fn-2025-41){#fnref-2025-41}^
Imagine a music album sharing agreement between three friends, where,
initially, only one holds a copy of some album: for example, Nirvana's
*Nevermind*. Under the centralized model of file sharing, the friend
holding the album would transmit two copies, one to each friend. The
power of *BitTorrent* comes from shifting the burden of sharing from a
single seeder (friend one) to a "swarm" of leechers (friends two and
three). On this model, the first leecher joining the network (friend
two, in our case) would begin to get his data from the seeder directly,
as before. But the second leecher would receive some bits from the
seeder and some from the first leecher, in a non-linear, asynchronous
fashion. In our example, we can imagine the remaining friend getting
some songs from the first friend and some from the second. The friend
who held the album originally now transmitted something less than two
full copies of the album, since the other two friends exchanged some
bits of information between themselves, lessening the load on the
original album holder.
When downloading from the *BitTorrent* network, a peer may receive some
bits from the beginning of the document, some from the middle, and some
from the end, in parts distributed among the members of the swarm. A
local application called the "client" is responsible for checking the
integrity of the pieces and for reassembling the them into a coherent
whole. A torrent "tracker" coordinates the activity between peers,
keeping track of who has what where. Having received the whole document,
a leecher can, in turn, become a seeder by sharing all of his downloaded
bits with the remaining swarm (who only have partial copies). The
leecher can also take the file offline, choosing not to share at
all.^[42](#fn-2025-42){#fnref-2025-42}^
The original protocol left torrent trackers vulnerable to charges of
aiding and abetting copyright
infringement.^[43](#fn-2025-43){#fnref-2025-43}^ Early in 2008, Cohen
extended *BitTorrent* to make use of "distributed sloppy hash tables"
(DHT) for storing peer locations without resorting to a central tracker.
Under these new guidelines, each peer would maintain a small routing
table pointing to a handful of nearby peer locations. In effect, DHT
placed additional responsibility on the swarm to become a tracker of
sorts, however "sloppy" and imperfect. By November of of 2009, *Pirate
Bay* announced its transition away from tracking entirely, in favor of
DHT and the related PEX and Magnetic Links protocols. At the time they
called it, "world's most resilient
tracking."^[44](#fn-2025-44){#fnref-2025-44}^
Despite these advancements, the decentralized model of file sharing
remains susceptible to several chronic ailments. The first follows from
the fact that ad-hoc distribution networks privilege popular material. A
file needs to be actively traded to ensure its availability. If nobody
is actively sharing and downloading Nirvana's *Nevermind*, the album is
in danger of fading out of the cloud. As one member wrote succinctly on
*Gimel* forums, "unpopular files are in danger of become
inaccessible."^[45](#fn-2025-45){#fnref-2025-45}^ This dynamic is less
of a concern for Hollywood blockbusters, but more so for "long tail"
specialized materials of the sort found in *Aleph*, and indeed, for
*Aleph* itself as a piece of software distributed through the network.
*Aleph* combats the problem of fading torrents by renting
"seedboxes"--servers dedicated to keeping the *Aleph* seeds containing
the archive alive, preserving the availability of the collection. The
server in production as of 2014 can serve up to 12tb of data speeds of
100-800 megabits per second. Other file sharing communities address the
issue by enforcing a certain download to upload ratio on members of
their network.
The lack of true anonymity is the second problem intrinsic to the
*BitTorrent* protocol. Peers sharing bits directly cannot but avoid
exposing their IP address (unless these are masked behind virtual
private networks or TOR relays). A "Sybil" attack becomes possible when
a malicious peer shares bits in bad faith, with the intent to log IP
addresses.^[46](#fn-2025-46){#fnref-2025-46}^ Researchers exploring this
vector of attack were able to harvest more than 91,000 IP addresses in
less than 24 hours of sharing a popular television
show.^[47](#fn-2025-47){#fnref-2025-47}^ They report that more than 9%
of requests made to their servers indicated "modified clients", which
are likely also to be running experiments in the DHT. Legitimate
copyright holders and copyright "trolls" alike have used this
vulnerability to bring lawsuits against individual sharers in
court.^[48](#fn-2025-48){#fnref-2025-48}^
These two challenges are further exacerbated in the case of *Aleph*,
which uses *BitTorrent* to distribute large parts of its own
architecture. These parts are relatively large--around 40-50GB each.
Long-term sustainability of *Aleph* as a distributed system therefore
requires a rare participant: one interested in downloading the archive
as a whole (as opposed to downloading individual books), one who owns
the hardware to store and transmit terabytes of data, and one possessing
the technical expertise to do so safely.
**Peer preservation**
In light of the challenges and the effort involved in maintaining the
archive, one would be remiss to describe *Aleph* merely in terms of book
piracy, understood in conventional terms of financial gain, theft, or
profiteering. Day-to-day labor of the core group is much more
comprehensible as a mode of commons-based peer production, which is, in
the canonical definition, work made possible by a "networked
environment," "radically decentralized, collaborative, and
non-proprietary; based on sharing resources and outputs among widely
distributed, loosely connected individuals who cooperate with each other
without relying on either market signals or managerial
commands."^[49](#fn-2025-49){#fnref-2025-49}^ *Aleph* answers the
definition of peer production, resembling in many respects projects like
*Linux*, *Wikipedia*, and *Project Gutenberg*.
Yet, *Aleph* is also patently a library. Its work can and should be
viewed in the broader context of Enlightenment ideals: access to
literacy, universal education, and the democratization of knowledge. The
very same ideals gave birth to the public library movement as a whole at
the turn of the 20th century, in the United States, Europe, and
Russia.^[50](#fn-2025-50){#fnref-2025-50}^ Parallels between free
library movements of the early 20th and the early 21st centuries point
to a social dynamic that runs contrary to the populist spirit of
commons-based peer production projects, in a mechanism that we describe
as peer preservation. The idea encompasses conflicting drives both to
share and to hoard information.
The roots of many public libraries lie in extensive private collections.
Bodleian Library at Oxford, for example, traces its origins back to the
collections of Thomas Cobham, Bishop of Worcester, Humphrey, Duke of
Gloucester, and to Thomas Bodley, himself an avid book collector.
Similarly, Poland's Zaluski Library, one of Europe's oldest, owes its
existence to the collecting efforts of the Zaluski brothers, both
bishops and bibliophiles.^[51](#fn-2025-51){#fnref-2025-51}^ As we
mentioned earlier, *Aleph* too began its life as an aggregator of
collections, including the personal libraries of Moshkov and Traum. When
books are scarce, private libraries are a sign of material wealth and
prestige. In the digital realm, where the cost of media acquisition is
low, collectors amass social capital. *Aleph* extends its collecting
efforts on *RR*, a much larger, moderated torrent exchange forum and
tracker. *RR* hosts a number of sub-forums dedicated to the exchange of
software, film, music, and books (where members of *Aleph* often make an
appearance). In the exchange economy of symbolic goods, top collectors
are known by their standing in the community, as measured by their
seniority, upload and download ratios, and the number of "releases." A
release is more than just a file: it must not duplicate items in the
archive and follows strict community guidelines related to packaging,
quality, and meta-data accompanying the document. Less experienced
members of the community treat high status numbers with reverence and
respect.
According to a question and answer session with an official *RR*
representative, *RR* is not particularly friendly to new
users.^[52](#fn-2025-52){#fnref-2025-52}^ In fact, high barriers to
entry are exactly what differentiates *RR* from sites like *The Pirate
Bay* and other unmoderated, open trackers. *RR* prides itself on the
"quality of its moderation." Unlike *Pirate Bay*, *RR* sees itself as a
"media library", where content is "organized and properly shelved." To
produce an acceptable book "release" one needs to create a package of
files, including well-formatted meta-data (following strict stylistic
rules) in the header, the name of the book, an image of its cover, the
year of release, author, genre, publisher, format, language, a required
description, and screenshots of a sample page. The files must be named
according to a convention, be "of the same kind" (that is belong to the
same collection), and be of the right size. Home-made scans are
discouraged and governed by a 1,000-words instruction manual. Scanned
books must have clear attribution to the releaser responsible for
scanning and processing.
More than that, guidelines indicate that smaller releases should be
expected to be "absorbed" into larger ones. In this way, a single novel
by Charles Dickens can and will be absorbed into his collected works,
which might further be absorbed into "Novels of 19th Century," and then
into "Foreign Fiction" (as a hypothetical, but realistic example).
According to the rules, the collection doing the absorbing must be "at
least 50% larger than the collection it is absorbing." Releases are
further governed by a subset or rules particular to the forum
subsections (e.g. journals, fiction, documentation, service manuals,
etc.).^[53](#fn-2025-53){#fnref-2025-53}^
All this to say that although barriers to acquisition are low, the
barriers to active participation are high and continually *increase with
time*. The absorption of smaller collections by larger favors the
veterans. Rules and regulations grow in complexity with the maturation
of the community, further widening the rift between senior and junior
peers. We are then witnessing something like the institutionalization of
a professional "librarian" class, whose task it is to protect the
collection from the encroachment of low-quality contributors. Rather
than serving the public, a librarian's primary commitment is to the
preservation of the archive as a whole. Thus what starts as a true peer
production project, may, in the end, grow to erect solid walls to
peering. This dynamic is already embodied in the history of public
libraries, where amateur librarians of the late 19th century eventually
gave way to their modern degree-holding counterparts. The conflicting
logistics of access and preservation may lead digital library
development along a similar path.
The expression of this dual push and pull dynamic in the observed
practices of peer preservation communities conforms to Derrida's insight
into the nature of the archive. Just as the walls of a library serve to
shelter the documents within, they also isolate the collection from the
public at large. Access and preservation, in that sense, subsist at
opposite and sometime mutually exclusive ends of the sharing spectrum.
And it may be that this dynamic is particular to all peer production
communities, like *Wikipedia*, which, according to recent studies, saw a
decline in new contributors due to increasingly strict rule
enforcement.^[54](#fn-2025-54){#fnref-2025-54}^ However, our results are
merely speculative at the moment. The analysis of a large dataset we
have collected as corollary to our field work online may offer further
evidence for these initial intuitions. In the meantime, it is not enough
to conclude that brick-and-mortar libraries should learn from these
emergent, distributed architectures of peer preservation. If the future
of *Aleph* is leading to increased institutionalization, the community
may soon face the fate embodied by its own procedures: the absorption of
smaller, wonderfully messy, ascending collections into larger, more
established, and more rigid social structures.
**Biographies**
Dennis Tenen teaches in the fields of new media and digital humanities
at Columbia University, Department of English and Comparative
Literature. His research often happens at the intersection of people,
texts, and technology. He is currently writing a book on minimal
computing, called *Plain Text*.
Maxwell Foxman is an adjunct professor at Marymount Manhattan College
and a PhD candidate in Communications at Columbia University, where he
studies the use and adoption of digital media into everyday life. He has
written on failed social media and on gamification in electoral
politics, newsrooms, and mobile media.
**References**
Allen, Elizabeth Akers, and James Phinney Baxter. *Dedicatory Exercises
of the Baxter Building*. Auburn, Me: Lakeside Press, 1889.
Anonymous author. "Library.nu: Modern era's 'Destruction of the Library
of Alexandria.'" *Breaking Culture*. Last edited on February 16, 2012
and archived on archived on January 14, 2014.
[http://breakingculture.tumblr.com/post/17697325088/gigapedia-rip](“https://web.archive.org/web/20140113135846/http://breakingculture.tumblr.com/post/17697325088/gigapedia-rip”).
Benkler, Yochai. *The Wealth of Networks: How Social Production
Transforms Markets and Freedom*. New Haven: Yale University Press, 2006.
Bittorrent.org. "The BitTorrent Protocol Specification." Last modified
October 20, 2012 and archived on June 13, 2014.
[http://www.bittorrent.org/beps/bep\_0003.html](“http://web.archive.org/web/20140613190300/http://www.bittorrent.org/beps/bep_0003.html”).
Bodo, Balazs. "Set the Fox to Watch the Geese: Voluntary IP Regimes in
Piratical File-Sharing Communities." In *Piracy: Leakages from
Modernity*. Litwin Books, LLC, 2012.
Bowker, Geoffrey C., and Susan Leigh Star. *Sorting Things Out:
Classification and Its Consequences*. The MIT Press, 1999.
Calandrillo, Steve P. "Economic Analysis of Property Rights in
Information: Justifications and Problems of Exclusive Rights, Incentives
to Generate Information, and the Alternative of a Government-Run Reward
System, an." *Fordham Intellectual Property, Media & Entertainment Law
Journal* 9 (1998): 301.
Calhoun, Craig. "Information Technology and the International Public
Sphere." *In Shaping the Network Society: the New Role of Civil Society
in Cyberspace*, edited by Douglas Schuler and Peter Day, 229--52. MIT
Press, 2004.
Castells, Manuel. "Communication, Power and Counter-Power in the Network
Society." *International Journal of Communication* 1 (2007): 238--66.
Cholez, Thibault, Isabelle Chrisment, and Olivier Festor. "Evaluation of
Sybil Attacks Protection Schemes in KAD." In *Scalability of Networks
and Services*, edited by Ramin Sadre and Aiko Pras, 70--82. Lecture
Notes in Computer Science 5637. Springer Berlin Heidelberg, 2009.
Cohen, Bram. *Incentives Build Robustness in BitTorrent*, May 22, 2003.
[http://www.bittorrent.org/bittorrentecon.pdf](“http://www.bittorrent.org/bittorrentecon.pdf”).
Cohen, Julie. "Creativity and Culture in Copyright Theory." *U.C. Davis
Law Review* 40 (2006): 1151.
Day, Brian R. *In Defense of Copyright: Creativity, Record Labels, and
the Future of Music*. SSRN Scholarly Paper. Rochester, NY: Social
Science Research Network, May 2010.
DiMaggio, Paul, Eszter Hargittai, W. Russell Neuman, and John P.
Robinson. "Social Implications of the Internet." *Annual Review of
Sociology* 27 (January 2001): 307--36.
Edwards, Paul N. "Infrastructure and Modernity: Force, Time, and Social
Organization in the History of Sociotechnical Systems." In *Modernity
and Technology*, 185--225, 2003.
---------. "Y2K: Millennial Reflections on Computers as Infrastructure."
*History and Technology* 15, no. 1-2 (1998): 7--29.
Edwards, Paul N., Geoffrey C. Bowker, Steven J. Jackson, and Robin
Williams. "Introduction: an Agenda for Infrastructure Studies." *Journal
of the Association for Information Systems* 10, no. 5 (2009): 364--74.
Ernesto. "US P2P Lawsuit Shows Signs of a 'Pirate Honeypot'."
Technology. *TorrentFreak*. Last edited in June 2011 and archived on
January 14, 2014.
[http://torrentfreak.com/u-s-p2p-lawsuit-shows-signs-of-a-pirate-honeypot-110601/](“https://web.archive.org/web/20140114200326/http://torrentfreak.com/u-s-p2p-lawsuit-shows-signs-of-a-pirate-honeypot-110601/”).
Gauravaram, Praveen, and Lars R. Knudsen. "Cryptographic Hash
Functions." In *Handbook of Information and Communication Security*,
edited by Peter Stavroulakis and Mark Stamp, 59--79. Springer Berlin
Heidelberg, 2010.
Greenwood, Thomas. *Public Libraries: a History of the Movement and a
Manual for the Organization and Management of Rate Supported Libraries*.
Simpkin, Marshall, Hamilton, Kent, 1890.
Halfaker, Aaron, R. Stuart Geiger, Jonathan T. Morgan, and John Riedl.
"The Rise and Decline of an Open Collaboration System: How Wikipedia's
Reaction to Popularity Is Causing Its Decline." *American Behavioral
Scientist*, December 2012, 0002764212469365.
Harris, Michael H. *History of Libraries of the Western World*. Fourth
Edition. Lanham, Md.; London: Scarecrow Press, 1999.
Hughes, Justin. "Philosophy of Intellectual Property, the." *Georgetown
Law Journal* 77 (1988): 287.
http://heinonline.org/HOL/Page?handle=hein.journals/glj77&id=309&div=&collection=journals.
Hugo, Victor. *Works of Victor Hugo*. New York: Nottingham Society,
1907.
International Publishers Association. "Publishers Strike Major Blow
against Internet Piracy." Last modified February 15, 2012.
[http://www.internationalpublishers.org/ipa-press-releases/286-publishers-strike-major-blow-against-internet-piracy](“http://www.internationalpublishers.org/ipa-press-releases/286-publishers-strike-major-blow-against-internet-piracy”).
Johnson, Simon for Reuters.com. "Pirate Bay Copyright Test Case Begins
in Sweden." Last edited on February 16, 2009 and archived on August 4,
2014.
[http://uk.reuters.com/article/2009/02/16/tech-us-sweden-piratebay-idUKTRE51F3K120090216](http://web.archive.org/web/20140804000829/http://uk.reuters.com/article/2009/02/16/tech-us-sweden-piratebay-idUKTRE51F3K120090216”).\]
Karaganis, Joe, ed. *Media Piracy in Emerging Economies*. Social Science
Research Network, March 2011.
[http://piracy.americanassembly.org/the-report/.](“http://piracy.americanassembly.org/the-report/”).
Landes, William M., and Richard A. Posner. *The Economic Structure of
Intellectual Property Law*. Harvard University Press, 2003.
Larkin, Brian. "Degraded Images, Distorted Sounds: Nigerian Video and
the Infrastructure of Piracy." *Public Culture* 16, no. 2 (2004):
289--314.
---------. "Pirate Infrastructures." In *Structures of Participation in
Digital Culture*, edited by Joe Karaganis, 74--87. New York: SSRC, 2008.
Lessig, Lawrence. *Free Culture: How Big Media Uses Technology and the
Law to Lock Down Culture and Control Creativity*. The Penguin Press,
2004.
Liang, Lawrence. "Shadow Libraries E-Flux," last edited 2012 and
archived on October 14, 2014.
http://www.e-flux.com/journal/shadow-libraries/.
Lobato, Ramon, and Leah Tang. "The Cyberlocker Gold Rush: Tracking the
Rise of File-Hosting Sites as Media Distribution Platforms."
*International Journal of Cultural Studies*, November 2013.
Losowsky, Andrew. "Book Downloading Site Targeted in Injunctions
Requested by 17 Publishers." *Huffington Post*, last edited on February
2012 and archived on October 14, 2014.
[http://www.huffingtonpost.com/2012/02/15/librarynu-book-downloading-injunction\_n\_1280383.html](“http://www.huffingtonpost.com/2012/02/15/librarynu-book-downloading-injunction_n_1280383.html”).
Papacharissi, Zizi. "The Virtual Sphere the Internet as a Public
Sphere." *New Media & Society* 4, no. 1 (February 2002): 9--27.
Priest, Eric. "The Future of Music and Film Piracy in China." *Berkeley
Technology Law Journal* 21 (2006): 795.
Salmon, Ricardo, Jimmy Tran, and Abdolreza Abhari. "Simulating a File
Sharing System Based on BitTorrent." In *Proceedings of the 2008 Spring
Simulation Multiconference*, 21:1--:5. SpringSim '08. San Diego, CA,
USA: Society for Computer Simulation International, 2008.
Shirky, Clay. *Here Comes Everybody: the Power of Organizing Without
Organizations*. New York: Penguin Press, 2008.
Star, Susan Leigh, and Geoffrey C. Bowker. "How to Infrastructure." In
*Handbook of New Media: Social Shaping and Social Consequences of ICTs*,
Updated Student Edition., 230--46. SAGE Publications Ltd, 2010.
Stuart, Mary. "Creating a National Library for the Workers' State: the
Public Library in Petrograd and the Rumiantsev Library Under Bolshevik
Rule." *The Slavonic and East European Review* 72, no. 2 (April 1994):
233--58.
---------. "'The Ennobling Illusion': the Public Library Movement in
Late Imperial Russia." *The Slavonic and East European Review* 76, no. 3
(July 1998): 401--40.
---------. "The Evolution of Librarianship in Russia: the Librarians of
the Imperial Public Library, 1808-1868." *The Library Quarterly* 64, no.
1 (January 1994): 1--29.
Timpanaro, J.P., T. Cholez, I Chrisment, and O. Festor. "BitTorrent's
Mainline DHT Security Assessment." In *2011 4th IFIP International
Conference on New Technologies, Mobility and Security (NTMS)*, 1--5,
2011.
TPB. "Worlds most resiliant tracking." Last edited November 17, 2009 and
archived on August 4, 2014.
[thepiratebay.se/blog/175](“http://web.archive.org/web/20140804015645/http://thepiratebay.se/blog/175”)
Vik. "Gigapedia: The greatest, largest and the best website for
downloading eBooks." Emotionallyspeaking.com. Last edited on August 10,
2009 and archived on July 15, 2012.
[http://archive.is/g205"\>http://vikas-gupta.in/2009/08/10/gigapedia-the-greatest-largest-and-the-best-website-for-downloading-free-e-books/](“http://archive.is/g205”).
1. [Victor Hugo, *Works of Victor Hugo* (New York: Nottingham Society,
1907), 230. [[↩](#fnref-2025-1)]{.footnotereverse}]{#fn-2025-1}
2. [Lawrence Liang, "Shadow Libraries E-Flux," 2012.
[[↩](#fnref-2025-2)]{.footnotereverse}]{#fn-2025-2}
3. [McKendrick, Joseph. *Libraries: At the Epicenter of the Digital
Disruption, The Library Resource Guide Benchmark Study on 2013/14
Library Spending Plans* (Unisphere Media, 2013).
[[↩](#fnref-2025-3)]{.footnotereverse}]{#fn-2025-3}
4. ["Archive Fever: a Freudian Impression," *Diacritics* 25, no. 2
(July 1995): 9--63.
[[↩](#fnref-2025-4)]{.footnotereverse}]{#fn-2025-4}
5. [Yochai Benkler, *The Wealth of Networks: How Social Production
Transforms Markets and Freedom* (New Haven: Yale University Press,
2006), 92; Paul DiMaggio et al., "Social Implications of the
Internet," *Annual Review of Sociology* 27 (January 2001): 320; Zizi
Papacharissi "The Virtual Sphere the Internet as a Public Sphere,"
*New Media & Society* 4.1 (2002): 9--27; Craig Calhoun "Information
Technology and the International Public Sphere," in *Shaping the
Network Society: the New Role of Civil Society in Cyberspace*, ed.
Douglas Schuler and Peter Day (MIT Press, 2004), 229--52.
[[↩](#fnref-2025-5)]{.footnotereverse}]{#fn-2025-5}
6. [Benkler, *The Wealth of Networks*, 442; Manuel Castells,
"Communication, Power and Counter-Power in the Network Society,"
*International Journal of Communication* (2007): 251; Lawrence
Lessig *Free Culture:How Big Media Uses Technology and the Law to
Lock Down Culture and Control Creativity* (The Penguin Press, 2004);
Clay Shirky Here Comes Everybody: the Power of Organizing Without
Organizations (New York: Penguin Press, 2008), 153.
[[↩](#fnref-2025-6)]{.footnotereverse}]{#fn-2025-6}
7. [Brian R. Day "In Defense of Copyright: Creativity, Record Labels,
and the Future of Music," *Seton Hall Journal of Sports and
Entertainment Law*, 21.1 (2011); William M. Landes and Richard A.
Posner, *The Economic Structure of Intellectual Property Law*
(Harvard University Press, 2003). For further discussion see
Steve P. Calandrillo, "Economic Analysis of Property Rights in
Information: Justifications and Problems of Exclusive Rights,
Incentives to Generate Information, and the Alternative of a
Government-Run Reward System" *Fordham Intellectual Property, Media
& Entertainment Law Journal* 9 (1998): 306; Julie Cohen, "Creativity
and Culture in Copyright Theory," *U.C. Davis Law Review* 40 (2006):
1151; Justin Hughes "Philosophy of Intellectual Property,"
*Georgetown Law Journal* 77 (1988): 303.
[[↩](#fnref-2025-7)]{.footnotereverse}]{#fn-2025-7}
8. [[piracylab.org](“http://piracylab.org”).
[[↩](#fnref-2025-8)]{.footnotereverse}]{#fn-2025-8}
9. ["Set the Fox to Watch the Geese: Voluntary IP Regimes in Piratical
File-Sharing Communities, in *Piracy: Leakages from Modernity*
(Litwin Books, LLC, 2012).
[[↩](#fnref-2025-9)]{.footnotereverse}]{#fn-2025-9}
10. ["The Future of Music and Film Piracy in China," *Berkeley
Technology Law Journal* 21 (2006): 795.
[[↩](#fnref-2025-10)]{.footnotereverse}]{#fn-2025-10}
11. ["The Cyberlocker Gold Rush: Tracking the Rise of File-Hosting Sites
as Media Distribution Platforms," *International Journal of Cultural
Studies*, (2013).
[[↩](#fnref-2025-11)]{.footnotereverse}]{#fn-2025-11}
12. [The injunctions name I\* and F\* N\* (also known as Smiley).
[[↩](#fnref-2025-12)]{.footnotereverse}]{#fn-2025-12}
13. ["Publishers Strike Major Blow against Internet Piracy" last
modified February 15, 2012 and archived on January 10, 2014,
[http://www.internationalpublishers.org/ipa-press-releases/286-publishers-strike-major-blow-against-internet-piracy](“http://web.archive.org/web/20140110160254/http://www.internationalpublishers.org/ipa-press-releases/286-publishers-strike-major-blow-against-internet-piracy”).
[[↩](#fnref-2025-13)]{.footnotereverse}]{#fn-2025-13}
14. [Including the German Publishers and Booksellers Association,
Cambridge University Press, Georg Thieme, Harper Collins, Hogrefe,
Macmillan Publishers Ltd., Cengage Learning, Elsevier, John Wiley &
Sons, The McGraw-Hill Companies, Pearson Education Ltd., Pearson
Education Inc., Oxford University Press, Springer, Taylor & Francis,
C.H. Beck as well as Walter De Gruyter. The legal proceedings are
also supported by the Association of American Publishers (AAP), the
Dutch Publishers Association (NUV), the Italian Publishers
Association (AIE) and the International Association of Scientific
Technical and Medical Publishers (STM).
[[↩](#fnref-2025-14)]{.footnotereverse}]{#fn-2025-14}
15. [Andrew Losowsky, "Book Downloading Site Targeted in Injunctions
Requested by 17 Publishers," *Huffington Post*, accessed on
September 1, 2014,
[http://www.huffingtonpost.com/2012/02/15/librarynu-book-downloading-injunction\_n\_1280383.html](“http://www.huffingtonpost.com/2012/02/15/librarynu-book-downloading-injunction_n_1280383.html”).
[[↩](#fnref-2025-15)]{.footnotereverse}]{#fn-2025-15}
16. [International Publishers Association.
[[↩](#fnref-2025-16)]{.footnotereverse}]{#fn-2025-16}
17. [Vik, "Gigapedia: The greatest, largest and the best website for
downloading eBooks," Emotionallyspeaking.com, last edited on August
10, 2009 and archived on July 15, 2012,
[http://archive.is/g205"\>http://vikas-gupta.in/2009/08/10/gigapedia-the-greatest-largest-and-the-best-website-for-downloading-free-e-books/](“http://archive.is/g205”).
[[↩](#fnref-2025-17)]{.footnotereverse}]{#fn-2025-17}
18. [Anonymous author, "Library.nu: Modern era's 'Destruction of the
Library of Alexandria,'" *Breaking Culture* (on tublr.com), last
edited on February 16, 2012 and archived on January 14, 2014,
[http://breakingculture.tumblr.com/post/17697325088/gigapedia-rip](“https://web.archive.org/web/20140113135846/http://breakingculture.tumblr.com/post/17697325088/gigapedia-rip”).
[[↩](#fnref-2025-18)]{.footnotereverse}]{#fn-2025-18}
19. [[http://torrentfreak.com/book-publishers-shut-down-library-nu-and-ifile-it-120215](“https://web.archive.org/web/20140110050710/http://torrentfreak.com/book-publishers-shut-down-library-nu-and-ifile-it-120215”)
archived on January 10, 2014.
[[↩](#fnref-2025-19)]{.footnotereverse}]{#fn-2025-19}
20. [[http://www.reddit.com/r/trackers/comments/ppfwc/librarynu\_admin\_the\_website\_is\_shutting\_down\_due](“https://web.archive.org/web/20140110050450/http://www.reddit.com/r/trackers/comments/ppfwc/librarynu_admin_the_website_is_shutting_down_due”)
archived on January 10, 2014.
[[↩](#fnref-2025-20)]{.footnotereverse}]{#fn-2025-20}
21. [[http://www.reddit.com/r/trackers/comments/ppfwc/librarynu\_admin\_the\_website\_is\_shutting\_down\_due](“https://web.archive.org/web/20140110050450/http://www.reddit.com/r/trackers/comments/ppfwc/librarynu_admin_the_website_is_shutting_down_due”)
orchived on January 10, 2014.
[[↩](#fnref-2025-21)]{.footnotereverse}]{#fn-2025-21}
22. [[www.reddit.com/r/trackers/comments/ppfwc/librarynu\_admin\_the\_website\_is\_shutting\_down\_due](“https://web.archive.org/web/20140110050450/http://www.reddit.com/r/trackers/comments/ppfwc/librarynu_admin_the_website_is_shutting_down_due”)
archived on January 10, 2014.
[[↩](#fnref-2025-22)]{.footnotereverse}]{#fn-2025-22}
23. [This point is made at length in the report on media piracy in
emerging economies, released by the American Assembly in 2011. See
Joe Karaganis, ed. *Media Piracy in Emerging Economies* (Social
Science Research Network, March 2011),
[http://piracy.americanassembly.org/the-report/](“http://piracy.americanassembly.org/the-report/”), I.
[[↩](#fnref-2025-23)]{.footnotereverse}]{#fn-2025-23}
24. [Lobato and Tang, "The Cyberlocker Gold Rush."
[[↩](#fnref-2025-24)]{.footnotereverse}]{#fn-2025-24}
25. [Lobato and Tang, "The Cyberlocker Gold Rush," 9.
[[↩](#fnref-2025-25)]{.footnotereverse}]{#fn-2025-25}
26. [Lobato and Tang, "The Cyberlocker Gold Rush," 7.
[[↩](#fnref-2025-26)]{.footnotereverse}]{#fn-2025-26}
27. [GIMEL/viewtopic.php?f=8&t=169; GIMEL/viewtopic.php?f=17&t=299.
[[↩](#fnref-2025-27)]{.footnotereverse}]{#fn-2025-27}
28. [GIMEL/viewtopic.php?f=17&t=299.
[[↩](#fnref-2025-28)]{.footnotereverse}]{#fn-2025-28}
29. [GIMEL/viewtopic.php?f=8&t=169. All quotes translated from Russian
by the authors, unless otherwise noted.
[[↩](#fnref-2025-29)]{.footnotereverse}]{#fn-2025-29}
30. [GIMEL/viewtopic.php?f=8&t=6999&p=41911.
[[↩](#fnref-2025-30)]{.footnotereverse}]{#fn-2025-30}
31. [GIMEL/viewtopic.php?f=8&t=757.
[[↩](#fnref-2025-31)]{.footnotereverse}]{#fn-2025-31}
32. [In this sense, we see our work as complementary to but not
exhausted by infrastructure studies. See Geoffrey C. Bowker and
Susan Leigh Star, *Sorting Things Out: Classification and Its
Consequences* (The MIT Press, 1999); Paul N. Edwards, "Y2K:
Millennial Reflections on Computers as Infrastructure," *History and
Technology* 15.1-2 (1998): 7--29; Paul N. Edwards, "Infrastructure
and Modernity: Force, Time, and Social Organization in the History
of Sociotechnical Systems," in *Modernity and Technology*, 2003,
185--225; Paul N. Edwards et al., "Introduction: an Agenda for
Infrastructure Studies," *Journal of the Association for Information
Systems* 10.5 (2009): 364--74; Brian Larkin "Degraded Images,
Distorted Sounds: Nigerian Video and the Infrastructure of Piracy,"
*Public Culture* 16.2 (2004): 289--314; Brian Larkin "Pirate
Infrastructures," in *Structures of Participation in Digital
Culture*, ed. Joe Karaganis (New York: SSRC, 2008), 74--87; Susan
Leigh Star and Geoffrey C. Bowker, "How to Infrastructure," in
*Handbook of New Media: Social Shaping and Social Consequences of
ICTs*, (SAGE Publications Ltd, 2010), 230--46.
[[↩](#fnref-2025-32)]{.footnotereverse}]{#fn-2025-32}
33. [For information on cryptographic hashing see Praveen Gauravaram and
Lars R. Knudsen, "Cryptographic Hash Functions," in *Handbook of
Information and Communication Security*, ed. Peter Stavroulakis and
Mark Stamp (Springer Berlin Heidelberg, 2010), 59--79.
[[↩](#fnref-2025-33)]{.footnotereverse}]{#fn-2025-33}
34. [See GIMEL/viewtopic.php?f=8&t=55kj and
GIMEL/viewtopic.php?f=8&t=18&sid=936.
[[↩](#fnref-2025-34)]{.footnotereverse}]{#fn-2025-34}
35. [GIMEL/viewtopic.php?f=8&t=714.
[[↩](#fnref-2025-35)]{.footnotereverse}]{#fn-2025-35}
36. [GIMEL/viewtopic.php?f=8&t=47.
[[↩](#fnref-2025-36)]{.footnotereverse}]{#fn-2025-36}
37. [GIMEL/viewtopic.php?f=17&t=175&hilit=RR&start=25.
[[↩](#fnref-2025-37)]{.footnotereverse}]{#fn-2025-37}
38. [GIMEL/viewtopic.php?f=17&t=104&start=450.
[[↩](#fnref-2025-38)]{.footnotereverse}]{#fn-2025-38}
39. [URL redacted; These numbers should be taken as a very rough
estimate because 1) we do not consider Alexa to be a reliable source
for web traffic and 2) some of the other figures cited in the report
are suspicious. For example, *Aleph* has a relatively small archive
of foreign fiction, at odds with the reported figure of 800,000
volumes. [[↩](#fnref-2025-39)]{.footnotereverse}]{#fn-2025-39}
40. [GIMEL/viewtopic.php?f=17&t=7061.
[[↩](#fnref-2025-40)]{.footnotereverse}]{#fn-2025-40}
41. ["The BitTorrent Protocol Specification," last modified October 20,
2012 and archived on June 13, 2014,
[http://www.bittorrent.org/beps/bep\_0003.html](“http://web.archive.org/web/20140613190300/http://www.bittorrent.org/beps/bep_0003.html”).
[[↩](#fnref-2025-41)]{.footnotereverse}]{#fn-2025-41}
42. [For more information on BitTorrent, see Bram Cohen, *Incentives
Build Robustness in BitTorrent*, last modified on May 22, 2003,
[http://www.bittorrent.org/bittorrentecon.pdf](“http://www.bittorrent.org/bittorrentecon.pdf”);
Ricardo Salmon, Jimmy Tran, and Abdolreza Abhari, "Simulating a File
Sharing System Based on BitTorrent," in *Proceedings of the 2008
Spring Simulation Multiconference*, SpringSim '08 (San Diego, CA,
USA: Society for Computer Simulation International, 2008), 21:1--5.
[[↩](#fnref-2025-42)]{.footnotereverse}]{#fn-2025-42}
43. [In 2008 *The Pirate Bay* co-founders Peter Sunde, Gottfrid
Svartholm Warg, Fredrik Neij, and Carl Lundstromwere were charged
with "conspiracy to break copyright related offenses" in Sweden. See
Simon Johnson for Reuters.com, "Pirate Bay Copyright Test Case
Begins in Sweden," last edited on February 16, 2009 and archived on
August 4, 2014,
[http://uk.reuters.com/article/2009/02/16/tech-us-sweden-piratebay-idUKTRE51F3K120090216](http://web.archive.org/web/20140804000829/http://uk.reuters.com/article/2009/02/16/tech-us-sweden-piratebay-idUKTRE51F3K120090216”).
[[↩](#fnref-2025-43)]{.footnotereverse}]{#fn-2025-43}
44. [TPB, "Worlds most resiliant tracking," last edited November 17,
2009 and archived on August 4, 2014,
[thepiratebay.se/blog/175](“http://web.archive.org/web/20140804015645/http://thepiratebay.se/blog/175”).
[[↩](#fnref-2025-44)]{.footnotereverse}]{#fn-2025-44}
45. [GIMEL/viewtopic.php?f=8&t=6999.
[[↩](#fnref-2025-45)]{.footnotereverse}]{#fn-2025-45}
46. [Thibault Cholez, Isabelle Chrisment, and Olivier Festor "Evaluation
of Sybil Attacks Protection Schemes in KAD," in *Scalability of
Networks and Services*, ed. Ramin Sadre and Aiko Pras, Lecture Notes
in Computer Science 5637 (Springer Berlin Heidelberg, 2009), 70--82.
[[↩](#fnref-2025-46)]{.footnotereverse}]{#fn-2025-46}
47. [J.P. Timpanaro et al., "BitTorrent's Mainline DHT Security
Assessment," in *2011 4th IFIP International Conference on New
Technologies, Mobility and Security (NTMS)*, 2011, 1--5.
[[↩](#fnref-2025-47)]{.footnotereverse}]{#fn-2025-47}
48. [Ernesto, "US P2P Lawsuit Shows Signs of a 'Pirate Honeypot',"
Technology, *TorrentFreak*, last edited in June 2011 and archived on
January 14, 2014,
[http://torrentfreak.com/u-s-p2p-lawsuit-shows-signs-of-a-pirate-honeypot-110601/](“https://web.archive.org/web/20140114200326/http://torrentfreak.com/u-s-p2p-lawsuit-shows-signs-of-a-pirate-honeypot-110601/”).
[[↩](#fnref-2025-48)]{.footnotereverse}]{#fn-2025-48}
49. [Benkler *The Wealth of Networks*, 60.
[[↩](#fnref-2025-49)]{.footnotereverse}]{#fn-2025-49}
50. [On the free and public library movement in England and the United
States see Thomas Greenwood, *Public Libraries: a History of the
Movement and a Manual for the Organization and Management of Rate
Supported Libraries* (Simpkin, Marshall, Hamilton, Kent, 1890);
Elizabeth Akers Allen and James Phinney Baxter, *Dedicatory
Exercises of the Baxter Building* (Auburn, Me: Lakeside Press,
1889). To read more about the history of free and public library
movements in Russia see Mary Stuart, "The Evolution of Librarianship
in Russia: the Librarians of the Imperial Public Library,
1808-1868," *The Library Quarterly* 64.1 (January 1994): 1--29; Mary
Stuart, "Creating a National Library for the Workers' State: the
Public Library in Petrograd and the Rumiantsev Library Under
Bolshevik Rule," *The Slavonic and East European Review* 72.2 (April
1994): 233--58; Mary Stuart "The Ennobling Illusion: the Public
Library Movement in Late Imperial Russia," *The Slavonic and East
European Review* 76.3 (July 1998): 401--40.
[[↩](#fnref-2025-50)]{.footnotereverse}]{#fn-2025-50}
51. [Michael H. Harris, *History of Libraries of the Western World*,
(London: Scarecrow Press, 1999), 136.
[[↩](#fnref-2025-51)]{.footnotereverse}]{#fn-2025-51}
52. [http://s\*.d\*.ru/comments/508985/.
[[↩](#fnref-2025-52)]{.footnotereverse}]{#fn-2025-52}
53. [RR/forum/viewtopic.php?t=1590026.
[[↩](#fnref-2025-53)]{.footnotereverse}]{#fn-2025-53}
54. [Aaron Halfaker et al."The Rise and Decline of an Open Collaboration
System: How Wikipedia's Reaction to Popularity Is Causing Its
Decline," *American Behavioral Scientist*, December 2012.
[[↩](#fnref-2025-54)]{.footnotereverse}]{#fn-2025-54}
:::
Series Navigation[[\<\< What Do Metrics Want? How Quantification
Prescribes Social Interaction on
Facebook](http://computationalculture.net/what-do-metrics-want/ "<< What Do Metrics Want? How Quantification Prescribes Social Interaction on Facebook")]{.series-nav-left}[[Modelling
biology -- working through (in-)stabilities and frictions
\>\>](http://computationalculture.net/modelling-biology/ "Modelling biology – working through (in-)stabilities and frictions >>")]{.series-nav-right}
:::
::: {.comments}
:::
Article printed from Computational Culture:
**http://computationalculture.net**
URL to article:
**http://computationalculture.net/book-piracy-as-peer-preservation/**
[Click here to print.](#Print "Click here to print.")
The Guide to techno-galactic software observing was compiled by Carlin
Wing, Martino Morandi, Peggy Pierrot, Anita, Christoph Haag, Michael
Murtaugh, Femke Snelting
License: Free Art License
Support:
Sources:
Constant, February 2018
::: {.footnotes}
1. [[[Haraway]{.fname}, [Donna]{.gname}, [Galison]{.fname},
[Peter]{.gname} and [Stump]{.fname}, [David J]{.gname}: [Modest
Witness: Feminist Diffractions in Science Studies]{.title},
[Stanford University Press]{.publisher}, [1996]{.date}.
]{.collection} [-\>](#eeffecbe)]{#ebceffee}
2. [Worksessions are intensive transdisciplinary moments, organised
twice a year by Constant. They aim to provide conditions for
participants with different experiences and capabilities to
Constant
The Techno-Galactic Guide to Software Observation
2018
::: {.toc}
[Introduction](#mtljymuz) [Encounter several collections of historical
hardware back-to-back](#njm5zwm4) [Interview people about their
histories with software](#mguzmza4) [Ask several people from different
fields and age-groups the same question: \"***What is
software?***\"](#odfkotky) [FMEM and /DEV/MEM](#mzcxodix)
[Pan/Monopsychism](#m2mwogri) [Fountain refreshment](#ndawnmy5) [Create
\"nannyware\": Software that observes and addresses the user](#mtk5yjbl)
[Useless scroll against productivity](#yzuwmdq4) [Investigating how
humans and machines negotiate the experience of time](#m2vjndu3)
[Quine](#nmi5mgjm) [Glossaries as an exercise](#zwu0ogu0) [Adding
qualifiers](#mja0m2i5) [Searching \"software\" through
software](#mmmwmje2) [Persist in calling everyone a Software Curious
Person](#ndhkmwey) [Setup a Relational software observatory consultancy
(RSOC)](#mmu1mgy0) [Agile Sun Salutation](#mta1ntzm) [Hand
reading](#mdu0mmji) [Bug reporting for sharing observations](#yznjodq3)
[Interface Détournement](#ytu5y2qy) [Comportments of software
(softwear)](#y2q4zju5) [Continuous integration](#mwrhm2y4) [make make
do](#zdixmgrm) [Flowcharts (Flow of the chart -- chart of the flow on
demand!)](#zweymtni) [Something in the Middle Maybe (SitMM)](#ywfin2e4)
[What is it like to be AN ELEVATOR?](#ntlimgqy) [Side Channel
Analysis](#ndg2zte4) [Compiling a bestiary of software logos](#njmzmjm1)
[Encounter several collections of historical hardware
back-to-back](#njm5zwm4) [Testing the testbed: testing software with
observatory ambitions (SWOA)](#mmy2zgrl) [Prepare a reader to think
theory with software](#mmmzmmrh)
:::
[]{#mtljymuz .anchor}
A guide to techno-galactic software observation
> I am less interested in the critical practice of reflection, of
> showing once-again that the emperor has no clothes, than in finding a
> way to *diffract* critical inquiry in order to make difference
> patterns in a more worldly way.^[1](#ebceffee)^
The techno-galactic software survival guide that you are holding right
now was collectively produced as an outcome of the Techno-Galactic
Software Observatory. This guide proposes several ways to achieve
critical distance from the seemingly endless software systems that
surround us. It offers practical and fantastical tools for the tactical
(mis)use of software, empowering/enabling users to resist embedded
paradigms and assumptions. It is a collection of methods for approaching
software, experiencing its myths and realities, its risks and benefits.
With the rise of online services, the use of software has increasingly
been knitted into the production of software, even while the rhetoric,
rights, and procedures continue to suggest that use and production
constitute separate realms. This knitting together and its corresponding
disavowal have an effect on the way software is used and produced, and
radically alters its operative role in society. The shifts ripple across
galaxies, through social structures, working conditions and personal
relations, resulting in a profusion of apparatuses aspiring to be
seamless while optimizing and monetizing individual and collective flows
of information in line with the interests of a handful of actors. The
diffusion of software services affects the personal, in the form of
intensified identity shaping and self-management. It also affects the
public, as more and more libraries, universities and public
infrastructures as well as the management of public life rely on
\"solutions\" provided by private companies. Centralizing data flows in
the clouds, services blur the last traces of the thin line that
separates bio- from necro-politics.
Given how fast these changes resonate and reproduce, there is a growing
urgency to engage in a critique of software that goes beyond taking a
distance, and that deals with the fact that we are inevitably already
entangled. How can we interact, intervene, respond and think with
software? What approaches can allow us to recognize the agency of
different actors, their ways of functioning and their politics? What
methods of observation enable critical inquiry and affirmative discord?
What techniques can we apply to resurface software where it has melted
into the infrastructure and into the everyday? How can we remember that
software is always at work, especially where it is designed to disappear
into the background?
We adopted the term of observation for a number of reasons. We regard
observation as a way to approach software, as one way to organize
engagement with its implications. Observation, and the enabling of
observation through intensive data-centric feedback mechanisms, is part
of the cybernetic principles that underpin present day software
production. Our aim was to scrutinize this methodology in its many
manifestations, including in \"observatories\" \-- high cost
infrastructures \[testing infrastructures?CITECLOSE23310 of observation
troubled by colonial, imperial traditions and their problematic
divisions of nature and culture \-- with the hope of opening up
questions about who gets to observe software (and how) and who is being
observed by software (and with what impact)? It is a question of power,
one that we answer, at least in part, with critical play.
We adopted the term techno-galactic to match the advertised capability
of \"scaling up to the universe\" that comes in contemporary paradigms
of computation, and to address different scales of software communities
and related political economies that involve and require observation.
Drawing on theories of software and computation developed in academia
and elsewhere, we grounded our methods in hands-on exercises and
experiments that you now can try at home. This Guide to Techno-Galactic
Software Observation offers methods developed in and inspired by the
context of software production, hacker culture, software studies,
computer science research, Free Software communities, privacy activism,
and artistic practice. It invites you to experiment with ways to stay
with the trouble of software.
The Techno-Galactic Software Observatory
----------------------------------------
In the summer of 2017, around thirty people gathered in Brussels to
explore practices of proximate critique with and of software in the
context of a worksession entitled \"Techno-Galactic Software
Observatory\".^[2](#bcaacdcf)^ The worksession called for
software-curious people of all kinds to ask questions about software.
The intuition behind such a call was that different types of engagement
requires a heterogeneous group of participants with different levels of
expertise, skill and background. During three sessions of two days,
participants collectively inspected the space-time of computation and
probed the universe of hardware-software separations through excursions,
exercises and conversations. They tried out various perspectives and
methods to look at the larger picture of software as a concept, as a
practice, and as a set of techniques.
The first two days of The Techno-Galactic Software Observatory included
visits to the Musée de l\'Informatique Pionnière en
Belgique^[3](#aaceaeff)^ in Namur and the Computermuseum
KULeuven^[4](#afbebabd)^. In the surroundings of these collections of
historical 'numerical artefacts', we started viewing software in a
long-term context. It offered us the occasion to reflect on the
conditions of its appearance, and allowed us to take on current-day
questions from a genealogical perspective. What is software? How did it
appear as a concept, in what industrial and governmental circumstances?
What happens to the material conditions of its production (minerals,
factory labor, hardware) when it evaporates into a cloud?
The second two days we focused on the space-time dimension of IT
development. The way computer programs and operating systems are
manufactured changed tremendously through time, and so did its
production times and places. From military labs via the mega-corporation
cubicles to the open-space freelancer utopia, what ruptures and
continuities can be traced in the production, deployment, maintenance
and destruction of software? From time-sharing to user-space partitions
and containerization, what separations were and are at work? Where and
when is software made today?
The Walk-in Clinic
------------------
The last two days at the Techno-galactic software observatory were
dedicated to observation and its consequences. The development of
software encompasses a series of practices whose evocative names are
increasingly familiar: feedback, report, probe, audit, inspect, scan,
diagnose, explore, test \... What are the systems of knowledge and power
within which these activities take place, and what other types of
observation are possible? As a practical set for our investigations, we
set up a walk-in clinic on the 25th floor of the World Trade Center,
where users and developers could arrive with software-questions of all
kinds.
> Do you suffer from the disappearance of your software into the cloud,
> feel oppressed by unequal user privilege, or experience the torment of
> software-ransom of any sort? Bring your devices and interfaces to the
> World Trade Center! With the help of a clear and in-depth session, at
> the Techno-Galactic Walk-In Clinic we guarantee immediate results. The
> Walk-In Clinic provides free hands-on observations to software curious
> people of all kinds. A wide range of professional and amateur
> practitioners will provide you with
> Software-as-a-Critique-as-a-Service on the spot. Available services
> range from immediate interface critique, collaborative code
> inspection, data dowsing, various forms of network analyses,
> unusability testing, identification of unknown viruses, risk
> assessment, opening of black-boxes and more. Free software
> observations provided. Last intake at 16:45.\
> (invitation to the Walk-In Clinic, June 2017)
On the following pages: Software as a Critique as a Service (SaaCaaS)
Directory and intake forms for Software Curious People (SCP).
The survival techniques described in the following guide are to be used
at your own risk in case of emergency regarding software curiosity. The
publisher will not accept any responsability in case of damages caused
by misuse, misundestanding of instruction or lack of curiosity. By
trying the action exposed in the guide, you accept the responsability of
loosing data or altering hardware, including hard disks, usb key, cloud
storage, screens by throwing them on the floor, or even when falling on
the floor with your laptop by tangling your feet in an entanglement of
cables. No harm has been done to human, animal, computers or plants
while creating the guide. No firearms or any kind of weapon is needed in
order to survive software.\
Just a little bit of patience.
**Software observation survival stresses**
**Physical fitness plays a great part of software observation. Be fit or
CTRL-Quit.**
When trying to observe software you might experience stresses as such :
*Anxiety*Sleep deprivation *Forgetting about eating*Loss of time
tracking
**Can you cope with software ? You have to.**
> our methods for observation, like mapping, come with their luggage.
[Close encounters]{.grouping} []{#njm5zwm4 .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.visit)
Encounter several collections of historical hardware
back-to-back]{.method .descriptor} [How]{.how .empty .descriptor}
This can be done by identifying one or more computer museums and visit
them with little time in-between. Visiting a friend with a large
basement and lots of left-over computer equipment can help. Seeing and
possibly touching hardware from different contexts
(state-administration, business, research, \...), periods of time,
cultural contexts (California, Germany, French-speaking Belgium) and
price ranges allows you to sense the interactions between hardware and
software development.
[Note: It\'s a perfect way to hear people speak about the objects and
their contexts, how they worked or not and how objects are linked one
with another. It also shows the economic and cultural aspects of
softwares.]{.note .descriptor} [WARNING: **DO NOT FOLD, SPINDLE OR
MUTILATE**]{.warning .descriptor} [Example: Spaghetti Suitcase]{.example
.descriptor}
At one point during the demonstration of a Bull computer, the guide
revealed the system\'s \"software\" \-- a suitcase sized module with
dozens of patch cords. She made the comment that the term \"spaghetti
code\" (a derogatory expression about early code usign many \"GOTO\"
statments) had its origin in this physical arrangement of code as
patchings.
Preserving old hardware in order to observe physical manifestation of
software. See software here : we did experienced the incredible
possibility of actually touching software.
[SHOW IMAGE HERE:
http://observatory.constantvzw.org/images/wednesday/IMG\_20170607\_113634\_585.jpg]{.tmp}
[SHOW IMAGE HERE:
http://gallery.constantvzw.org/var/resizes/Techno-Galactic-Software-Observatory/IMG\_1163.JPG?m=1496916927]{.tmp}
[Example: Playing with the binary. Bull cards. Happy operator! Punch
card plays.]{.example .descriptor}
\"The highlight of the collection is to revive a real punch card
workshop of the 1960s.\"
[Example: Collection de la Maison des Écritures d\'Informatique & Bible,
Maredsous]{.example .descriptor}
The particularity of the collection lies in the fact that it\'s the
conservation of multiple stages of life of a software since its initial
computerization until today. The idea of introducing informatics into
the work of working with/on the Bible (versions in Hebrew, Greek, Latin,
and French) dates back to 1971, via punch card recordings and their
memorization on magnetic tape. Then came the step of analyzing texts
using computers.
[SHOW IMAGE HERE:
http://gallery.constantvzw.org/var/resizes/Preparing-the-Techno-galactic-Software-Observatory/DSC05019.JPG?m=1490635726]{.tmp}
[TODO: RELATES TO
http://pad.constantvzw.org/p/observatory.guide.jean.heuns]{.tmp}
[]{#mguzmza4 .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.jean.heuns)
Interview people about their histories with software]{.method
.descriptor} [What: Observe personnal narratives around software
history. Retrace the path of relation to software, how it changed during
the years and what are the human access memories that surrounds it. To
look at software through personal relations and emotions.]{.what
.descriptor} [How: Interviews are a good way to do it. Informal
conversations also.]{.how .descriptor}
Jean Heuns has been collecting servers, calculators, softwares, magnetic
tapes hard disks for xxx years. Found an agreement for them to be
displayed in the department hallways. Department of Computer sciences -
Kul Leuven.
[SHOW IMAGE HERE:
http://gallery.constantvzw.org/var/albums/Techno-Galactic-Software-Observatory/PWFU3350.JPG]{.tmp}
[SHOW IMAGE HERE:
http://gallery.constantvzw.org/var/albums/Techno-Galactic-Software-Observatory/PWFU3361.JPG]{.tmp}
[SHOW IMAGE HERE:
http://gallery.constantvzw.org/var/albums/Techno-Galactic-Software-Observatory/PWFU3356.JPG]{.tmp}
[SHOW IMAGE HERE:
http://gallery.constantvzw.org/var/albums/Techno-Galactic-Software-Observatory/PWFU3343.JPG]{.tmp}
[TODO: RELATES TO]{.tmp} []{#odfkotky .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.samequestion)
Ask several people from different fields and age-groups the same
question: \"***What is software?***\"]{.method .descriptor} [Remember:
The answers to this question will vary depending on who is asking it to
who.]{.remember .descriptor} [What: By paying close attention to the
answers, and possibly logging them, observations on the ambiguous place
and nature of software can be made.]{.what .descriptor}
[Example]{.example .empty .descriptor}
Jean Huens (system administrator at the department of Computer Science,
KULeuven): \"*It is difficult to answer the question \'what is
software\', but I know what is good software*\"
Thomas Cnudde (hardware designer at ESAT - COSIC, Computer Security and
Industrial Cryptography, KULeuven): \"*Software is a list of sequential
instructions! Hardware for me is made of silicon, software a sequence of
bits in a file. But naturally I am biased: I\'m a hardware designer so I
like to consider it as unique and special*\".
Amal Mahious (Director of NAM-IP, Namur): \"*This, you have to ask the
specialists.*\"
` {.verbatim}
*what is software?
--the unix filesystem says: it's a file----what is a file?
----in the filesystem, if you ask xxd:
------ it's a set of hexadecimal bytes
-------what is hexadecimal bytes?
------ -b it's a set of binary 01s
----if you ask objdump
-------it's a set of instructions
--side channel researching also says:
----it's a set of instructions
--the computer glossary says:
----it's a computer's programs, plus the procedure for their use http://etherbox.local/home/pi/video/A_Computer_Glossary.webm#t=02:26
------ a computer's programs is a set of instrutions for performing computer operations `
[Remember: To answer the question \"*what is software*\" depends on the
situation, goal, time, and other contextual influences.]{.remember
.descriptor} [TODO: RELATES TO
http://pad.constantvzw.org/p/observatory.guide.everyonescp]{.tmp}
[]{#mzcxodix .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.devmem) FMEM
and /DEV/MEM]{.method .descriptor} [What: Different ways of exploring
your memory (RAM). Because in unix everything is a file, you can access
your memory as if it were a file.]{.what .descriptor} [Urgency: To try
and observe the operational level of software, getting closer to the
workings, the instruction-being of an executable/executing file, the way
it is when it is loaded into memory rather than when it sits in the
harddisk]{.urgency .descriptor} [Remember: In Unix-like operating
systems, a device file or special file is an interface for a device
driver that appears in a file system as if it were an ordinary file. In
the early days you could fully access your memory via the memory device
(`/dev/mem`) but over time the access was more and more restricted in
order to avoid malicious processes to directly access the kernel memory.
The kernel option CONFIG\_STRICT\_DEVMEM was introduced in kernel
version 2.6 and upper (2.6.36--2.6.39, 3.0--3.8, 3.8+HEAD). So you\'ll
need to use the Linux kernel module fmem: this module creates
`/dev/fmem` device, that can be used for accessing physical memory
without the limits of /dev/mem (1MB/1GB, depending on
distribution).]{.remember .descriptor}
`/dev/mem` tools to explore processes stored in the memory
ps ax | grep process
cd /proc/numberoftheprocess
cat maps
\--\> check what it is using
The proc filesystem is a pseudo-filesystem which provides an interface
to kernel data structures. It is commonly mounted at `/proc`. Most of it
is read-only, but some files allow kernel variables to be changed.
dump to a file\--\>change something in the file\--\>dump new to a
file\--\>diff oldfile newfile
\"where am i?\"
to find read/write memory addresses of a certain process\
`awk -F "-| " '$3 ~ /rw/ { print $1 " " $2}' /proc/PID/maps`{.bash}
Besides opening the memory dump with an hex editor you can also try and
explore it with other tools or devices. You can open it as a raw image,
you can play it as a sound or perhaps send it directly to your
frame-buffer device (`/dev/fb0`).
[WARNING: Although your memory may look like/sound like/read like
gibberish, it may contain sensitive information about you and your
computer!]{.warning .descriptor} [Example]{.example .empty .descriptor}
[SHOW IMAGE HERE:
http://observatory.constantvzw.org/images/Screenshot\_from\_2017-06-07\_164407.png]{.tmp}
[TODO: BOX: Forensic and debuggung tools can be used to explore and
problematize the layers of abstraction of computing.]{.tmp} [TODO:
RELATES TO
http://pad.constantvzw.org/p/observatory.guide.monopsychism]{.tmp}
[]{#m2mwogri .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.monopsychism)
Pan/Monopsychism]{.method .descriptor} [What: Reading and writing
sectors of memory from/to different computers]{.what .descriptor} [How:
Shell commands and fmem kernel module]{.how .descriptor} [Urgency:
Memory, even when it is volatile, is a trace of the processes happening
in your computer in the form of saved information, and is therefore more
similar to a file than to a process. Challenging the file/process
divide, sharing memory with others will allow a more intimate relation
with your and other\'s computers.]{.urgency .descriptor} [About:
Monopsychism is the philosophical/theological doctrine according to
which there exists but one intellect/soul, shared by all beings.]{.about
.descriptor} [TODO: RELATES TO
http://pad.constantvzw.org/p/observatory.guide.devmem]{.tmp} [Note: The
parallel allocation and observation of the same memory sector in two
different computers is in a sense the opposite process of machine
virtualization, where the localization of multiple virtual machines in
one physical comptuers can only happen by rigidly separating the memory
sectors dedicated to the different virtual machines.]{.note .descriptor}
[WARNING: THIS METHOD HAS NOT BEEN TESTED, IT CAN PROBABLY DAMAGE YOUR
RAM MEMORY AND/OR COMPUTER]{.warning .descriptor}
First start the fmem kernel module in both computers:
`sudo sh fmem/run.sh`{.bash}
Then load part of your computer memory into the other computer via dd
and ssh:
or it could go through the memory of different computers one after the other and take and leave something there `
[Temporality]{.grouping} []{#ndawnmy5 .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.fountain)
Fountain refreshment]{.method .descriptor} [What: Augmenting a piece of
standardised office equipment designed to dispense water to perform a
decorative function.]{.what .descriptor} [How: Rearranging space as
conditioning observations (WTC vs. Museum vs. University vs. Startup
Office vs. Shifting Walls that became Water Fountains)]{.how
.descriptor} [Who: Gaining access to standardised water dispensing
equipment turned out to be more difficult than expected as such
equipment is typically licensed / rented rather than purchased outright.
Acquiring a unit that could be modified required access to secondary
markets of second hand office equiment in order to purchase a disused
model.]{.who .descriptor} [Urgency: EU-OSHA (European Agency for Safety
and Health at Work) Directive 2003/10/EC noise places describes the
minimum health and safety requirements regarding the exposure of workers
to the risks arising from physical agents (noise). However no current
European guidelines exist on the potential benefitial uses of tactially
designed additive noise systems.]{.urgency .descriptor}
The Techno-Galactic Software Observatory -- Comfortable silence, one way
mirrors
A drinking fountain and screens of one-way mirrors as part of the work
session \"*The Techno-Galactic Software Observatory*\" organised by
Constant.
For the past 100 years the western ideal of a corporate landscape has
been has been moving like a pendulum, oscillating between grids of
cubicles and organic, open landscapes, in a near to perfect 25-year
rhythm. These days the changes in office organisation is supplemented by
sound design, in corporate settings mostly to create comfortable
silence. Increase the sound and the space becomes more intimate, the
person on the table next to you can not immediately hear what you are
saying. It seems that actual silence in public and corporate spaces has
not been sought after since the start of the 20th century. Actual
silence is not at the moment considered comfortable. One of the visible
symptoms of our desire to take the edge off the silence is to be
observed through the appearance of fountains in public space. The
fountains purpose being to give off neutral sound, like white noise
without the negative connotations. However as a sound engineer\'s
definition of noise is unwanted sound that all depends on ones personal
relation to the sound of dripping water.
This means that there needs to be a consistent inoffensiveness to create
comfortable silence.
In corporate architecture the arrival of glass buildings were originally
seen as a symbol of transparency, especially loved by governmental
buildings. Yet the reflectiveness of this shiny surface once combined
with strong light -- known as the treason of the glass -- was only
completely embraced at the invention of one-way-mirror foil. And it was
the corporate business-world that would come to be known for their
reflective glass skyscrapers. As the foil reacts to light, it appears
transparent to someone standing in the dark, while leaving the side with
the most light with an opaque surface. Using this foil as room dividers
in a room with a changing light, what is hidden or visible will vary
throughout the day. So will the need for comfortable silence. Disclaimer
:\
Similar to the last 100 years of western office organisation,\
this fountain only has two modes:\
on or off
If it is on it also offers two options\
cold water and hot water
This fountain has been tampered with and has not in any way been
approved by a proffesional fountain cleaner. I do urge you to consider
this before you take the decision to drink from the fountain.
Should you chose to drink from the fountain, then I urge you to write
your name on your cup, in the designated area, for a customised
experience of my care for you.
Nannyware is software meant to protect users while limiting their space
of activity. It is software that passive-aggressively suggests or
enforces some kind of discipline. In other words, create a form of
parental control extended to adults by means of user experience / user
interfaces.
Nannyware is a form of Content-control software: software designed to
restrict or control the content a reader is authorised to access,
especially when utilised to restrict material delivered over the
Internet via the Web, e-mail, or other means. Content-control software
determines what content will be available or be blocked.
[How]{.how .empty .descriptor}
> \[\...RestrictionsCITECLOSE23310 can be applied at various levels: a
> government can attempt to apply them nationwide (see Internet
> censorship), or they can, for example, be applied by an ISP to its
> clients, by an employer to its personnel, by a school to its students,
> by a library to its visitors, by a parent to a child\'s computer, or
> by an individual user to his or her own computer.^[5](#fcefedaf)^
[Who]{.who .empty .descriptor}
> Unlike filtering, accountability software simply reports on Internet
> usage. No blocking occurs. In setting it up, you decide who will
> receive the detailed report of the computer's usage. Web sites that
> are deemed inappropriate, based on the options you've chosen, will be
> red-flagged. Because monitoring software is of value only "after the
> fact", we do not recommend this as a solution for families with
> children. However, it can be an effective aid in personal
> accountability for adults. There are several available products out
> there.^[6](#bffbbeaf)^
[Urgency]{.urgency .empty .descriptor}
> As with all new lifestyle technologies that come along, in the
> beginning there is also some chaos until their impact can be assessed
> and rules put in place to bring order and respect to their
> implementation and use in society. When the automobile first came into
> being there was much confusion regarding who had the right of way, the
> horse or the car. There were no paved roads, speed limits, stop signs,
> or any other traffic rules. Many lives were lost and much property was
> destroyed as a result. Over time, government and society developed
> written and unwritten rules as to the proper use of the
> car.^[7](#bbfcbcfa)^
[WARNING]{.warning .empty .descriptor}
> Disadvantages of explicit proxy deployment include a user\'s ability
> to alter an individual client configuration and bypass the proxy. To
> counter this, you can configure the firewall to allow client traffic
> to proceed only through the proxy. Note that this type of firewall
> blocking may result in some applications not working
> properly.^[8](#ededebde)^
[Example]{.example .empty .descriptor}
> The main problem here is that the settings that are required are
> different from person to person. For example, I use workrave with a 25
> second micropause every two and a half minute, and a 10 minute
> restbreak every 20 minutes. I need these frequent breaks, because I\'m
> recovering from RSI. And as I recover, I change the settings to fewer
> breaks. If you have never had any problem at all (using the computer,
> that is), then you may want much fewer breaks, say 10 seconds
> micropause every 10 minutes, and a 5 minute restbreak every hour. It
> is very hard to give proper guidelines here. My best advice is to play
> around and see what works for you. Which settings \"feel right\".
> Basically, that\'s how Workrave\'s defaults evolve.^[9](#cfbbbfdd)^
[SHOW IMAGE HERE: !\[Content-control software\](
http://www.advicegoddess.com/archives/2008/05/03/nannyware.jpg )]{.tmp}
[SHOW IMAGE HERE: !\[A \"nudge\" from your music player
\](http://img.wonderhowto.com/img/10/25/63533437022064/0/disable-high-volume-warning-when-using-headphones-your-samsung-galaxy-s4.w654.jpg)]{.tmp}
[SHOW IMAGE HERE: !\[Emphasis on the body\]
(http://classicallytrained.net/wp-content/uploads/2014/10/take-a-break.jpg)]{.tmp}
[SHOW IMAGE HERE: !\[ \"Slack is trying to be my friend but it\'s more
like a slightly insensitive and slightly bossy acquaintance.\"
\@briecode \] (https://pbs.twimg.com/media/CuZLgV4XgAAYexX.jpg)]{.tmp}
[SHOW IMAGE HERE: !\[Slack is trying to be my friend but it\'s more like
a slightly insensitive and slightly bossy acquaintance.\]
(https://pbs.twimg.com/media/CuZLgV4XgAAYexX.jpg)]{.tmp} [SHOW IMAGE
HERE:
!\[\](https://images.duckduckgo.com/iu/?u=http%3A%2F%2Fi0.wp.com%2Fatherbeg.com%2Fwp-content%2Fuploads%2F2015%2F06%2FWorkrave-Restbreak-Shoulder.png&f=1)]{.tmp}
Facebook is working on an app to stop you from drunk-posting \"Yann
LeCun, who overseas the lab, told Wired magazine that the program would
be like someone asking you, \'Uh, this is being posted publicly. Are you
sure you want your boss and your mother to see this?\'\"
[SHOW IMAGE HERE: !\[This Terminal Dashboard Reminds You to Take a Break
When You\'re Lost Deep Inside the Command
Line\](https://i.kinja-img.com/gawker-media/image/upload/s\--\_of0PoM2\--/c\_fit,fl\_progressive,q\_80,w\_636/eegvqork0qizokwrlemz.png)]{.tmp}
[SHOW IMAGE HERE: !\[\](http://waterlog.gd/images/homescreen.png)]{.tmp}
[SHOW IMAGE HERE:
!\[\](https://pbs.twimg.com/media/C6oKTduWcAEruIE.jpg:large)]{.tmp}
[TODO: RELATES TO]{.tmp} []{#yzuwmdq4 .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.scrollresistance)
Useless scroll against productivity]{.method .descriptor} []{#m2vjndu3
.anchor} [[Method:](http://pad.constantvzw.org/p/observatory.guide.time)
Investigating how humans and machines negotiate the experience of
time]{.method .descriptor} [What]{.what .empty .descriptor} [SHOW IMAGE
HERE:
http://observatory.constantvzw.org/images/Screenshot\_from\_2017-06-10\_172547.png]{.tmp}
[How: python script]{.how .descriptor} [Example]{.example .empty
.descriptor}
` {.verbatim}
# ends of time
https://en.wikipedia.org/wiki/Year_2038_problem
Exact moment of the epoch:
03:14:07 UTC on 19 January 2038
## commands
local UNIX time of this machine
%XBASHCODE: date +%s
UNIX time + 1
%BASHCODE: echo $((`date +%s` +1 ))
## goodbye unix time
while :
do
sleep 1
figlet $((2147483647 - `date +%s`))
done
# Sundial Time Protocol Group tweaks
printf 'Current Time in Millennium Unix Time: '
printf $((2147483647 - `date +%s`))
echo
sleep 2
echo $((`cat ends-of-times/idletime` + 2)) > ends-of-times/idletime
idletime=`cat ends-of-times/idletime`
echo
figlet "Thank you for having donated 2 seconds to our ${idletime} seconds of collective SSH pause "
echo
echo
[TODO: RELATES TO]{.tmp} [Languaging]{.grouping} []{#nmi5mgjm .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.quine)
Quine]{.method .descriptor} [What: A program whose function consists of
displaying its own code. Also known as \"self-replicating
program\"]{.what .descriptor} [Why: Quines show the tension between
\"software as language\" and \"software as operation\".]{.why
.descriptor} [How: By running a quine you will get your code back. You
may do a step forward and wonder about functionality and aesthetics,
uselessness and performativity, data and code.]{.how .descriptor}
[Example: A quine (Python). When executed it outputs the same text as
the source:]{.example .descriptor}
` {.sourceCode .python}
s = 's = %r\nprint(s%%s)'
print(s%s) `
[Example: A oneline unibash/etherpad quine, created during relearn
2017:]{.example .descriptor}
The encounter with quines may deeply affect you. You may want to write
one and get lost in trying to make an ever shorter and more elegant one.
You may also take quines as point of departure or limit-ideas for
exploring software dualisms.
\"A quine is without why. It prints because it prints. It pays no
attention to itself, nor does it asks whether anyone sees it.\" \"Aquine
is aquine is aquine. \" Aquine is not a quine This is not aquine
[Remember: Although seemingly absolutely useless, quines can be used as
exploits.]{.remember .descriptor}
Exploring boundaries/tensions
databases treat their content as data (database punctualization) some
exploits manage to include operations in a database
[TODO: RELATES TO
http://pad.constantvzw.org/p/observatory.guide.monopsychism]{.tmp}
[]{#zwu0ogu0 .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.glossary)
Glossaries as an exercise]{.method .descriptor} [What: Use the technique
of psychanalytic listening to compile (gather, collect, bring together)
a list of key words for understanding software.]{.what .descriptor}
[How: Create a shared document that participants can add words to as
their importance emerges.To do pyschoanalytic listening, let your
attention float freely, hovering evenly, over a conversation or a text
until something catches its ear. Write down what your ear/eye catches.
When working in a collective context invite others to participate in
this project and describe the practice to them. Each individual may move
in and out of this mode of listening according to their interest and
desire and may add as many words to the list as they want. Use this list
to create an index of software observation.]{.how .descriptor} [When:
This is best done in a bounded context. In the case of the
Techno-Galactic Observatory, our bounded contexts includes the six day
work session and the pages and process of this publication.]{.when
.descriptor} [Who: The so-inclined within the group]{.who .descriptor}
[Urgency: Creating and troubling categories]{.urgency .descriptor}
[Note: Do not remove someone else\'s word from the glossary during the
accumulation phase. If an editing and cutting phase is desired this
should be done after the collection through collective consensus.]{.note
.descriptor} [WARNING: This method is not exclusive to and was not
developed for software observation. It may lead to awareness of
unconscious processes and to shifts in structures of feeling and
relation.]{.warning .descriptor} [Example]{.example .empty .descriptor}
` {.verbatim}
Agile
Code
Colonial
Command Line
Communication
Connectivity
Emotional
Galaxies
Green
Guide
Kernel
Imperial
Issues
Machine
Mantra
Memory
Museum
Observation
ProductionPower
Programmers
Progress
Relational
Red
Scripting
Scrum
Software
Survival
Technology
Test
Warning
WhiteBoard
Yoga `
[TODO: RELATES TO]{.tmp} []{#mja0m2i5 .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.validation)
Adding qualifiers]{.method .descriptor} [Remember: \"\[V\]alues are
properties of things and states of affairs that we care about and strive
to attain\...vlaues expressed in technical systems are a function of
their uses as well as their features and designs.\" Values at Play in
Digital Games, Mary Flanagan and Helen Nissenbaum]{.remember
.descriptor} [What: Bringing a moral, ethical, or otherwise
evaluative/adjectival/validating lens.]{.what .descriptor} [How:
Adjectives create subcategories. They narrow the focus by naming more
specifically the imagined object at hand and by implicitly excluding all
objects that do not meet the criteria of the qualifier. The more
adjectives that are added, the easier it becomes to answer the question
what is software. Or so it seems. Consider what happens if you add the
words good, bad, bourgeois, queer, stable, or expensive to software. Now
make a list of adjectives and try it for yourself. Level two of this
exercise consists of observing a software application and deducing from
this the values of the individuals, companies, and societies that
produced it.]{.how .descriptor} [Note: A qualifier may narrow down
definitions to undesirable degrees.]{.note .descriptor} [WARNING: This
exercise may be more effective at identifying normative and ideological
assumptions at play in the making, distributing, using, and maintaining
of software than at producing a concise definition.]{.warning
.descriptor} [Example: \"This morning, Jan had difficulties to answer
the question \"what is software\", but he said that he could answer the
question \"what is good software\". What is good software?]{.example
.descriptor} [TODO: RELATES TO]{.tmp} []{#mmmwmje2 .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.softwarethrough)
Searching \"software\" through software]{.method .descriptor} [What: A
quick way to sense the ambiguity of the term \'software\', is to go
through the manual files on your hard drive and observe in which cases
is the term used.]{.what .descriptor} [How: command-line oneliner]{.how
.descriptor} [Why: Software is a polymorphic term that take different
meanings and comes with different assumptions for the different agents
involved in its production, usage and all other forms of encounter and
subjection. From the situated point of view of the software present on
your machine, when and why does software call itself as such?]{.why
.descriptor} [Example]{.example .empty .descriptor}
so software exists only outside your computer? only in general terms?
checking for the word software in all man pages:
grep -nr software /usr/local/man
!!!!
software appears only in terms of license:
This program is free software
This software is copyright (c)
we don\'t run software. we still run programs.\
nevertheless software is everywhere
[TODO: RELATES TO
http://pad.constantvzw.org/p/observatory.guide.samequestion]{.tmp}
[]{#ndhkmwey .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.everyonescp)
Persist in calling everyone a Software Curious Person]{.method
.descriptor} [What: Persistance in naming is a method for changing a
person\'s relationship to software by (sometimes forcibly) call everyone
a Software Curious Person.]{.what .descriptor} [How: Insisting on
curiosity as a relation, rather than for example \'fear\' or
\'admiration\' might help cut down the barriers between different types
of expertise and allows multiple stakeholders feel entitled to ask
questions, to engage, to investigate and to observe.]{.how .descriptor}
[Urgency: Software is too important to not be curious about.
Observations could benefit from recognising different forms of
knowledge. It seems important to engage with software through multiple
interests, not only by means of technical expertise.]{.urgency
.descriptor} [Example: This method was used to address each of the
visitors at the Techno-Galactic Walk-in Clinic.]{.example .descriptor}
[TODO: RELATES TO]{.tmp} [Healing]{.grouping} []{#mmu1mgy0 .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.relational)
Setup a Relational software observatory consultancy (RSOC)]{.method
.descriptor} [Remember]{.remember .empty .descriptor}
- Collectivise research around hacking to save time.
- Self-articulate software needs as your own Operating (system)
perspective.
- Change the lens by looking to software through a time perspective.
[What: By paying a visit to our ethnomethodology interview practice
you'll learn to observe software from different angles / perspectives.
Our practionners passion is to make the \"what is the relation to
software\" discussion into a service.]{.what .descriptor} [How: Reading
the signs. Considering the everchanging nature of software development
and use and its vast impact on globalized societies, it is necessary to
recognize some of the issues of how software is (often) either
passively-perceived or actively-observed, without an articulation of the
relations. We offer a method to read the signs of the relational aspect
of software observance. It\'s a crucial aspect of our guide. It will
give you another view on software that will shape your ability to
survive any kind of software disaster.]{.how .descriptor} [SHOW IMAGE
HERE: !\[Reading the signs. From: John \"Lofty\" Wiseman, SAS Survival
Handbook: The Ultimate Guide to Surviving Anywhere\](
http://gallery.constantvzw.org/index.php/Techno-Galactic-Software-Observatory/IMAG1319
)]{.tmp} [WARNING]{.warning .empty .descriptor} [SHOW IMAGE HERE: have a
advertising blob for the RSOC with a smiling doctor welcoming
image]{.tmp} [Example]{.example .empty .descriptor}
What follows is an example of a possible diagnostic questionnaire.
Sample Questionnaire
--------------------
**What to expect** You will obtain a cartography of software users
profiles. It will help you to shape your own relation to software. You
will be able to construct your own taxonomy and classifcation of
software users that is needed in order to find a means of rescue in case
of a software catastrophy.
- SKILLS\
- What kind of user would you say that you are?
- What is your most frequently used type of software?
- How often do you install/experiment/learn new software?
- History
- What is your first recollection of software use?
- How often do / when did you last purchase software or pay for a
software service?
- Ethics
- What is the software feature you care about the most?
- Do you use any free software?
- if yes than
- do you remember your first attempt at using this software
service? Do you still use it? If not why?
- Do you pay for media distribution/streaming services?
- Do you remember your first attempt at using free software and how
did that make you feel?
- Have you used any of these software services : facebook, dating app
(grindr, tinder, etc.), twitter, instagram or equivalent.
- Can you talk about your favorite apps or webtools that you use
regularly?
- What is most popular software your friends use?
- SKILL
- Would you say that you are a specilised user?
- Have you ever used the command line?
- Do you know about scripting?
- Have you ever edited an HTML page? A CSS file? A PHP file? A
configuration file?
- Can you talk about your most technical encounter with your computer
/ telephone?
- ECONOMY\
- How do you pay for your software use?
- Please elaborate (for example, do you buy the software? /
contribute in kind / deliver services or support)
- What is the last software that you paid for using?
- What online services are you currently paying for?
- Is someone paying for your use of service?
- Personal
- What stories do you have concerning contracts and administration in
relation to your software, Internet or computer?
- How does software help you shape your relations with other people?
- From which countries does your softwares come from / reside? How do
you feel about that?
- Have you ever read a terms of software service, what about one that
is not targeting the American market?
Possible/anticipated user profiles
----------------------------------
### \...meAsHardwareOwnerSoftwareUSER:
\"I did not own a computer personally until very very late as I did not
enjoy gaming as a kid or had interest in spending much time behind PC
beyond work (and work computer). My first was hence I think in 2005 and
it was a SGI workstation that was the computer of the year 2000 (cost
10.000USD) and I got it for around 300USD. Proprietary drivers for
unified graphics+RAM were never released, so it remained a software
dead-end in gorgeous blue curved chassis
http://www.sgidepot.co.uk/sgidepot/pics/vwdocs.jpg\"
### \...meAsSoftwareCONSUMER:
\"I payed/purchased software only twice in my life (totalling less then
25eur), as I could access most commercial software as widely pirated in
Balkans and later had more passion for FLOSS anyway, this made me relate
to software as material to exchange and work it, rather than commodity
goods I could or not afford.\"
### \...meAsSoftwareINVESTOR:
\"I did it as both of those apps were niche products in early beta (one
was Jeeper Elvis, real-time-non-linear-video-editor for BeOS) that
failed to reach market, but I think I would likely do it again and only
in that mode (supporting the bleeding edge and off-stream work), but
maybe with more than 25eur.\"
### \...meAsSoftwareUserOfOS:
\"I would spend most of 80s ignoring computers, 90ties figuring out
software from high-end to low-end, starting with OSF/DecAlpha and SunOS,
than IRIX and MacOS, finally Win 95/98 SE, that permanently pushed me
into niches (of montly LINUX distro install fests, or even QNX/Solaris
experiments and finally BeOS use).\"
### \...meAsSoftwareWEBSURFER:
\"I got used to websurfing in more than 15 windows on UNIX systems and
never got used to less than that ever since, furthermore with addition
of more browser options this number only multiplied (always wondered if
my first system was Windows 3.11 - would I be a more focused person and
how would that form my relations to browser windows\>tabs).\"
### \...meAsSoftwareUserOfPropertarySoftware:
\"I signed one NDA contract in person on the paper and with ink on a
rainy day while stopping of at trainstaion in north Germany for the
software that was later to be pulled out of market due to problematic
licencing agreement (intuitivly I knew it was wrong) - it had too much
unprofessional pixeleted edges in its graphics.
### \...meAsSoftwareUserOfDatingWebsites:
\"I got one feature request implemented by a prominent dating website
(to search profiles by language they speak), however I was never
publicly acknowledged (though I tried to make use of it few times), that
made our relations feel a bit exploitative and underappreciated. \"
### \...meAsSoftwareUserTryingToGoPRO:
\"my only two attempts to get into the software company failed as they
insisted on full time commitments. Later I found out ones were
intimidated in interview and other gave it to a person that negotiated
to work part time with friend! My relation to professionalism is likely
equally complex and pervert as one to the software.\"
Case study : W. W.
------------------
\...ww.AsExperiencedAdventerousUSER - experiments with software every
two days as she uses FLOSS and Gnu/Linux, cares the most for maliabity
of the software - as a result she has big expectations of flexibility
even in software category which is quite conventional and stability
focused like file-hosting.
\...ww.AsAnInevstorInSoftware - paid compiled version of FLOSS audio
software 5 years ago as she is supportive of economy and work around
production, maintainance and support, but she also used closed
hardware/software where she had to agree on licences she finds unfair,
but then she was hacking it in order to use it as an expert - when she
had time.
\...ww.AsCommunicationSoftwareUSER - she is not using commercial social
networks, so she is very concious of information transfers and time
relations, but has no strong media/format/design focus.
Q: What is your first recollection of software use?\
A: ms dos in 1990 at school \_ i was 15 or 16. oh no 12. Basic in 1986.
Q: What are the emotions related to this use?\
A: fun. i\'m good at this. empowering
Q: How often do / when did you last purchase software or pay for a
software service?\
A: I paid for ardour five years ago. I paid the developper directly. For
the compiled version. I paid for the service. I pay for my website and
email service at domaine public.
Q: What kind of user would you say you are?\
A: An experienced user drawing out the line. I don\'t behave.
Q: Is there a link between this and your issue?\
A: Even if it\'s been F/LOSS there is a lot of decision power in my
package.
Q: What is your most frequently used type of software?\
A: Web browser. email. firefox & thunderbird
Q: How often do you install/experiment/learn new software?\
A: Every two days. I reinstall all the time. my old lts system died.
stop being supported last april. It was linux mint something.
Q: Do you know about scripting?\
A: I do automating scripts for any operation i have to doi several times
like format conversion.
Q: Can you talk about your most technical encounter with your computer /
telephone?\
A: I\'ve tried to root it. but i didn\'t succeed.
Q: How much time do you wish to spend on such activities like hacking,
rooting your device?\
A: hours. you should take your time
Q: Did you ever sign licence agreement you were not agree with? How does
that affect you?\
A: This is the first thing your when you have a phone. it\'s obey or
die.
Q: What is the software feature you care for the most?\
A: malleability. different ways to approach a problem, a challenge, an
issue.
Q: Do you use any free software?\
A: yes. there maybe are some proprietary drivers.
Q: Do you remember your first attempt at using free software and how did
that make you feel?\
A: Yes i installed my dual boot in \... 10 years ago. scared and
powerful.
Q: Do you use one of this software service: facebook, dating app (grindr
of sort), twitter, instagram or equivalent?\
A: Google, gmail that\'s it
Q: Can you talk about your favorite apps or webtools that you use
regularly?\
A: Music player. vanilla music and f-droid. browser. I pay attention to
clearing my history, no cookies. I also have iceweasel. Https by
default. Even though i have nothing to hide.
Q: What stories around contracts and administration in relation to your
software internet or computer?\
A: Nothing comes to my mind. i\'m not allowed to do, to install on
phone. When it\'s an old phone, there is nothing left that is working
you have to do it.
Q: How does software help you shape your relations with other people?\
A: It\'s a hard question. if it\'s communication software of course
it\'s it\'s nature to be related to other people.there is an expectency
of immediate reply, of information transfer\...It\'s troubling your
relation with people in certain situations.
Q: From which countries does your softwares live / is coming from? How
do you feel about that?\
A: i think i chose the netherlands as a miror. you are hoping to reflect
well in this miror.
Q: Have you ever read a terms of software service; one that is not
targeting the American market?\
A: i have read them. no.
> Agile software development describes a set of values and principles
> for software development under which requirements and solutions evolve
> through the collaborative effort of self-organizing cross-functional
> teams. It advocates adaptive planning, evolutionary development, early
> delivery, and continuous improvement, and it encourages rapid and
> flexible response to change. These principles support the definition
> and continuing evolution of many software development
> methods.^[10](#dbabcece)^
[What: You will be observing yourself]{.what .descriptor} [How]{.how
.empty .descriptor}
> Scrum is a framework for managing software development. It is designed
> for teams of three to nine developers who break their work into
> actions that can be completed within fixed duration cycles (called
> \"sprints\"), track progress and re-plan in daily 15-minute stand-up
> meetings, and collaborate to deliver workable software every sprint.
> Approaches to coordinating the work of multiple scrum teams in larger
> organizations include Large-Scale Scrum, Scaled Agile Framework (SAFe)
> and Scrum of Scrums, among others.^[11](#eefcbaac)^
[When: Anywhere where it\'s possible to lie on the floor]{.when
.descriptor} [Who]{.who .empty .descriptor}
> Self-organization and motivation are important, as are interactions
> like co-location and pair programming. It is better to have a good
> team of developers who communicate and collaborate well, rather than a
> team of experts each operating in isolation. Communication is a
> fundamental concept.^[12](#fbaeffab)^
[Urgency: Using Agile software development methods to develop a new path
into your professional and personal life towards creativity, focus and
health.]{.urgency .descriptor} [WARNING]{.warning .empty .descriptor}
> The agile movement is in some ways a bit like a teenager: very
> self-conscious, checking constantly its appearance in a mirror,
> accepting few criticisms, only interested in being with its peers,
> rejecting en bloc all wisdom from the past, just because it is from
> the past, adopting fads and new jargon, at times cocky and arrogant.
> But I have no doubts that it will mature further, become more open to
> the outside world, more reflective, and also therefore more
> effective.^[13](#edabeeaf)^
Hello and welcome to the presentation of the agile yoga methodology. I
am Allegra, and today I\'m going to be your personal guide to YOGA, an
acronym for why organize? Go agile! I\'ll be part of your team today and
we\'ll do a few exercises together as an introduction to a new path into
your professional and personal life towards creativity, focus and
health.
A few months ago, I was stressed, overwhelmed with my work, feeling
alone, inadequate, but since I started practicing agile yoga, I feel
more productive. I have many clients as an agile yoga coach, and I\'ve
seen new creative business opportunities coming to me as a software
developer.
For this first experience with the agile yoga method and before we do
physical exercises together, I would like to invite you to close your
eyes. Make yourself comfortable, lying on the floor, or sitting with
your back on the wall. Close your eyes, relax. Get comfortable. Feel the
weight of your body on the floor or on the wall. Relax.
Leave your troubles at the door. Right now, you are not procrastinating,
you are having a meeting at the \,
a professional building dedicated to business, you are meeting yourself,
you are your own business partner, you are one. You are building your
future.
You are in a room standing with your team, a group of lean programmers.
You are watching a white board together. You are starting your day, a
very productive day as you are preparing to run a sprint together. Now
you turn towards each other, making a scrum with your team, you breathe
together, slowly, inhaling and exhaling together, slowly, feeling the
air in and out of your body. Now you all turn towards the sun to prepare
to do your ASSanas, the agile Sun Salutations or ASS with the team
dedicated ASS Master. She\'s guiding you. You start with Namaskar, the
Salute. your palms joined together, in prayer pose. you all reflect on
the first principle of the agile manifesto. your highest priority is to
satisfy the customer through early and continuous delivery of valuable
software.
Next pose, is Ardha Chandrasana or (Half Moon Pose). With a deep
inhalation, you raise both arms above your head and tilt slightly
backward arching your back. you welcome changing requirements, even late
in development. Agile processes harness change for the customer\'s
competitive advantage. then you all do Padangusthasana (Hand to Foot
Pose). With a deep exhalation, you bend forward and touch the mat, both
palms in line with your feet, forehead touching your knees. you deliver
working software frequently.
Surya Darshan (Sun Sight Pose). With a deep inhalation, you take your
right leg away from your body, in a big backward step. Both your hands
are firmly planted on your mat, your left foot between your hands. you
work daily throughout the project, business people and developers
together. now, you\'re flowing into Purvottanasana (Inclined Plane) with
a deep inhalation by taking your right leg away from your body, in a big
backward step. Both your hands are firmly planted on your mat, your left
foot between your hands. you build projects around motivated
individuals. you give them the environment and support they need, and
you trust them to get the job done.
You\'re in Adho Mukha Svanasana (Downward Facing Dog Pose). With a deep
exhalation, you shove your hips and butt up towards the ceiling, forming
an upward arch. Your arms are straight and aligned with your head. The
most efficient and effective method of conveying information to and
within a development team is face-to-face conversation.
Then, Sashtang Dandawat (Forehead, Chest, Knee to Floor Pose). With a
deep exhalation, you lower your body down till your forehead, chest,
knees, hands and feet are touching the mat, your butt tilted up. Working
software is the primary measure of progress.
Next is Bhujangasana (Cobra Pose). With a deep inhalation, you slowly
snake forward till your head is up, your back arched concave, as much as
possible. Agile processes promote sustainable development. You are all
maintaining a constant pace indefinitely, sponsors, developers, and
users together.
Now back into Adho Mukha Svanasana (Downward Facing Dog Pose).
Continuous attention to technical excellence and good design enhances
agility.
And then again to Surya Darshan (Sun Sight Pose). Simplicity\--the art
of maximizing the amount of work not done\--is essential. Then to
Padangusthasana (Hand to Foot Pose). The best architectures,
requirements, and designs emerge from self-organizing teams.
You all do again Ardha Chandrasana (Half Moon Pose). At regular
intervals, you as the team reflect on how to become more effective, then
tune and adjust your behavior accordingly. you end our ASSanas session
with a salute to honor your agile yoga practices. you have just had a
productive scrum meeting. now i invite you to open your eyes, move your
body around a bit, from the feet up to the head and back again.
Stand up on your feet and let\'s do a scrum together if you\'re ok being
touched on the arms by someone else. if not, you can do it on your own.
so put your hands on the shoulder of the SCP around you. now we\'re
joined together, let\'s look at the screen together as we inhale and
exhale. syncing our body together to the rythms of our own internal
software, modulating our oxygen level intake requirements to the oxygen
availability of our service facilities.
Now, let\'s do together a couple of exercise to protect and strengthen
our wrists. as programmers, as internauts, as entrepreneurs, they are a
very crucial parts of the body to protect. in order to be able to type,
to swipe, to shake hands vigourously, we need them in good health. So
bring to hands towards each other in a prayer pose, around a book, a
brick. You can do it without but I\'m using my extreme programming book
- embrace change - for that. So press the palms together firmly, press
the pad of your fingers together. do that while breathing in and out
twice.
Now let\'s expand our arms towards us, in the air, face and fingers
facing down. like we\'re typing. make your shoulders round. let\'s
breath while visualizing in our heads the first agile mantra :
Individuals and interactions over processes and tools.
Now let\'s bring back the arms next to the body and raise them again.
And let\'s move our hands towards the ceiling this time. Strenghtening
our back. In our head, the second mantra. Working software over
comprehensive documentation. now let\'s bring back the hands in the
standing position. Then again the first movement while visualizing the
third mantra : Customer collaboration over contract negotiation and then
the second movement thinking about the fourth and last mantra :
Responding to change over following a plan and of course we continue
breathing. Now to finish this session, let\'s do a sprint together in
the corridor !
[SHOW IMAGE HERE: !\[\](
http://observatory.constantvzw.org/guide/agileyoga/8-Poses-Yoga-Your-Desk.contours.png
)]{.tmp} [SHOW IMAGE HERE: !\[\](
http://observatory.constantvzw.org/guide/agileyoga/gayolab-office-chair-for-yoga.contours.png
)]{.tmp} [TODO: RELATES TO]{.tmp} []{#mdu0mmji .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.blobservation)
Hand reading]{.method .descriptor} [How: Visit the Future Blobservation
Booth to have your fortunes read and derive life insight from the wisdom
of software.]{.how .descriptor} [What: Put your hand in the reading
booth and get your line read.]{.what .descriptor} [Why: The hand which
holds your mouse everyday hides many secrets.]{.why .descriptor}
[Example]{.example .empty .descriptor}
` {.verbatim .wrap}
* sample reading timeline:
* 15:00 a test user, all tests clear and systems are online a user who said goodbye to us another user a user who thought it'd be silly to say thank you to the machine but thank you very much another kind user who said thank you yet another kind user another user, no feeback a nice user who found the reading process relieving yet another kind user a scared user! took the hand out but ended up trusting the system. "so cool thanks guys" another user a young user! this is a funny computer
* 15:35 another nice user
* 15:40 another nice user
* 15:47 happy user (laughing)
* 15:51 user complaining about her fortune, saying it's not true. Found the reading process creepy but eased up quickly
* 15:59 another nice user: http://etherbox.local:9001/p/SCP.sedyst.md
* 16:06 a polite user
* 16:08 a friendly playful user (stephanie)
* 16:12 a very giggly user (wendy)
* 16:14 a playful user - found the reading process erotic - DEFRAGMENTING? NO! Thanks Blobservation http://etherbox.local:9001/p/SCP.loup.md
* 16:19 a curious user
* 16:27 a friendly user but oh no, we had a glitch and computer crashed. But we still delivered the fortune. We got a thank you anyway
* 16:40 a nice user, the printer jammed but it was sorted out quickly *16:42 another nice user
* 16:50 nice user (joak)
* 16:52 yet another nice user (jogi)
* 16:55 happy user! (peter w)
* 16:57 more happy user (pierre h)
* 16:58 another happy user
* 17:00 super happy user (peggy)
* 17:02 more happy user `
[Example]{.example .empty .descriptor}
> Software time is not the same as human time. Computers will run for AS
> LONG AS THEY WILL BE ABLE TO, provided sufficient power is available.
> You, as a human, don\'t have the luxury of being always connected to
> the power grid and this have to rely on your INTERNAL BATTERY. Be
> aware of your power cycles and set yourself to POWER-SAVING MODE
> whenever possible.
[SHOW IMAGE HERE:
http://gallery.constantvzw.org/var/resizes/Techno-Galactic-Software-Observatory/IMAG1407.jpg?m=1497344230]{.tmp}
[TODO: RELATES TO]{.tmp} []{#yznjodq3 .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.dirty) Bug
reporting for sharing observations]{.method .descriptor} [What: Etherpad
had stopped working but it was unclear why. Where does etherpad
\'live\'?]{.what .descriptor} [How: Started by looking around the pi\'s
filesystem by reading /var/log/syslog in /opt/etherpad and in a
subdirectory named var/ there was dirty.db, and dirty it was.]{.how
.descriptor} [When: Monday morning]{.when .descriptor} [Urgency:
Software (etherpad) not working and the Walk-in Clinic was about to
start.]{.urgency .descriptor} [Note:
http://pad.constantvzw.org/p/observatory.inventory.jogi]{.note
.descriptor}
from jogi\@mur.at to \[Observatory\] When dirty.db get\'s dirty
Dear all,
as promised yesterday, here my little report regarding the broken
etherpad.
\ \#\#\# When dirty.db get\'s dirty
When I got to WTC on Monday morning the etherpad on etherbox.local was
disfunct. Later someone said that in fact etherpad had stopped working
the evening before, but it was unclear why. So I started looking around
the pi\'s filesystem to find out what was wrong. Took me a while to find
the relevant lines in /var/log/syslog but it became clear that there was
a problem with the database. Which database? Where does etherpad
\'live\'? I found it in /opt/etherpad and in a subdirectory named var/
there it was: dirty.db, and dirty it was.
A first look at the file revealed no apparent problem. The last lines
looked like this:
What I did not see at the time was that there were some (AFAIR something
around 150) binary zeroes at the end of the file. I used tail for the
first look and that tool silently ignored the zeroes at the end of the
file. It was Martino who suggested using different tools (xxd in that
case) and that showed the cause of the problem. The file looked
something like this:
which means: write the first 793080162 blocks of size 1 byte to a new
file. After half an hour or so I checked on the size of the new file and
saw that some 10% of the copying had been done. No way this would get
done in time for the walk-in-clinic. Back to the drawing board.
Using a text editor was no real option btw since even vim has a hard
time with binary zeroes and the file was really big. But there was
hexedit! Martino installed it and copied dirty.db onto his computer.
After some getting used to the various commands to navigate in hexedit
the unwanted zeroes were gone in an instant. The end of the file looked
like this now:
Martino asked about the trailing \'.\' character and I checked a
different copy of the file. No \'.\' there, so that had to go too. My
biggest mistake in a long time! The \'.\' we were seeing in Martino\'s
copy of the file was in fact a \'\' (0a)! We did not realize that,
copied the file back to etherbox.local and waited for etherpad to resume
it\'s work. But no luck there, for obvious reasons.
We ended up making backups of dirty.db in various stages of deformation
and Martino started a brandnew pad so we could use pads for the walk-
in-clinic. The processing tool chain has been disabled btw. We did not
want to mess up any of the already generated .pdf, .html and .md files.
We still don\'t know why exactly etherpad stopped working sometime
Sunday evening or how the zeroes got into the file dirty.db. Anita
thought that she caused the error when she adjusted time on
etherbox.local, but the logfile does not reflect that. The last clean
entry in /var/log/syslog regarding nodejs/etherpad is recorded with a
timestamp of something along the line of \'Jun 10 10:17\'. Some minutes
later, around \'Jun 10 10:27\' the first error appears. These timestamps
reflect the etherbox\'s understanding of time btw, not \'real time\'.
It might be that the file just got too big for etherpad to handle it.
The size of the repaired dirty.db file was already 757MB. That could btw
explain why etherpad was working somewhat slugishly after some days.
There is still a chance that the time adjustment had an unwanted side
effect, but so far there is no obvious reason for what had happened.
\ \-- J.Hofmüller
> The analysis of common sense, as opposed to the exercise of it, must
> then begin by redrawing this erased distinction between the mere
> matter-of-fact apprehension of reality\--or whatever it is you want to
> call what we apprehend merely and matter-of-factly\--and
> down-to-earth, colloquial wisdom, judgements, and assessments of it.
[What: Observe and catalog the common gestures, common comportments, and
common sense(s) surrounding software.]{.what .descriptor} [How: This can
be done through observation of yourself or others. Separate the
apprehended and matter of fact from the meanings, actions, reactions,
judgements, and assessments that the apprehension occasions. Step 1:
Begin by assembling a list of questions such as: When you see a software
application icon what are you most likely to do? When a software
application you are using presents you with a user agreement what are
you most likely to do? When a software applciation does something that
frustrates you what are you most likely to do? When a software
application you are using crashes what are you most likely to do? Step
2: Write down your responses and the responses of any subjects you are
observing. Step 3: For each question, think up three other possible
responses. Write these down. Step 4: (this step is only for the very
curious) Try the other possible responses out the next time you
encounter each of the given scenarios.]{.how .descriptor} [Note: The
common senses and comportments of software are of course informed and
conditioned by those of hardware and so perhaps this is more accurately
a method for articulating comportments of computing.]{.note .descriptor}
[WARNING: Software wears on both individual and collective bodies and
selves. Software may harm your physical and emotional health and that of
your society both by design and by accident.]{.warning .descriptor}
[TODO: RELATES TO Agile Sun Salutation, Natasha Schull\'s Addicted by
Design]{.tmp} [Flow-regulation, logistics, seamlessness]{.grouping}
[]{#mwrhm2y4 .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.continuousintegration)
Continuous integration]{.method .descriptor} [What: Continuous
integration is a sophisticated form of responsibility management: it is
the fascia of services. Continous integration picks up after all other
services and identifies what needs to happen so that they can work in
concert. Continuous integration is a way of observing the evolution of
(micro)services through cybernetic (micro)management.]{.what
.descriptor} [How: Continuous integration keeps track of changes to all
services and allows everyone to observe if they still can work together
after all the moving parts are fitted together.]{.how .descriptor}
[When: Continuous integration comes to prominence in a world of
distributed systems where there are many parts being organized
simultaneously. Continuous integration is a form of observation that
helps (micro)services maintain a false sense of independence and
decentralization while constantly subjecting them to centralized
feedback.]{.when .descriptor} [Who: Continuous integration assumes that
all services will submit themselves to the feedback loops of continuous
integration. This could be a democratic process or not.]{.who
.descriptor} [Urgency: Continuous integration reconfigures divisions of
labor in the shadows of automation. How can we surface and question its
doings and undoings?]{.urgency .descriptor} [WARNING: When each service
does one thing well, the service makers tend to assume everybody else is
doing the things they do not want to do.]{.warning .descriptor}
At TGSO continuous integration was introduced as a service that responds
to integration hell when putting together a number of TGSO services for
a walk-in software clinic. Due to demand, the continuous integration
service was extended to do \"service discovery\" and \"load balancing\"
once the walk-in clinic was in operation.
Continuous integration worked by visiting the different services of the
walk-in clinic to check for updates, test the functionality and think
through implications of integration with other services. If the pieces
didn\'t fit, continuous integration delivered error messages and
solution options.
When we noticed that software curious persons visiting the walk-in
clinic may have troubles finding the different services, and that some
services may be overloaded with software curious persons, continuous
integration was extended. We automated service registration using
colored tape and provided a lookup registry for software curious
persons.
Load balancing meant that software curious persons were forwarded to
services that had capacity. If all other services were full, the load
balancer defaulted to sending the software curious person to the [Agile
Sun
Salutation](http://pad.constantvzw.org/p/observatory.guide.agile.yoga)
service.
[WARNING: At TGSO the bundling of different functionalities into the
continuous integration service broke the \"do one thing well\"
principle, but saved the day (we register this as technical debt for the
next iteration of the walk-in clinic).]{.warning .descriptor} [Remember:
Continous integration may be the string that holds your current software
galaxy together.]{.remember .descriptor}
\"More technically, I am interested in how things bounce around in
computer systems. I am not sure if these two things are relted, but I
hope continuous integration will help me.\"
[]{#zdixmgrm .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.pipeline) make
make do]{.method .descriptor} [What: Makefile as a method for
quick/collective assemblages + observing amalgamates/pipelines]{.what
.descriptor} [Note: Note:
http://observatory.constantvzw.org/etherdump/makefile.raw.html]{.note
.descriptor}
etherpad-\>md-\>pdf-\>anything pipeline. makefile as a method for
quick/collective assemblages + observing amalgamates/pipelines CHRISTOPH
[]{#zweymtni .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.ssogy)
Flowcharts (Flow of the chart -- chart of the flow on demand!)]{.method
.descriptor} [Example]{.example .empty .descriptor} [SHOW IMAGE HERE:
!\[\]( http://observatory.constantvzw.org/images/symbols/ibm-ruler.jpg
)]{.tmp} [SHOW IMAGE HERE: !\[\](
http://observatory.constantvzw.org/images/symbols/burroughs-ruler.jpg
)]{.tmp} [SHOW IMAGE HERE: !\[\](
http://observatory.constantvzw.org/images/symbols/rectangle.png )]{.tmp}
[SHOW IMAGE HERE: !\[\](
http://observatory.constantvzw.org/images/symbols/curly\_rec.png
)]{.tmp} [SHOW IMAGE HERE: !\[\](
http://observatory.constantvzw.org/images/symbols/curly\_rec-2.png
)]{.tmp} [SHOW IMAGE HERE: !\[\](
http://observatory.constantvzw.org/images/symbols/flag.png )]{.tmp}
[SHOW IMAGE HERE: !\[\](
http://observatory.constantvzw.org/images/symbols/trapec.png )]{.tmp}
[SHOW IMAGE HERE: !\[Claude Shannon Information Diagram Blanked: Silvio
Lorusso\](
http://silviolorusso.com/wp-content/uploads/2012/02/shannon\_comm\_channel.gif
)]{.tmp} [TODO: RELATES TO]{.tmp}
[Beingontheside/inthemiddle/behind]{.grouping} []{#ywfin2e4 .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.somethinginthemiddlemaybe)
Something in the Middle Maybe (SitMM)]{.method .descriptor} [What: The
network traffic gets observed. There are different sniffing software out
there which differ in granularity and how far the user can taylor the
different functionality. SitMM builds on one of these tools called
[scapy](http://www.secdev.org/projects/scapy/).]{.what .descriptor}
[How: SitMM takes a closer look at the network traffic coming from/going
to a software curious person\'s device. The software curious person
using SitMM may ask to filter the traffic based on application or device
of interest.]{.how .descriptor} [Who]{.who .empty .descriptor}
The software curious person gets to observe their own traffic. Ideally,
observing ones own network traffic should be available to anyone, but
using such software can be deemed illegal under different jurisdictions.
For example, in the US wiretap law limit packet-sniffing to parties
owning the network that is being sniffed or the availability of consent
from one of the communicating parties. Section 18 U.S. Code § 2511 (2)
(a) (i) says:
> It shall not be unlawful \... to intercept \... while engaged in any
> activity which is a necessary incident to the rendition of his service
> or to the protection of the rights or property of the provider of that
> service
See here for a
[paper](http://spot.colorado.edu/%7Esicker/publications/issues.pdf) on
the topic. Google went on a big legal spree to defend their right to
capture unencrypted wireless traffic with google street view cars. The
courts were concerned about wiretapping and infringements on the privacy
of users, and not with the leveraging of private and public WiFi
infrastructure for the gain of a for profit company. The case raises
hard questions about the state, ownership claims and material reality of
WiFi signals. So, while WiFi sniffing is common and the tools like SitMM
are widely available, it is not always possible for software curious
persons to use them legally or to neatly filter out \"their traffic\"
from that of \"others\".
[When: SitMM can be used any time a software curious person feels the
weight of the (invisible) networks.]{.when .descriptor} [Why: SitMM is
intended to be a tool that gives artists, designers and educators an
easy to use custom WiFi router to work with networks and explore the
aspects of our daily communications that are exposed when we use WiFi.
The goal is to use the output to encourage open discussions about how we
use our devices online.]{.why .descriptor} [Example]{.example .empty
.descriptor}
Snippets of a Something In The Middle, Maybe - Report
[TODO: RELATES TO]{.tmp} []{#ntlimgqy .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.whatisitliketobeanelevator)
What is it like to be AN ELEVATOR?]{.method .descriptor} [What:
Understanding software systems by becoming them]{.what .descriptor}
[TODO: extend this text \.... how to observe software in the world
around you. How to observe an everyday software experience and translate
this into a flowchart )]{.tmp} [How: Creating a flowchart to incarnate a
software system you use everyday]{.how .descriptor} [WARNING: Uninformed
members of the public may panic when confronted with a software
performance in a closed space.]{.warning .descriptor} [Example: What is
it like to be an elevator?]{.example .descriptor}
` {.verbatim}
what
is
it
like
to be
an
elevator?
from 25th floor to 1st floor
light on button light of 25th floor
check current floor
if current floor is 25th floor
no
if current floor is ...
go one floor up
... smaller than 25th floor
go one floor down
... bigger than 25th floor
stop elevator
turn button light off of 25th floor
turn door light on
open door of elevator
play sound opening sequence
yes
start
user pressed button of 25th floor
close door of elevator
if door is closed
user pressed 1st floor button
start timer for door closing
if timer is running more than three seconds
yes
yes
light on button
go one floor down
no
if current floor is 1st floor
update floor indicator
check current floor
stop elevator
no
yes
light off button
turn door light on
open door of elevator
play sound opening sequence
end
update floor indicator `
[SHOW IMAGE HERE:
http://observatory.constantvzw.org/documents/joseph/flowchart.pdf]{.tmp}
[TODO: RELATES TO]{.tmp} []{#ndg2zte4 .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.sidechannel)
Side Channel Analysis]{.method .descriptor} [Urgency: Side Channel
attacks are possible by disregarding the abstraction of software into
pure logic: the physical effects of the running of the software become
backdoors to observe its functioning, both threatening the control of
processes and the re-affirming the materiality of software.]{.urgency
.descriptor} [WARNING: **engineers are good guys!**]{.warning
.descriptor} [Example]{.example .empty .descriptor} [SHOW IMAGE HERE:
https://www.tek.com/sites/default/files/media/image/119-4146-00%20Near%20Field%20Probe%20Set.png.jpg]{.tmp}
[SHOW IMAGE HERE:
http://gallery.constantvzw.org/index.php/Techno-Galactic-Software-Observatory/PWFU3377]{.tmp}
[TODO: RELATES TO]{.tmp} [Collections / collecting]{.grouping}
[]{#njmzmjm1 .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.bestiary)
Compiling a bestiary of software logos]{.method .descriptor} [What:
Since the early days of GNU-linux and cemented through the ubiquitous
O\'Reilly publications, the visual culture of software relies heavily on
animal representations. But what kinds of animals, and to what
effect?]{.what .descriptor} [How]{.how .empty .descriptor}
Compile a collection of logos and note the metaphors for observation: \*
stethoscope \* magnifying glass \* long neck (giraffe)
[Example]{.example .empty .descriptor}
` {.verbatim}
% http://animals.oreilly.com/browse/
% [check Testing the testbed pads for examples]
% [something on bestiaries] `
[TODO: RELATES TO]{.tmp} []{#njm5zwm4 .anchor} []{#mmy2zgrl .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.testingtestbed)
Testing the testbed: testing software with observatory ambitions
(SWOA)]{.method .descriptor} [WARNING: this method may make more sense
if you first take a look at the [Something in the Middle Maybe
(SitMM)](http://pad.constantvzw.org/p/observatory.guide.sitmm) which is
an instance of a SWOA]{.warning .descriptor} [How: The interwebs hosts
many projects that aim to produce software for observing software, (from
now on Software With Observatory Ambitions (SWOA)). A comparative
methodology can be produced by testing different SWOA to observe
software of interest. Example: use different sniffing software to
observe wireless networks, e.g., wireshark vs tcpdump vs SitMM.
Comparing SWOA reveals what is seen as worthy of observation (e.g., what
protocols, what space, which devices), the granularity of the
observation (e.g., how is the observation captured, in what detail), the
logo and conceptual framework of choice etc. This type of observation
may be turned into a service (See also: Something in the Middle Maybe
(SitMM)).]{.how .descriptor} [When: Ideally, SWOA can be used everywhere
and in every situation. In reality, institutions, laws and
administrators like to limit the use of SWOA on infrastructures to
people who are also administering these networks. Hence, we are
presented with the situation that the use of SWOA is condoned when it is
down by researchers and pen testers (e.g., they were hired) and shunned
when done by others (often subject to name calling as hackers or
attackers).]{.when .descriptor} [What: Deep philosophical moment: most
software has a recursive observatory ambition (it wants to be observed
in its execution, output etc.). Debuggers, logs, dashboards are all
instances of software with observatory ambitions and can not be
separated from software itself. Continuous integration is the act of
folding the whole software development process into one big feedback
loop. So, what separates SWOA from software itself? Is it the intention
of observing software with a critical, agonistic or adversarial
perspective vs one focused on productivity and efficiency that
distinguishes SWOA from software? What makes SWOA a critical practice
over other forms of sotware observation. If our methodology is testing
SWOA, then is it a meta critique of critique?]{.what .descriptor} [Who:
If you can run multiple SWOAs, you can do it. The question is: will
people like it if you turn your gaze on their SWOA based methods of
observation? Once again we find that observation can surface power
asymmetries and lead to defensiveness or desires to escape the
observation in the case of the observed, and a instinct to try to
conceal that observation is taking place.]{.who .descriptor} [Urgency:
If observation is a form of critical engagement in that it surfaces the
workings of software that are invisible to many, it follows that people
would develop software to observe (SWOAs). Testing SWOAs puts this form
of critical observation to test with the desire to understand how what
is made transparent through each SWOA also makes things invisible and
reconfigures power.]{.urgency .descriptor} [Note: Good SWOA software
usually uses an animal as a logo.:D]{.note .descriptor} [WARNING: Many
of the SWOA projects we looked at are promises more than running
software/available code. Much of it is likely to turn into obsolete
gradware, making testing difficult.]{.warning .descriptor} [TODO:
RELATES TO
http://pad.constantvzw.org/p/observatory.guide.bestiary]{.tmp} [TODO:
RELATES TO http://pad.constantvzw.org/p/observatory.guide.sitmm]{.tmp}
[]{#mmmzmmrh .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.reader)
Prepare a reader to think theory with software]{.method .descriptor}
[What: Compile a collection of texts about software.]{.what .descriptor}
[How: Choose texts from different realms. Software observations are
mostly done in the realm of the technological and the pragmatic. Also
the ecology of texts around software includes first and foremost
manuals, technical documentation and academic papers by software
engineers and these all \'live\' in different realms. More recently, the
field of software studies opened up additional perspectives fuelled by
cultural studies and sometimes filosophy. By compiling a reader \...
ways of speaking/writing about. Proximity.]{.how .descriptor}
[Example]{.example .empty .descriptor}
` {.verbatim .wrap}
Pull some quotes from the reader, for example from the chapter: Observation and its consequences
Lilly Irani, Hackathons and the Making of Entrepreneurial Citizenship, 2015 http://sci-hub.bz/10.1177/0162243915578486
Kara Pernice (Nielsen Norman Group), Talking with Participants During a Usability Test, January 26, 2014, https://www.nngroup.com/articles/talking-to-users/
Matthew G. Kirschenbaum, Extreme Inscription: Towards a Grammatology of the Hard Drive. 2004 http://texttechnology.mcmaster.ca/pdf/vol13_2_06.pdf
Alexander R. Galloway, The Poverty of Philosophy: Realism and Post-Fordism, Critical Inquiry. 2013, http://cultureandcommunication.org/galloway/pdf/Galloway,%20Poverty%20of%20Philosophy.pdf
Edward Alcosser, James P. Phillips, Allen M. Wolk, How to Build a Working Digital Computer. Hayden Book Company, 1968. https://archive.org/details/howtobuildaworkingdigitalcomputer_jun67
Matthew Fuller, "It looks like you're writing a letter: Microsoft Word", Nettime, 5 Sep 2000. https://library.memoryoftheworld.org/b/xpDrXE_VQeeuDDpc5RrywyTJwbzD8eatYGHKmyT2A_HnIHKb
Barbara P. Aichinger, DDR Memory Errors Caused by Row Hammer. 2015 www.memcon.com/pdfs/proceedings2015/SAT104_FuturePlus.pdf
Fangfei Liu, Yuval Yarom, Qian Ge, Gernot Heiser, Ruby B. Lee. Last-Level Cache Side-Channel Attacks are Practical. 2015 http://palms.ee.princeton.edu/system/files/SP_vfinal.pdf `
[TODO: RELATES TO
http://pad.constantvzw.org/p/observatory.guide.samequestion]{.tmp}
[]{#ytjmmmni .anchor}
Colophon
The Guide to techno-galactic software observing was compiled by Carlin
Wing, Martino Morandi, Peggy Pierrot, Anita, Christoph Haag, Michael
Murtaugh, Femke Snelting
License: Free Art License
Support:
Sources:
Constant, February 2018
::: {.footnotes}
1. [[[Haraway]{.fname}, [Donna]{.gname}, [Galison]{.fname},
[Peter]{.gname} and [Stump]{.fname}, [David J]{.gname}: [Modest
Witness: Feminist Diffractions in Science Studies]{.title},
[Stanford University Press]{.publisher}, [1996]{.date}.
]{.collection} [-\>](#eeffecbe)]{#ebceffee}
2. [Worksessions are intensive transdisciplinary moments, organised
twice a year by Constant. They aim to provide conditions for
participants with different experiences and capabilities to
temporarily link their practice and to develop ideas, prototypes and
research projects together. For the worksessions, primarily Free,
Libre and Open Source software is used and material that is
available under ??? [-\>](#fcdcaacb)]{#bcaacdcf}
3. [http://www.nam-ip.be [-\>](#ffeaecaa)]{#aaceaeff}
4. [http://www.etwie.be/database/actor/computermuseum-ku-leuven
[-\>](#dbabebfa)]{#afbebabd}
5. [[contributors]{.fname}, [Wikipedia]{.gname}: [Content-control
software --- Wikipedia, The Free Encyclopedia]{.title},
[2018]{.date}. [-\>](#fadefecf)]{#fcefedaf}
6. [[UrbanMinistry.org]{.fname}, [TechMission]{.gname}:
[SafeFamilies.org \| Accountability Software: Encyclopedia of Urban
Ministry]{.title}, [2018]{.date}. [-\>](#faebbffb)]{#bffbbeaf}
7. [[Content Watch Holdings]{.fname}, [Inc]{.gname}: [Protecting Your
Family]{.title}, [2018]{.date}. [-\>](#afcbcfbb)]{#bbfcbcfa}
8. [[websense.com]{.fname}, []{.gname}: [Explicit and transparent proxy
deployments]{.title}, [2012]{.date}. [-\>](#edbedede)]{#ededebde}
9. [[workrave.org]{.fname}, []{.gname}: [Frequently Asked
Questions]{.title}, [2018]{.date}. [-\>](#ddfbbbfc)]{#cfbbbfdd}
10. [[contributors]{.fname}, [Wikipedia]{.gname}: [Agile software
development --- Wikipedia, The Free Encyclopedia]{.title},
[2018]{.date}. [-\>](#ececbabd)]{#dbabcece}
11. [[contributors]{.fname}, [Wikipedia]{.gname}: [Scrum (software
development) --- Wikipedia, The Free Encyclopedia]{.title},
[2018]{.date}. [-\>](#caabcfee)]{#eefcbaac}
12. [[contributors]{.fname}, [Wikipedia]{.gname}: [The Manifesto for
Agile Software Development]{.title}, [2018]{.date}.
[-\>](#baffeabf)]{#fbaeffab}
13. [[Kruchten]{.fname}, [Philippe]{.gname}: [Agile's Teenage
Crisis?]{.title}, [2011]{.date}. [-\>](#faeebade)]{#edabeeaf}
:::