How might we ensure the survival and availability of community libraries,
individual collections and other precarious archives? If these libraries,
archives and collections are unwanted by official institutions or, worse,
buried beneath good intentions and bureaucracy, then what tools and platforms
and institutions might we develop instead?
While trying to both formulate and respond to these questions, we began making
Dat Library and HyperReadings:
**Dat Library** distributes libraries across many computers so that many
people can provide disk space and bandwidth, sharing in the labour and
responsibility of the archival infrastructure.
**HyperReadings** implements ‘reading lists’ or a structured set of pointers
(a list, a syllabus, a bibliography, etc.) into one or more libraries,
_activating_ the archives.
## Installation
The easiest way to get started is to install [Dat Library as a desktop
app](http://dat-dat-dat-library.hashbase.io), but there is also a programme
called ‘[datcat](http://github.com/sdockray/dat-cardcat)’, which can be run on
the command line or included in other NodeJS projects.
## Accidents of the Archive
The 1996 UNESCO publication [Lost Memory: Libraries and Archives Destroyed in
the Twentieth Century](http://www.stephenmclaughlin.net/ph-
library/texts/UNESCO%201996%20-%20Lost%20Memory_%20Libraries%20and%20Archives%20Destroyed%20in%20the%20Twentieth%20Century.pdf)
makes the fragility of historical repositories startlingly clear. “[A]cidified
paper that crumbles to dust, leather, parchment, film and magnetic light
attacked by light, heat humidity or dust” all assault archives. “Floods,
fires, hurricanes, storms, earthquakes” and, of course, “acts of war,
bombardment and fire, whether deliberate or accidental” wiped out significant
portions of many hundreds of major research libraries worldwide. When
expanding the scope to consider public, private, and community libraries, that
number becomes uncountable.
Published during the early days of the World Wide Web, the report acknowledges
the emerging role of digitization (“online databases, CD-ROM etc.”), but today
we might reflect on the last twenty years, which has also introduced new forms
of loss.
Digital archives and libraries are subject to a number of potential hazards:
technical accidents like disk failures, accidental deletions, misplaced data
and imperfect data migrations, as well as political-economic accidents like
defunding of the hosting institution, deaccessioning parts of the collection
and sudden restrictions of access rights. Immediately after library.nu was
shut down on the grounds of copyright infringement in 2012, [Lawrence Liang
wrote](https://kafila.online/2012/02/19/library-nu-r-i-p/) of feeling “first
and foremost a visceral experience of loss.”
Whatever its legal status, the abrupt absence of a collection of 400,000 books
appears to follow a particularly contemporary pattern. In 2008, Aaron Swartz
moved millions of US federal court documents out from behind a paywall,
resulting in a trial and an FBI investigation. Three years later he was
arrested and indicted for a similar gesture, systematically downloading
academic journal articles from JSTOR. That year, Kazakhstani scientist
Alexandra Elbakyan began [Sci-Hub](https://en.wikipedia.org/wiki/Sci-Hub) in
response to scientific journal articles that were prohibitively expensive for
scholars based outside of Western academic institutions. (See for further analysis and an alternative
approach to the same issues: “When everyone is librarian, library is
everywhere.”) The repository, growing to more than 60 millions papers, was
sued in 2015 by Elsevier for $15 million, resulting in a permanent injunction.
Library Genesis, another library of comparable scale, finds itself in a
similar legal predicament.
Arguably one of the largest digital archives of the “avant-garde” (loosely
defined), UbuWeb is transparent about this fragility. In 2011, its founder
[Kenneth Goldsmith wrote](http://www.ubu.com/resources/): “by the time you
read this, UbuWeb may be gone. […] Never meant to be a permanent archive, Ubu
could vanish for any number of reasons: our ISP pulls the plug, our university
support dries up, or we simply grow tired of it.” Even the banality of
exhaustion is a real risk to these libraries.
The simple fact is that some of these libraries are among the largest in the
world yet are subject to sudden disappearance. We can only begin to guess at
what the contours of “Lost Memory: Libraries and Archives Destroyed in the
Twenty-First Century” will be when it is written ninety years from now.
## Non-profit, non-state archives
Cultural and social movements have produced histories which are only partly
represented in state libraries and archives. Often they are deemed too small
or insignificant or, in some cases, dangerous. Most frequently, they are not
deemed to be anything at all — they are simply neglected. While the market,
eager for new resources to exploit, might occasionally fill in the gaps, it is
ultimately motivated by profit and not by responsibility to communities or
archives. (We should not forget the moment [Amazon silently erased legally
purchased copies of George Orwell’s
1984](http://www.nytimes.com/2009/07/18/technology/companies/18amazon.html)
from readers’ Kindle devices because of a change in the commercial agreement
with the publisher.)
So, what happens to these minor libraries? They are innumerable, but for the
sake of illustration let’s say that each could be represented by a single
book. Gathered together, these books would form a great library (in terms of
both importance and scale). But to extend the metaphor, the current reality
could be pictured as these books flying off their shelves to the furthest
reaches of the world, their covers flinging open and the pages themselves
scattering into bookshelves and basements, into the caring hands of relatives
or small institutions devoted to passing these words on to future generations.
While the massive digital archives listed above (library.nu, Library Genesis,
Sci-Hub, etc.) could play the role of the library of libraries, they tend to
be defined more as sites for [biblioleaks](https://www.jmir.org/2014/4/e112/).
Furthermore, given the vulnerability of these archives, we ought to look for
alternative approaches that do not rule out using their resources, but which
also do not _depend_ on them.
Dat Library takes the concept of “a library of libraries” not to manifest it
in a single, universal library, but to realise it progressively and partially
with different individuals, groups and institutions.
## Archival properties
So far, the emphasis of this README has been on _durability_ , and the
“accidents of the archive” have been instances of destruction and loss. The
persistence of an archive is, however, no guarantee of its _accessibility_ , a
common reality in digital libraries where access management is ubiquitous.
Official institutions police access to their archives vigilantly for the
ostensible purpose of preservation, but ultimately create a rarefied
relationship between the archives and their publics. Disregarding this
precious tendency toward preciousness, we also introduce _adaptability_ as a
fundamental consideration in the making of the projects Dat Library and
HyperReadings.
To adapt is to fit something for a new purpose. It emphasises that the archive
is not a dead object of research but a set of possible tools waiting to be
activated in new circumstances. This is always a possibility of an archive,
but we want to treat this possibility as desirable, as the horizon towards
which these projects move. We know how infrastructures can attenuate desire
and simply make things difficult. We want to actively encourage radical reuse.
In the following section, we don’t define these properties but rather discuss
how we implement (or fail to implement) them in software, while highlighting
some of the potential difficulties introduced.
### Durability
In 1964, in the midst of the “loss” of the twentieth-century, Paul Baran’s
RAND Corporation publication [On Distributed
Communications](https://www.rand.org/content/dam/rand/pubs/research_memoranda/2006/RM3420.pdf)
examined “redundancy as one means of building … highly survivable and reliable
communications systems”, thus midwifing the military foundations of the
digital networks that we operate within today. While the underlying framework
of the Internet generally follows distributed principles, the client–server/
request–response model of the HTTP protocol is highly centralised in practice
and is only as durable as the server.
Capitalism places a high value on originality and novelty, as exemplified in
art where the ultimate insult would to be the label “redundant”. Worse than
being derivative or merely unoriginal, being redundant means having no reason
to exist — a uselessness that art can’t tolerate. It means wasting a perfectly
good opportunity to be creative or innovative. In a relational network, on the
other hand, redundancy is a mode of support. It doesn’t stimulate competition
to capture its effects, but rather it is a product of cooperation. While this
attitude of redundancy arose within a Western military context, one can’t help
but notice that the shared resources, mutual support, and common
infrastructure seem fundamentally communist in nature. Computer networks are
not fundamentally exploitative or equitable, but they are used in specific
ways and they operate within particular economies. A redundant network of
interrelated, mutually supporting computers running mostly open-source
software can be the guts of an advanced capitalist engine, like Facebook. So,
could it be possible to organise our networked devices, embedded as they are
in a capitalist economy, in an anti-capitalist way?
Dat Library is built on the [Dat
Protocol](https://github.com/datproject/docs/blob/master/papers/dat-paper.md),
a peer-to-peer protocol for syncing folders of data. It is not the first
distributed protocol ([BitTorrent](https://en.wikipedia.org/wiki/BitTorrent)
is the best known and is noted as an inspiration for Dat), nor is it the only
new one being developed today ([IPFS](https://ipfs.io) or the Inter-Planetary
File System is often referenced in comparison), but it is unique in its
foundational goals of preserving scientific knowledge as a public good. Dat’s
provocation is that by creating custom infrastructure it will be possible to
overcome the accidents that restrict access to scientific knowledge. We would
specifically acknowledge here the role that the Dat community — or any
community around a protocol, for that matter — has in the formation of the
world that is built on top of that protocol. (For a sense of the Dat
community’s values — see its [code of conduct](https://github.com/datproject
/Code-of-Conduct/blob/master/CODE_OF_CONDUCT.md).)
When running Dat Library, a person sees their list of libraries. These can be
thought of as similar to a
[torrent](https://en.wikipedia.org/wiki/Torrent_file), where items are stored
across many computers. This means that many people will share in the provision
of disk space and bandwidth for a particular library, so that when someone
loses electricity or drops their computer, the library will not also break.
Although this is a technical claim — one that has been made in relation to
many projects, from Baran to BitTorrent — it is more importantly a social
claim: the users and lovers of a library will share the library. More than
that, they will share in the work of ensuring that it will continue to be
shared.
This is not dissimilar to the process of reading generally, where knowledge is
distributed and maintained through readers sharing and referencing the books
important to them. As [Peter Sloterdijk
describes](https://rekveld.home.xs4all.nl/tech/Sloterdijk_RulesForTheHumanZoo.pdf),
written philosophy is “reinscribed like a chain letter through the
generations, and despite all the errors of reproduction — indeed, perhaps
because of such errors — it has recruited its copyists and interpreters into
the ranks of brotherhood (sic)”. Or its sisterhood — but, the point remains
clear that the reading / writing / sharing of texts binds us together, even in
disagreement.
### Accessibility
In the world of the web, durability is synonymous with accessibility — if
something can’t be accessed, it doesn’t exist. Here, we disentangle the two in
order to consider _access_ independent from questions of resilience.
##### Technically Accessible
When you create a new library in Dat, a unique 64-digit “key” will
automatically be generated for it. An example key is
`6f963e59e9948d14f5d2eccd5b5ac8e157ca34d70d724b41cb0f565bc01162bf`, which
points to a library of texts. In order for someone else to see the library you
have created, you must provide to them your library’s unique key (by email,
chat, on paper or you could publish it on your website). In short, _you_
manage access to the library by copying that key, and then every key holder
also manages access _ad infinitum_.
At the moment this has its limitations. A Dat is only writable by a single
creator. If you want to collaboratively develop a library or reading list, you
need to have a single administrator managing its contents. This will change in
the near future with the integration of
[hyperdb](https://github.com/mafintosh/hyperdb) into Dat’s core. At that
point, the platform will enable multiple contributors and the management of
permissions, and our single key will become a key chain.
How is this key any different from knowing the domain name of a website? If a
site isn’t indexed by Google and has a suitably unguessable domain name, then
isn’t that effectively the same degree of privacy? Yes, and this is precisely
why the metaphor of the key is so apt (with whom do you share the key to your
apartment?) but also why it is limited. With the key, one not only has the
ability to _enter_ the library, but also to completely _reproduce_ the
library.
##### Consenting Accessibility
When we say “accessibility”, some hear “information wants to be free” — but
our idea of accessibility is not about indiscriminate open access to
everything. While we do support, in many instances, the desire to increase
access to knowledge where it has been restricted by monopoly property
ownership, or the urge to increase transparency in delegated decision-making
and representative government, we also recognise that Indigenous knowledge
traditions often depend on ownership, control, consent, and secrecy in the
hands of the traditions’ people. [see [“Managing Indigenous Knowledge and
Indigenous Cultural and Intellectual
Property”](https://epress.lib.uts.edu.au/system/files_force/Aus%20Indigenous%20Knowledge%20and%20Libraries.pdf?download=1),
pg 83] Accessibility understood in merely quantitative terms isn’t able to
reconcile these positions, which this is why we refuse to limit “access” to a
question of technology.
While “digital rights management” technologies have been developed almost
exclusively for protecting the commercial interests of capitalist property
owners within Western intellectual property regimes, many of the assumptions
and technological implementations are inadequate for the protection of
Indigenous knowledge. Rather than describing access in terms of commodities
and ownership of copyright, it might be defined by membership, status or role
within a community, and the rules of access would not be managed by a
generalised legal system but by the rules and traditions of the people and
their knowledge. [[“The Role of Information Technologies in Indigenous
Knowledge
Management”](https://epress.lib.uts.edu.au/system/files_force/Aus%20Indigenous%20Knowledge%20and%20Libraries.pdf?download=1),
101-102] These rights would not expire, nor would they be bought and sold,
because they are shared, i.e., held in common.
It is important, while imagining the possibilities of a technological
protocol, to also consider how different _cultural protocols_ might be
implemented and protected through the life of a project like Dat Library.
Certain aspects of this might be accomplished through library metadata, but
ultimately it is through people hosting their own archives and libraries
(rather than, for example, having them hosted by a state institution) that
cultural protocols can be translated and reproduced. Perhaps we should flip
the typical question of how might a culture exist within digital networks to
instead ask how should digital networks operate within cultural protocols?
### Adaptability (ability to use/modify as one’s own)
Durability and accessibility are the foundations of adoptability. Many would
say that this is a contradiction, that adoption is about use and
transformation and those qualities operate against the preservationist grain
of durability, that one must always be at the expense of the other. We say:
perhaps that is true, but it is a risk we’re willing to take because we don’t
want to be making monuments and cemeteries that people approach with reverence
or fear. We want tools and stories that we use and adapt and are always making
new again. But we also say: it is through use that something becomes
invaluable, which may change or distort but will not destroy — this is the
practical definition of durability. S.R. Ranganathan’s very first Law of
Library Science was [“BOOKS ARE FOR
USE”](https://babel.hathitrust.org/cgi/pt?id=uc1.$b99721;view=1up;seq=37),
which we would extend to the library itself, such that when he arrives at his
final law, [“THE LIBRARY IS A LIVING
ORGANISM”](https://babel.hathitrust.org/cgi/pt?id=uc1.$b99721;view=1up;seq=432),
we note that to live means not only to change, but also to live _in the
world_.
To borrow and gently distort another concept of Raganathan’s concepts, namely
that of ‘[Infinite
Hospitality](http://www.dextersinister.org/MEDIA/PDF/InfiniteHospitality.pdf)’,
it could be said that we are interested in ways to construct a form of
infrastructure that is infinitely hospitable. By this we mean, infrastructure
that accommodates the needs and desires of new users/audiences/communities and
allows them to enter and contort the technology to their own uses. We really
don’t see infrastructure as aimed at a single specific group, but rather that
it should generate spaces that people can inhabit as they wish. The poet Jean
Paul once wrote that books are thick letters to friends. Books as
infrastructure enable authors to find their friends. This is how we ideally
see Dat Library and HyperReadings working.
## Use cases
We began work on Dat Library and HyperReadings with a range of exemplary use
cases, real-world circumstances in which these projects might intervene. Not
only would the use cases make demands on the software we were and still are
beginning to write, but they would also give us demands to make on the Dat
protocol, which is itself still in the formative stages of development. And,
crucially, in an iterative feedback loop, this process of design produces
transformative effects on those situations described in the use cases
themselves, resulting in further new circumstances and new demands.
### Thorunka
Wendy Bacon and Chris Nash made us aware of Thorunka and Thor.
_Thorunka_ and _Thor_ were two underground papers in the early 1970’s that
spewed out from a censorship controversy surrounding the University of New
South Wales student newspaper _Tharunka_. Between 1971 and 1973, the student
magazine was under focused attack from the NSW state police, with several
arrests made on charges of obscenity and indecency. Rather than ceding to the
charges, this prompted a large and sustained political protest from Sydney
activists, writers, lawyers, students and others, to which _Thorunka_ and
_Thor_ were central.
> “The campaign contested the idea of obscenity and the legitimacy of the
legal system itself. The newspapers campaigned on the war in Vietnam,
Aboriginal land rights, women’s and gay liberation, and the violence of the
criminal justice system. By 1973 the censorship regime in Australia was
broken. Nearly all the charges were dropped.” – [Quotation from the 107
Projects Event](http://107.org.au/event/tharunka-thor-journalism-politics-
art-1970-1973/).
Although the collection of issues of _Tharunka_ is largely accessible [via
Trove](http://trove.nla.gov.au/newspaper/page/24773115), the subsequent issues
of _Thorunka_ , and later _Thor_ , are not. For us, this demonstrates clearly
how collections themselves can encourage modes of reading. If you focus on
_Tharunka_ as a singular and long-standing periodical, this significant
political moment is rendered almost invisible. On the other hand, if the
issues are presented together, with commentary and surrounding publications,
the political environment becomes palpable. Wendy and Chris have kindly
allowed us to make their personal collection available via Dat Library (the
key is: 73fd26846e009e1f7b7c5b580e15eb0b2423f9bea33fe2a5f41fac0ddb22cbdc), so
you can discover this for yourself.
### Academia.edu alternative
Academia.edu, started in 2008, has raised tens of millions of dollars as a
social network for academics to share their publications. As a for-profit
venture, it is rife with metrics and it attempts to capitalise on the innate
competition and self-promotion of precarious knowledge workers in the academy.
It is simultaneously popular and despised: popular because it fills an obvious
desire to share the fruits of ones intellectual work, but despised for the
neoliberal atmosphere that pervades every design decision and automated
correspondence. It is, however, just trying to provide a return on investment.
[Gary Hall has written](http://www.garyhall.info/journal/2015/10/18/does-
academiaedu-mean-open-access-is-becoming-irrelevant.html) that “its financial
rationale rests … on the ability of the angel-investor and venture-capital-
funded professional entrepreneurs who run Academia.edu to exploit the data
flows generated by the academics who use the platform as an intermediary for
sharing and discovering research”. Moreover, he emphasises that in the open-
access world (outside of the exploitative practice of for-profit publishers
like Elsevier, who charge a premium for subscriptions), the privileged
position is to be the one “ _who gate-keeps the data generated around the use
of that content_ ”. This lucrative position has been produced by recent
“[recentralising tendencies](http://commonstransition.org/the-revolution-will-
not-be-decentralised-blockchains/)” of the internet, which in Academia’s case
captures various, scattered open access repositories, personal web pages, and
other archives.
Is it possible to redecentralise? Can we break free of the subjectivities that
Academia.edu is crafting for us as we are interpellated by its infrastructure?
It is incredibly easy for any scholar running Dat Library to make a library of
their own publications and post the key to their faculty web page, Facebook
profile or business card. The tricky — and interesting — thing would be to
develop platforms that aggregate thousands of these libraries in direct
competition with Academia.edu. This way, individuals would maintain control
over their own work; their peer groups would assist in mirroring it; and no
one would be capitalising on the sale of data related to their performance and
popularity.
We note that Academia.edu is a typically centripetal platform: it provides no
tools for exporting one’s own content, so an alternative would necessarily be
a kind of centrifuge.
This alternative is becoming increasingly realistic. With open-access journals
already paving the way, there has more recently been a [call for free and open
access to citation data](https://www.insidehighered.com/news/2017/12/06
/scholars-push-free-access-online-citation-data-saying-they-need-and-deserve-
access). [The Initiative for Open Citations (I4OC)](https://i4oc.org) is
mobilising against the privatisation of data and working towards the
unrestricted availability of scholarly citation data. We see their new
database of citations as making this centrifugal force a possibility.
### Publication format
In writing this README, we have strung together several references. This
writing might be published in a book and the references will be listed as
words at the bottom of the page or at the end of the text. But the writing
might just as well be published as a HyperReadings object, providing the
reader with an archive of all the things we referred to and an editable
version of this text.
A new text editor could be created for this new publication format, not to
mention a new form of publication, which bundles together a set of
HyperReadings texts, producing a universe of texts and references. Each
HyperReadings text might reference others, of course, generating something
that begins to feel like a serverless World Wide Web.
It’s not even necessary to develop a new publication format, as any book might
be considered as a reading list (usually found in the footnotes and
bibliography) with a very detailed description of the relationship between the
consulted texts. What if the history of published works were considered in
this way, such that we might always be able to follow a reference from one
book directly into the pages of another, and so on?
### Syllabus
The syllabus is the manifesto of the twenty-first century. From [Your
Baltimore “Syllabus”](https://apis4blacklives.wordpress.com/2015/05/01/your-
baltimore-syllabus/), to
[#StandingRockSyllabus](https://nycstandswithstandingrock.wordpress.com/standingrocksyllabus/),
to [Women and gender non-conforming people writing about
tech](https://docs.google.com/document/d/1Qx8JDqfuXoHwk4_1PZYWrZu3mmCsV_05Fe09AtJ9ozw/edit),
syllabi are being produced as provocations, or as instructions for
reprogramming imaginaries. They do not announce a new world but they point out
a way to get there. As a programme, the syllabus shifts the burden of action
onto the readers, who will either execute the programme on their own fleshy
operating system — or not. A text that by its nature points to other texts,
the syllabus is already a relational document acknowledging its own position
within a living field of knowledge. It is decidedly not self-contained,
however it often circulates as if it were.
If a syllabus circulated as a HyperReadings document, then it could point
directly to the texts and other media that it aggregates. But just as easily
as it circulates, a HyperReadings syllabus could be forked into new versions:
the syllabus is changed because there is a new essay out, or because of a
political disagreement, or because following the syllabus produced new
suggestions. These forks become a family tree where one can follow branches
and trace epistemological mutations.
## Proposition (or Presuppositions)
While the software that we have started to write is a proposition in and of
itself, there is no guarantee as to _how_ it will be used. But when writing,
we _are_ imagining exactly that: we are making intuitive and hopeful
presuppositions about how it will be used, presuppositions that amount to a
set of social propositions.
### The role of individuals in the age of distribution
Different people have different technical resources and capabilities, but
everyone can contribute to an archive. By simply running the Dat Library
software and adding an archive to it, a person is sharing their disk space and
internet bandwidth in the service of that archive. At first, it is only the
archive’s index (a list of the contents) that is hosted, but if the person
downloads the contents (or even just a small portion of the contents) then
they are sharing in the hosting of the contents as well. Individuals, as
supporters of an archive or members of a community, can organise together to
guarantee the durability and accessibility of an archive, saving a future
UbuWeb from ever having to worry about if their ‘ISP pulling the plug’. As
supporters of many archives, as members of many communities, individuals can
use Dat Library to perform this function many times over.
On the Web, individuals are usually users or browsers — they use browsers. In
spite of the ostensible interactivity of the medium, users are kept at a
distance from the actual code, the infrastructure of a website, which is run
on a server. With a distributed protocol like Dat, applications such as
[Beaker Browser](https://beakerbrowser.com) or Dat Library eliminate the
central server, not by destroying it, but by distributing it across all of the
users. Individuals are then not _just_ users, but also hosts. What kind of
subject is this user-host, especially as compared to the user of the server?
Michel Serres writes in _The Parasite_ :
> “It is raining; a passer-by comes in. Here is the interrupted meal once
more. Stopped for only a moment, since the traveller is asked to join the
diners. His host does not have to ask him twice. He accepts the invitation and
sits down in front of his bowl. The host is the satyr, dining at home; he is
the donor. He calls to the passer-by, saying to him, be our guest. The guest
is the stranger, the interrupter, the one who receives the soup, agrees to the
meal. The host, the guest: the same word; he gives and receives, offers and
accepts, invites and is invited, master and passer-by… An invariable term
through the transfer of the gift. It might be dangerous not to decide who is
the host and who is the guest, who gives and who receives, who is the parasite
and who is the table d’hote, who has the gift and who has the loss, and where
hospitality begins with hospitality.” — Michel Serres, The Parasite (Baltimore
and London: The Johns Hopkins University Press), 15–16.
Serres notes that _guest_ and _host_ are the same word in French; we might say
the same for _client_ and _server_ in a distributed protocol. And we will
embrace this multiplying hospitality, giving and taking without measure.
### The role of institutions in the age of distribution
David Cameron launched a doomed initiative in 2010 called the Big Society,
which paired large-scale cuts in public programmes with a call for local
communities to voluntarily self-organise to provide these essential services
for themselves. This is not the political future that we should be working
toward: since 2010, austerity policies have resulted in [120,000 excess deaths
in England](http://bmjopen.bmj.com/content/7/11/e017722). In other words,
while it might seem as though _institutions_ might be comparable to _servers_
, inasmuch as both are centralised infrastructures, we should not give them up
or allow them to be dismantled under the assumption that those infrastructures
can simply be distributed and self-organised. On the contrary, institutions
should be defended and organised in order to support the distributed protocols
we are discussing.
One simple way for a larger, more established institution to help ensure the
durability and accessibility of diverse archives is through the provision of
hardware, network capability and some basic technical support. It can back up
the archives of smaller institutions and groups within its own community while
also giving access to its own archives so that those collections might be put
to new uses. A network of smaller institutions, separated by great distances,
might mirror each other’s archives, both as an expression of solidarity and
positive redundancy and also as a means of circulating their archives,
histories and struggles amongst each of the others.
It was the simultaneous recognition that some documents are too important to
be privatised or lost to the threats of neglect, fire, mould, insects, etc.,
that prompted the development of national and state archives (See page 39 in
[Beredo, B. C., Import of the archive: American colonial bureaucracy in the
Philippines, 1898-1916](http://hdl.handle.net/10125/101724)). As public
institutions they were, and still are, tasked with often competing efforts to
house and preserve while simultaneously also ensuring access to public
documents. Fire and unstable weather understandably have given rise to large
fire-proof and climate-controlled buildings as centralised repositories,
accompanied by highly regulated protocols for access. But in light of new
technologies and their new risks, as discussed above, it is compelling to
argue now that, in order to fulfil their public duty, public archives should
be distributing their collections where possible and providing their resources
to smaller institutions and community groups.
Through the provision of disk space, office space, grants, technical support
and employment, larger institutions can materially support smaller
organisations, individuals and their archival afterlives. They can provide
physical space and outreach for dispersed collectors, gathering and piecing
together a fragmented archive.
But what happens as more people and collections are brought in? As more
institutional archives are allowed to circulate outside of institutional
walls? As storage is cut loose from its dependency on the corporate cloud and
into forms of interdependency, such as mutual support networks? Could this
open up spaces for new forms of not-quite-organisations and queer-
institutions? These would be almost-organisations that uncomfortable exist
somewhere between the common categorical markings of the individual and the
institution. In our thinking, its not important what these future forms
exactly look like. Rather, as discussed above, what is important to us is that
in writing software we open up spaces for the unknown, and allow others agency
to build the forms that work for them. It is only in such an atmosphere of
infinite hospitality that we see the future of community libraries, individual
collections and other precarious archives.
## A note on this text
This README was, and still is being, collaboratively written in a
[Git](https://en.wikipedia.org/wiki/Git)
[repository](https://en.wikipedia.org/wiki/Repository_\(version_control\)).
Git is a free and open-source tool for version control used in software
development. All the code for Hyperreadings, Dat Library and their numerous
associated modules are managed openly using Git and hosted on GitHub under
open source licenses. In a real way, Git’s specification formally binds our
collaboration as well as the open invitation for others to participate. As
such, the form of this README reflects its content. Like this text, these
projects are, by design, works in progress that are malleable to circumstances
and open to contributions, for example by opening a pull request on this
document or raising an issue on our GitHub repositories.
Sollfrank & Dockray
Expanded Appropriation
2013
Sean Dockray
Expanded Appropriation
Berlin, 4 January 2013
[00:13]
Public School [00:17]
We decided to give up doing a gallery because… Well, for one, the material
conditions weren’t so great for it. But I think people who open up galleries
do it in really challenging conditions, so there is no reason why we couldn’t
have done a gallery in that basement. [00:37] I think we were actually
disinterested in exhibition as a format. After a few years – I mean, we did
something like 35 things that could easily be called exhibitions, in a span of
5 years leading up to that. [00:55] I think we just wanted to try something
else. And so we already had started a project called The Public School a year
prior, so we decided that we would use our space primarily as a school.
[01:10] At that time those two things happened. We eliminated the gallery and
then ended up with two new galleries and a school instead!
[01:20] What The Public School is… it’s been going now for five fears. It
began just as a structure or even a diagram, or an idea or something. [01:43]
And the idea is that people would propose things that they wanted to learn
about, or to teach to other people. And then there would be a kind of process
where we use our space or the Internet to allow people to sign up to say they
are also interested in this idea. And then the School’s job would be to turn
those ideas into real meetings of people, real classes where people got
together. [02:15] So in that sense the curriculum would be developed in
public. It wouldn't be public just simply in the sense that anyone could go to
it, but it’d be public in the sense that anyone could produce the form of it.
[02:32] And again, I need a lot more time, I think, to talk about all the
dimensions to it, but in broad strokes that’s kind of what it is. [02:43]
Although we started in Los Angeles, in the basement of our original gallery
five years ago, it’s now been in around a dozen cities around the world, where
people are operating according to the same process, and then sometimes in
conversation with one another. And there’ve been 500-600 classes, and 2000 or
so proposals made in that time.
[03:18]
Motivation
[03:22]
It was in the air at the time already, so I don’t think it’d be an entirely
independent impulse – number one. But I had actually tried to start a couple
of things that had failed. [03:41] Like Aaaaarg – I tried to set up some
physical reading groups that would complement the online archive. So, in Los
Angeles the idea would be that we’d meet and talk about things that were being
posted to the website. So, yes, reading groups. But they never really went
anywhere. They were always really small, and they kind of run out of steam
quite quickly because no one was interested. [04:10] So in a way The Public
School was a later iteration of something that I’d already been trying for a
while. But the other thing was that by doing these reading groups,
intuitively, I knew what was wrong. [04:31] Although I like to read, that is
not all of what education is to me. To me learning and education is something
that is more inclusive of a lot more of what we experience in life, than
simply theoretical discussions. The structures didn’t really allow that in a
way. [04:56] The Public School came out of just trying to imagine what kind of
structure would be inclusive to overcome some of those self-imposed
limitations. [05:14] I’m very interested in technology in a hands-on way. I
like to code and electronics – hacking around with electronics. And at the
same time, I like to read and I like to write. And then once you go down that
line then you think, well, I like music a lot and I like to play chess as
well. [05:46] I think about all these things that I like to do, and I just
thought about how a lot of these gestures towards education that I tried to do
previously, in no way embraced me as a whole person. So in that sense, it was
based in personal interest. [06:22] But the other personal interest had to do
with personal motivation, it had to do with running an art space for, at that
point, four years. And actually seeing the way that that happened, because I’m
not a curator. [06:38] And so the act of putting on exhibitions for me was
less about making value judgments, and more about trying to contribute to the
cultural life of my city, and also provide opportunities that didn’t exist in
Los Angeles. [06:57] For example, no one really knew how to show work with
technology, and we were able to, because, for instance I knew how to set up
projectors, fix electronics or get things to start and stop, and that kind of
stuff. [07:13] But over the course of running it, because it is an exhibition
space, I found myself put into the role of being a curator – Fiona and I both
did. And it was kind of an uncomfortable role to be deciding what became
visible and what wouldn’t be. [07:32] And one thing that was never visible was
the sort of mechanisms by which an institution made certain things visible.
[07:40] So the public in The Public School actually in a way is trying to
eliminate that whole apparatus, or at least, put that apparatus as something
that we didn’t want to be solely the ones interacting with. We wanted that
apparatus to be… that our entire community, the community of people who is
participating in the programme – that they were the ones responsible for it.
[08:14] So that would shift programming, but also accountability and all these
things, to the people who are actually participating in the life of the space.
[08:28]
Technical Infrastructure
[08:32]
The technical infrastructure is incredibly important because at the moment
that’s people’s primary experience of the project. They make proposals on the
website, and then the classes are actually organised by people through the
website. So the website, the entire technical infrastructure becomes the
engine for getting events to happen. [09:01] It’s not an essential part. At
the very beginning we did it on paper, and we had the website and the paper
kind of simultaneously. And we’d print things out onto paper that would be
accessible by coming into the space, and vice versa, we'd enter things from
the paper back into the website. [09:26] But at the moment it’s mostly
orchestrated through the website. And it’s been three versions of it, like
three separate pieces of software, and the last two it’s been Kayla Waldorf
and myself who have been programming it. And we have… [09:45] Number one,
we’ve organised lots of classes, so we’re very involved in the life of the
school. And in a way we try to programme the site according to (A) what would
make things work, but (B), like you say, in a way that expresses the politics,
as we see them, of the site. [10:14] And so almost at every level, at every
design decision that Kayla might be making, or every kind of code or database
decision, you know, interactive decision that I might be making – those
conversations and those ideas are finding their way into that. [10:45] And
vice versa, that you see code, in a certain way, as not determining politics,
but certainly influencing what people see as possible and also choices that
they see available to them, and things like that. [11:09] I guess as users of
the site, as organisers of The Public School and as programmers, this kind of
relationship between the project and the software is quite intertwined.
[11:28] And I don’t think that… I think that typically art institutions use a
website as a kind of publicity vehicle, as a kind of postcard or something
that fits into their broadcasting of a programme, as something as a glue
between their space and their audience. [11:49] And I think for us the website
is actually integral to the space and to the audience. There is more of a
continuum between the space, programme, website and audience.
[12:04]
Aaaaarg.org
[12:08]
It started out small. In a way, it was an extension of what I think as a
practice that all of us are familiar with, which is sharing books that we’ve
read, or sharing articles that we’ve read, especially if your work is somehow
in relationship to things that you might be reading. [12:41] In my
architecture school, for instance, we would read lots and lots, and then we’d
be making work in parallel. It wouldn’t be that either would determine the
other, but in the end, there is a strong relationship between the ideas that
you have and what you see as possible, and the things that you are reading.
[13:07] So as part of the student culture, especially among my friends, the
people that I identified with in school, we’d be discovering different parts
of the library independently. And then when we found something that was quite
moving in whatever way then we would photocopy it to keep it for ourselves
later. [13:34] And we’d also give it to each other as a kind of secret tool,
or something like that, you know, like you have the sense that when you found
something that is really good – and specially if other people aren’t even
interested – then you feel really empowered by having access to that, by being
able to read it and reread it. [14:02] And then you feel more empowered when
there is a community of other people. It may be a small one, but who have read
that thing as well, because then you start building a kind of shared frame of
reference, a shared vocabulary and a shared way of seeing the world, and
seeing what you’re working on. [14:22] And I think out of that comes projects,
like you actually work on projects together, you collaborate, you correspond
with other people or you actually share the work. And that’s what happened.
[14:41] I started Aaaaarg.org after I moved from New York to Los Angeles, so I
was quite far away from some of the people that I was working with – and just
continuing with that very basic activity of sharing reading material in order
to have that shared vocabulary to be able to work together.
[15:08]
Content
[15:12]
It turned out to be architecture at the very beginning. But we all had really
broad understandings of what architecture meant and what it included, so there
was a lot of media theory, art history and philosophy, and occasionally some
architecture too. [15:38] And so that became the initial kind of seed. And I
think everything has, as the site expanded from there, to be not just me and
some collaborators, or then collaborators of collaborators, and then friends
of those people, and so on. [16:03] It’s kind of a ripple effect outwards.
What happened was something that is quite common to almost any platform, which
is this kind of feedback. Even in an open structure, it's never truly open.
There’re always rules in place, there’s always a past history, and those two
things go a long way to influence what happens in the future. [16:33] I’m sure
a lot of people will come to the site who are interested in one thing, and
then find nothing in the site that speaks to them, and then disappear. Whereas
other people, the site really spoke to them, and so what they would contribute
can also fit according to that sense, to that inclination.
[16:59]
Dynamics of growth and community-building
[17:04]
Especially when I’m involved in this kind of projects, I don’t like being
alone. Obviously it contributes a lot to the work, not only because there’s
more people, but actually the kind of relationships and negotiations that
happen in that work are interesting in themselves. [17:29] So anyway, it was
never all that interesting for it to be a private library. I mean, we all have
private libraries, but there is this potential as well, which I think wasn’t
part of the project at the beginning, it really was a tool for sharing in a
particular kind of context. [17:56] But I think, obviously, you know, once
people saw it then they saw a sort of potential in it, because you see what
happens on the Internet and you know that in certain cases you can read from
it and you can write to it. [18:18] And you also know that, although there
still [are] various forms of digital exclusion, that it's quite accessible
relative to other forms, other libraries, like university libraries, for
instance.
[18:37]
Cornelia Sollfrank: It’s not just about having access to certain material, but
what is related to it, and what’s really important, is the dynamics of
building a community and the context, and even smaller discourses around
certain issues, which you don’t have necessarily if you just download a text.
Then you have the text but you don’t have somebody to talk to, or you don’t
write your opinion about it to someone. So that’s, I think, what comes with
the project, which makes it very valuable to a lot of people.
[19:13]
Yes. That’s going back to what I was saying about some of the failures before
The Public School, which was... As the site was growing, as Aaaaarg was
growing, all of a sudden there would be things in there that I didn’t know
about before, that someone felt it was important to share. [19:37] And because
someone felt that it was important to share it, I felt it was important to
read it. And I did, but then I wanted to read it with other people. [19:51]
So, some of those reading groups were always attempts to produce some social
context for the theory.
[20:06] Having a library as if the archive itself is the library – but having
that isn't really that interesting to me. What's interesting is having some
social context that I can feel involved in (not that I ‘have’ to be involved
in it), but having some social context to make use of that reading material.
[20:42]
Copyright
[20:47]
At the beginning it was never a component of the project, because of that sort
of natural extension between what I see as a perfectly… something that I think
that we all do already. And especially in architecture and art, if you are
involved in reading you give books to people. Like you gave me your book… And
I’ve passed on a number of books. [21:34] If I print out something to read and
I’m done with it, then I’m more likely to pass it on than I’m to shred it – I
have to keep it in my closet forever, what do I do with it? If I think I’m
truly done with it, even for a moment, then I’m more likely to pass it on.
[22:00] So at the beginning it had nothing to do with piracy, it had
everything to do with wanting to share things with other people. And a lot of
times it's not just in this abstract “I kind of like to share,” but it was
project-based, and I think it became a little bit more abstract. [22:24] But I
think actually over time, when people were sharing things, sometimes they did
it with this sort of abstract recipient of that sharing, and that they would
think, “I have access to this and I know that other people want access to it,
and so that’s going to be why I share it.” [22:46] In other cases, I know that
people were trying to organise a reading group, and this is quite common,
which is that people would be organising something and then how are they going
to distribute the reading material. Yes, they could give everyone a link to
Amazon so they all order their own book, maybe that would be better for
Amazon. [23:13] But there are another ways that they would organise the
reading material there. A lot of times the stuff they wanted to read was
already on Aaaaarg. Sometimes they had to upload a few new things. [23:26] And
so that’s how a lot of it grew and that’s why people are involved. And I think
sharing was what drove the project. And then it really wasn’t for 3 years that
even there was anything even relating to copyright issues. No one complained
for all that time. [23:53] And then when complains came in then, you know, we
responded by taking it down. It was quite simple. [24:05] But then later in
the life of the project, the copyright problems sort of, in a way,
retroactively made the project more about piracy than about sharing.
[24:22]
Attempts to control file-sharing
[24:26]
Either through making activity which used to be legal, illegal, or which used
to be in a kind of grey area because there wasn’t a framework in place for it,
that sort of draw hard lines to say that something in now illegal. [24:46] And
then there is the technological forms of negation, I think, which is to
actually make it impossible for people to do something that they used to be
able to do – signing copies of a file and not allowing it to open if it’s not
opening in the right place, or through the cloud, through this kind of new
marketing opportunities of centralising a lot of files in one place, and then
sort of governing the access through sites like Spotify. [25:29] Amazon does
the same thing, you know, also with their e-books, where they own the device,
the distribution network and the servers. And so by controlling the entire
pipeline, there’s a lot more control over what people do. [25:51] For
instance, you have to jailbreak the Kindle in to order to share a book. Again,
something that we used to be able to do, now we actually have to break the law
or break our devices. [26:05] So these two things, I think, are how it gets
dealt with. And of course, there’s always responses to those things. [26:12] I
think the technological one is a big [one] ... to me that’s the more
challenging one, especially now, because what’s been produced is much more
miniaturised and a lot more difficult to...
C.S.: Hack?
[26:30] Yes. And also you can’t hack the server farm that’s located in, you
know, this really remote part of some country that you’ve never been to.
Shouldn’t say never. In fact, I’ll say never, just to see if someone can.
[26:50] Positive things would be to say, if we take a more expansive view of
the economy, look at who is making money, and then make an appeal for that.
Because there are people who are making money, like Apple is making a lot of
money, and other people who aren’t making money. [27:15] And I don’t think you
can blame the readers, for instance, for the fact that writers and publishers
aren’t making money, because the readers are going into that too, because of
the same forces. [27:28] So you look at who is making the money, and I think
that is a political argument that needs to be made, that this money is
actually being kind of hoarded by some of these companies, because they are
sort of gaming the system and the restructuring of the economy, but also how
we consume entertainment, and all this kind of things, and the restructuring
of production around the globe.
[27:59] I don’t think sites like Aaaaarg do anything more than point out a
kind of dynamic that is existing in the world – to think that somehow you can
sort of turn that into something positive, you know, in a way that gets
capitalism to stop exploiting people – like it seems silly to me, capitalism
exploits people...
[28:31]
Publishing landscape
[28:35]
I think that the role of the publishers [is] already changing, because of the
Internet and because of companies like Amazon, who changed not only selling
books. They changed not only the bookstore, but also changed the entire
distribution model, which then changes the way publishers work – and more and
more, even the entire life cycle of a book, you know, from the writing to the
sort of organisation and communication, to the distribution to the
consumption. [29:09] The entire life cycle of a book is happening through
these networks, from the software that we write it on, and where is that stuff
stored, you know – is a Google Docs or some other thing? –, and our e-mails
that are circulating, and the accounting software. [29:31] A lot of it is
changing through the entire pipeline anyway, so to me, it’s really difficult
to say how publishing is changing because the entire flow, the entire
apparatus is changing.
[29:48] At the beginning, Aaaaarg was a way of bringing readers together, and
to allow readers to sort of give value to certain things that they were
reading. And I think that’s always been a form of publishing to me. [30:09]
Yes, someone is responsible for having the book edited, having it printed it,
distributing it, there’s a huge material expense in all of that. [30:21] But
then you also have the life of the book after it gets to the store. And it
continues to have a life, like sometimes it lives for decades and decades, and
it goes between readers, it goes through sidewalk vendors, and used book
stores, and sits on people’s libraries, and goes to public libraries. [30:44]
And I would say that Aaaaarg is sort of in that part of the life cycle.
[30:54] These platforms become sort of new publishers themselves, but I
haven’t really thought that kind of statement through enough. In a way, if
publishing is to make something public and to create publics, then of course,
that’s something that Aaaaarg has done since the beginning. [31:22] It made
things public to people who maybe didn’t exist for before, and it also
produced communities of people around books – I mean, if that’s what a
publication and a publisher does, then, of course, it kind of does that within
the context of the Internet, and it does that by both using and producing
social relations between people.
[31:50]
Reading / books
[31:54]
I have lots of books, and I buy them from anywhere. I buy them, as much as it
pains me to admit it, I buy them from Amazon, I buy them from bookstores, I
buy them from used books stores, I buy them on the street, I find them in
trash, I’ve photocopied so many parts of books at the library, because they
didn’t circulate or something, or because I only had four hours to look at the
book; I’ve gotten things for my friends, I’ve gotten things from classes that
I used to take when I was a student but I still have. [32:37] And then with
the Internet, then I'd see it on a screen, sometimes I print that out, you
know. I’m not a purist in any way about reading or about books, I’m not
particularly sentimental about ‘the book.’ Even though I love books and I see
what’s nice about them, I think that every sort of form a book takes has its
own kind of… there’s something unique about it. [33:11] Honestly, this kind
of, let’s say, increase in e-Pubs and PDFs hasn’t really changed my
relationship to books at all. It’s the same as it’s always been, which is,
I’ll read it, how I can get it. And maybe there’s slightly now forms, and
sometimes I read on a little… I bought a touchpad when they had a fire sale a
while ago, so I read on that.
[33:44] And maybe I’m making an obvious argument here, but you see, if you've
ever scanned a book you know that it takes time, and you know that you screw
up quite a lot, and sometimes those screw ups find their way in, and the
labour that goes into making a scan finds its way in. [34:02] And it’s only
through really good scans that you can manage to sort of eliminate a lot of
that, a lot of the traces of that labour. But I know that, in the entire
history of Aaaaarg, the files will always show the labour of the person who is
trying to get something up to share it with other people. It’s not a
frictionless easy activity, there is work that’s involved in it. [34:31] And I
find some of the scans were quite beautiful in that way, even when they
weren’t necessarily so good to read.
[34:41] There’s actually, if we go to scale… Again, I have way more books that
I could possibly read, physical books. And I’m going to continue buying more,
acquiring more through my entire life, I’m sure of it. And I think that’s just
part of loving books and loving to read, you have more than you can possibly
deal with. [35:11] And I think, on a level of scale, maybe, with the Internet
we find ourselves, in orders of magnitude, [with] more than we could possibly
deal with. But in a way, it’s the same kind of anxiety, and the limits are
more or less the same. [35:29] But then there are maybe even new opportunities
for new ways of reading that weren’t available before. I could flip through a
book in a certain way, but maybe now with the possibility of indexing the
whole content of a book, and doing searches, and creating ways of visually
displaying books and relationships between books, and between parts of books,
and this kind of things, and also making lists, and making lists with other
people – all of these maybe provide new ways of reading which weren't
available. [36:13] And of course it means that then other ways of reading that
get sort of buried and, you know, lost. And I’m sure that that's true too,
that slow deep reading maybe isn’t as prevalent as different types of
referencing and stuff. [36:32] Not to say that it’s totally identical, but
certainly an evolution. I don’t think that progression is so linear, that it’s
pure loss, or anything like that.
[36:44]
Form and content
[36:49] For me what’s interesting is to try and examine how structure and
form, or structure and content, form and content – I mean, that’s kind of
another on-going question, how structure is not divorced from content.
Structure is not simply a container for the content, any more than the mind
and body are distinct entities – but that the structure that something takes
influences the shape that content takes, and also the ways that people might
approach that context, or use it in this kind of things. And likewise, the
content begins to affect the structure as well. [37:47] Why I’m interested in
structures is because they aren’t deterministic, they don’t determine what’s
going to happen. And all the projects that you mention are things that I think
of, let’s say, as platforms or something, in the sense that they have… they
involve a lot of people quite often, more than just me, and they also have…
the duration is not specified in advance, and what’s going to happen in them
is not specified in advance. [38:30] So they’re experimental in that way, and
they have that in common. And that is what’s interesting to me, is the
production of situations where we don’t know what’s going to happen. [38:51]
And sometimes when focusing on a work you have vision for what that work is
going to be, and then all your work goes into realising that, and, of course,
you have surprises along the way, but then you get something that surprisingly
ends up like what you kind of imagined at the beginning – that way of working
doesn’t really interest me. I sort of become bored pretty early on in that
process. [39:23] Whereas the kind of longer term thing where the initial
conditions actually produce a situation that’s a little unstable, and
therefore what happens is also kind of unpredictable and unstable, to me this
is about opening up other possibilities for things as small as being together
for a short time, but also as big as ways of living.
[40:00] On the one level, these are structural projects, but on another level
they are all kind of structural appropriations in a way, or appropriations of
structures, like from a gallery, a library, a school, another gallery. [40:23]
And I was actually thinking about that I kind of wish that (and I imagine
soon, maybe in the next decade or two) an art historian will make this kind of
argument for evolving the concept of appropriation, to go beyond objects to…
Because in a way appropriation enters into the discourse when reproduction…
[40:52] I think appropriation it’s been something, let’s say, that maybe is a
historical concept. So at certain point in history maybe it even has a
different name, there’s different ways that it happens, there are different
cultural responses to it. [41:09] And I think that in the twentieth century,
especially with mechanical reproduction, appropriation becomes quite clear
what it is, because images or sounds, you know, things became distributed and
available for people to actually materially use. [41:30] And the tools that
people have available to make work as well allow for this type of reuse of
what’s being circulated through the world. [41:45] And I guess what I’m sort
of saying is, if that’s appropriation of objects, then there might even be a
time now, especially as the economy sort of shifted from being simply about
commodity – the production, and sale and consumption of commodities) – to now,
if we try to understand critically the economy now, it’s something that’s much
more complicated – it involves financialization, debt and derivative trading,
and all this kind of things. [42:25] And so, perhaps also if appropriation is
a historical idea, then appropriation also needs to be updated, and this would
mean – for me this would mean appropriation of systems. [42:46] So rather than
the appropriation of what’s been distributed, it’s the appropriation of the
system of distribution. And to me these are also projects that I get excited
about at the moment. [43:04] In a way it also makes sense, because if
photographs were circulating around the world, and that was, you know, a new
thing, to see that sort of imagery circulating in that way, at a certain point
in time a century ago; then now I think we are even having a similar reaction
to something like Facebook, which to me kind comes out of nowhere, and
suddenly it exists in the world as a structure that is organising a certain
part of the activity of, you know, hundreds of millions of people. [43:47] And
so I think, in a way, that’s the level on which maybe we can start thinking of
appropriation, at a level of this kind of large scale systems. But then that
brings up a whole new set of questions, like what do you call that, number
one. Number two, obviously the legal framework that’s in place, obviously that
will cause problems.