[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/philosophy right-to-read.uk.html po/right-t...
|
From: |
GNUN |
|
Subject: |
www/philosophy right-to-read.uk.html po/right-t... |
|
Date: |
Mon, 31 Oct 2016 22:57:29 +0000 (UTC) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 16/10/31 22:57:29
Modified files:
philosophy : right-to-read.uk.html
Added files:
philosophy/po : right-to-read.uk-diff.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/right-to-read.uk.html?cvsroot=www&r1=1.13&r2=1.14
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/right-to-read.uk-diff.html?cvsroot=www&rev=1.1
Patches:
Index: right-to-read.uk.html
===================================================================
RCS file: /web/www/www/philosophy/right-to-read.uk.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- right-to-read.uk.html 4 Aug 2016 13:59:12 -0000 1.13
+++ right-to-read.uk.html 31 Oct 2016 22:57:28 -0000 1.14
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/philosophy/right-to-read.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/philosophy/po/right-to-read.uk.po">
+ https://www.gnu.org/philosophy/po/right-to-read.uk.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/philosophy/right-to-read.html"
+ --><!--#set var="DIFF_FILE" value="/philosophy/po/right-to-read.uk-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2016-09-01" --><!--#set
var="ENGLISH_PAGE" value="/philosophy/right-to-read.en.html" -->
<!--#include virtual="/server/header.uk.html" -->
<!-- Parent-Version: 1.79 -->
@@ -15,6 +20,7 @@
<!--#include virtual="/philosophy/po/right-to-read.translist" -->
<!--#include virtual="/server/banner.uk.html" -->
+<!--#include virtual="/server/outdated.uk.html" -->
<h2>ÐÑаво пÑоÑиÑаÑи</h2>
<p>
@@ -490,7 +496,7 @@
<p class="unprintable"><!-- timestamp start -->
Ðновлено:
-$Date: 2016/08/04 13:59:12 $
+$Date: 2016/10/31 22:57:28 $
<!-- timestamp end -->
</p>
Index: po/right-to-read.uk-diff.html
===================================================================
RCS file: po/right-to-read.uk-diff.html
diff -N po/right-to-read.uk-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/right-to-read.uk-diff.html 31 Oct 2016 22:57:29 -0000 1.1
@@ -0,0 +1,501 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/philosophy/right-to-read.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.79 -->
+<title>The Right to Read
+- GNU Project - Free Software Foundation</title>
+<style type="text/css" media="print,screen"><!--
+hr { margin: 1.2em 0; }
+#content ul li p { margin-top: 1em; }
+#AuthorsNote ul li { margin-top: 1.3em; }
+#content div.announcement { margin-bottom: 2em; }
+--></style>
+<!--#include virtual="/philosophy/po/right-to-read.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>The Right to Read</h2>
+
+<p>
+by <a href="http://www.stallman.org/"><strong>Richard
Stallman</strong></a></p>
+
+<p>
+<em>This article appeared in the February 1997 issue
+of <cite>Communications of the ACM</cite> (Volume 40, Number
+2).</em></p>
+<hr />
+
+<blockquote><p>
+ From <cite>The Road To Tycho</cite>, a collection of
+ articles about the antecedents of the Lunarian
+ Revolution, published in Luna City in 2096.
+</p></blockquote>
+
+<p>
+For Dan Halbert, the road to Tycho began in college—when Lissa
+Lenz asked to borrow his computer. Hers had broken down, and unless
+she could borrow another, she would fail her midterm project. There
+was no one she dared ask, except Dan.</p>
+
+<p>
+This put Dan in a dilemma. He had to help her—but if he lent
+her his computer, she might read his books. Aside from the fact that
+you could go to prison for many years for letting someone else read
+your books, the very idea shocked him at first. Like everyone, he had
+been taught since elementary school that sharing books was nasty and
+wrong—something that only pirates would do.</p>
+
+<p>
+And there wasn't much chance that the SPA—the Software
+Protection Authority—would fail to catch him. In his software
+class, Dan had learned that each book had a copyright monitor that
+reported when and where it was read, and by whom, to Central
+Licensing. (They used this information to catch reading pirates, but
+also to sell personal interest profiles to retailers.) The next time
+his computer was networked, Central Licensing would find out. He, as
+computer owner, would receive the harshest punishment—for not
+taking pains to prevent the crime.</p>
+
+<p>
+Of course, Lissa did not necessarily intend to read his books. She
+might want the computer only to write her midterm. But Dan knew she
+came from a middle-class family and could hardly afford the tuition,
+let alone her reading fees. Reading his books might be the only way
+she could graduate. He understood this situation; he himself had had
+to borrow to pay for all the research papers he read. (Ten percent of those
+fees went to the researchers who wrote the papers; since Dan aimed for
+an academic career, he could hope that his own research papers, if
+frequently referenced, would bring in enough to repay this loan.)</p>
+
+<p>
+Later on, Dan would learn there was a time when anyone could go to the
+library and read journal articles, and even books, without having to
+pay. There were independent scholars who read thousands of pages
+without government library grants. But in the 1990s, both commercial
+and nonprofit journal publishers had begun charging fees for access.
+By 2047, libraries offering free public access to scholarly literature
+were a dim memory.</p>
+
+<p>
+There were ways, of course, to get around the SPA and Central
+Licensing. They were themselves illegal. Dan had had a classmate in
+software, Frank Martucci, who had obtained an illicit debugging tool,
+and used it to skip over the copyright monitor code when reading
+books. But he had told too many friends about it, and one of them
+turned him in to the SPA for a reward (students deep in debt were
+easily tempted into betrayal). In 2047, Frank was in prison, not for
+pirate reading, but for possessing a debugger.</p>
+
+<p>
+Dan would later learn that there was a time when anyone could have
+debugging tools. There were even free debugging tools available on CD
+or downloadable over the net. But ordinary users started using them
+to bypass copyright monitors, and eventually a judge ruled that this
+had become their principal use in actual practice. This meant they
+were illegal; the debuggers' developers were sent to prison.</p>
+
+<p>
+Programmers still needed debugging tools, of course, but debugger
+vendors in 2047 distributed numbered copies only, and only to
+officially licensed and bonded programmers. The debugger Dan used in
+software class was kept behind a special firewall so that it could be
+used only for class exercises.</p>
+
+<p>
+It was also possible to bypass the copyright monitors by installing a
+modified system kernel. Dan would eventually find out about the free
+kernels, even entire free operating systems, that had existed around
+the turn of the century. But not only were they illegal, like
+debuggers—you could not install one if you had one, without
+knowing your computer's root password. And neither
+the FBI nor
+Microsoft Support would tell you that.</p>
+
+<p>
+Dan concluded that he couldn't simply lend Lissa his computer. But he
+couldn't refuse to help her, because he loved her. Every chance to
+speak with her filled him with delight. And that she chose him to ask
+for help, that could mean she loved him too.</p>
+
+<p>
+Dan resolved the dilemma by doing something even more
+unthinkable—he lent her the computer, and told her his password.
+This way, if Lissa read his books, Central Licensing would think he
+was reading them. It was still a crime, but the SPA would not
+automatically find out about it. They would only find out if Lissa
+reported him.</p>
+
+<p>
+Of course, if the school ever found out that he had given Lissa his
+own password, it would be curtains for both of them as students,
+regardless of what she had used it for. School policy was that any
+interference with their means of monitoring students' computer use was
+grounds for disciplinary action. It didn't matter whether you did
+anything harmful—the offense was making it hard for the
+administrators to check on you. They assumed this meant you were
+doing something else forbidden, and they did not need to know what it
+was.</p>
+
+<p>
+Students were not usually expelled for this—not directly.
+Instead they were banned from the school computer systems, and would
+inevitably fail all their classes.</p>
+
+<p>
+Later, Dan would learn that this kind of university policy started
+only in the 1980s, when university students in large numbers began
+using computers. Previously, universities maintained a different
+approach to student discipline; they punished activities that were
+harmful, not those that merely raised suspicion.</p>
+
+<p>
+Lissa did not report Dan to the SPA. His decision to help her led to
+their marriage, and also led them to question what they had been
+taught about piracy as children. The couple began reading about the
+history of copyright, about the Soviet Union and its restrictions on
+copying, and even the original United States Constitution. They moved
+to Luna, where they found others who had likewise gravitated away from
+the long arm of the SPA. When the Tycho Uprising began in 2062, the
+universal right to read soon became one of its central aims.</p>
+
+<div class="announcement">
+<blockquote>
+<p><a href="http://defectivebydesign.org/ebooks.html">Join our
mailing list about the dangers of <span
class="removed"><del><strong>eBooks</a>.</p></strong></del></span>
<span class="inserted"><ins><em>e-books</a>.</p></em></ins></span>
+</blockquote>
+</div>
+
+<div id="AuthorsNote">
+<h3>Author's Notes</h3>
+
+<ul>
+<li>This story is supposedly a historical article that will be written in
+the future by someone else, describing Dan Halbert's youth under a
+repressive society shaped by the unjust forces that use “pirate” as
+propaganda. So it uses the terminology of that society.
+I have tried to project it forwards into something more visibly
+oppressive. See <a
+href="/philosophy/words-to-avoid.html#Piracy">“Piracy”</a>.
+</li>
+
+<li>
+<p>Computer-enforced restrictions on lending or reading books (and other
+kinds of published works) are known as DRM, short for
+“Digital Restrictions Management”. To
+eliminate DRM, the Free Software Foundation has
+established the <a href="http://DefectiveByDesign.org">Defective by
+Design</a> campaign. We ask for your support.</p>
+</li>
+
+<li>
+<p>The <span class="inserted"><ins><em>Electronic Frontier Foundation, a
separate organization not
+related to the Free Software Foundation, also campaigns against
+DRM.</p>
+</li>
+
+<li>
+<p>The</em></ins></span> following note has been updated several times
since the first
+publication of the story.</p>
+
+<p>
+The battle for the right to read is already being fought. Although it
+may take 50 years for our past freedoms to fade into obscurity, most
+of the specific repressive laws and practices described above have
+already been proposed; some have been enacted into law in the US and
+elsewhere. In the US, the 1998 Digital Millennium Copyright Act
+(DMCA) gave explicit government backing to the
+computer-enforced restrictions known as DRM, by making the
+distribution of programs that can break DRM a crime. The European
+Union imposed similar restrictions in a 2001 copyright directive, in a
+form not quite as strong.</p>
+
+<p>
+The US campaigns to impose such rules on the rest of the world through
+so-called “free trade” treaties.
+<a href="https://stallman.org/business-supremacy-treaties.html">
+Business-supremacy treaties</a> is a more fitting term for them, since
+they are designed to give business dominion over nominally democratic
+states. The DMCA's policy of criminalizing programs that
+break DRM is one of many unjust policies that these treaties impose
+across a wide range of fields.</p>
+
+<p>
+The US has imposed DMCA requirements on Australia, Panama, Colombia
+and South Korea through bilateral agreements, and on countries such as
+Costa Rica through another treaty, CAFTA. Obama has escalated the
+campaign with two new proposed treaties, the TPP and the TTIP. The
+TPP would impose the DMCA, along with many other wrongs, on 12
+countries on the Pacific Ocean. The TTIP would impose similar
+strictures on Europe. <span class="removed"><del><strong>Americans should
demand their congressional
+representatives reject the attempt to approve the TPP in the lame-duck
+session after the 2016 election.</p>
+
+<p>
+With Windows Vista, Microsoft admitted it had built in a back door:
+Microsoft can use it to forcibly install software
+“upgrades,” even if users consider them rather
to</strong></del></span> <span class="inserted"><ins><em>All these treaties
must</em></ins></span> be
+<span class="removed"><del><strong>downgrades. It can also order all machines
running Vista to refuse to
+run a certain device driver. The main purpose of Vista's clampdown on
+users was to impose DRM that users can't
overcome.</p></strong></del></span> <span
class="inserted"><ins><em>defeated, or
+abolished.</p></em></ins></span>
+
+<p>
+Even the World Wide Web Consortium has fallen under the shadow of the
+copyright industry; it is on the verge of approving a DRM system as an
+official part of the web specifications.</p>
+
+<p>
+Nonfree software tends to have <a href="/proprietary/">abusive
+features of many kinds</a>, which <span
class="removed"><del><strong>support</strong></del></span> <span
class="inserted"><ins><em>lead to</em></ins></span> the conclusion that
+<a href="/philosophy/free-software-even-more-important.html">you can
+never trust a nonfree program</a>. We must insist on free (libre)
+software only, and reject nonfree programs.</p>
+
+<p>
+<span class="inserted"><ins><em>With Windows Vista, Microsoft admitted it had
built in a back door:
+Microsoft can use it to forcibly install software
+“upgrades,” even if users consider them rather to be
+downgrades. It can also order all machines running Vista to refuse to
+run a certain device driver. The main purpose of Vista's clampdown on
+users was to impose DRM that users can't overcome. Of course, Windows
+10 is no better</p>
+
+<p></em></ins></span>
+One of the ideas in the story was not proposed in reality until 2002.
+This is the idea that the FBI and Microsoft will keep the
+root passwords for your personal computers, and not let you have
+them.</p>
+
+<p>
+The proponents of this scheme gave early versions names such as
+“trusted computing” and “Palladium”, but as
+ultimately put into use, it is called “secure boot”.</p>
+
+<p>
+What Microsoft keeps is not exactly a password in the traditional
+sense; no person ever types it on a terminal. Rather, it is a
+signature and encryption key that corresponds to a second key stored
+in your computer. This enables Microsoft, and potentially any web
+sites that cooperate with Microsoft, the ultimate control over what
+the user can do on per own computer. Microsoft is likely to use that
+control on behalf of the FBI when asked: it
+already <a href="/proprietary/malware-microsoft.html">shows
+the NSA security bugs in Windows</a> to exploit.</p>
+
+<p>
+Secure boot can be implemented in a way that permits the user to
+specify the signature key and decide what software to sign. In
+practice, PCs designed for Windows 10 carry only Microsoft's key, and
+whether the machine's owner can install any other system (such as
+GNU/Linux) is under Microsoft's control. We call this <em>restricted
+boot</em>.</p>
+
+<p>
+In 1997, when this story was first published, the SPA was
+threatening small Internet service providers, demanding they permit
+the SPA to monitor all users. Most ISPs surrendered when
+threatened, because they could not afford to fight back in court. One
+ISP, Community ConneXion in Oakland, California, refused the demand
+and was actually sued. The SPA later dropped the suit,
+but the DMCA gave it the power it sought.</p>
+
+<p>
+The SPA, which actually stands for Software Publishers
+Association, has been replaced in its police-like role by the Business
+Software Alliance. The BSA is not, today, an official
+police force; unofficially, it acts like one. Using methods
+reminiscent of the erstwhile Soviet Union, it invites people to inform
+on their coworkers and friends. A BSA terror campaign in
+Argentina in 2001 made slightly veiled threats that people sharing
+software would be raped in prison.</p>
+
+<p>
+The university security policies described above are not imaginary.
+For example, a computer at one Chicago-area university displayed this
+message upon login:</p>
+
+<blockquote><p>
+This system is for the use of authorized users only. Individuals using
+this computer system without authority or in the excess of their authority
+are subject to having all their activities on this system monitored and
+recorded by system personnel. In the course of monitoring individuals
+improperly using this system or in the course of system maintenance, the
+activities of authorized user may also be monitored. Anyone using this
+system expressly consents to such monitoring and is advised that if such
+monitoring reveals possible evidence of illegal activity or violation of
+University regulations system personnel may provide the evidence of such
+monitoring to University authorities and/or law enforcement officials.
+</p></blockquote>
+
+<p>
+This is an interesting approach to the Fourth Amendment: pressure most
+everyone to agree, in advance, to waive their rights under it.</p>
+</li>
+</ul>
+</div>
+
+<h3 id="BadNews">Bad News</h3>
+
+<p>
+The battle for the right to read is <span class="removed"><del><strong>already
in progress,</strong></del></span> <span class="inserted"><ins><em>going
against us so far.</em></ins></span>
+The enemy is organized, <span
class="removed"><del><strong>while</strong></del></span> <span
class="inserted"><ins><em>and</em></ins></span> we are <span
class="removed"><del><strong>not, so it is going against
us.</strong></del></span> <span class="inserted"><ins><em>not.</em></ins></span>
+</p>
+
+<p>Today's commercial
+<span class="removed"><del><strong>ebooks</strong></del></span>
+<span class="inserted"><ins><em>e-books</em></ins></span> <a
href="/philosophy/the-danger-of-ebooks.html"> abolish
+readers' traditional freedoms</a>. Amazon's e-book reader product,
+which I call the “Amazon Swindle” because it's designed to
+swindle readers out of the traditional freedoms of readers of books,
+is run by software with several
+demonstrated <a href="/proprietary/malware-kindle-swindle.html">Orwellian
+functionalities</a>. Any one of them calls for rejecting the product
+completely:</p>
+
+<ul>
+<li><p>It spies on everything the user does: it reports which book
the
+user is reading, and which page, and it reports when the user highlights
+text, and any notes the user enters.</p></li>
+
+<li><p>It has DRM, which is intended to block users from
+sharing copies.</p></li>
+
+<li><p>It has a back door with which Amazon can remotely erase any
book.
+In 2009, it erased thousands of copies of 1984, by George
Orwell.</p></li>
+
+<li><p>In case all that isn't Orwellian enough, there is a
universal
+back door with which Amazon can remotely change the software, and
+introduce any other form of nastiness.</p></li>
+</ul>
+
+<p>Amazon's e-book distribution is oppressive, too. It identifies the
+user and records what books the user obtains. It also requires users
+to agree to an antisocial contract that they won't share copies with
+others. My conscience tells me that, if I had agreed to such a
+contract, the lesser evil would be to defy it and share copies anyway;
+however, to be entirely good, <span
class="removed"><del><strong>we</strong></del></span> <span
class="inserted"><ins><em>I</em></ins></span> should not agree to it in the
first <span class="removed"><del><strong>place.</p></strong></del></span>
+<span class="inserted"><ins><em>place. Therefore, I refuse to agree to such
contracts, whether for
+software, for e-books, for music, or for anything
else.</p></em></ins></span>
+
+<p>If we want to stop the bad news and create some good news, we need
+to organize and fight. <span
class="removed"><del><strong>The</strong></del></span> <span
class="inserted"><ins><em>Subscribe to the</em></ins></span>
+FSF's <a href="http://defectivebydesign.org"> Defective by
Design</a>
+campaign <span class="removed"><del><strong>has made a start; subscribe to the
campaign's mailing
+list</strong></del></span> to lend a hand. <span
class="removed"><del><strong>And</strong></del></span> <span
class="inserted"><ins><em>You
+can</em></ins></span> <a href="http://www.fsf.org/associate">join the
FSF</a> to <span class="removed"><del><strong>help
fund</strong></del></span> <span class="inserted"><ins><em>support
+our work more generally. There is also a <a href="/help/help.html">list
of ways
+to participate in</em></ins></span> our <span
class="removed"><del><strong>work.</strong></del></span> <span
class="inserted"><ins><em>work</a>.</em></ins></span>
+</p>
+
+<h3 id="References">References</h3>
+
+<ul>
+ <li>The administration's “White Paper”: Information
+ Infrastructure Task Force, Intellectual Property [<a
+ href="/philosophy/not-ipr.html">sic</a>] and the
+ National Information Infrastructure: The Report of the Working
+ Group on Intellectual Property [sic] Rights (1995).</li>
+
+ <li><a
href="http://www.wired.com/wired/archive/4.01/white.paper_pr.html">An
+ explanation of the White Paper:
+ The Copyright Grab</a>, Pamela Samuelson, Wired, Jan.
1996</li>
+
+ <li><a
href="http://www.law.duke.edu/boylesite/sold_out.htm">Sold Out</a>,
+ James Boyle, New York Times, 31 March 1996</li>
+
+ <li><a
href="http://web.archive.org/web/20130508120533/http://www.interesting-people.org/archives/interesting-people/199611/msg00012.html">Public
Data or Private Data</a>,
+ Washington Post, 4 Nov 1996. </li>
+
+ <li><a <span
class="removed"><del><strong>href="http://www.public-domain.org/">Union</strong></del></span>
<span
class="inserted"><ins><em>href="https://web.archive.org/web/20151113122141/http://public-domain.org/">Union</em></ins></span>
for the Public
+ Domain</a>—an organization which aims to resist and
+ reverse the overextension of copyright and patent powers.</li>
+</ul>
+
+<hr />
+<blockquote id="fsfs"><p class="big">This essay is published
+in <a
href="http://shop.fsf.org/product/free-software-free-society/"><cite>Free
+Software, Free Society: The Selected Essays of Richard
+M. Stallman</cite></a>.</p></blockquote>
+
+<h5>Other Texts to Read</h5>
+
+<ul>
+ <li><a href="/philosophy/philosophy.html">Philosophy of the
+ GNU Project</a></li>
+ <li><a
href="http://www.computerworld.com/article/2596679/networking/copy-protection--just-say-no.html";
+ id="copy-protection">Copy Protection: Just Say No</a>,
+ published in Computer World.</li>
+</ul>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF. Broken links and other corrections or suggestions can be sent
+to <a
href="mailto:address@hidden"><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden">
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+ files generated as part of manuals) on the GNU web server should
+ be under CC BY-ND 4.0. Please do NOT change or remove this
+ without talking with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the
+ document. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright © 1996, 2002, 2007, 2009, 2010, 2014, 2015, 2016
Richard Stallman</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
+Commons Attribution-NoDerivatives 4.0 International
License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2016/10/31 22:57:29 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/philosophy right-to-read.uk.html po/right-t...,
GNUN <=