www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www licenses/fdl-howto-opt.ja.html licenses/gpl...


From: GNUN
Subject: www licenses/fdl-howto-opt.ja.html licenses/gpl...
Date: Tue, 28 Jun 2016 03:59:45 +0000 (UTC)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     16/06/28 03:59:44

Modified files:
        licenses       : fdl-howto-opt.ja.html gpl-faq.ja.html 
                         license-list.ja.html licenses.ja.html 
        licenses/old-licenses: fdl-1.2-translations.ja.html 
        licenses/old-licenses/po: fdl-1.2-translations.ja-en.html 
        licenses/po    : fdl-howto-opt.ja-en.html fdl-howto-opt.ja.po 
                         gpl-faq.ja-en.html gpl-faq.ja.po 
                         license-list.ja-en.html license-list.ja.po 
                         licenses.ja-en.html licenses.ja.po 
        philosophy     : basic-freedoms.ja.html 
        philosophy/po  : basic-freedoms.ja-en.html basic-freedoms.ja.po 
                         who-does-that-server-really-serve.nl.po 
                         who-does-that-server-really-serve.translist 
        proprietary    : proprietary-sabotage.ja.html 
        proprietary/po : proprietary-sabotage.de.po 
                         proprietary-sabotage.fr.po 
                         proprietary-sabotage.it.po 
                         proprietary-sabotage.ja-diff.html 
                         proprietary-sabotage.ja.po 
                         proprietary-sabotage.pot 
                         proprietary-sabotage.ru.po 
Added files:
        philosophy     : who-does-that-server-really-serve.nl.html 
        philosophy/po  : who-does-that-server-really-serve.nl-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/fdl-howto-opt.ja.html?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-faq.ja.html?cvsroot=www&r1=1.74&r2=1.75
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/license-list.ja.html?cvsroot=www&r1=1.79&r2=1.80
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/licenses.ja.html?cvsroot=www&r1=1.45&r2=1.46
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/fdl-1.2-translations.ja.html?cvsroot=www&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/fdl-1.2-translations.ja-en.html?cvsroot=www&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/fdl-howto-opt.ja-en.html?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/fdl-howto-opt.ja.po?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.ja-en.html?cvsroot=www&r1=1.23&r2=1.24
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.ja.po?cvsroot=www&r1=1.68&r2=1.69
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.ja-en.html?cvsroot=www&r1=1.32&r2=1.33
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.ja.po?cvsroot=www&r1=1.139&r2=1.140
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/licenses.ja-en.html?cvsroot=www&r1=1.30&r2=1.31
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/licenses.ja.po?cvsroot=www&r1=1.60&r2=1.61
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/basic-freedoms.ja.html?cvsroot=www&r1=1.33&r2=1.34
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/who-does-that-server-really-serve.nl.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/basic-freedoms.ja-en.html?cvsroot=www&r1=1.23&r2=1.24
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/basic-freedoms.ja.po?cvsroot=www&r1=1.20&r2=1.21
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/who-does-that-server-really-serve.nl.po?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/who-does-that-server-really-serve.translist?cvsroot=www&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/who-does-that-server-really-serve.nl-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/proprietary-sabotage.ja.html?cvsroot=www&r1=1.13&r2=1.14
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-sabotage.de.po?cvsroot=www&r1=1.51&r2=1.52
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-sabotage.fr.po?cvsroot=www&r1=1.48&r2=1.49
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-sabotage.it.po?cvsroot=www&r1=1.51&r2=1.52
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-sabotage.ja-diff.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-sabotage.ja.po?cvsroot=www&r1=1.49&r2=1.50
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-sabotage.pot?cvsroot=www&r1=1.27&r2=1.28
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-sabotage.ru.po?cvsroot=www&r1=1.65&r2=1.66

Patches:
Index: licenses/fdl-howto-opt.ja.html
===================================================================
RCS file: /web/www/www/licenses/fdl-howto-opt.ja.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- licenses/fdl-howto-opt.ja.html      3 Feb 2016 09:13:13 -0000       1.11
+++ licenses/fdl-howto-opt.ja.html      28 Jun 2016 03:59:43 -0000      1.12
@@ -25,7 +25,7 @@
       Permission is granted to copy, distribute and/or modify this
       document under the terms of the GNU Free Documentation License,
       Version 1.3 or any later version published by the Free Software
-      Foundation; with no Invariant Sections, no Front-Cover Texts and
+      Foundation; with no Invariant Sections, no Front-Cover Texts, and
       no Back-Cover Texts.  A copy of the license is included in the
       section entitled "GNU Free Documentation License".
 </pre>
@@ -130,7 +130,7 @@
 
 <!-- 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 3.0 US.  Please do NOT change or remove this
+     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
@@ -144,11 +144,11 @@
      
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright &copy; 2000, 2008, 2014 Free Software Foundation, Inc.</p>
+<p>Copyright &copy; 2000, 2008, 2014, 2016 Free Software Foundation, Inc.</p>
 
 <p>このページは<a rel="license"
-href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.ja";>Creative
-Commons Attribution-NoDerivs 3.0 United States 
License</a>の条件で許諾されます。</p>
+href="http://creativecommons.org/licenses/by-nd/4.0/deed.ja";>Creative
+Commons Attribution-NoDerivs 4.0 International 
License</a>の条件で許諾されます。</p>
 
 <!--#include virtual="/server/bottom-notes.ja.html" -->
 <div class="translators-credits">
@@ -159,7 +159,7 @@
 <p class="unprintable"><!-- timestamp start -->
 最終更新:
 
-$Date: 2016/02/03 09:13:13 $
+$Date: 2016/06/28 03:59:43 $
 
 <!-- timestamp end -->
 </p>

Index: licenses/gpl-faq.ja.html
===================================================================
RCS file: /web/www/www/licenses/gpl-faq.ja.html,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -b -r1.74 -r1.75
--- licenses/gpl-faq.ja.html    14 Apr 2016 10:00:24 -0000      1.74
+++ licenses/gpl-faq.ja.html    28 Jun 2016 03:59:43 -0000      1.75
@@ -100,7 +100,7 @@
 href="#GPLAndNonfreeOnSameMachine">あるGPLの及ぶプログラム
と、それと関係のない不自由なプログラム
を同じコンピュータに置いても問題ありませんか?</a></li>
   
     <li><a
-href="#CanIDemandACopy">GPLの及ぶプログラム
のコピーを誰かが持っていると知っているå 
´åˆã€ã‚ãŸã—はかれにコピーを下さいと要求できますか?</a></li>
+href="#CanIDemandACopy">GPLの及ぶプログラム
のコピーを誰かが持っていると知っているå 
´åˆã€ã‚ãŸã—はその人にコピーを下さいと要求できますか?</a></li>
 
     <li><a
 href="#WhatDoesWrittenOfferValid">この「いかなる第三者
に対しても法的に有効な書面による申し出」とは何のことですか?
@@ -362,7 +362,7 @@
 href="#v3ConditionalWarranty">GPLv3が及ぶプログラムを配布したå 
´åˆã€ãƒ¦ãƒ¼ã‚¶ãŒãã®ãƒ—ログラム
を改変したら無効となるような保証を提供することはできますか?</a></li>
 
     <li><a
-href="#v3CoworkerConveying">GPLv3の及ぶプログラム
のコピーを会社の同僚にあげたå 
´åˆã€ãã®ã‚³ãƒ”ーをかれに「運搬」したことになりますか?</a></li>
+href="#v3CoworkerConveying">GPLv3の及ぶプログラム
のコピーを会社の同僚にあげたå 
´åˆã€ãã®ã‚³ãƒ”ーをその人に「運搬」したことになりますか?</a></li>
 
     <li><a
 
href="#SourceInCVS">もし、わたしがFTPサーバでバイナリを提供し、ソースは、CVSやSubversionのようなバージョン・コントロール・システãƒ
 
のソースコード・リポジトリへのリンクによって提供したå 
´åˆã€ã‚ãŸã—はGPLv3を遵守しているでしょうか?</a></li>
@@ -616,11 +616,11 @@
 <dd><p>その通りです。</p></dd>
 
 
-<dt id="CanIDemandACopy">GPLの及ぶプログラム
のコピーを誰かが持っていると知っているå 
´åˆã€ã‚ãŸã—はかれにコピーを下さいと要求できますか? <span
+<dt id="CanIDemandACopy">GPLの及ぶプログラム
のコピーを誰かが持っていると知っているå 
´åˆã€ã‚ãŸã—はその人にコピーを下さいと要求できますか? 
<span
 class="anchor-reference-id">(<a href="#CanIDemandACopy"
 >#CanIDemandACopy</a>)</span></dt>
 <dd><p>
-いいえ。GPLは、かれに<em>かれがそれを選んだå 
´åˆã€ãã®æ™‚に</em>、プログラムのコピーを作成し、再é…
å¸ƒã™ã‚‹è¨±å¯ã‚’与えます。それをかれが選ぶとき、かれは、プログラãƒ
 ã‚’再配布しない権利も持つのです。</p></dd>
+いいえ。GPLは、ある人に<em>もし、その人がそうすることを選んã
 å ´åˆã€ãã®æ™‚に</em>、プログラムのコピーを作成し、再é…
å¸ƒã™ã‚‹è¨±å¯ã‚’与えます。その人は、プログラムを再é…
å¸ƒã™ã‚‹é¸æŠžã‚’しない権利も持つのです。</p></dd>
 
 
 <dt id="WhatDoesWrittenOfferValid">この「いかなる第三者
に対しても法的に有効な書面による申し出」とは何のことですか?
@@ -1096,7 +1096,7 @@
 たとえば、わたしのプログラム
がハードウェアの設計に使われているとして、その設計図も自由でなければならないと要求することはできるでしょうか?
 <span
 class="anchor-reference-id">(<a href="#GPLOutput" >#GPLOutput</a>)</span></dt>
 <dd><p>
-一般的に言って、それは法的に不可能です。著作権法は人ã€
…があなたのプログラム
とかれらのデータを使って作った出力結果の利用に関して、あなたに何の発言権も与えていません。ユーザがあなたのプログラãƒ
 ã‚’使ってかれ自身のデータを入力ないし変換したå 
´åˆã€å‡ºåŠ›çµæžœã®è‘—作権はかれに属すのであって、あなたにではありません。もっと一般的に言えば、あるプログラãƒ
 ãŒå…¥åŠ›ã‚’他の形式に変換するå 
´åˆã€å‡ºåŠ›çµæžœã®è‘—作権の状態は、生成の元となったå…
¥åŠ›ã®ãã‚Œã‚’継承するのです。</p>
+一般的に言って、それは法的に不可能です。著作権法は人ã€
…があなたのプログラム
とかれらのデータを使って作った出力結果の利用に関して、あなたに何の発言権も与えていません。ユーザがあなたのプログラãƒ
 ã‚’使ってその人自身のデータを入力ないし変換したå 
´åˆã€å‡ºåŠ›çµæžœã®è‘—作権はその人に属すのであって、あなたにではありません。もっと一般的に言えば、あるプログラãƒ
 ãŒå…¥åŠ›ã‚’他の形式に変換するå 
´åˆã€å‡ºåŠ›çµæžœã®è‘—作権の状態は、生成の元となったå…
¥åŠ›ã®ãã‚Œã‚’継承するのです。</p>
 
 
<p>ですから、あなたが出力結果の利用に関して発言権を持つ唯一の方法は、出力結果の本質的な部分が(多かれ少なかれ)あなたのプログラãƒ
 ã®ãƒ†ã‚­ã‚¹ãƒˆã‹ã‚‰è¤‡è£½ã•ã‚Œã¦ã„ã‚‹å 
´åˆã§ã™ã€‚たとえば、Bison(上記を参ç…
§)の出力結果は、もしわたしたちがこの特定のケースに関して例外を設けなければ、GNU
 GPLが及んでいたでしょう。</p>
@@ -1314,9 +1314,8 @@
 もしわたしがGPLが使われたプログラム
の著作権を有しているならば、わたしも著作権譲渡を要求すべきでしょうか?
 もしそうなら、どうやって?  <span
 class="anchor-reference-id">(<a href="#AssignCopyright"
 >#AssignCopyright</a>)</span></dt>
-<dd><p>
-わたしたちの弁護士は、侵害者に対して法廷で<a
-href="/licenses/why-assign.html">GPLを強制する上で最良の立å 
´</a>に立つには、プログラムの著作権の状æ…
‹ã‚’可能な限り単純に保つべきだ
と述べています。このため、わたしたちは貢献者
のみなさんに対し、FSFに対するご自分の貢献に関する著作権を譲渡するか、著作権を主張せずパブリックドメインに置くことをお願いしています。</p>
+<dd><p> わたしたちの弁護士は、侵害者に対して法廷で<a
+href="/licenses/why-assign.html">GPLを強制する上で最良の立å 
´</a>に立つには、プログラムの著作権の状æ…
‹ã‚’可能な限り単純に保つべきだ
と述べています。このため、わたしたちは貢献者
のみなさんに対し、FSFに対するご自分の貢献に関する著作権を譲渡するか、貢献に関して著作権を主張しないことをお願いしています。</p>
 
 <p>また、わたしたちは個々の貢献者が彼らの雇用者
(もしいれば)からの著作権放棄声明を得て、そういった雇用è€
…
たちが将来になって貢献を所有していると主張することがないよう保証することもお願いしています。</p>
 
@@ -1552,10 +1551,10 @@
 
<p>しかしながら、その組織がコピーをほかの組織や個人に移したとき、それはé
…å¸ƒã¨ãªã‚Šã¾ã™ã€‚特に、そのå 
´æ‰€ä»¥å¤–での利用のためにコントラクタにコピーを提供することは、é
…å¸ƒã§ã™ã€‚</p></dd>
 
 
-<dt id="StolenCopy">誰かがGPLの及ぶプログラムのバージョンがå…
¥ã£ãŸCDを盗みました。GPLは、かれに、このバージョンを再é…
å¸ƒã™ã‚‹æ¨©åˆ©ã‚’与えますか? <span
+<dt id="StolenCopy">誰かがGPLの及ぶプログラムのバージョンがå…
¥ã£ãŸCDを盗みました。GPLは、その盗人に、このバージョンを再é
…å¸ƒã™ã‚‹æ¨©åˆ©ã‚’与えますか? <span
 class="anchor-reference-id">(<a href="#StolenCopy" 
>#StolenCopy</a>)</span></dt>
 <dd><p>
-そのバージョンが(盗み以前に)既にどこかにリリースされているのであれば、盗んã
 äººã¯ãŠãã‚‰ãã‚³ãƒ”ーを作成し、再é…
å¸ƒã™ã‚‹æ¨©åˆ©ã‚’GPLのもとで有するでしょう。しかし、CDを盗んã
 ã“とで刑務所にå…
¥ã‚‹ã®ãªã‚‰ã°ã€ã‹ã‚Œã¯ãã†ã™ã‚‹å‰ã«è§£æ”¾ã•ã‚Œã‚‹ã¾ã§å¾…つ必
要があるかもしれません。</p>
+そのバージョンが(盗み以前に)既にどこかにリリースされているのであれば、盗人はおそらくコピーを作成し、再é
…
å¸ƒã™ã‚‹æ¨©åˆ©ã‚’GPLのもとで有するでしょう。しかし、CDを盗んã
 ã“とで刑務所にå…
¥ã‚‹ã®ãªã‚‰ã°ã€ç›—人はそうする前に解放されるまで待つ必
要があるかもしれません。</p>
 
 
<p>もし、問題のそのバージョンが、発表されていないもので、ある会社によってそのトレード・シークレットと考えられているのならば、その他の状況にもよりますが、それをå
…
¬è¡¨ã™ã‚‹ã“とはトレード・シークレットの法律の違反となる可能性があります。GPLはこれを変更はできません。もし、その会社がそのバージョンをリリースしようとし、それでもなお、トレード・シークレットとみなそうとするのならば、それはGPLに違反するでしょう。しかし、その会社がそのバージョンをリリースしていなければ、そのような違反は起こりません。</p></dd>
 
@@ -1878,7 +1877,7 @@
 <dt id="DRMProhibited">GPLv3はDRMを禁止しますか? <span 
class="anchor-reference-id">(<a
 href="#DRMProhibited" >#DRMProhibited</a>)</span></dt>
 <dd><p>
-禁止しません。GPLv3でリリースされたコードを使って、あなたの望むあらゆる種類のDRM技術を開発することが可能です。しかし、こうするå
 ´åˆã€ç¬¬3節は、そのシステム
は効果的な技術的「保護」手段とはみなされないことになる、と述べています。これは、ã
 ã‚Œã‹ãŒDRMを破った場合、かれはかれのソフトウェアをé…
å¸ƒã™ã‚‹ã“とが自由にでき、DMCAや同様な法律によって妨げられることはないということです。</p>
+禁止しません。GPLv3でリリースされたコードを使って、あなたの望むあらゆる種類のDRM技術を開発することが可能です。しかし、こうするå
 ´åˆã€ç¬¬3節は、そのシステム
は効果的な技術的「保護」手段とはみなされないことになる、と述べています。これは、ã
 ã‚Œã‹ãŒDRMを破った場合、その人はかれのソフトウェアをé…
å¸ƒã™ã‚‹ã“とが自由にでき、DMCAや同様な法律によって妨げられることはないということです。</p>
 
 <p>いつもどおり、GNU GPLはソフトウェアで人々
が何をするか制限をせず、(ソフトウェアが)ほかの人を制限することを禁止するã
 ã‘です。</p></dd>
 
@@ -1896,7 +1895,7 @@
 >#GiveUpKeys</a>)</span></dt>
 <dd><p>
 いいえ。署名鍵をリリースする必
要があるかもしれないただ
一つのケースは、GPLのソフトウェアをUser
-Productの中に運搬し、そのハードウェアが、そのソフトウェアを動作させる前に有効な暗号署名を確認するå
 
´åˆã§ã™ã€‚この特定のケースでは、そのデバイスを所有する誰もに対して、要求があれば、署名し、かれのデバイスに改変したソフトウェアをインストールし実行できるよう、鍵を提供するå¿
…要があるでしょう。デバイスの個々
が異なる鍵を使っている場合、それぞれの購入者
には、かれのデバイスの鍵だけを与える必
要があります。</p></dd>
+Productの中に運搬し、そのハードウェアが、そのソフトウェアを動作させる前に有効な暗号署名を確認するå
 
´åˆã§ã™ã€‚この特定のケースでは、そのデバイスを所有する誰もに対して、要求があれば、署名し、そのデバイスに改変したソフトウェアをインストールし実行できるよう、鍵を提供するå¿
…要があるでしょう。デバイスの個々
が異なる鍵を使っている場合、それぞれの購入者
には、そのデバイスの鍵だけを与える必
要があります。</p></dd>
 
 
 <dt id="v3VotingMachine">GPLv3は投票者
が投票マシンで動いているソフトウェアを改変することを要請しますか?
 <span
@@ -1974,7 +1973,7 @@
 あなたが必
要なことのすべては、あなたのインタフェースで、ユーザに対し、「適切な法律上の告知」が容易に利用可能となることを確実にすることです。たとえば、音声インタフェースを書いたå
 
´åˆã€å‘ŠçŸ¥ã‚’音読するコマンドを含むことができるでしょう。</p></dd>
 
 
-<dt id="v3CoworkerConveying">GPLv3の及ぶプログラム
のコピーを会社の同僚にあげたå 
´åˆã€ãã®ã‚³ãƒ”ーをかれに「運搬」したことになりますか? 
<span
+<dt id="v3CoworkerConveying">GPLv3の及ぶプログラム
のコピーを会社の同僚にあげたå 
´åˆã€ãã®ã‚³ãƒ”ーをその人に「運搬」したことになりますか?
 <span
 class="anchor-reference-id">(<a href="#v3CoworkerConveying"
 >#v3CoworkerConveying</a>)</span></dt>
 <dd><p>
@@ -2141,10 +2140,8 @@
 <dt 
id="AGPLv3ServerAsUser">あるネットワーク・クライアントのソフトウェアがAGPLv3でリリースされたå
 
´åˆã€ã‚„りとりするサーバにソースコードを提供できるようにしなければなりませんか?
 <span class="anchor-reference-id">(<a href="#AGPLv3ServerAsUser"
 >#AGPLv3ServerAsUser</a>)</span></dt>
-<dd><p>
-どのようなå…
¸åž‹çš„なサーバ=クライアントの関係においても、それは要求されるべきではありません。AGPLv3は「コンピュータネットワークを通じてé
 
隔でそれとやりとりするすべてのユーザ」に対し、あるプログラãƒ
 
がソースコードを提供することを要求します。ほとんどのサーバ=クライアントのアーキテクチャでは、そのクライアントとやりとりするそのサーバ・オペレータが「ユーザ」であると議論するのは単に不合理で、何の意味を持たないでしょう。</p>
-
-<p>HTTPを例として考えましょう。すべてのHTTPクライアントはサーバにある機能を提供することを期å¾
…
します。サーバは形式に則った要求に対し、仕様に則った応答を返すべきです。その逆は真ではありません。サーバはクライアントが、サーバの送ったデータに対してなにか特定のことをなすと仮定することはできません。クライアントはWebブラウザかもしれないし、RSSリーダ、スパイダ、ネットワーク監視ツール、あるいは特別の目的のプログラãƒ
 
かもしれません。クライアントが何をするかについて、サーバは絶対的にどのような仮定も置くべきではありません。ですから、サーバ・オペレータがそのソフトウェアのユーザであると考えることには、意味を持つ方法がないのです。</p></dd>
+<dd>
+    <p>AGPLv3は「コンピュータネットワークを通じて遠
隔でそれとやりとりするすべてのユーザ」に対し、あるプログラãƒ
 
がソースコードを提供することを要求します。そのプログラãƒ
 
を「クライアント」もしくは「サーバ」と呼ぶかどうかは関係しません。問うべき問題は、ある人がネットワークを通じてé
 éš”でそのプログラムでやりとりするかどうかです。 </p></dd>
 
 <dt 
id="AGPLProxy">プロキシサーバを実行するソフトウェアがAGPLでライセンスされているとします。そのコードとやりとりするユーザに、どのようにソースの申し出を提供できるでしょうか?<span
 class="anchor-reference-id">(<a href="#AGPLProxy">#AGPLProxy</a>)</span></dt>
@@ -2409,7 +2406,7 @@
 <p class="unprintable"><!-- timestamp start -->
 最終更新:
 
-$Date: 2016/04/14 10:00:24 $
+$Date: 2016/06/28 03:59:43 $
 
 <!-- timestamp end -->
 </p>

Index: licenses/license-list.ja.html
===================================================================
RCS file: /web/www/www/licenses/license-list.ja.html,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -b -r1.79 -r1.80
--- licenses/license-list.ja.html       14 Apr 2016 08:33:51 -0000      1.79
+++ licenses/license-list.ja.html       28 Jun 2016 03:59:43 -0000      1.80
@@ -1019,7 +1019,8 @@
 OpenSSLライセンス</a> <span class="anchor-reference-id"> (<a
 href="#OpenSSL">#OpenSSL</a>)</span></dt>
 <dd>
-<p>OpenSSLのライセンスは2種類のライセンスが連結されたものです。そのうち一つはSSLeayのライセンスです。あなたは両方に従わなければなりません。この二è€
…
の結合は、コピーレフトの自由ソフトウェアライセンスとなっており、これはGNU
+<p>OpenSSLのライセンスは2種類のライセンスが連結されたものです。一つは&ldquo;OpenSSL
+License&rdquo;と呼ばれ、もう一つはSSLeayのライセンスです。あなたは両方に従わなければなりません。この二è€
…
の結合は、コピーレフトの自由ソフトウェアライセンスとなっており、これはGNU
 GPLと両立しません。また、このライセンスは <a 
href="#OriginalBSD">オリジナルBSDライセンス</a>や<a
 href="#apache1">Apache 1ライセンス</a>のような宣伝条項
を有しています。</p>
 
@@ -1894,7 +1895,7 @@
 <p class="unprintable"><!-- timestamp start -->
 最終更新:
 
-$Date: 2016/04/14 08:33:51 $
+$Date: 2016/06/28 03:59:43 $
 
 <!-- timestamp end -->
 </p>

Index: licenses/licenses.ja.html
===================================================================
RCS file: /web/www/www/licenses/licenses.ja.html,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -b -r1.45 -r1.46
--- licenses/licenses.ja.html   13 Feb 2016 09:57:16 -0000      1.45
+++ licenses/licenses.ja.html   28 Jun 2016 03:59:43 -0000      1.46
@@ -10,6 +10,26 @@
 <!--#include virtual="/server/banner.ja.html" -->
 <h2>ライセンス</h2>
 
+<div class="summary">
+<h3 class="no-display">もくじ</h3>
+<ul>
+  <li><a href="#Evaluation">ライセンスの評価</a></li>
+  <li><a 
href="#CommonResources">わたしたちのソフトウェア・ライセンスのå
…±é€šã®ãƒªã‚½ãƒ¼ã‚¹</a></li>
+  <li><a href="#GPL">GNU一般公衆ライセンス</a></li>
+  <li><a href="#LGPL">GNU劣等一般公衆ライセンス</a></li>
+  <li><a href="#AGPL">GNUアフェロ一般公衆ライセンス</a></li>
+  <li><a href="#FDL">GNU自由文書ライセンス</a></li>
+  <li><a href="#Exceptions">GNUライセンスの例外</a></li>
+  <li><a href="#LicenseURLs">ライセンスのURL</a></li>
+  <li><a href="#UnofficialTransl">非公式な翻訳</a></li>
+  <li><a href="#VerbatimCopying">そのままの複製とé…
å¸ƒã«ã¤ã„て</a></li>
+  <li><a 
href="#FSLicenses">自由ソフトウェアのライセンス一覧</a></li>
+  <li><a href="#WhatIsCopyleft">コピーレフトとはなにか?</a></li>
+  <li><a 
href="#OtherWorks">その他の作品のためのライセンス</a></li>
+</ul>
+<hr class="no-display" />
+</div>
+
 <p>
 公開されるソフトウェアは<a
 
href="/philosophy/free-sw.html">自由ソフトウェア</a>であるべきです。自由ソフトウェアとするには、自由ソフトウェアのもとでリリースされるå¿
…要があります。通常、わたしたちは、<a
@@ -31,13 +51,13 @@
 
 <p>また、<a 
href="/licenses/bsd.html">BSDのライセンスの問題</a>を論じたページもあります。</p>
 
-<h3>ライセンスの評価</h3>
+<h3 id="Evaluation">ライセンスの評価</h3>
 
 <p>ライセンスに遭遇して、それが<a
 href="/licenses/license-list.html">ライセンス一覧</a>にないå 
´åˆã€è‡ªç”±ãªãƒ©ã‚¤ã‚»ãƒ³ã‚¹ã‹ã©ã†ã‹è©•ä¾¡ã‚’わたしたちに問い合わせすることができます。ライセンスのコピーを(それをみつけたURLとともに)<a
 href="mailto:address@hidden";>address@hidden</a>までメールしてくだ
さい。わたしたちのスタッフと役員会のライセンシングの専門家がレビューします。ライセンスに普通でない条件があったり、理念的に難しい問題があるå
 
´åˆãŒã‚りますから、すばやく決定できる、とは約束できません。</p>
 
-<h3>わたしたちのソフトウェア・ライセンスのå…
±é€šã®ãƒªã‚½ãƒ¼ã‚¹</h3>
+<h3 
id="CommonResources">わたしたちのソフトウェア・ライセンスのå…
±é€šã®ãƒªã‚½ãƒ¼ã‚¹</h3>
 
 
<p>わたしたちのさまざまなライセンスを理解し用いることを助けるために、たくさんのリソースがあります:</p>
 
@@ -170,7 +190,7 @@
 <p><a href="old-licenses/">古いライセンスのページ</a>も見てくだ
さい。</p>
 
 
-<h3>非公式な翻訳</h3>
+<h3 id="UnofficialTransl">非公式な翻訳</h3>
 
 <p>
 
法的に言えば、オリジナル(英語)版のライセンスが、そのライセンスを用いたGNUプログラãƒ
 ã‚„他のプログラムの実際の配布条項
を規定します。しかし、人々
がライセンスをよりよく理解する一助として、わたしたちは非å
…
¬å¼ãªç¿»è¨³ã«é–¢ã™ã‚‹ã‚ãŸã—たちの規則に従う限り、他の言語への翻訳をå
…¬é–‹ã™ã‚‹ã“とを許可しています。
@@ -185,18 +205,20 @@
 
 <h3 id="VerbatimCopying">そのままの複製と配布について</h3>
 
-<p>標準的なGNUウェブページの著作権条項は今は<a
-href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative Commons
-Attribution-NoDerivs 3.0 United States
-License</a>です。かつては(いくつかのページについては今もなお)、<em><span
-class="highlight">本文にこの著作権表示を残す限り、この文章
全体のいかなる媒体における、そのままの複製およびé…
å¸ƒã‚‚、使用料なしに許可する</span></em>、でした。この&ldquo;verbatim
-license&rdquo;については、以下のエバン・モグレンによる解説に留意して下さい:</p>
+<p>GNUウェブページのための標準の著作権の条項
は、現在、<a
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.ja";>Creative
+Commons Attribution-NoDerivs 3.0 United States
+License</a>です。かつては(そして現在もいくつかのページは)、こうでした:</p>
 
-<p>
-「『いかなる媒体における、そのままの複製』というフレーズの意図は、ページのヘッダやフッタその他の文書整形に関する状æ
…‹ã¯ä¿æŒã—なくても構わないということです。ただ
し、ハイパーリンクの使えるメディアもそうでないメディアでも、ウェブリンクの(脚注や、非HTMLのメディアではその他の形式のURL表示による)保持は要求されます」
-</p>
+<blockquote><p>この記事全体のそのままのコピーと配布はå…
¨ä¸–界的に許諾されます。ロイヤリティなしで、いかなる媒体でも、この告知が保存される限りにおいて。</p></blockquote>
+
+<p>この「そのままのライセンス」についてエバン・モグレンの以下のコメントに注意くã
 ã•ã„:</p>
+
+<blockquote><p>
+「『いかなる媒体における、そのままの複製』というフレーズの意図は、ページのヘッダやフッタその他の文書整形に関する状æ
…‹ã¯ä¿æŒã—なくても構わないということです。ただ
し、ハイパーリンクの使えるメディアもそうでないメディアでも、ウェブリンクの(脚注や、非HTMLのメディアではその他の形式のURL表示による)保持は要求されます。」
+</p></blockquote>
 
-<h3>自由ソフトウェアのライセンス一覧</h3>
+<h3 id="FSLicenses">自由ソフトウェアのライセンス一覧</h3>
 
 <ul>
   <li>
@@ -273,7 +295,7 @@
 数多くの異なるプログラムで同じ配布条項
を用いると、コードを様々な異なるプログラム
間でコピーすることが容易になります。それらはすべて同じé
…å¸ƒæ¡é …なので、条項が両立するかどうか考える必
要はありません。劣等GPLには配布条項
を普通のGPLに変更してもよいという規定があり、GPLで保護された他のプログラãƒ
 ã®ãªã‹ã«ã€ãã®ã‚³ãƒ¼ãƒ‰ã‚’使うことができます。
 </p>
 
-<h3>その他の作品のためのライセンス</h3>
+<h3 id="OtherWorks">その他の作品のためのライセンス</h3>
 
 <p>
 公開されたソフトウェアと文書は、<a
@@ -358,7 +380,7 @@
 <p class="unprintable"><!-- timestamp start -->
 最終更新:
 
-$Date: 2016/02/13 09:57:16 $
+$Date: 2016/06/28 03:59:43 $
 
 <!-- timestamp end -->
 </p>

Index: licenses/old-licenses/fdl-1.2-translations.ja.html
===================================================================
RCS file: /web/www/www/licenses/old-licenses/fdl-1.2-translations.ja.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- licenses/old-licenses/fdl-1.2-translations.ja.html  3 Feb 2016 09:13:24 
-0000       1.18
+++ licenses/old-licenses/fdl-1.2-translations.ja.html  28 Jun 2016 03:59:43 
-0000      1.19
@@ -102,9 +102,7 @@
        id="GFDLJapaneseTranslation">Japanese</a>
        translation of the GFDL</li>
 -->
-<li><code>[ko]</code> <a
-href="http://korea.gnu.org/people/chsong/copyleft/fdl-1.2.ko.html";>韓国語</a>訳のGFDL</li>
-  <li><code>[pl]</code> <a
+<li><code>[pl]</code> <a
 
href="http://gnu.org.pl/text/gfdl12-pl.html";>ポーランド語</a>訳のGFDL</li>
 
   <!-- these translations have links other than to www.fsf.org and www.gnu.org
@@ -172,7 +170,7 @@
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
 <p>Copyright &copy; 1996, 1997, 1998, 1999, 2004, 2005, 2006, 2007, 2008, 2009,
-2013, 2014, 2015 Free Software Foundation, Inc.</p>
+2013, 2014, 2015, 2016 Free Software Foundation, Inc.</p>
 
 <p>このページは<a rel="license"
 href="http://creativecommons.org/licenses/by-nd/4.0/deed.ja";>Creative
@@ -187,7 +185,7 @@
 <p class="unprintable"><!-- timestamp start -->
 最終更新:
 
-$Date: 2016/02/03 09:13:24 $
+$Date: 2016/06/28 03:59:43 $
 
 <!-- timestamp end -->
 </p>

Index: licenses/old-licenses/po/fdl-1.2-translations.ja-en.html
===================================================================
RCS file: 
/web/www/www/licenses/old-licenses/po/fdl-1.2-translations.ja-en.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- licenses/old-licenses/po/fdl-1.2-translations.ja-en.html    1 Sep 2015 
16:28:01 -0000       1.12
+++ licenses/old-licenses/po/fdl-1.2-translations.ja-en.html    28 Jun 2016 
03:59:43 -0000      1.13
@@ -128,7 +128,6 @@
        id="GFDLJapaneseTranslation">Japanese</a>
        translation of the GFDL</li>
 -->
-  <li><code>[ko]</code> <a 
href="http://korea.gnu.org/people/chsong/copyleft/fdl-1.2.ko.html";>Korean</a> 
translation of the GFDL</li>
   <li><code>[pl]</code> <a 
href="http://gnu.org.pl/text/gfdl12-pl.html";>Polish</a>
        translation of the GFDL</li>
 <!-- these translations have links other than to www.fsf.org and www.gnu.org
@@ -189,7 +188,7 @@
      Information document, www.gnu.org/prep/maintain. -->
 
 <p>Copyright &copy; 1996, 1997, 1998, 1999, 2004, 2005, 2006, 2007,
-2008, 2009, 2013, 2014, 2015 Free Software Foundation, Inc.</p>
+2008, 2009, 2013, 2014, 2015, 2016 Free Software Foundation, Inc.</p>
 
 <p>This page is licensed under a <a rel="license"
 href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
@@ -199,7 +198,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2015/09/01 16:28:01 $
+$Date: 2016/06/28 03:59:43 $
 <!-- timestamp end -->
 </p>
 </div>

Index: licenses/po/fdl-howto-opt.ja-en.html
===================================================================
RCS file: /web/www/www/licenses/po/fdl-howto-opt.ja-en.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- licenses/po/fdl-howto-opt.ja-en.html        28 Apr 2014 07:59:09 -0000      
1.5
+++ licenses/po/fdl-howto-opt.ja-en.html        28 Jun 2016 03:59:43 -0000      
1.6
@@ -25,7 +25,7 @@
       Permission is granted to copy, distribute and/or modify this
       document under the terms of the GNU Free Documentation License,
       Version 1.3 or any later version published by the Free Software
-      Foundation; with no Invariant Sections, no Front-Cover Texts and
+      Foundation; with no Invariant Sections, no Front-Cover Texts, and
       no Back-Cover Texts.  A copy of the license is included in the
       section entitled "GNU Free Documentation License".
 </pre>
@@ -159,7 +159,7 @@
 
 <!-- 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 3.0 US.  Please do NOT change or remove this
+     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
@@ -174,17 +174,17 @@
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
 
-<p>Copyright &copy; 2000, 2008, 2014 Free Software Foundation, Inc.</p>
+<p>Copyright &copy; 2000, 2008, 2014, 2016 Free Software Foundation, Inc.</p>
 
 <p>This page is licensed under a <a rel="license"
-href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
-Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+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: 2014/04/28 07:59:09 $
+$Date: 2016/06/28 03:59:43 $
 <!-- timestamp end -->
 </p>
 </div>

Index: licenses/po/fdl-howto-opt.ja.po
===================================================================
RCS file: /web/www/www/licenses/po/fdl-howto-opt.ja.po,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- licenses/po/fdl-howto-opt.ja.po     28 Jun 2016 03:50:24 -0000      1.10
+++ licenses/po/fdl-howto-opt.ja.po     28 Jun 2016 03:59:43 -0000      1.11
@@ -54,6 +54,7 @@
 "は、以下のようになります:"
 
 #. type: Content of: <pre>
+#, no-wrap
 msgid ""
 "      Permission is granted to copy, distribute and/or modify this\n"
 "      document under the terms of the GNU Free Documentation License,\n"

Index: licenses/po/gpl-faq.ja-en.html
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.ja-en.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- licenses/po/gpl-faq.ja-en.html      14 Apr 2016 10:00:27 -0000      1.23
+++ licenses/po/gpl-faq.ja-en.html      28 Jun 2016 03:59:43 -0000      1.24
@@ -104,7 +104,7 @@
     program and an unrelated non-free program on the same computer?</a></li>
   
     <li><a href="#CanIDemandACopy">If I know someone has a copy of a
-    GPL-covered program, can I demand he give me a copy?</a></li>
+    GPL-covered program, can I demand they give me a copy?</a></li>
 
     <li><a href="#WhatDoesWrittenOfferValid">What does &ldquo;written offer
     valid for any third party&rdquo; mean in GPLv2? Does that mean everyone
@@ -463,7 +463,7 @@
 
     <li><a href="#v3CoworkerConveying">If I give a copy of a
     GPLv3-covered program to a coworker at my company, have I
-    &ldquo;conveyed&rdquo; the copy to him?</a></li>
+    &ldquo;conveyed&rdquo; the copy to that coworker?</a></li>
 
     <li><a href="#SourceInCVS">Am I complying with GPLv3 if I offer
     binaries on an FTP server and sources by way of a link to a source
@@ -834,14 +834,14 @@
 
 
 <dt id="CanIDemandACopy">If I know someone has a copy of a GPL-covered
-    program, can I demand he give me a copy?
+    program, can I demand they give me a copy?
  <span class="anchor-reference-id">(<a href="#CanIDemandACopy"
  >#CanIDemandACopy</a>)</span></dt>
 <dd><p>
-No.  The GPL gives him permission to make and redistribute copies of
-the program <em>if and when he chooses to do so</em>.  He also has the
-right not to redistribute the program, when that is what he
-chooses.</p></dd>
+No.  The GPL gives a person permission to make and redistribute copies
+of the program <em>if and when that person chooses to do so</em>.
+That person also has the right not to choose to redistribute the
+program.</p></dd>
 
 
 <dt id="WhatDoesWrittenOfferValid">What does &ldquo;written offer
@@ -1061,7 +1061,7 @@
  >#WhyMustIInclude</a>)</span></dt>
 <dd><p>
 Including a copy of the license with the work is vital so that
-everyone who gets a copy of the program can know what his rights are.</p>
+everyone who gets a copy of the program can know what their rights are.</p>
 
 <p>It might be tempting to include a URL that refers to the license,
 instead of the license itself.  But you cannot be sure that the URL
@@ -1582,8 +1582,8 @@
 <dd><p>
 In general this is legally impossible; copyright law does not give you
 any say in the use of the output people make from their data using
-your program.  If the user uses your program to enter or convert his
-own data, the copyright on the output belongs to him, not you.  More
+your program.  If the user uses your program to enter or convert her
+own data, the copyright on the output belongs to her, not you.  More
 generally, when a program translates its input into some other form,
 the copyright status of the output inherits that of the input it was
 generated from.</p>
@@ -1974,13 +1974,12 @@
     I do this, too?  If so, how?
  <span class="anchor-reference-id">(<a href="#AssignCopyright"
  >#AssignCopyright</a>)</span></dt>
-<dd><p>
-Our lawyers have told us that to be in the <a
-href="/licenses/why-assign.html">best position to enforce the GPL</a> in
-court against violators, we should keep the copyright status of the
-program as simple as possible.  We do this by asking each contributor to
-either assign the copyright on his contribution to the FSF, or disclaim
-copyright on it and thus put it in the public domain.</p>
+<dd><p> Our lawyers have told us that to be in the <a
+href="/licenses/why-assign.html">best position to enforce the GPL</a>
+in court against violators, we should keep the copyright status of the
+program as simple as possible.  We do this by asking each contributor
+to either assign the copyright on contributions to the FSF, or
+disclaim copyright on contributions.</p>
 
 <p>We also ask individual contributors to get copyright disclaimers from
 their employers (if any) so that we can be sure those employers won't
@@ -2405,14 +2404,14 @@
 
 <dt id="StolenCopy">If someone steals
     a CD containing a version of a GPL-covered program, does the GPL
-    give him the right to redistribute that version?
+    give the theif the right to redistribute that version?
  <span class="anchor-reference-id">(<a href="#StolenCopy"
  >#StolenCopy</a>)</span></dt>
 <dd><p>
-If the version has been released elsewhere, then the thief probably
-does have the right to make copies and redistribute them under the GPL,
-but if he is imprisoned for stealing the CD he may have to wait until
-his release before doing so.</p>
+If the version has been released elsewhere, then the thief
+probably does have the right to make copies and redistribute them
+under the GPL, but if the theif is imprisoned for stealing the CD,
+they may have to wait until their release before doing so.</p>
 
 <p>If the version in question is unpublished and considered by a company
 to be its trade secret, then publishing it may be a violation of trade
@@ -3062,7 +3061,7 @@
 kind of DRM technology you like.  However, if you do this, section 3
 says that the system will not count as an effective technological
 &ldquo;protection&rdquo; measure, which means that if someone breaks the
-DRM, he will be free to distribute his software too, unhindered by the DMCA
+DRM, she will be free to distribute her software too, unhindered by the DMCA
 and similar laws.</p>
 
 <p>As usual, the GNU GPL does not restrict what people do in software,
@@ -3093,14 +3092,14 @@
  <span class="anchor-reference-id">(<a href="#GiveUpKeys"
  >#GiveUpKeys</a>)</span></dt>
 <dd><p>
-No.  The only time you would be required to release signing keys is
-if you conveyed GPLed software inside a User Product, and its hardware
+No.  The only time you would be required to release signing keys is if
+you conveyed GPLed software inside a User Product, and its hardware
 checked the software for a valid cryptographic signature before it
 would function. In that specific case, you would be required to
 provide anyone who owned the device, on demand, with the key to sign
-and install modified software on his device so that it will run.  If
+and install modified software on the device so that it will run.  If
 each instance of the device uses a different key, then you need only
-give each purchaser the key for his instance.</p></dd>
+give each purchaser a key for that instance.</p></dd>
 
 
 <dt id="v3VotingMachine">Does GPLv3 require that voters be able to
@@ -3238,7 +3237,7 @@
 
 <dt id="v3CoworkerConveying">If I give a copy of a GPLv3-covered
     program to a coworker at my company, have I &ldquo;conveyed&rdquo; the
-    copy to him?
+    copy to that coworker?
  <span class="anchor-reference-id">(<a href="#v3CoworkerConveying"
  >#v3CoworkerConveying</a>)</span></dt>
 <dd><p>
@@ -3550,24 +3549,14 @@
     the servers it interacts with?
  <span class="anchor-reference-id">(<a href="#AGPLv3ServerAsUser"
  >#AGPLv3ServerAsUser</a>)</span></dt>
-<dd><p>
-This should not be required in any typical server-client
-relationship.  AGPLv3 requires a program to offer source code to
-&ldquo;all users interacting with it remotely through a computer
-network.&rdquo; In most server-client architectures, it simply
-wouldn't be reasonable to argue that the server operator is a
-&ldquo;user&rdquo; interacting with the client in any meaningful
-sense.</p>
-
-<p>Consider HTTP as an example.  All HTTP clients expect servers to
-provide certain functionality: they should send specified responses to
-well-formed requests.  The reverse is not true: servers cannot assume
-that the client will do anything in particular with the data they
-send.  The client may be a web browser, an RSS reader, a spider, a
-network monitoring tool, or some special-purpose program.  The server
-can make absolutely no assumptions about what the client will
-do&mdash;so there's no meaningful way for the server operator to be
-considered a user of that software.</p></dd>
+<dd>
+    <p>AGPLv3 requires a program to offer source code to &ldquo;all
+users interacting with it remotely through a computer network.&rdquo;
+It doesn't matter if you call the program a &ldquo;client&rdquo;
+or a &ldquo;server,&rdquo; the
+question you need to ask is whether or not there is a reasonable
+expectation that a person will be interacting with the program
+remotely over a network. </p></dd>
 
 <dt id="AGPLProxy">For software that runs a proxy server licensed
     under the AGPL, how can I provide an offer of source to users
@@ -3869,7 +3858,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2016/04/14 10:00:27 $
+$Date: 2016/06/28 03:59:43 $
 <!-- timestamp end -->
 </p>
 </div>

Index: licenses/po/gpl-faq.ja.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.ja.po,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -b -r1.68 -r1.69
--- licenses/po/gpl-faq.ja.po   28 Jun 2016 03:50:24 -0000      1.68
+++ licenses/po/gpl-faq.ja.po   28 Jun 2016 03:59:43 -0000      1.69
@@ -1658,9 +1658,9 @@
 "give me a copy? <span class=\"anchor-reference-id\">(<a href="
 "\"#CanIDemandACopy\" >#CanIDemandACopy</a>)</span>"
 msgstr ""
-"GPLの及ぶプログラム
のコピーを誰かが持っていると知っているå 
´åˆã€ã‚ãŸã—はその人に"
-"コピーを下さいと要求できますか? <span 
class=\"anchor-reference-id\">(<a href="
-"\"#CanIDemandACopy\" >#CanIDemandACopy</a>)</span>"
+"GPLの及ぶプログラム
のコピーを誰かが持っていると知っているå 
´åˆã€ã‚ãŸã—はその人"
+"にコピーを下さいと要求できますか? <span 
class=\"anchor-reference-id\">(<a "
+"href=\"#CanIDemandACopy\" >#CanIDemandACopy</a>)</span>"
 
 #. type: Content of: <dl><dd><p>
 msgid ""
@@ -1668,9 +1668,9 @@
 "the program <em>if and when that person chooses to do so</em>.  That person "
 "also has the right not to choose to redistribute the program."
 msgstr ""
-"いいえ。GPLは、ある人に<em>もし、その人がそうすることを選んã
 å ´åˆã€ãã®æ™‚に</em>、プログラムの"
-"コピーを作成し、再é…
å¸ƒã™ã‚‹è¨±å¯ã‚’与えます。その人は、プロ"
-"グラムを再配布する選択をしない権利も持つのです。"
+"いいえ。GPLは、ある人に<em>もし、その人がそうすることを選んã
 å ´åˆã€ãã®æ™‚に</"
+"em>、プログラムのコピーを作成し、再é…
å¸ƒã™ã‚‹è¨±å¯ã‚’与えます。その人は、プログラ"
+"ムを再配布する選択をしない権利も持つのです。"
 
 #. type: Content of: <dl><dt>
 msgid ""
@@ -3201,10 +3201,10 @@
 msgstr ""
 
"一般的に言って、それは法的に不可能です。著作権法は人ã€
…があなたのプログラムと"
 
"かれらのデータを使って作った出力結果の利用に関して、あなたに何の発言権も与え"
-"ていません。ユーザがあなたのプログラム
を使ってその人自身のデータを入力ないし変"
-"換したå 
´åˆã€å‡ºåŠ›çµæžœã®è‘—作権はその人に属すのであって、あなたにではありません。"
-"もっと一般的に言えば、あるプログラムがå…
¥åŠ›ã‚’他の形式に変換する場合、出力結果"
-"の著作権の状態は、生成の元となったå…
¥åŠ›ã®ãã‚Œã‚’継承するのです。"
+"ていません。ユーザがあなたのプログラム
を使ってその人自身のデータを入力ないし"
+"変換したå 
´åˆã€å‡ºåŠ›çµæžœã®è‘—作権はその人に属すのであって、あなたにではありませ"
+"ん。もっと一般的に言えば、あるプログラムがå…
¥åŠ›ã‚’他の形式に変換する場合、出力"
+"結果の著作権の状態は、生成の元となったå…
¥åŠ›ã®ãã‚Œã‚’継承するのです。"
 
 #. type: Content of: <dl><dd><p>
 msgid ""
@@ -4015,8 +4015,8 @@
 "わたしたちの弁護士は、侵害者に対して法廷で<a 
href=\"/licenses/why-assign.html"
 "\">GPLを強制する上で最良の立å 
´</a>に立つには、プログラムの著作権の状態を可能"
 "な限り単純に保つべきだ
と述べています。このため、わたしたちは貢献者
のみなさん"
-"に対し、FSFに対するご自分の貢献に関する著作権を譲渡するか、貢献に関して著作権を主張"
-"しないことをお願いしています。"
+"に対し、FSFに対するご自分の貢献に関する著作権を譲渡するか、貢献に関して著作権"
+"を主張しないことをお願いしています。"
 
 #. type: Content of: <dl><dd><p>
 msgid ""
@@ -4887,9 +4887,9 @@
 "the GPL give the theif the right to redistribute that version? <span class="
 "\"anchor-reference-id\">(<a href=\"#StolenCopy\" >#StolenCopy</a>)</span>"
 msgstr ""
-"誰かがGPLの及ぶプログラムのバージョンがå…
¥ã£ãŸCDを盗みました。GPLは、その盗人に、"
-"このバージョンを再配布する権利を与えますか? <span 
class=\"anchor-reference-id"
-"\">(<a href=\"#StolenCopy\" >#StolenCopy</a>)</span>"
+"誰かがGPLの及ぶプログラムのバージョンがå…
¥ã£ãŸCDを盗みました。GPLは、その盗人"
+"に、このバージョンを再配布する権利を与えますか? <span 
class=\"anchor-"
+"reference-id\">(<a href=\"#StolenCopy\" >#StolenCopy</a>)</span>"
 
 #. type: Content of: <dl><dd><p>
 msgid ""
@@ -4898,10 +4898,10 @@
 "the theif is imprisoned for stealing the CD, they may have to wait until "
 "their release before doing so."
 msgstr ""
-"そのバージョンが(盗み以前に)既にどこかにリリースされているのであれば、盗"
-"人はおそらくコピーを作成し、再é…
å¸ƒã™ã‚‹æ¨©åˆ©ã‚’GPLのもとで有するでしょう。しか"
-"し、CDを盗んだことで刑務所にå…
¥ã‚‹ã®ãªã‚‰ã°ã€ç›—人はそうする前に解放されるまで待"
-"つ必要があるかもしれません。"
+"そのバージョンが(盗み以前に)既にどこかにリリースされているのであれば、盗人は"
+"おそらくコピーを作成し、再é…
å¸ƒã™ã‚‹æ¨©åˆ©ã‚’GPLのもとで有するでしょう。しかし、CD"
+"を盗んだことで刑務所にå…
¥ã‚‹ã®ãªã‚‰ã°ã€ç›—人はそうする前に解放されるまで待つ必要"
+"があるかもしれません。"
 
 #. type: Content of: <dl><dd><p>
 msgid ""
@@ -6227,8 +6227,8 @@
 
"禁止しません。GPLv3でリリースされたコードを使って、あなたの望むあらゆる種類の"
 "DRM技術を開発することが可能です。しかし、こうするå 
´åˆã€ç¬¬3節は、そのシステム"
 
"は効果的な技術的「保護」手段とはみなされないことになる、と述べています。これ"
-"は、だれかがDRMを破ったå 
´åˆã€ãã®äººã¯ã‹ã‚Œã®ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ã‚’é…
å¸ƒã™ã‚‹ã“とが自由にで"
-"き、DMCAや同様な法律によって妨げられることはないということです。"
+"は、だれかがDRMを破ったå 
´åˆã€ãã®äººã¯ã‹ã‚Œã®ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ã‚’配布することが自由に"
+"でき、DMCAや同様な法律によって妨げられることはないということです。"
 
 #. type: Content of: <dl><dd><p>
 msgid ""
@@ -6297,10 +6297,10 @@
 "いいえ。署名鍵をリリースする必
要があるかもしれないただ一つのケースは、GPLのソ"
 "フトウェアをUser 
Productの中に運搬し、そのハードウェアが、そのソフトウェアを"
 "動作させる前に有効な暗号署名を確認するå 
´åˆã§ã™ã€‚この特定のケースでは、そのデ"
-"バイスを所有する誰もに対して、要求があれば、署名し、そのデバイスに改変した"
-"ソフトウェアをインストールし実行できるよう、鍵を提供するå¿
…要があるでしょう。"
-"デバイスの個々が異なる鍵を使っているå 
´åˆã€ãã‚Œãžã‚Œã®è³¼å…¥è€…には、そのデバイ"
-"スの鍵だけを与える必要があります。"
+"バイスを所有する誰もに対して、要求があれば、署名し、そのデバイスに改変したソ"
+"フトウェアをインストールし実行できるよう、鍵を提供するå¿
…要があるでしょう。デ"
+"バイスの個々が異なる鍵を使っているå 
´åˆã€ãã‚Œãžã‚Œã®è³¼å…¥è€…には、そのデバイスの"
+"鍵だけを与える必要があります。"
 
 #. type: Content of: <dl><dt>
 msgid ""
@@ -6562,8 +6562,8 @@
 "\"anchor-reference-id\">(<a href=\"#v3CoworkerConveying\" "
 ">#v3CoworkerConveying</a>)</span>"
 msgstr ""
-"GPLv3の及ぶプログラムのコピーを会社の同僚にあげたå 
´åˆã€ãã®ã‚³ãƒ”ーをその人に「運"
-"搬」したことになりますか? <span class=\"anchor-reference-id\">(<a 
href="
+"GPLv3の及ぶプログラムのコピーを会社の同僚にあげたå 
´åˆã€ãã®ã‚³ãƒ”ーをその人に"
+"「運搬」したことになりますか? <span 
class=\"anchor-reference-id\">(<a href="
 "\"#v3CoworkerConveying\" >#v3CoworkerConveying</a>)</span>"
 
 #. type: Content of: <dl><dd><p>
@@ -7167,10 +7167,11 @@
 "expectation that a person will be interacting with the program remotely over "
 "a network."
 msgstr ""
-"AGPLv3は「コンピュータネットワークを通じて遠
隔でそれとやりとり"
-"するすべてのユーザ」に対し、あるプログラム
がソースコードを提供することを要求"
-"します。そのプログラム
を「クライアント」もしくは「サーバ」と呼ぶかどうかは関係しません。"
-"問うべき問題は、ある人がネットワークを通じて遠
隔でそのプログラムでやりとりするかどうかです。"
+"AGPLv3は「コンピュータネットワークを通じて遠
隔でそれとやりとりするすべての"
+"ユーザ」に対し、あるプログラム
がソースコードを提供することを要求します。その"
+"プログラム
を「クライアント」もしくは「サーバ」と呼ぶかどうかは関係しません。"
+"問うべき問題は、ある人がネットワークを通じて遠
隔でそのプログラムでやりとりす"
+"るかどうかです。"
 
 #. type: Content of: <dl><dt>
 msgid ""

Index: licenses/po/license-list.ja-en.html
===================================================================
RCS file: /web/www/www/licenses/po/license-list.ja-en.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -b -r1.32 -r1.33
--- licenses/po/license-list.ja-en.html 14 Apr 2016 08:33:51 -0000      1.32
+++ licenses/po/license-list.ja-en.html 28 Jun 2016 03:59:43 -0000      1.33
@@ -1442,12 +1442,12 @@
     <span class="anchor-reference-id">
        (<a href="#OpenSSL">#OpenSSL</a>)</span></dt>
 <dd>
-<p>The license of OpenSSL is a conjunction of two licenses, one of them
-being the license of SSLeay.  You must follow both.  The combination
-results in a copyleft free software license that is incompatible with
-the GNU GPL.  It also has an advertising clause like the <a
-href="#OriginalBSD">original BSD license</a> and the <a
-href="#apache1">Apache&nbsp;1 license</a>.</p>
+<p>The license of OpenSSL is a conjunction of two licenses, one called
+&ldquo;OpenSSL License&rdquo; and the other being the license of SSLeay. You 
must
+follow both.  The combination results in a copyleft free software
+license that is incompatible with the GNU GPL.  It also has an
+advertising clause like the <a href="#OriginalBSD">original BSD
+license</a> and the <a href="#apache1">Apache&nbsp;1 license</a>.</p>
 
 <p>We recommend using GNUTLS instead of OpenSSL in software you write.
 However, there is no reason not to use OpenSSL and applications that
@@ -2649,7 +2649,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2016/04/14 08:33:51 $
+$Date: 2016/06/28 03:59:43 $
 <!-- timestamp end -->
 </p>
 </div>

Index: licenses/po/license-list.ja.po
===================================================================
RCS file: /web/www/www/licenses/po/license-list.ja.po,v
retrieving revision 1.139
retrieving revision 1.140
diff -u -b -r1.139 -r1.140
--- licenses/po/license-list.ja.po      28 Jun 2016 03:50:24 -0000      1.139
+++ licenses/po/license-list.ja.po      28 Jun 2016 03:59:43 -0000      1.140
@@ -2710,13 +2710,12 @@
 "like the <a href=\"#OriginalBSD\">original BSD license</a> and the <a href="
 "\"#apache1\">Apache&nbsp;1 license</a>."
 msgstr ""
-"OpenSSLのライセンスは2種類のライセンスが連結されたものです。一つは"
-"&ldquo;OpenSSL License&rdquo;と呼ばれ、もう一つは"
-"SSLeayのライセンスです。あなたは両方に従わなければなりません。この二è€
…の結合"
-"は、コピーレフトの自由ソフトウェアライセンスとなっており、これはGNU
 GPLと両立"
-"しません。また、このライセンスは <a 
href=\"#OriginalBSD\">オリジナルBSDライセ"
-"ンス</a>や<a href=\"#apache1\">Apache 
1ライセンス</a>のような宣伝条項を有して"
-"います。"
+"OpenSSLのライセンスは2種類のライセンスが連結されたものです。一つは&ldquo;"
+"OpenSSL 
License&rdquo;と呼ばれ、もう一つはSSLeayのライセンスです。あなたは両"
+"方に従わなければなりません。この二者
の結合は、コピーレフトの自由ソフトウェア"
+"ライセンスとなっており、これはGNU 
GPLと両立しません。また、このライセンスは "
+"<a href=\"#OriginalBSD\">オリジナルBSDライセンス</a>や<a href="
+"\"#apache1\">Apache 1ライセンス</a>のような宣伝条項
を有しています。"
 
 #. type: Content of: <dl><dd><p>
 msgid ""

Index: licenses/po/licenses.ja-en.html
===================================================================
RCS file: /web/www/www/licenses/po/licenses.ja-en.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- licenses/po/licenses.ja-en.html     13 Feb 2016 09:57:34 -0000      1.30
+++ licenses/po/licenses.ja-en.html     28 Jun 2016 03:59:43 -0000      1.31
@@ -6,6 +6,26 @@
 <!--#include virtual="/server/banner.html" -->
 <h2>Licenses</h2>
 
+<div class="summary">
+<h3 class="no-display">Table of Contents</h3>
+<ul>
+  <li><a href="#Evaluation">Evaluating Licenses</a></li>
+  <li><a href="#CommonResources">Common Resources for our Software 
Licenses</a></li>
+  <li><a href="#GPL">The GNU General Public License</a></li>
+  <li><a href="#LGPL">The GNU Lesser General Public License</a></li>
+  <li><a href="#AGPL">The GNU Affero General Public License</a></li>
+  <li><a href="#FDL">The GNU Free Documentation License</a></li>
+  <li><a href="#Exceptions">Exceptions to GNU Licenses</a></li>
+  <li><a href="#LicenseURLs">License URLs</a></li>
+  <li><a href="#UnofficialTransl">Unofficial Translations</a></li>
+  <li><a href="#VerbatimCopying">Verbatim Copying and Distribution</a></li>
+  <li><a href="#FSLicenses">List of Free Software Licenses</a></li>
+  <li><a href="#WhatIsCopyleft">What Is Copyleft?</a></li>
+  <li><a href="#OtherWorks">Licenses for Other Types of Works</a></li>
+</ul>
+<hr class="no-display" />
+</div>
+
 <p>
 Published software should be <a href="/philosophy/free-sw.html">free
 software</a>.  To make it free software, you need to release it
@@ -38,7 +58,7 @@
 
 <p>We also have a page that discusses <a href="/licenses/bsd.html">the BSD 
License Problem</a>.</p>
 
-<h3>Evaluating Licenses</h3>
+<h3 id="Evaluation">Evaluating Licenses</h3>
 
 <p>If you come across a license not mentioned in our
 <a href="/licenses/license-list.html">license list</a>, you can ask us
@@ -50,7 +70,7 @@
 difficult philosophical problems, so we can't promise to decide
 quickly.</p>
 
-<h3>Common Resources for our Software Licenses</h3>
+<h3 id="CommonResources">Common Resources for our Software Licenses</h3>
 
 <p>We have a number of resources to help people understand and use our
 various licenses:</p>
@@ -228,7 +248,7 @@
 <p>See also the <a href="old-licenses/">old licenses page</a>.</p>
 
 
-<h3>Unofficial Translations</h3>
+<h3 id="UnofficialTransl">Unofficial Translations</h3>
 
 <p>
 Legally speaking, the original (English) version of the licenses is what
@@ -251,21 +271,25 @@
 <p>The standard copyright terms for GNU web pages is now the <a
 href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
 Commons Attribution-NoDerivs 3.0 United States License</a>.  It used to
-be (and for a few pages still is): <em><span class="highlight">Verbatim
+be (and for a few pages still is):</p>
+
+<blockquote><p>Verbatim
 copying and distribution of this entire article are permitted worldwide,
 without royalty, in any medium, provided this notice is
-preserved</span>.</em> Please note the following commentary about this
+preserved.</p></blockquote>
+
+<p>Please note the following commentary about this
 &ldquo;verbatim license&rdquo; by Eben Moglen:</p>
 
-<p>
+<blockquote><p>
 &ldquo;Our intention in using the phrase &lsquo;verbatim copying in
 any medium&rsquo; is not to require retention of page headings and
 footers or other formatting features.  Retention of weblinks in both
 hyperlinked and non-hyperlinked media (as notes or some other form of
-printed URL in non-HTML media) is required&rdquo;.
-</p>
+printed URL in non-HTML media) is required.&rdquo;
+</p></blockquote>
 
-<h3>List of Free Software Licenses</h3>
+<h3 id="FSLicenses">List of Free Software Licenses</h3>
 
 <ul>
   <li>
@@ -392,7 +416,7 @@
 GPL, so that you can copy code into another program covered by the GPL.
 </p>
 
-<h3>Licenses for Other Types of Works</h3>
+<h3 id="OtherWorks">Licenses for Other Types of Works</h3>
 
 <p>
 We believe that published software and documentation should be
@@ -471,7 +495,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2016/02/13 09:57:34 $
+$Date: 2016/06/28 03:59:43 $
 <!-- timestamp end -->
 </p>
 </div>

Index: licenses/po/licenses.ja.po
===================================================================
RCS file: /web/www/www/licenses/po/licenses.ja.po,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -b -r1.60 -r1.61
--- licenses/po/licenses.ja.po  28 Jun 2016 03:50:24 -0000      1.60
+++ licenses/po/licenses.ja.po  28 Jun 2016 03:59:43 -0000      1.61
@@ -36,7 +36,8 @@
 msgid ""
 "<a href=\"#CommonResources\">Common Resources for our Software Licenses</a>"
 msgstr ""
-"<a 
href=\"#CommonResources\">わたしたちのソフトウェア・ライセンスのå
…±é€šã®ãƒªã‚½ãƒ¼ã‚¹</a>"
+"<a 
href=\"#CommonResources\">わたしたちのソフトウェア・ライセンスのå
…±é€šã®ãƒª"
+"ソース</a>"
 
 #. type: Content of: <div><ul><li>
 msgid "<a href=\"#GPL\">The GNU General Public License</a>"
@@ -72,8 +73,7 @@
 
 #. type: Content of: <div><ul><li>
 msgid "<a href=\"#FSLicenses\">List of Free Software Licenses</a>"
-msgstr ""
-"<a href=\"#FSLicenses\">自由ソフトウェアのライセンス一覧</a>"
+msgstr "<a 
href=\"#FSLicenses\">自由ソフトウェアのライセンス一覧</a>"
 
 #. type: Content of: <div><ul><li>
 msgid "<a href=\"#WhatIsCopyleft\">What Is Copyleft?</a>"
@@ -586,23 +586,25 @@
 "still is):"
 msgstr ""
 "GNUウェブページのための標準の著作権の条項は、現在、<a 
href=\"http://";
-"creativecommons.org/licenses/by-nd/3.0/us/deed.ja\">Creative Commons 
Attribution-NoDerivs 3.0 United States 
License</a>です。かつては(そして現在もいくつかのページは)、"
-"こうでした:"
+"creativecommons.org/licenses/by-nd/3.0/us/deed.ja\">Creative Commons "
+"Attribution-NoDerivs 3.0 United States 
License</a>です。かつては(そして現在も"
+"いくつかのページは)、こうでした:"
 
 #. type: Content of: <blockquote><p>
 msgid ""
 "Verbatim copying and distribution of this entire article are permitted "
 "worldwide, without royalty, in any medium, provided this notice is preserved."
 msgstr ""
-"この記事全体のそのままのコピーと配布はå…
¨ä¸–界的に許諾されます。ロイヤリティなしで、"
-"いかなる媒体でも、この告知が保存される限りにおいて。"
+"この記事全体のそのままのコピーと配布はå…
¨ä¸–界的に許諾されます。ロイヤリティな"
+"しで、いかなる媒体でも、この告知が保存される限りにおいて。"
 
 #. type: Content of: <p>
 msgid ""
 "Please note the following commentary about this &ldquo;verbatim "
 "license&rdquo; by Eben Moglen:"
 msgstr ""
-"この「そのままのライセンス」についてエバン・モグレンの以下のコメントに注意くã
 ã•ã„:"
+"この「そのままのライセンス」についてエバン・モグレンの以下のコメントに注意く"
+"ださい:"
 
 #. type: Content of: <blockquote><p>
 msgid ""

Index: philosophy/basic-freedoms.ja.html
===================================================================
RCS file: /web/www/www/philosophy/basic-freedoms.ja.html,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -b -r1.33 -r1.34
--- philosophy/basic-freedoms.ja.html   3 Feb 2016 09:13:44 -0000       1.33
+++ philosophy/basic-freedoms.ja.html   28 Jun 2016 03:59:43 -0000      1.34
@@ -15,17 +15,15 @@
 </p>
 
 <ul>
+  <li>アーカイブされた(1999年4月24日)Wayback Machineで<a href=
+"https://web.archive.org/web/19990424100121/http://www.ciec.org/";>市民のインターネット強化連合</a>は議会のインターネットにå
…
¬é–‹ã•ã‚Œã‚‹è³‡æ–™ã‚’規制しようとする最初の試み、通信品位法(CDA)、に反対するよう連帯しましたが、アメリカ合衆国最高裁は1997å¹´6月26日、これを違憲と判断しました。このサイトはCDAのケースのランドマークのリソースとして、保存されています。</li>
+
   <li>
-    <a href=
-"http://www.ciec.org/";>市民のインターネット強化連合</a>は議会のインターネットにå
…
¬é–‹ã•ã‚Œã‚‹è³‡æ–™ã‚’規制しようとする最初の試み、通信品位法(CDA)、に反対するよう連帯しましたが、アメリカ合衆国最高裁は1997å¹´6月26日、これを違憲と判断しました。このサイトはCDAのケースのランドマークのリソースとして、保存されています。
-  </li>
+    <!-- activating this link… site is archived as of July 09, 1998 -->
+アーカイブされた(1998年7月9日)Wayback Machineで<a
+href="https://web.archive.org/web/19980709161803/http://vtw.org/";>選挙民テレコミュニケーションウォッチ</a>と彼らの優れた声明の電子メーリングリスト。</li>
 
-<!-- removing this link.. site is dead as of June 07 2004
   <li>
-The <a href="http://www.vtw.org/";>Voters Telecommunications Watch</a>
-       and their excellent announcement electronic mailing list.</li>
-    -->
-<li>
     <a href="/philosophy/censoring-emacs.html">Censoring GNU
 Emacs</a>は、通信品位法(CDA)がGNUプロジェクトに要求したGNU
 Emacsの検閲と、このことが皮肉にも検閲者
が望んでいた効果とはå…
¨ãé€†ã‚’もたらしたことを説明します。
@@ -41,15 +39,13 @@
 
href="http://www.eff.org/blueribbon.html";>ブルーリボンキャンペーン</a>、オンラインでの言論、å
 ±é“、団結の自由のための活動です。
   </li>
 
-<!-- removing this link.. site is dead as of June 07 2004
   <li>
-You can read <a href="http://www.vtw.org/speech/index.html#decision";>the
-       June 1996 appeals court decision</a>
-       rejecting censorship of the Internet.  But remember, this decision
-       is <em>not</em> final!  First, the Supreme Court will agree or disagree;
-       then Congress gets a chance to look for another method of 
censorship.</li>
-    -->
-<li><a 
href="/philosophy/savingeurope.html">ヨーロッパをソフトウェア特許から救おう</a></li>
+    <!-- activating this link… site is archived as of December 01, 2001 -->
+アーカイブされたWayback Machine で(2001年12月1日)、<a
+href="https://web.archive.org/web/20011201050533/http://www.vtw.org/speech/";>1996å¹´6月の控訴審の判断</a>でインターネットの検閲が否定されたことを読むことができます。しかし、忘れないでくã
 ã•ã„。この判断は最終では<em>ありません</em>!
+第一に、最高裁は同意もしくは否定するでしょう。そして、議会は別の検閲の方法を探す機会を狙っています。</li>
+
+  <li><a 
href="/philosophy/savingeurope.html">ヨーロッパをソフトウェア特許から救おう</a></li>
 
   <li>
     
コンピュータ開発と電子的コミュニケーションの自由のために活動する<a
@@ -94,12 +90,11 @@
 </div>
 
 <p>Copyright &copy; 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2007,
-2014 Free Software Foundation, Inc.</p>
+2014, 2016 Free Software Foundation, Inc.</p>
 
 <p>このページは<a rel="license"
-href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.ja";>Creative
-Commons Attribution-NoDerivs 3.0 United States 
License</a>の条件で許諾されます。
-</p>
+href="http://creativecommons.org/licenses/by-nd/4.0/deed.ja";>Creative
+Commons Attribution-NoDerivs 4.0 International 
License</a>の条件で許諾されます。</p>
 
 <!--#include virtual="/server/bottom-notes.ja.html" -->
 <div class="translators-credits">
@@ -110,7 +105,7 @@
 <p class="unprintable"><!-- timestamp start -->
 最終更新:
 
-$Date: 2016/02/03 09:13:44 $
+$Date: 2016/06/28 03:59:43 $
 
 <!-- timestamp end -->
 </p>

Index: philosophy/po/basic-freedoms.ja-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/basic-freedoms.ja-en.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- philosophy/po/basic-freedoms.ja-en.html     28 Apr 2014 07:01:46 -0000      
1.23
+++ philosophy/po/basic-freedoms.ja-en.html     28 Jun 2016 03:59:44 -0000      
1.24
@@ -12,19 +12,19 @@
 </p>
 
 <ul>
-  <li>
-    The <a href="http://www.ciec.org/";> Citizens Internet Empowerment
-    Coalition</a> came together to oppose Congress' first attempt to
-    regulate material published on the Internet, the Communications
-    Decency Act, which the U.S. Supreme Court found unconstitutional
-    on June 26, 1997.  Their site is being preserved as a resource on
-    the landmark CDA case.
-  </li>
-
-  <!-- removing this link.. site is dead as of June 07 2004
-  <li>The <a href="http://www.vtw.org/";>Voters Telecommunications Watch</a>
-       and their excellent announcement electronic mailing list.</li>
-    -->
+  <li>The <a
+    
href="https://web.archive.org/web/19990424100121/http://www.ciec.org/";>Citizens
+    Internet Empowerment Coalition</a> at the Wayback Machine (archived April
+    24, 1999) came together to oppose Congress' first attempt to regulate
+    material published on the Internet, the Communications Decency Act, which
+    the U.S. Supreme Court found unconstitutional on June 26, 1997. Their site
+    is being preserved as a resource on the landmark CDA case.</li>
+
+  <li><!-- activating this link… site is archived as of July 09, 1998 -->
+    The <a
+    href="https://web.archive.org/web/19980709161803/http://vtw.org/";>Voters
+    Telecommunications Watch</a> at the Wayback Machine (archived July 09,
+    1998) and their excellent announcement electronic mailing list.</li>
     
   <li>
     <a href="/philosophy/censoring-emacs.html">Censoring GNU Emacs</a>
@@ -45,13 +45,14 @@
     for Online Freedom of Speech, Press and Association.
   </li>
 
-  <!-- removing this link.. site is dead as of June 07 2004
-  <li>You can read <a href="http://www.vtw.org/speech/index.html#decision";>the
-       June 1996 appeals court decision</a>
-       rejecting censorship of the Internet.  But remember, this decision
-       is <em>not</em> final!  First, the Supreme Court will agree or disagree;
-       then Congress gets a chance to look for another method of 
censorship.</li>
-    -->
+  <li><!-- activating this link… site is archived as of December 01, 2001 -->
+    You can read <a
+    
href="https://web.archive.org/web/20011201050533/http://www.vtw.org/speech/";>the
+    June 1996 appeals court decision</a> at the Wayback Machine (archived
+    December 01, 2001) rejecting censorship of the Internet. But remember, this
+    decision is <em>not</em> final! First, the Supreme Court will agree or
+    disagree; then Congress gets a chance to look for another method of
+    censorship.</li>
 
   <li><a href="/philosophy/savingeurope.html">Saving Europe from Software 
Patents</a></li>
 
@@ -93,18 +94,17 @@
 </div>
 
 <p>Copyright &copy; 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
-2007, 2014 Free Software Foundation, Inc.</p>
+2007, 2014, 2016 Free Software Foundation, Inc.</p>
 
 <p>This page is licensed under a <a rel="license"
-href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
-Commons Attribution-NoDerivs 3.0 United States License</a>.
-</p>
+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: 2014/04/28 07:01:46 $
+$Date: 2016/06/28 03:59:44 $
 <!-- timestamp end -->
 </p>
 </div>

Index: philosophy/po/basic-freedoms.ja.po
===================================================================
RCS file: /web/www/www/philosophy/po/basic-freedoms.ja.po,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- philosophy/po/basic-freedoms.ja.po  28 Jun 2016 03:50:25 -0000      1.20
+++ philosophy/po/basic-freedoms.ja.po  28 Jun 2016 03:59:44 -0000      1.21
@@ -45,12 +45,12 @@
 "which the U.S. Supreme Court found unconstitutional on June 26, 1997. Their "
 "site is being preserved as a resource on the landmark CDA case."
 msgstr ""
-"アーカイブされた(1999年4月24日)Wayback Machineで"
-"<a href= 
\"https://web.archive.org/web/19990424100121/http://www.ciec.org/\";>市民のインターネット強化連合</a>は議会のイ"
-"ンターネットにå…
¬é–‹ã•ã‚Œã‚‹è³‡æ–™ã‚’規制しようとする最初の試み、通信品位法(CDA)、に"
-"反対するよう連帯しましたが、アメリカ合衆国最高裁は1997年6月26日、これを違憲と"
-"判断しました。このサイトはCDAのケースのランドマークのリソースとして、保存され"
-"ています。"
+"アーカイブされた(1999年4月24日)Wayback Machineで<a href= 
\"https://web.";
+"archive.org/web/19990424100121/http://www.ciec.org/\";>市民のインターネット強"
+"化連合</a>は議会のインターネットにå…
¬é–‹ã•ã‚Œã‚‹è³‡æ–™ã‚’規制しようとする最初の試"
+"み、通信品位法(CDA)、に反対するよう連帯しましたが、アメリカ合衆国最高裁は1997"
+"年6月26日、これを違憲と判断しました。このサイトはCDAのケースのランドマークの"
+"リソースとして、保存されています。"
 
 #.  activating this link… site is archived as of July 09, 1998 
 #. type: Content of: <ul><li>
@@ -59,10 +59,9 @@
 "\">Voters Telecommunications Watch</a> at the Wayback Machine (archived July "
 "09, 1998) and their excellent announcement electronic mailing list."
 msgstr ""
-"アーカイブされた(1998年7月9日)Wayback Machineで"
-"<a href=\"https://web.archive.org/web/19980709161803/http://vtw.org/";
-"\">選挙民テレコミュニケーションウォッチ</a>"
-"と彼らの優れた声明の電子メーリングリスト。"
+"アーカイブされた(1998年7月9日)Wayback Machineで<a 
href=\"https://web.archive.";
+"org/web/19980709161803/http://vtw.org/\";>選挙民テレコミュニケーションウォッチ"
+"</a>と彼らの優れた声明の電子メーリングリスト。"
 
 #. type: Content of: <ul><li>
 msgid ""
@@ -104,11 +103,12 @@
 "will agree or disagree; then Congress gets a chance to look for another "
 "method of censorship."
 msgstr ""
-"アーカイブされたWayback Machine で(2001年12月1日)、<a 
href=\"https://web.archive.org/web/20011201050533/http://www.";
-"vtw.org/speech/\">1996年6月の控訴審の判断</a>でインターネットの検閲が否定されたことを"
-"読むことができます。"
-"しかし、忘れないでくだ
さい。この判断は最終では<em>ありません</em>! 
第一に、最高裁"
-"は同意もしくは否定するでしょう。そして、議会は別の検閲の方法を探す機会を狙っています。"
+"アーカイブされたWayback Machine で(2001年12月1日)、<a 
href=\"https://web.";
+"archive.org/web/20011201050533/http://www.vtw.org/speech/\";>1996年6月の控訴審"
+"の判断</a>でインターネットの検閲が否定されたことを読むことができます。しか"
+"し、忘れないでくだ
さい。この判断は最終では<em>ありません</em>! 
第一に、最高裁"
+"は同意もしくは否定するでしょう。そして、議会は別の検閲の方法を探す機会を狙っ"
+"ています。"
 
 #. type: Content of: <ul><li>
 msgid ""

Index: philosophy/po/who-does-that-server-really-serve.nl.po
===================================================================
RCS file: /web/www/www/philosophy/po/who-does-that-server-really-serve.nl.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- philosophy/po/who-does-that-server-really-serve.nl.po       27 Jun 2016 
19:31:32 -0000      1.3
+++ philosophy/po/who-does-that-server-really-serve.nl.po       28 Jun 2016 
03:59:44 -0000      1.4
@@ -14,7 +14,6 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2016-06-07 05:25+0000\n"
 "X-Generator: Poedit 1.5.4\n"
 
 #. type: Content of: <title>
@@ -109,20 +108,20 @@
 msgid ""
 "Our solution to this problem is developing <em>free software</em> and "
 "rejecting proprietary software.  Free software means that you, as a user, "
-"have four essential freedoms: (0)&nbsp;to run the program as you wish, "
-"(1)&nbsp;to study and change the source code so it does what you wish, "
-"(2)&nbsp;to redistribute exact copies, and (3)&nbsp;to redistribute copies "
-"of your modified versions.  (See the <a href=\"/philosophy/free-sw.html"
-"\">free software definition</a>.)"
+"have four essential freedoms: (0)&nbsp;to run the program as you wish, (1)"
+"&nbsp;to study and change the source code so it does what you wish, (2)&nbsp;"
+"to redistribute exact copies, and (3)&nbsp;to redistribute copies of your "
+"modified versions.  (See the <a href=\"/philosophy/free-sw.html\">free "
+"software definition</a>.)"
 msgstr ""
 "Onze oplossing voor dit probleem is het ontwikkelen van <em>vrije software</"
 "em> en het niet accepteren van niet-vrije software. Vrije software betekent "
-"dat jij, als gebruiker, vier essenti&euml;le vrijheden hebt. De vrijheid: "
-"(0)&nbsp;om het programma uit te voeren zoals jij wilt, (1)&nbsp;om de "
-"broncode te bestuderen en te wijzigen, zodat het werkt zoals jij wilt, "
-"(2)&nbsp;om exacte kopie&euml;n te verspreiden en (3)&nbsp;om kopie&euml;n "
-"van jouw aangepaste versies te verspreiden. (Zie de <a href=\"/philosophy/"
-"free-sw.html\">definitie van vrije software</a>.)"
+"dat jij, als gebruiker, vier essenti&euml;le vrijheden hebt. De vrijheid: (0)"
+"&nbsp;om het programma uit te voeren zoals jij wilt, (1)&nbsp;om de broncode "
+"te bestuderen en te wijzigen, zodat het werkt zoals jij wilt, (2)&nbsp;om "
+"exacte kopie&euml;n te verspreiden en (3)&nbsp;om kopie&euml;n van jouw "
+"aangepaste versies te verspreiden. (Zie de <a href=\"/philosophy/free-sw.html"
+"\">definitie van vrije software</a>.)"
 
 #. type: Content of: <p>
 msgid ""

Index: philosophy/po/who-does-that-server-really-serve.translist
===================================================================
RCS file: 
/web/www/www/philosophy/po/who-does-that-server-really-serve.translist,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- philosophy/po/who-does-that-server-really-serve.translist   19 Jan 2016 
07:09:09 -0000      1.16
+++ philosophy/po/who-does-that-server-really-serve.translist   28 Jun 2016 
03:59:44 -0000      1.17
@@ -11,6 +11,7 @@
 <span dir="ltr"><a lang="ja" hreflang="ja" 
href="/philosophy/who-does-that-server-really-serve.ja.html">日本語</a>&nbsp;[ja]</span>
 &nbsp;
 <span dir="ltr"><a lang="ko" hreflang="ko" 
href="/philosophy/who-does-that-server-really-serve.ko.html">한국어</a>&nbsp;[ko]</span>
 &nbsp;
 <span dir="ltr"><a lang="lt" hreflang="lt" 
href="/philosophy/who-does-that-server-really-serve.lt.html">lietuvių</a>&nbsp;[lt]</span>
 &nbsp;
+<span dir="ltr"><a lang="nl" hreflang="nl" 
href="/philosophy/who-does-that-server-really-serve.nl.html">Nederlands</a>&nbsp;[nl]</span>
 &nbsp;
 <span dir="ltr"><a lang="pl" hreflang="pl" 
href="/philosophy/who-does-that-server-really-serve.pl.html">polski</a>&nbsp;[pl]</span>
 &nbsp;
 <span dir="ltr"><a lang="ro" hreflang="ro" 
href="/philosophy/who-does-that-server-really-serve.ro.html">română</a>&nbsp;[ro]</span>
 &nbsp;
 <span dir="ltr"><a lang="ru" hreflang="ru" 
href="/philosophy/who-does-that-server-really-serve.ru.html">русский</a>&nbsp;[ru]</span>
 &nbsp;
@@ -27,6 +28,7 @@
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/philosophy/who-does-that-server-really-serve.ja.html" title="日本語" 
/>
 <link rel="alternate" type="text/html" lang="ko" hreflang="ko" 
href="/philosophy/who-does-that-server-really-serve.ko.html" title="한국어" 
/>
 <link rel="alternate" type="text/html" lang="lt" hreflang="lt" 
href="/philosophy/who-does-that-server-really-serve.lt.html" title="lietuvių" 
/>
+<link rel="alternate" type="text/html" lang="nl" hreflang="nl" 
href="/philosophy/who-does-that-server-really-serve.nl.html" title="Nederlands" 
/>
 <link rel="alternate" type="text/html" lang="pl" hreflang="pl" 
href="/philosophy/who-does-that-server-really-serve.pl.html" title="polski" />
 <link rel="alternate" type="text/html" lang="ro" hreflang="ro" 
href="/philosophy/who-does-that-server-really-serve.ro.html" title="română" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/philosophy/who-does-that-server-really-serve.ru.html" 
title="русский" />

Index: proprietary/proprietary-sabotage.ja.html
===================================================================
RCS file: /web/www/www/proprietary/proprietary-sabotage.ja.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- proprietary/proprietary-sabotage.ja.html    21 Jun 2016 17:00:01 -0000      
1.13
+++ proprietary/proprietary-sabotage.ja.html    28 Jun 2016 03:59:44 -0000      
1.14
@@ -3,7 +3,7 @@
  http://www.gnu.org/proprietary/po/proprietary-sabotage.ja.po</a>'
  --><!--#set var="ORIGINAL_FILE" value="/proprietary/proprietary-sabotage.html"
  --><!--#set var="DIFF_FILE" 
value="/proprietary/po/proprietary-sabotage.ja-diff.html"
- --><!--#set var="OUTDATED_SINCE" value="2016-04-22" --><!--#set 
var="ENGLISH_PAGE" value="/proprietary/proprietary-sabotage.en.html" -->
+ --><!--#set var="OUTDATED_SINCE" value="2016-04-22" -->
 
 <!--#include virtual="/server/header.ja.html" -->
 <!-- Parent-Version: 1.77 -->
@@ -217,7 +217,7 @@
 <p class="unprintable"><!-- timestamp start -->
 最終更新:
 
-$Date: 2016/06/21 17:00:01 $
+$Date: 2016/06/28 03:59:44 $
 
 <!-- timestamp end -->
 </p>

Index: proprietary/po/proprietary-sabotage.de.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-sabotage.de.po,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -b -r1.51 -r1.52
--- proprietary/po/proprietary-sabotage.de.po   20 Jun 2016 02:30:20 -0000      
1.51
+++ proprietary/po/proprietary-sabotage.de.po   28 Jun 2016 03:59:44 -0000      
1.52
@@ -7,7 +7,7 @@
 msgstr ""
 "Project-Id-Version: proprietary-sabotage.html\n"
 "Report-Msgid-Bugs-To: Webmasters <address@hidden>\n"
-"POT-Creation-Date: 2016-06-10 18:55+0000\n"
+"POT-Creation-Date: 2016-06-28 03:55+0000\n"
 "PO-Revision-Date: 2016-06-16 22:00+0200\n"
 "Last-Translator: Jоегg Kоhпе <joeko (AT) online [PUNKT] de>\n"
 "Language-Team: www-de <address@hidden>\n"
@@ -15,6 +15,7 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2016-06-28 03:55+0000\n"
 
 #. type: Content of: <title>
 msgid "Proprietary Sabotage - GNU Project - Free Software Foundation"
@@ -447,6 +448,13 @@
 
 #. type: Content of: <ul><li><p>
 msgid ""
+"In a court settlement Sony is <a href=\"http://arstechnica.com/tech-";
+"policy/2016/06/if-you-used-to-run-linux-on-your-ps3-you-could-get-55-from-"
+"sony/\"> now paying for the sabotage</a>."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
 "LG <a href=\"http://www.techdirt.com/articles/20140511/17430627199/lg-will-";
 "take-smart-out-your-smart-tv-if-you-dont-agree-to-share-your-viewing-search-"
 "data-with-third-parties.shtml\">disabled network features</a> on "

Index: proprietary/po/proprietary-sabotage.fr.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-sabotage.fr.po,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -b -r1.48 -r1.49
--- proprietary/po/proprietary-sabotage.fr.po   10 Jun 2016 19:53:32 -0000      
1.48
+++ proprietary/po/proprietary-sabotage.fr.po   28 Jun 2016 03:59:44 -0000      
1.49
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: proprietary-sabotage.html\n"
-"POT-Creation-Date: 2016-06-10 18:55+0000\n"
+"POT-Creation-Date: 2016-06-28 03:55+0000\n"
 "PO-Revision-Date: 2016-06-10 21:47+0200\n"
 "Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
 "Language-Team: French <address@hidden>\n"
@@ -15,6 +15,7 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2016-06-28 03:55+0000\n"
 "Plural-Forms: \n"
 "X-Generator: Gtranslator 2.91.5\n"
 
@@ -414,6 +415,13 @@
 
 #. type: Content of: <ul><li><p>
 msgid ""
+"In a court settlement Sony is <a href=\"http://arstechnica.com/tech-";
+"policy/2016/06/if-you-used-to-run-linux-on-your-ps3-you-could-get-55-from-"
+"sony/\"> now paying for the sabotage</a>."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
 "LG <a href=\"http://www.techdirt.com/articles/20140511/17430627199/lg-will-";
 "take-smart-out-your-smart-tv-if-you-dont-agree-to-share-your-viewing-search-"
 "data-with-third-parties.shtml\">disabled network features</a> on "

Index: proprietary/po/proprietary-sabotage.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-sabotage.it.po,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -b -r1.51 -r1.52
--- proprietary/po/proprietary-sabotage.it.po   10 Jun 2016 18:59:46 -0000      
1.51
+++ proprietary/po/proprietary-sabotage.it.po   28 Jun 2016 03:59:44 -0000      
1.52
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: proprietary-sabotage.html\n"
-"POT-Creation-Date: 2016-06-10 18:55+0000\n"
+"POT-Creation-Date: 2016-06-28 03:55+0000\n"
 "PO-Revision-Date: 2016-05-22 20:48+0100\n"
 "Last-Translator: Andrea Pescetti <address@hidden>\n"
 "Language-Team: Italian <address@hidden>\n"
@@ -403,6 +403,13 @@
 
 #. type: Content of: <ul><li><p>
 msgid ""
+"In a court settlement Sony is <a href=\"http://arstechnica.com/tech-";
+"policy/2016/06/if-you-used-to-run-linux-on-your-ps3-you-could-get-55-from-"
+"sony/\"> now paying for the sabotage</a>."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
 "LG <a href=\"http://www.techdirt.com/articles/20140511/17430627199/lg-will-";
 "take-smart-out-your-smart-tv-if-you-dont-agree-to-share-your-viewing-search-"
 "data-with-third-parties.shtml\">disabled network features</a> on "

Index: proprietary/po/proprietary-sabotage.ja-diff.html
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-sabotage.ja-diff.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- proprietary/po/proprietary-sabotage.ja-diff.html    21 Jun 2016 17:00:01 
-0000      1.1
+++ proprietary/po/proprietary-sabotage.ja-diff.html    28 Jun 2016 03:59:44 
-0000      1.2
@@ -200,7 +200,11 @@
 code that blocked users from changing the firmware, and we responded by
 calling for a &lt;a href="http://boycottsony.org"&gt;boycott of
 Sony &lt;/a&gt;.
-&lt;/p&gt;&lt;/li&gt;
+<span class="removed"><del><strong>&lt;/p&gt;&lt;/li&gt;</strong></del></span>
+<span class="inserted"><ins><em>&lt;/p&gt;
+
+&lt;p&gt;In a court settlement Sony is &lt;a 
href="http://arstechnica.com/tech-policy/2016/06/if-you-used-to-run-linux-on-your-ps3-you-could-get-55-from-sony/"&gt;
+now paying for the sabotage&lt;/a&gt;.&lt;/p&gt;&lt;/li&gt;</em></ins></span>
 
 &lt;li&gt;&lt;p&gt;
 LG &lt;a 
href="http://www.techdirt.com/articles/20140511/17430627199/lg-will-take-smart-out-your-smart-tv-if-you-dont-agree-to-share-your-viewing-search-data-with-third-parties.shtml"&gt;disabled
@@ -290,7 +294,7 @@
 
 &lt;p class="unprintable"&gt;Updated:
 &lt;!-- timestamp start --&gt;
-$Date: 2016/06/21 17:00:01 $
+$Date: 2016/06/28 03:59:44 $
 &lt;!-- timestamp end --&gt;
 &lt;/p&gt;
 &lt;/div&gt;

Index: proprietary/po/proprietary-sabotage.ja.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-sabotage.ja.po,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -b -r1.49 -r1.50
--- proprietary/po/proprietary-sabotage.ja.po   10 Jun 2016 18:59:46 -0000      
1.49
+++ proprietary/po/proprietary-sabotage.ja.po   28 Jun 2016 03:59:44 -0000      
1.50
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: proprietary-sabotage.html\n"
-"POT-Creation-Date: 2016-06-10 18:55+0000\n"
+"POT-Creation-Date: 2016-06-28 03:55+0000\n"
 "PO-Revision-Date: 2016-03-08 13:34+0900\n"
 "Last-Translator: NIIBE Yutaka <address@hidden>\n"
 "Language-Team: Japanese <address@hidden>\n"
@@ -394,6 +394,13 @@
 
 #. type: Content of: <ul><li><p>
 msgid ""
+"In a court settlement Sony is <a href=\"http://arstechnica.com/tech-";
+"policy/2016/06/if-you-used-to-run-linux-on-your-ps3-you-could-get-55-from-"
+"sony/\"> now paying for the sabotage</a>."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
 "LG <a href=\"http://www.techdirt.com/articles/20140511/17430627199/lg-will-";
 "take-smart-out-your-smart-tv-if-you-dont-agree-to-share-your-viewing-search-"
 "data-with-third-parties.shtml\">disabled network features</a> on "

Index: proprietary/po/proprietary-sabotage.pot
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-sabotage.pot,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- proprietary/po/proprietary-sabotage.pot     10 Jun 2016 18:59:46 -0000      
1.27
+++ proprietary/po/proprietary-sabotage.pot     28 Jun 2016 03:59:44 -0000      
1.28
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: proprietary-sabotage.html\n"
-"POT-Creation-Date: 2016-06-10 18:55+0000\n"
+"POT-Creation-Date: 2016-06-28 03:55+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <address@hidden>\n"
 "Language-Team: LANGUAGE <address@hidden>\n"
@@ -279,6 +279,13 @@
 
 #. type: Content of: <ul><li><p>
 msgid ""
+"In a court settlement Sony is <a "
+"href=\"http://arstechnica.com/tech-policy/2016/06/if-you-used-to-run-linux-on-your-ps3-you-could-get-55-from-sony/\";>
 "
+"now paying for the sabotage</a>."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
 "LG <a "
 
"href=\"http://www.techdirt.com/articles/20140511/17430627199/lg-will-take-smart-out-your-smart-tv-if-you-dont-agree-to-share-your-viewing-search-data-with-third-parties.shtml\";>disabled
 "
 "network features</a> on <em>previously purchased</em> &ldquo;smart&rdquo; "

Index: proprietary/po/proprietary-sabotage.ru.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-sabotage.ru.po,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -b -r1.65 -r1.66
--- proprietary/po/proprietary-sabotage.ru.po   10 Jun 2016 19:59:29 -0000      
1.65
+++ proprietary/po/proprietary-sabotage.ru.po   28 Jun 2016 03:59:44 -0000      
1.66
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: proprietary-sabotage.html\n"
-"POT-Creation-Date: 2016-06-10 18:55+0000\n"
+"POT-Creation-Date: 2016-06-28 03:55+0000\n"
 "PO-Revision-Date: 2016-06-10 17:51+0000\n"
 "Last-Translator: Ineiev <address@hidden>\n"
 "Language-Team: Russian <address@hidden>\n"
@@ -15,6 +15,7 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2016-06-28 03:55+0000\n"
 
 #. type: Content of: <title>
 msgid "Proprietary Sabotage - GNU Project - Free Software Foundation"
@@ -404,6 +405,13 @@
 
 #. type: Content of: <ul><li><p>
 msgid ""
+"In a court settlement Sony is <a href=\"http://arstechnica.com/tech-";
+"policy/2016/06/if-you-used-to-run-linux-on-your-ps3-you-could-get-55-from-"
+"sony/\"> now paying for the sabotage</a>."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
 "LG <a href=\"http://www.techdirt.com/articles/20140511/17430627199/lg-will-";
 "take-smart-out-your-smart-tv-if-you-dont-agree-to-share-your-viewing-search-"
 "data-with-third-parties.shtml\">disabled network features</a> on "

Index: philosophy/who-does-that-server-really-serve.nl.html
===================================================================
RCS file: philosophy/who-does-that-server-really-serve.nl.html
diff -N philosophy/who-does-that-server-really-serve.nl.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ philosophy/who-does-that-server-really-serve.nl.html        28 Jun 2016 
03:59:44 -0000      1.1
@@ -0,0 +1,504 @@
+<!--#set var="ENGLISH_PAGE" 
value="/philosophy/who-does-that-server-really-serve.en.html" -->
+
+<!--#include virtual="/server/header.nl.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Wie dient die server eigenlijk echt? - GNU-project - Free Software
+Foundation</title>
+
+<!--#include 
virtual="/philosophy/po/who-does-that-server-really-serve.translist" -->
+<!--#include virtual="/server/banner.nl.html" -->
+<h2>Wie dient die server eigenlijk echt?</h2>
+
+<p>door <strong>Richard Stallman</strong></p>
+
+<blockquote><p>(De eerste versie verscheen  in de <a
+href="http://www.bostonreview.net/richard-stallman-free-software-DRM";>
+Boston Review</a>.)</p></blockquote>
+
+<p><strong>Op het internet is niet-vrije software niet de enige manier om je
+vrijheid te verliezen. Service als Softwarevervanging, of SaaSS, is een
+andere manier om iemand anders macht te geven over jouw
+computeractiviteiten.</strong></p>
+
+<p>Waar het om gaat is dat je zeggenschap hebt over een programma dat iemand
+anders heeft geschreven (als het tenminste vrij is), terwijl je nooit
+zeggenschap kunt hebben over een dienst die iemand anders beheert. Gebruik
+dus nooit een dienst als een programma in principe hetzelfde kan.</p>
+
+
+<p>SaaSS betekent dat je iemand anders' dienst gebruikt, in plaats van jouw
+eigen kopie van een programma. Wij hebben de uitdrukking bedacht; artikelen
+en advertenties gebruiken 'm niet, en ze zullen je niet vertellen dat hun
+dienst SaaSS is. In plaats daarvan gebruiken ze waarschijnlijk de vage en
+afleidende term &ldquo;cloud&rdquo;, wat een noemer is voor SaaSS en vele
+andere praktijken, waarvan sommigen gebruikers misbruiken en andere weer
+prima zijn. Met de uitleg en voorbeelden op deze pagina kan je vaststellen
+of een dienst SaaSS is.</p>
+
+<h3>Achtergrond: hoe niet-vrije software jouw vrijheid wegneemt</h3>
+
+<p>Digitale technologie kan je vrijheid geven, maar het kan jouw vrijheid ook
+wegnemen. De zeggenschap over onze eigen computeractiviteiten werd eerst
+bedreigd door <em>niet-vrije software</em>: software waar gebruikers geen
+controle over hebben, omdat de eigenaar (een bedrijf zoals Apple of
+Microsoft) er controle over heeft. Die eigenaar maakt vaak misbruik van deze
+onrechtvaardige macht door middel van malafide functies in het programma,
+zoals spionage, achterdeurtjes, en <a
+href="http://DefectiveByDesign.org";>digitaal beheer van beperkingen
+(DRM)</a> (door hun eigen propaganda &ldquo;digitaal beheer van
+rechten&rdquo;genoemd).</p>
+
+<p>Onze oplossing voor dit probleem is het ontwikkelen van <em>vrije
+software</em> en het niet accepteren van niet-vrije software. Vrije software
+betekent dat jij, als gebruiker, vier essenti&euml;le vrijheden hebt. De
+vrijheid: (0)&nbsp;om het programma uit te voeren zoals jij wilt,
+(1)&nbsp;om de broncode te bestuderen en te wijzigen, zodat het werkt zoals
+jij wilt, (2)&nbsp;om exacte kopie&euml;n te verspreiden en (3)&nbsp;om
+kopie&euml;n van jouw aangepaste versies te verspreiden. (Zie de <a
+href="/philosophy/free-sw.html">definitie van vrije software</a>.)</p>
+
+<p>Met vrije software kunnen wij als gebruikers weer zeggenschap krijgen over
+onze eigen computeractiviteiten. Er bestaat nog steeds niet-vrije software,
+maar we kunnen het uitsluiten van ons leven, en velen onder ons hebben dat
+gedaan. Nu krijgen we echter een andere verleidelijke manier aangeboden om
+de controle over onze computeractiviteiten kwijt te raken: Service als
+Softwarevervanging (SaaSS). In het belang van onze vrijheid moeten we ook
+dat niet accepteren. </p>
+
+<h3>Hoe Service als Softwarevervanging je van je vrijheid berooft</h3>
+
+<p>Service als Softwarevervanging (SaaSS) betekent dat je een dienst gebruikt,
+in plaats van jouw eigen kopie van een programma. Concreet betekent het dat
+iemand een netwerkserver opzet die bepaalde computertaken
+doet&mdash;bijvoorbeeld het bewerken van een foto, het vertalen van tekst
+naar een andere taal, enz.&mdash;en vervolgens gebruikers uitnodigt om die
+activiteiten via die server te doen. Een gebruiker daarvan stuurt zijn
+gegevens naar die server, die dan de <em>computeractiviteiten van de
+gebruiker zelf</em> uitvoert met de verstrekte gegevens. Vervolgens stuurt
+de server de resultaten terug naar de gebruiker of handelt op eigen houtje
+namens hem. </p>
+
+<p>Die computeractiviteit behoort toe aan <em>de gebruiker</em>, omdat hij het
+in principe ook zelf had kunnen doen, door het uitvoeren van een programma
+op zijn eigen computer (of de gebruiker nu de beschikking heeft over dat
+programma of niet). In de gevallen dat deze aanname niet klopt, is het geen
+SaaSS.</p>
+
+<p>Deze servers ontnemen de controle van de gebruiker nog meer dan bij
+niet-vrije software. Met niet-vrije software krijgen gebruikers vaak een
+uitvoerbaar bestand maar niet de broncode. Dat maakt het moeilijk om te
+bestuderen wat het programma eigenlijk doet, en moeilijk om het te
+veranderen.</p>
+
+<p>Met SaaSS krijgen gebruikers niet eens een uitvoerbaar bestand dat hun
+computeractiviteiten doet: het staat op de server van iemand anders, waar de
+gebruikers het niet kunnen zien of aanraken. Dus is het onmogelijk om vast
+te stellen wat het eigenlijk doet, en onmogelijk om het te veranderen. </p>
+
+<p>Bovendien leidt SaaSS automatisch tot gevolgen die even erg zijn als de
+malafide functies van bepaalde niet-vrije software.</p>
+
+<p> Sommige niet-vrije programma's zijn bijvoorbeeld &ldquo;spyware&rdquo;: het
+programma <a href="/philosophy/proprietary-surveillance.html">verstuurt
+gegevens over de computeractiviteiten van de gebruiker</a>. Microsoft
+Windows verstuurt informatie over de activiteiten van de gebruiker naar
+Microsoft. Windows Media Player rapporteert waar elke gebruiker naar kijkt
+of luistert. De Amazon Kindle meldt welke pagina's van welke boeken de
+gebruiker leest, en wanneer. Angry Birds verstuurt alle bezochte locaties
+van de gebruiker.</p>
+
+<p>In tegenstelling tot niet-vrije software heeft SaaSS geen achterbakse code
+nodig om de gegevens van de gebruiker te krijgen. In plaats daarvan moeten
+gebruikers hun gegevens naar de server versturen om het te kunnen
+gebruiken. Dit heeft hetzelfde effect als spyware: de serverbeheerder krijgt
+de gegevens&mdash;zonder speciale moeite, dit is hoe SaaSS werkt. Amy Webb,
+iemand die nooit de bedoeling had om foto's van haar dochter te publiceren,
+maakte de fout SaaSS (Instagram) te gebruiken om haar foto's te
+bewerken. Uiteindelijk <a
+href="http://www.slate.com/articles/technology/data_mine_1/2013/09/privacy_facebook_kids_don_t_post_photos_of_your_kids_on_social_media.html";>waren
+ze daar uitgelekt</a>.
+</p>
+
+<p>Theoretisch gezien zou homomorfische versleuteling op een dag zover
+gevorderd kunnen zijn, dat SaaSS-diensten zouden kunnen worden ontworpen om
+geen gegevens van de gebruiker te kunnen begrijpen. Zulke diensten
+<em>zouden</em> zo kunnen worden ingesteld dat ze gebruikers niet
+bespioneren; dat betekent echter niet dat ze dat ook niet zullen
+<em>doen</em>. </p>
+
+<p>Sommige niet-vrije besturingssystemen hebben een universele achterdeur,
+waarmee iemand anders op afstand softwareveranderingen kan
+installeren. Windows heeft bijvoorbeeld een universele achterdeur waarmee
+Microsoft andere software op de machine kan forceren. Bijna alle mobiele
+telefoons hebben ook er ook &eacute;&eacute;ntje. Sommige niet-vrije
+programma's hebben ook een universele achterdeur; het Steam-programma voor
+GNU/Linux stelt de ontwikkelaar in staat om op afstand gewijzigde versies te
+installeren.</p>
+
+<p>Met SaaSS kan de serverbeheerder de gebruikte software op de server
+veranderen. Het is terecht dat hij dit moet kunnen doen; het is immers zijn
+computer. Het resultaat is echter hetzelfde als het gebruiken van een
+niet-vrij programma met een universele achterdeur: iemand heeft de macht om
+stilletjes te kunnen veranderen hoe de gebruiker zijn computeractiviteiten
+uitvoert.</p>
+
+<p>SaaSS is dus gelijkwaardig aan het gebruiken van niet-vrije software met
+spyware en een universele achterdeur. Het geeft de serverbeheerder
+onrechtvaardige macht over de gebruiker, en die macht moeten we niet
+accepteren. </p>
+
+<h3>SaaSS en SaaS</h3>
+
+<p>In het begin noemden we deze problematische praktijk &ldquo;SaaS&rdquo;, wat
+staat voor &ldquo;Software als een Service&rdquo;. Die term wordt vaak
+gebruikt voor het opzetten van software op een server in plaats van het
+aanbieden van een kopie ervan aan gebruikers. We dachten dat het precies die
+zaken beschrijft waar dit probleem voorkomt.</p>
+
+<p>Daarna kwamen we erachter dat de term SaaS soms wordt gebruikt voor
+communicatiediensten&mdash;activiteiten waarbij deze kwestie niet van
+toepassing is. De term &ldquo;Software als een Service&rdquo; legt daarnaast
+niet uit <em>waarom</em> deze praktijk slecht is. Dus introduceerden we de
+term &ldquo;Service als Softwarevervanging&rdquo;, die de slechte praktijk
+verduidelijkt en uitlegt wat er slecht aan is.</p>
+
+<h3>Het verschil tussen SaaSS en niet-vrije software</h3>
+
+<p>SaaSS en niet-vrije software leiden tot dezelfde schadelijke resultaten,
+maar het mechanisme erachter is anders. Met niet-vrije software is het
+mechanisme dat jij een kopie hebt die moeilijk en/of illegaal is om te
+veranderen. Met SaaSS is het mechanisme dat je de kopie die jouw
+computeractiviteiten doet, niet eens hebt.</p>
+
+<p>Deze twee kwesties worden vaak verward, en niet alleen per
+ongeluk. Web-ontwikkelaars gebruiken de term &ldquo;webapplicatie&rdquo; als
+één noemer om de serversoftware samen te nemen met programma's die in je
+browser (op jouw machine) worden uitgevoerd. Sommige webpagina's installeren
+niet-triviale, soms zelfs grote JavaScript-programma's in jouw browser
+zonder je dit te vertellen of te vragen. <a
+href="/philosophy/javascript-trap.html">Wanneer deze JavaScript-programma's
+niet-vrij zijn</a> is dit net zo onrechtvaardig als andere niet-vrije
+software. Hier houden we ons echter bezig met de kwestie van het gebruik van
+de dienst zelf.</p>
+
+<p>Veel aanhangers van vrije software menen dat het probleem van SaaSS kan
+worden opgelost door het ontwikkelen van vrije software voor servers. In het
+belang van de serverbeheerder kan hij maar beter vrije software gebruiken;
+anders, hebben die ontwikkelaars/eigenaars macht over de server in plaats
+van de serverbeheerder zelf. En het helpt de gebruikers van de server al
+helemaal niet. Maar als de programma's op de server vrij zijn, beschermt dat
+<em>de gebruikers van de server</em> niet tegen de consequenties van
+SaaSS. Deze vrije programma's bevrijden de serverbeheerder, maar niet de
+gebruikers van de server.</p>
+
+<p>Het publiceren van de broncode van serversoftware is gemeenschappelijk
+belang: hiermee kunnen gebruikers met de nodige kennis soortgelijke servers
+opzetten, misschien zelfs met gewijzigde software. <a
+href="/licenses/license-recommendations.html">Wij raden de GNU Affero GPL
+aan</a> als licentie voor programma's die vaak op servers gebruikt worden.</p>
+
+<p>Geen van deze servers zal jou echter zeggenschap geven over de
+computeractiviteiten die je ermee doet, behalve als het <em>jouw</em> server
+is (één waarvan de serversoftware onder jouw controle staat, ongeacht of de
+machine van jou is). Het is prima om de server van een vriend te gebruiken
+voor sommige taken, net zoals je vriend misschien de software op jouw
+computer onderhoudt. Buiten dat zijn al deze servers voor jou SaaSS. SaaSS
+onderwerpt je altijd aan de macht van de serverbeheerder, en de enige
+oplossing is: <em>Gebruik geen SaaSS!</em> Gebruik niet de server van iemand
+anders om jouw eigen computeractiviteiten uit te voeren met gegevens die jij
+verstrekt.</p>
+
+<p>Deze kwestie toont het verschil aan tussen &ldquo;open&rdquo; en
+&ldquo;vrij&rdquo;. Broncode die open source (open bron) is, <a
+href="/philosophy/free-open-overlap.html">is bijna altijd vrij</a>. Het idee
+van een <a href="http://opendefinition.org/software-service";>&ldquo;open
+software&rdquo;-dienst</a>, wat betekent dat de serversoftware open source
+en/of vrij is, slaagt er niet in om het SaaSS-probleem op te lossen.</p>
+
+<p>Diensten zijn wezenlijk verschillend van programma's, en de ethische
+kwesties die zich aandienen bij diensten zijn fundamenteel anders dan de
+kwesties die programma's oproepen. Om verwarring te vermijden, <a
+href="/philosophy/network-services-arent-free-or-nonfree.html"> beschrijven
+we een service niet als &ldquo;vrij&rdquo; or &ldquo;niet-vrij&rdquo;</a>.</p>
+
+<h3>Het verschil tussen SaaSS en andere netwerkdiensten</h3>
+
+<p>Welke online diensten zijn SaaSS? Het duidelijkste voorbeeld is een
+vertaaldienst, die bijvoorbeeld Engelse tekst naar Nederlandse tekst
+vertaalt. Het vertalen van een tekst voor jezelf is een activiteit die
+helemaal van jou is. Je zou het kunnen doen door een programma te gebruiken
+op je eigen computer, mits je het juiste programma hebt (de ethische keuze
+daarbij is een vrij programma). De vertaaldienst vervangt dat programma, dus
+is het Service als Softwarevervanging, of SaaSS. Het ontzegt jou zeggenschap
+over je eigen computeractiviteiten, en doet jou dus onrecht aan.</p>
+
+<p>Een ander duidelijk voorbeeld is het gebruik van een dienst als Flickr of
+Instagram om een foto te bewerken. Het bewerken van foto's is iets dat
+mensen al decennialang op hun eigen computer doen. Wanneer je dit doet met
+een server die jij niet beheert, in plaats van met je eigen computer, is dit
+SaaSS. </p>
+
+<p>Het verwerpen van SaaSS betekent niet dat je weigert elke netwerkserver te
+gebruiken die iemand anders beheert. De meeste servers zijn geen SaaSS,
+omdat de taken die hierop worden uitgevoerd een vorm van communicatie zijn,
+en niet de eigen computeractiviteiten van de gebruiker.</p>
+
+<p>Het oorspronkelijke idee van webservers was niet dat zij jouw activiteiten
+gingen doen; ze waren bedoeld om informatie te publiceren waar jij toegang
+tot hebt. Vandaag de dag is dit wat de meeste websites doen, en hier komt
+het SaaSS-probleem niet bij kijken: iemand anders' gepubliceerde informatie
+bekijken is niet hetzelfde als je eigen computeractiviteiten uitvoeren. Het
+gebruiken van een blogwebsite om je eigen werkstukken te publiceren is ook
+geen SaaSS, evenals het gebruiken van een microblogging-dienst zoals Twitter
+of StatusNet. (Deze diensten hebben misschien andere problemen, maar dat
+hangt af van details.) Hetzelfde geldt voor andere communicatie die niet
+priv&eacute; is, zoals chatgroepen.</p>
+
+<p>In essentie is het gebruik van een online sociaal netwerk een vorm van
+communicatie en publicatie, geen SaaSS. Een dienst die vooral bedoeld is
+voor sociale netwerken kan echter ook andere functies of uitbreidingen
+hebben die wel SaaSS zijn.</p>
+
+<p>Als een dienst geen SaaSS is, is het niet per definitie prima. Bij diensten
+komen ook andere ethische kwesties kijken. Facebook verspreidt bijvoorbeeld
+video's in Flash, wat gebruikers onder druk zet om niet-vrije software te
+installeren; het vereist ook het uitvoeren van niet-vrije JavaScript-code;
+en het geeft gebruikers een misleidende indruk van wat privacy inhoudt,
+terwijl ze hun leven blootleggen aan Facebook. Dit zijn belangrijke dingen,
+die niks te maken hebben met SaaSS.
+</p>
+
+<p>Diensten zoals zoekmachines verzamelen gegevens over het hele internet en
+laten jou het bestuderen. Het bekijken van hun verzameling van gegevens is
+niet jouw eigen computeractiviteit op de gebruikelijke manier&mdash;jij hebt
+die informatie niet gegeven&mdash;dus het gebruiken van een dienst om het
+internet te doorzoeken is geen SaaSS. Het gebruiken van de server van iemand
+anders om zoekfunctionaliteit te implementeren voor je eigen website is
+<em>wel</em> SaaSS.</p>
+
+<p>Online kopen is geen SaaSS, omdat de computeractiviteit niet <em>jouw
+eigen</em> activiteit is; het wordt gezamenlijk gedaan door jou en de
+winkel. De echte kwestie bij online winkelen gaat erom of jij de andere
+partij vertrouwt met jouw geld en andere persoonlijke informatie (beginnend
+met je naam). </p>
+
+<p>Opslagplaatsen zoals Savannah en SourceForge zijn niet noodzakelijkerwijs
+SaaSS, omdat de taak van de opslagplaats is om gegevens te publiceren.</p>
+
+<p>Servers van een gezamenlijk project gebruiken is geen SaaSS omdat de
+computeractiviteit die jij op die manier doet, niet jouw eigen activiteit
+is. Als je bijvoorbeeld pagina's op Wikipedia bewerkt, voer je niet je eigen
+computeractiviteit uit; je werkt samen met de activiteiten van
+Wikipedia. Wikipedia beheert zijn eigen servers, maar organisaties en
+individuen ervaren het SaaSS-probleem als zij hun eigen computeractiviteiten
+uitvoeren op de server van iemand anders.</p>
+
+<p>Sommige websites bieden meerdere diensten aan, en als één geen SaaSS is, 
is
+een andere misschien wel SaaSS. De hoofddienst van Facebook is bijvoorbeeld
+het sociale netwerk, en dat is geen SaaSS; echter, het ondersteunt ook
+toepassingen van derde partijen, waarvan sommige SaaSS zijn. De hoofddienst
+van Flickr is het verspreiden van foto's, wat geen SaaSS is, maar het bevat
+ook functies voor het bewerken van foto's, wat SaaSS is. Op dezelfde manier
+is het publiceren van een foto op Instagram geen SaaSS, maar deze dienst
+gebruiken om een foto te veranderen is dat wel. </p>
+
+<p>Google Docs laat ons zien hoe ingewikkeld de evaluatie van &eacute;&eacute;n
+enkele dienst kan worden. Het nodigt mensen uit om een document te bewerken
+door middel van het uitvoeren van een groot <a
+href="/philosophy/javascript-trap.html">niet-vrij JavaScript-programma</a>,
+overduidelijk verkeerd. Het biedt echter ook een API aan voor het uploaden
+en downloaden van documenten in standaardformaten. Een
+vrije-softwarebewerker kan dit doen met deze API. Dit gebruiksscenario is
+geen SaaSS, omdat het Google Docs gebruikt als opslagplaats. Als je al jouw
+gegevens aan een bedrijf laat zien is dit slecht, maar dat is een
+privacy-kwestie, geen SaaSS; afhankelijk zijn van een dienst om toegang te
+hebben tot je gegevens is slecht, maar dit is een kwestie van risico, geen
+SaaSS. Aan de andere kant, het gebruiken van de dienst om documentformaten
+om te zetten is <em>wel</em> SaaSS, omdat het iets is dat je had kunnen doen
+met een geschikt programma (uiteraard vrij) op je eigen computer.</p>
+
+<p>Het gebruiken van Google Docs met een vrije tekstverwerker zal natuurlijk
+niet vaak voorkomen. Meestal gebruiken mensen het door middel van het
+niet-vrije JavaScript-programma, wat net zo slecht is als ieder ander
+niet-vrij programma. Dit scenario zou ook SaaSS in zich kunnen hebben; dat
+hangt af van welk deel van het bewerken door het JavaScript-programma wordt
+gedaan en welk gedeelte op de server. We weten dat niet, maar dat is  ook
+niet belangrijk omdat SaaSS en niet-vrije software in dezelfde mate onrecht
+doen aan de gebruiker.</p>
+
+<p>Het publiceren via iemand anders' opslagplaats werpt geen privacykwesties
+op, maar het publiceren via Google Docs heeft een speciaal probleem: het is
+onmogelijk om zelfs alleen maar <em>de tekst te bekijken</em> van een Google
+Docs-document in een browser zonder de niet-vrije JavaScript-code uit te
+voeren. Dus zou je Google Docs niet moeten gebruiken om iets te
+publiceren&mdash;maar de reden heeft niet te maken met SaaSS.</p>
+
+<p>De IT-industrie ontmoedigt mensen om het onderscheid te maken. Daar is het
+modewoord &ldquo;cloud computing&rdquo; voor bedoeld. Die term is in nevelen
+gehuld en kan verwijzen naar bijna elk gebruik van het internet. Het omvat
+SaaSS en vele andere vormen van netwerkgebruik. In elke context heeft een
+auteur die schrijft over de &ldquo;cloud&rdquo; vaak een specifieke
+betekenis in gedachten, maar legt vaak niet uit dat deze term in andere
+artikelen een andere betekenis kan hebben. De term zorgt ervoor dat mensen
+dingen gaan generaliseren die eigenlijk individueel bekeken moeten worden.</p>
+
+<p>Als &ldquo;cloud computing&rdquo; een betekenis heeft, is dat in ieder geval
+niet een manier om te computeren, maar een manier om te denken over
+computeren: een onverschillige benadering die zegt: &ldquo;Stel geen
+vragen. Maak je geen zorgen over wie zeggenschap heeft over jouw
+computeractiviteiten of wie jouw gegevens bewaart. Controleer vooral niet of
+er een haak in onze dienst zit voordat je slikt. Vertrouw bedrijven zonder
+te twijfelen.&rdquo; Anders gezegd: &ldquo;Wees een onbenul.&rdquo; Een
+nevelige gedachtegang is een obstakel voor logisch nadenken. Laten we de
+term &ldquo;cloud.&rdquo; vermijden om duidelijk te kunnen nadenken over
+computeractiviteiten.</p>
+
+<h3 id="renting">Het verschil tussen het huren van een server en SaaSS</h3>
+
+<p>Als je een server huurt (echt of virtueel), waar software op staat onder
+jouw controle, is dat geen SaaSS. Bij SaaSS beslist iemand anders welke
+software op de server uitgevoerd wordt en bepaalt daarom hoe je jouw
+computeractiviteiten uitvoert. In het geval waarbij jij de software op de
+server installeert, bepaal jij welke activiteiten het voor jou uitvoert. Dus
+de gehuurde server is feitelijk jouw computer. Voor deze kwestie telt het
+als de jouwe.</p>
+
+<p>De <em>gegevens</em> op de gehuurde server op afstand zijn minder veilig dan
+een eigen server thuis, maar dat is een andere kwestie dan SaaSS.</p>
+
+<h3>Omgaan met het SaaSS-probleem</h3>
+
+<p>Slechts een klein gedeelte van alle websites doen aan SaaSS; de meeste
+hebben niks te maken met deze kwestie. Maar wat moeten we doen met websites
+die hier wel mee van doen hebben?</p>
+
+<p>Voor het simpele geval waarbij je jouw eigen computeractiviteiten uitvoert
+met gegevens in eigen handen, is de oplossing eenvoudig: gebruik je eigen
+kopie van een vrij programma. Doe je tekstbewerkingsactiviteiten met jouw
+kopie van een vrije tekstbewerker zoals GNU Emacs of een vrije
+tekstverwerker. Doe je fotobewerkingen met jouw kopie van een vrij programma
+zoals GIMP. Wat als er geen vrij programma beschikbaar is? Een niet-vrij
+programma of SaaSS zou jouw vrijheid wegnemen, dus moet je die niet
+gebruiken. Je kan je tijd of geld besteden aan de ontwikkeling van een vrije
+vervanging.</p>
+
+<p>Wat doen we als we als groep willen samenwerken met andere individuen? Het
+is misschien moeilijk om dit vandaag de dag te doen zonder gebruik te maken
+van een server, en jouw groep weet misschien niet hoe je je eigen server
+kunt gebruiken. Als je de server van iemand anders gebruikt, vertrouw dan op
+zijn minst niet de server van een bedrijf. Met een contract alleen heb je
+als consument geen bescherming, behalve als je een gat ontdekt en een
+aanklacht kan indienen, en het bedrijf schrijft zijn contracten
+waarschijnlijk op zo'n manier dat het veel soorten misbruik toestaat. De
+staat kan jouw gegevens opvragen van het bedrijf samen met de gegevens van
+wie dan ook, zoals Obama heeft gedaan met telefoonbedrijven, waarbij we er
+ook maar even vanuit gaan dat het bedrijf niet vrijwillig meewerkt, zoals de
+telefoonbedrijven in de VS die hun klanten illegaal aftapten voor Bush. Als
+je een server moet gebruiken, gebruik dan een server waarvan je de
+beheerders vertrouwd op andere dan commerci&euml;le gronden.</p>
+
+<p>Op de wat langere termijn kunnen we echter alternatieven voor het gebruiken
+van servers opzetten. We kunnen bijvoorbeeld een peer-to-peer-programma
+maken waarmee mensen kunnen samenwerken door hun gegevens versleuteld te
+delen. De vrije-softwaregemeenschap zou gedecentraliseerde
+peer-to-peer-vervangingen voor belangrijke &ldquo;webapplicaties&rdquo;
+moeten ontwikkelen. Het zou slim kunnen zijn om die uit te geven onder de <a
+href="/licenses/why-affero-gpl.html"> GNU Affero GPL</a>, omdat iemand
+anders deze programma's waarschijnlijk gemakkelijk kan omzetten in
+server-gebaseerde programma's. Het <a href="/">GNU-project</a> zoekt
+vrijwilligers om te werken aan zulke vervangingen. We nodigen andere
+vrije-softwareprojecten ook uit om deze kwestie mee te nemen in hun 
ontwerp.</p>
+
+<p>In de tussentijd, als een bedrijf jou uitnodigt om zijn server te gebruiken
+voor jouw eigen computertaken, geef niet toe; gebruik geen SaaSS. Koop of
+installeer geen &ldquo;thin clients&rdquo;, wat simpelweg computers zijn die
+zo zwak zijn dat ze het echte werk op een server doen, behalve als je deze
+gaat doen met <em>jouw</em> server. Gebruik een echte computer en houd je
+gegevens daar. Doe je eigen computeractiviteiten met jouw eigen kopie van
+een vrij programma, in het belang van jouw vrijheid.</p>
+
+<h3>Zie ook:</h3>
+<p><a href="/philosophy/bug-nobody-allowed-to-understand.html">De bug die
+niemand mag begrijpen</a>.</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.nl.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Gelieve algemene vragen over FSF &amp; GNU te sturen naar <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>. Er zijn ook nog <a
+href="/contact/">andere manieren om in contact te komen</a> met de
+FSF. Foute links en andere correcties graag sturen aan <a
+href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>
+
+        &lt;address@hidden&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>. -->
+We doen ons best om goede vertalingen te maken maar staan altijd open voor
+verbeteringen. Suggesties, op- en aanmerkingen sturen aan: <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+<p>Zie <a href="/server/standards/README.translations.html"> Translations
+README</a> voor informatie over het onderhoud van vertalingen op deze
+website.</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; 2010, 2013, 2015, 2016 Richard Stallman</p>
+
+<p>Deze pagina is uitgebracht onder een <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
+Naamsvermelding-GeenAfgeleideWerken 4.0 Internationaal licentie</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.nl.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+ </div>
+
+<p class="unprintable"><!-- timestamp start -->
+Bijgewerkt:
+
+$Date: 2016/06/28 03:59:44 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: philosophy/po/who-does-that-server-really-serve.nl-en.html
===================================================================
RCS file: philosophy/po/who-does-that-server-really-serve.nl-en.html
diff -N philosophy/po/who-does-that-server-really-serve.nl-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ philosophy/po/who-does-that-server-really-serve.nl-en.html  28 Jun 2016 
03:59:44 -0000      1.1
@@ -0,0 +1,469 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>Who Does That Server Really Serve?
+- GNU Project - Free Software Foundation</title>
+
+<!--#include 
virtual="/philosophy/po/who-does-that-server-really-serve.translist" -->
+<!--#include virtual="/server/banner.html" -->
+   
+<h2>Who does that server really serve?</h2>
+
+<p>by <strong>Richard Stallman</strong></p>
+
+<blockquote><p>(The first version was published
+in <a href="http://www.bostonreview.net/richard-stallman-free-software-DRM";>
+Boston Review</a>.)</p></blockquote>
+
+<p><strong>On the Internet, proprietary software isn't the only way to
+lose your freedom.  Service as a Software Substitute, or SaaSS, is
+another way to give someone else power over your computing.</strong></p>
+
+<p>The basic point is, you can have control over a program someone else
+wrote (if it's free), but you can never have control over a service
+someone else runs, so never use a service where in principle a program
+would do.</p>
+
+
+<p>SaaSS means using a service implemented by someone else as a
+substitute for running your copy of a program.  The term is ours;
+articles and ads won't use it, and they won't tell you whether a
+service is SaaSS.  Instead they will probably use the vague and
+distracting term &ldquo;cloud&rdquo;, which lumps SaaSS together with
+various other practices, some abusive and some ok.  With the
+explanation and examples in this page, you can tell whether a service
+is SaaSS.</p>
+
+<h3>Background: How Proprietary Software Takes Away Your Freedom</h3>
+
+<p>Digital technology can give you freedom; it can also take your
+freedom away.  The first threat to our control over our computing came
+from <em>proprietary software</em>: software that the users cannot
+control because the owner (a company such as Apple or Microsoft)
+controls it.  The owner often takes advantage of this unjust power by
+inserting malicious features such as spyware, back doors, and <a
+href="http://DefectiveByDesign.org";>Digital Restrictions Management
+(DRM)</a> (referred to as &ldquo;Digital Rights Management&rdquo; in
+their propaganda).</p>
+
+<p>Our solution to this problem is developing <em>free software</em>
+and rejecting proprietary software.  Free software means that you, as
+a user, have four essential freedoms: (0)&nbsp;to run the program as
+you wish, (1)&nbsp;to study and change the source code so it does what
+you wish, (2)&nbsp;to redistribute exact copies, and (3)&nbsp;to
+redistribute copies of your modified versions.  (See
+the <a href="/philosophy/free-sw.html">free software
+definition</a>.)</p>
+
+<p>With free software, we, the users, take back control of our
+computing.  Proprietary software still exists, but we can exclude it
+from our lives and many of us have done so.  However, we are now
+offered another tempting way to cede control over our computing:
+Service as a Software Substitute (SaaSS).  For our freedom's sake, we
+have to reject that too.</p>
+
+<h3>How Service as a Software Substitute Takes Away Your Freedom</h3>
+
+<p>Service as a Software Substitute (SaaSS) means using a service as a
+substitute for running your copy of a program.  Concretely, it means
+that someone sets up a network server that does certain computing
+tasks&mdash;for instance, modifying a photo, translating text into
+another language, etc.&mdash;then invites users to do computing via
+that server.  A user of the server would send her data to the server,
+which does <em>her own computing</em> on the data thus provided, then
+sends the results back to her or acts directly on her behalf.</p>
+
+<p>The computing is <em>her own</em> because, by assumption, she
+could, in principle, have done it by running a program on her own
+computer (whether or not that program is available to her at
+present).  In cases where this assumption is not so, it isn't SaaSS.</p>
+
+<p>These servers wrest control from the users even more inexorably
+than proprietary software.  With proprietary software, users typically
+get an executable file but not the source code.  That makes it hard to
+study the code that is running, so it's hard to determine what the
+program really does, and hard to change it.</p>
+
+<p>With SaaSS, the users do not have even the executable file that
+does their computing: it is on someone else's server, where the users
+can't see or touch it.  Thus it is impossible for them to ascertain
+what it really does, and impossible to change it.</p>
+
+<p>Furthermore, SaaSS automatically leads to consequences equivalent
+to the malicious features of certain proprietary software.</p>
+
+<p> For instance, some proprietary programs are &ldquo;spyware&rdquo;:
+the program <a href="/philosophy/proprietary-surveillance.html">
+sends out data about users' computing activities</a>.
+Microsoft Windows sends information about users' activities to
+Microsoft.  Windows Media Player reports what each user watches or
+listens to.  The Amazon Kindle reports which pages of which books the
+user looks at, and when.  Angry Birds reports the user's geolocation
+history.</p>
+
+<p>Unlike proprietary software, SaaSS does not require covert code to
+obtain the user's data.  Instead, users must send their data to the
+server in order to use it.  This has the same effect as spyware: the
+server operator gets the data&mdash;with no special effort, by the
+nature of SaaSS.  Amy Webb, who intended never to post any photos of
+her daughter, made the mistake of using SaaSS (Instagram) to edit
+photos of her.  Eventually
+<a 
href="http://www.slate.com/articles/technology/data_mine_1/2013/09/privacy_facebook_kids_don_t_post_photos_of_your_kids_on_social_media.html";>
 they
+leaked from there</a>.
+</p>
+
+<p>Theoretically, homomorphic encryption might some day advance to the
+point where future SaaSS services might be constructed to be unable to
+understand some of the data that users send them.  Such
+services <em>could</em> be set up not to snoop on users; this does not
+mean they <em>will</em> do no snooping.</p>
+
+<p>Some proprietary operating systems have a universal back door,
+permitting someone to remotely install software changes.  For
+instance, Windows has a universal back door with which Microsoft can
+forcibly change any software on the machine.  Nearly all portable
+phones have them, too.  Some proprietary applications also have
+universal back doors; for instance, the Steam client for GNU/Linux
+allows the developer to remotely install modified versions.</p>
+
+<p>With SaaSS, the server operator can change the software in use on
+the server.  He ought to be able to do this, since it's his computer;
+but the result is the same as using a proprietary application program
+with a universal back door: someone has the power to silently impose
+changes in how the user's computing gets done.</p>
+
+<p>Thus, SaaSS is equivalent to running proprietary software with
+spyware and a universal back door.  It gives the server operator
+unjust power over the user, and that power is something we must
+resist.</p>
+
+<h3>SaaSS and SaaS</h3>
+
+<p>Originally we referred to this problematical practice as
+&ldquo;SaaS&rdquo;, which stands for &ldquo;Software as a
+Service&rdquo;.  It's a commonly used term for setting up software on a
+server rather than offering copies of it to users, and we thought it
+described precisely the cases where this problem occurs.</p>
+
+<p>Subsequently we became aware that the term SaaS is sometimes used for
+communication services&mdash;activities for which this issue is not
+applicable.  In addition, the term &ldquo;Software as a Service&rdquo;
+doesn't explain <em>why</em> the practice is bad.  So we coined the term
+&ldquo;Service as a Software Substitute&rdquo;, which defines the bad
+practice more clearly and says what is bad about it.</p>
+
+<h3>Untangling the SaaSS Issue from the Proprietary Software Issue</h3>
+
+<p>SaaSS and proprietary software lead to similar harmful results, but
+the mechanisms are different.  With proprietary software, the
+mechanism is that you have and use a copy which is difficult and/or
+illegal to change.  With SaaSS, the mechanism is that you don't have
+the copy that's doing your computing.</p>
+
+<p>These two issues are often confused, and not only by accident.  Web
+developers use the vague term &ldquo;web application&rdquo; to lump
+the server software together with programs run on your machine in your
+browser.  Some web pages install nontrivial, even large JavaScript
+programs into your browser without informing
+you.  <a href="/philosophy/javascript-trap.html">When these JavaScript
+programs are nonfree</a>, they cause the same sort of injustice as any
+other nonfree software.  Here, however, we are concerned with the
+issue of using the service itself.</p>
+
+<p>Many free software supporters assume that the problem of SaaSS will
+be solved by developing free software for servers.  For the server
+operator's sake, the programs on the server had better be free; if
+they are proprietary, their developers/owners have power over the
+server.  That's unfair to the server operator, and doesn't help the
+server's users at all.  But if the programs on the server are free,
+that doesn't protect <em>the server's users</em> from the effects of
+SaaSS.  These programs liberate the server operator, but not the
+server's users.</p>
+
+<p>Releasing the server software source code does benefit the
+community: it enables suitably skilled users to set up similar
+servers, perhaps changing the
+software.  <a href="/licenses/license-recommendations.html"> We
+recommend using the GNU Affero GPL</a> as the license for programs
+often used on servers.</p>
+
+<p>But none of these servers would give you control over computing you
+do on it, unless it's <em>your</em> server (one whose software load
+you control, regardless of whether the machine is your property).  It
+may be OK to trust your friend's server for some jobs, just as you
+might let your friend maintain the software on your own computer.
+Outside of that, all these servers would be SaaSS for you.  SaaSS
+always subjects you to the power of the server operator, and the only
+remedy is, <em>Don't use SaaSS!</em>  Don't use someone else's server
+to do your own computing on data provided by you.</p>
+
+<p>This issue demonstrates the depth of the difference between
+&ldquo;open&rdquo; and &ldquo;free&rdquo;.  Source code that is open
+source <a href="/philosophy/free-open-overlap.html">is, nearly always,
+free</a>.  However, the idea of
+an <a href="http://opendefinition.org/software-service";>&ldquo;open
+software&rdquo; service</a>, meaning one whose server software is open
+source and/or free, fails to address the issue of SaaSS.</p>
+
+<p>Services are fundamentally different from programs, and the ethical
+issues that services raise are fundamentally different from the issues
+that programs raise.  To avoid confusion,
+we <a href="/philosophy/network-services-arent-free-or-nonfree.html">
+avoid describing a service as &ldquo;free&rdquo; or
+&ldquo;proprietary.&rdquo;</a></p>
+
+<h3>Distinguishing SaaSS from Other Network Services</h3>
+
+<p>Which online services are SaaSS?  The clearest example is a
+translation service, which translates (say) English text into Spanish
+text.  Translating a text for you is computing that is purely yours.
+You could do it by running a program on your own computer, if only you
+had the right program.  (To be ethical, that program should be free.)
+The translation service substitutes for that program, so it is Service
+as a Software Substitute, or SaaSS.  Since it denies you control
+over your computing, it does you wrong.</p>
+
+<p>Another clear example is using a service such as Flickr or
+Instagram to modify a photo.  Modifying photos is an activity that
+people have done in their own computers for decades; doing it in a
+server you don't control, rather than your own computer, is SaaSS.</p>
+
+<p>Rejecting SaaSS does not mean refusing to use any network servers
+run by anyone other than you.  Most servers are not SaaSS because the
+jobs they do are some sort of communication, rather than the user's
+own computing.</p>
+
+<p>The original idea of web servers wasn't to do computing for you, it
+was to publish information for you to access.  Even today this is what
+most web sites do, and it doesn't pose the SaaSS problem, because
+accessing someone's published information isn't doing your own
+computing.  Neither is use of a blog site to publish your own works,
+or using a microblogging service such as Twitter or StatusNet.  (These
+services may or may not have other problems, depending on details.)
+The same goes for other communication not meant to be private, such as
+chat groups.</p>
+
+<p>In its essence, social networking is a form of communication and
+publication, not SaaSS.  However, a service whose main facility is
+social networking can have features or extensions which are SaaSS.</p>
+
+<p>If a service is not SaaSS, that does not mean it is OK.  There are
+other ethical issues about services.  For instance, Facebook
+distributes video in Flash, which pressures users to run nonfree
+software; it requires running nonfree JavaScript code; and it gives
+users a misleading impression of privacy while luring them into baring
+their lives to Facebook.  Those are important issues, different from
+the SaaSS issue.
+</p>
+
+<p>Services such as search engines collect data from around the web
+and let you examine it.  Looking through their collection of data
+isn't your own computing in the usual sense&mdash;you didn't provide
+that collection&mdash;so using such a service to search the web is not
+SaaSS.  However, using someone else's server to implement a search
+facility for your own site <em>is</em> SaaSS.</p>
+
+<p>Purchasing online is not SaaSS, because the computing
+isn't <em>your own</em> activity; rather, it is done jointly by and
+for you and the store.  The real issue in online shopping is whether
+you trust the other party with your money and other personal
+information (starting with your name).</p>
+
+<p>Repository sites such as Savannah and SourceForge are not
+inherently SaaSS, because a repository's job is publication of data
+supplied to it.</p>
+
+<p>Using a joint project's servers isn't SaaSS because the computing
+you do in this way isn't your own.  For instance, if you edit pages on
+Wikipedia, you are not doing your own computing; rather, you are
+collaborating in Wikipedia's computing.  Wikipedia controls its own
+servers, but organizations as well as individuals encounter the
+problem of SaaSS if they do their computing in someone else's
+server.</p>
+
+<p>Some sites offer multiple services, and if one is not SaaSS,
+another may be SaaSS.  For instance, the main service of Facebook is
+social networking, and that is not SaaSS; however, it supports
+third-party applications, some of which are SaaSS.  Flickr's main
+service is distributing photos, which is not SaaSS, but it also has
+features for editing photos, which is SaaSS.  Likewise, using
+Instagram to post a photo is not SaaSS, but using it to transform the
+photo is SaaSS.</p>
+
+<p>Google Docs shows how complex the evaluation of a single service
+can become.  It invites people to edit a document by running a
+large <a href="/philosophy/javascript-trap.html">nonfree JavaScript
+program</a>, clearly wrong.  However, it offers an API for uploading
+and downloading documents in standard formats.  A free software editor
+can do so through this API.  This usage scenario is not SaaSS, because
+it uses Google Docs as a mere repository.  Showing all your data to a
+company is bad, but that is a matter of privacy, not SaaSS; depending
+on a service for access to your data is bad, but that is a matter of
+risk, not SaaSS.  On the other hand, using the service for converting
+document formats <em>is</em> SaaSS, because it's something you could
+have done by running a suitable program (free, one hopes) in your own
+computer.</p>
+
+<p>Using Google Docs through a free editor is rare, of course.  Most
+often, people use it through the nonfree JavaScript program, which is
+bad like any nonfree program.  This scenario might involve SaaSS, too;
+that depends on what part of the editing is done in the JavaScript
+program and what part in the server.  We don't know, but since SaaSS
+and proprietary software do similar wrong to the user, it is not
+crucial to know.</p>
+
+<p>Publishing via someone else's repository does not raise privacy
+issues, but publishing through Google Docs has a special problem: it
+is impossible even to <em>view the text</em> of a Google Docs document
+in a browser without running the nonfree JavaScript code.  Thus, you
+should not use Google Docs to publish anything&mdash;but the reason
+is not a matter of SaaSS.</p>
+
+<p>The IT industry discourages users from making these distinctions.
+That's what the buzzword &ldquo;cloud computing&rdquo; is for.  This
+term is so nebulous that it could refer to almost any use of the
+Internet.  It includes SaaSS as well as many other network usage
+practices.  In any given context, an author who writes
+&ldquo;cloud&rdquo; (if a technical person) probably has a specific
+meaning in mind, but usually does not explain that in other articles
+the term has other specific meanings.  The term leads people to
+generalize about practices they ought to consider individually.</p>
+
+<p>If &ldquo;cloud computing&rdquo; has a meaning, it is not a way of
+doing computing, but rather a way of thinking about computing: a
+devil-may-care approach which says, &ldquo;Don't ask questions.  Don't
+worry about who controls your computing or who holds your data.  Don't
+check for a hook hidden inside our service before you swallow it.
+Trust companies without hesitation.&rdquo; In other words, &ldquo;Be a
+sucker.&rdquo; A cloud in the mind is an obstacle to clear thinking.
+For the sake of clear thinking about computing, let's avoid the term
+&ldquo;cloud.&rdquo;</p>
+
+<h3 id="renting">Renting a Server Distinguished from SaaSS</h3>
+
+<p>If you rent a server (real or virtual), whose software load you
+have control over, that's not SaaSS.  In SaaSS, someone else decides
+what software runs on the server and therefore controls the computing
+it does for you.  In the case where you install the software on the
+server, you control what computing it does for you.  Thus, the rented
+server is virtually your computer.  For this issue, it counts as
+yours.</p>
+
+<p>The <em>data</em> on the rented remote server is less secure than
+if you had the server at home, but that is a separate issue from
+SaaSS.</p>
+
+<h3>Dealing with the SaaSS Problem</h3>
+
+<p>Only a small fraction of all web sites do SaaSS; most don't raise
+the issue.  But what should we do about the ones that raise it?</p>
+
+<p>For the simple case, where you are doing your own computing on data
+in your own hands, the solution is simple: use your own copy of a free
+software application.  Do your text editing with your copy of a free
+text editor such as GNU Emacs or a free word processor.  Do your photo
+editing with your copy of free software such as GIMP.  What if there
+is no free program available?  A proprietary program or SaaSS would
+take away your freedom, so you shouldn't use those.  You can contribute
+your time or your money to development of a free replacement.</p>
+
+<p>What about collaborating with other individuals as a group?  It may
+be hard to do this at present without using a server, and your group
+may not know how to run its own server.  If you use someone else's
+server, at least don't trust a server run by a company.  A mere
+contract as a customer is no protection unless you could detect a
+breach and could really sue, and the company probably writes its
+contracts to permit a broad range of abuses.  The state can subpoena
+your data from the company along with everyone else's, as Obama has
+done to phone companies, supposing the company doesn't volunteer them
+like the US phone companies that illegally wiretapped their customers
+for Bush.  If you must use a server, use a server whose operators give
+you a basis for trust beyond a mere commercial relationship.</p>
+
+<p>However, on a longer time scale, we can create alternatives to
+using servers.  For instance, we can create a peer-to-peer program
+through which collaborators can share data encrypted.  The free
+software community should develop distributed peer-to-peer
+replacements for important &ldquo;web applications&rdquo;.  It may be
+wise to release them under
+the <a href="/licenses/why-affero-gpl.html"> GNU Affero GPL</a>, since
+they are likely candidates for being converted into server-based
+programs by someone else.  The <a href="/">GNU project</a> is looking
+for volunteers to work on such replacements.  We also invite other
+free software projects to consider this issue in their design.</p>
+
+<p>In the meantime, if a company invites you to use its server to do
+your own computing tasks, don't yield; don't use SaaSS.  Don't buy or
+install &ldquo;thin clients&rdquo;, which are simply computers so weak
+they make you do the real work on a server, unless you're going to use
+them with <em>your</em> server.  Use a real computer and keep your
+data there.  Do your own computing with your own copy of a free
+program, for your freedom's sake.</p>
+
+<h3>See also:</h3>
+<p><a href="/philosophy/bug-nobody-allowed-to-understand.html">The
+Bug Nobody is Allowed to Understand</a>.</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:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&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:address@hidden";>
+        &lt;address@hidden&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; 2010, 2013, 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/06/28 03:59:44 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]