summaryrefslogtreecommitdiff
path: root/talermerchantdemos/blog/articles/en/surveillance-testimony.html
diff options
context:
space:
mode:
Diffstat (limited to 'talermerchantdemos/blog/articles/en/surveillance-testimony.html')
-rw-r--r--talermerchantdemos/blog/articles/en/surveillance-testimony.html123
1 files changed, 123 insertions, 0 deletions
diff --git a/talermerchantdemos/blog/articles/en/surveillance-testimony.html b/talermerchantdemos/blog/articles/en/surveillance-testimony.html
new file mode 100644
index 0000000..11fe655
--- /dev/null
+++ b/talermerchantdemos/blog/articles/en/surveillance-testimony.html
@@ -0,0 +1,123 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.86 -->
+<title>Surveillance Testimony - GNU Project - Free Software Foundation</title>
+ <!--#include virtual="/philosophy/po/surveillance-testimony.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Surveillance Testimony</h2>
+
+<p><em>Richard Stallman's statement to the Cambridge City Council, Jan 22, 2018,
+about the proposed Cambridge surveillance ordinance.</em></p>
+<hr class="thin" />
+
+<p><strong>Mayor McGovern:</strong> Thank you. Richard Stallman followed by Elaine DeRosa.</p>
+
+<p><strong>RMS:</strong> I'm here to speak about the proposed surveillance ordinance.
+I've got a copy of what I printed out, and I have some suggestions.</p>
+
+<p>First of all there's a Definition of &ldquo;surveillance&rdquo; which I think is
+too narrow. In addition to &ldquo;movements, behavior and actions,&rdquo; it
+should include communications.</p>
+
+<p>Furthermore, instead of just saying &ldquo;in a matter that is reasonably
+likely to raise concerns,&rdquo; any recording of what is observed should be
+assumed to raise civil liberties concerns.</p>
+
+<p>There's also a definition of &ldquo;surveillance technology&rdquo;, which I think is
+far too limited.</p>
+
+<p>I suggest that any physical device or system including computers running
+software that has surveillance capability is surveillance technology.
+Any technology that can do surveillance is surveillance technology.</p>
+
+<p>The definition of &ldquo;surveillance capability&rdquo; I think is pretty good.</p>
+
+<p>In addition, when it comes to what to do about surveillance
+technology, the Emergency Permission seems far too loose. It would be
+easy to interpret this such that one could decide there's nowadays
+some sort of threat, and there always will be [that threat], so
+surveillance is permitted on an emergency basis forever.</p>
+
+<p>Well, that's the kind of false emergency that we shouldn't accept.
+This requirement should be specific and clear enough that that can't
+pass under it.</p>
+
+<p>I suggest treating it like a wiretap or searching people's houses.</p>
+
+<p>Now there are times when it's possible to search someone's house
+urgently. That's permitted. But in general you have to get a court
+order [to do a search].</p>
+
+<p>And I think that same requirement should apply to any kind of surveillance
+that hasn't gone through the regular process.</p>
+
+<p>[Item] number 9 talks about &ldquo;persons injured in violation of the Ordinance&rdquo;,
+but I don't think there's a definition of what it means to be injured.</p>
+
+<p>I'd like to suggest that to be surveilled is to be injured.</p>
+
+<p>Thank you.</p>
+
+</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 &amp; GNU inquiries to
+<a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</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:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</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:web-translators@gnu.org">
+ &lt;web-translators@gnu.org&gt;</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 &copy; 2018 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: 2018/12/15 14:02:39 $
+<!-- timestamp end -->
+</p>
+</div>
+</div><!-- for class="inner", starts in the banner include -->
+</body>
+</html>