From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Filipe Silva Newsgroups: gmane.emacs.devel Subject: Re: official Emacs Docker image Date: Fri, 3 Feb 2017 22:37:55 -0200 Message-ID: References: <87k29gsgam.fsf@lifelogs.com> <87k29cmq1u.fsf@elephly.net> <8737g0qw7z.fsf@lifelogs.com> <87vasvnvty.fsf@lifelogs.com> <87bmumrkzn.fsf@flea> <87tw8cr7v0.fsf@flea> <87wpd7rc70.fsf@xsteve.at> <8760krqtf9.fsf@flea> <87shnuq1z2.fsf@flea> <865B41B3-9001-4F4A-9CF2-0C648100E0B2@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c095082067ef60547a99cc5 X-Trace: blaine.gmane.org 1486168687 20152 195.159.176.226 (4 Feb 2017 00:38:07 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 4 Feb 2017 00:38:07 +0000 (UTC) Cc: Ted Zlatanov , Emacs developers To: Jean-Christophe Helary Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Feb 04 01:38:03 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cZoMc-00051v-Cm for ged-emacs-devel@m.gmane.org; Sat, 04 Feb 2017 01:38:02 +0100 Original-Received: from localhost ([::1]:37446 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZoMh-0005pA-Jm for ged-emacs-devel@m.gmane.org; Fri, 03 Feb 2017 19:38:07 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59934) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZoMY-0005p5-W5 for emacs-devel@gnu.org; Fri, 03 Feb 2017 19:38:00 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cZoMX-0002ds-BA for emacs-devel@gnu.org; Fri, 03 Feb 2017 19:37:59 -0500 Original-Received: from mail-oi0-x22f.google.com ([2607:f8b0:4003:c06::22f]:35569) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cZoMX-0002dR-3U for emacs-devel@gnu.org; Fri, 03 Feb 2017 19:37:57 -0500 Original-Received: by mail-oi0-x22f.google.com with SMTP id j15so20563976oih.2 for ; Fri, 03 Feb 2017 16:37:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Svr9FgZIV5QXGdqnPGbPJ0xBhyDf8tG4Sd/l4XBMgKw=; b=SKKQuMaC4mIPwJy0LcjJerfQh2PgPFIncjcghn9aieMJ701F2M3cHnWbYGsYKvpyhj Qg+KdlLPdBbCrvAsIUfYFqzZosu4d5BSXNjh3us2WUSb195UiPL5oDKjQe+ByuFxWqC0 p5/gYDAy1RalajQseOzTGNbcXi1icyrUANXO3d2htgDUP4GjQgix2gW7mk8sCtBOR4OU JQ9SSiLjR0fRhTsGunYLwYx4i/Yuc5MssGi/RdvpTZq47T8rYtng2NSK6VimjFYKtKzj WSk7nXb58b0N/yIrGtIcETtvA2rt+ZqyTmrCDOEJ7CZLiSz/ck4tzRpwBDQ4cFc0vtch DHTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Svr9FgZIV5QXGdqnPGbPJ0xBhyDf8tG4Sd/l4XBMgKw=; b=tThwvTKYDBNmTU4aUkonmzAJ/tSIQxq5Xrv7bKZsSqi/u8kQh4Ynu/fvJBEFfNIq8G TjZk0t/oNNnFb5lIjKrsvzRcMadTakd3WytX4tQ0j4ikUgquf6BIZFQmpFEKoKYllu5T yZiFDuDJD3rPqZLDwKGEac62TOo7hdh2dkktf2et4xGxYkQfafZlMwZfQZrijXgxunQe gx+yVs4xy1qaInOEUPTSOIRrMygFV5DVWJ5Mhgb6lajfGgu8as0/fgKp+0bCfNPbUfi6 PhxSc0r+0dWzuD8wgCtB9JL1C4jBLmPjpiIUzB6251a3rrlpbOhSdDlVkLNn01xebOLz hInw== X-Gm-Message-State: AIkVDXJsvRufCLTB2gsRUq/d9u42K/uqWDpXX+e+QgO8CXI8zDJz+7tlsFr4rGRH2rpSvzkqBHA3ffUO8GzCFw== X-Received: by 10.202.241.70 with SMTP id p67mr7510212oih.67.1486168676267; Fri, 03 Feb 2017 16:37:56 -0800 (PST) Original-Received: by 10.157.56.242 with HTTP; Fri, 3 Feb 2017 16:37:55 -0800 (PST) In-Reply-To: <865B41B3-9001-4F4A-9CF2-0C648100E0B2@gmail.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4003:c06::22f X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:211947 Archived-At: --94eb2c095082067ef60547a99cc5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sometimes people minify js to make better usage of the network, not because they want to hide from you the js source code to gain more power over you as a user. There's no practical way to run your specific modified version of js in a browser to customize your own site experience because the js code is just a tailor made client for the site's server code. Look this way: They could have rendered the whole html that you see in the server side, and still there are tons of websites that do that. and in that case you would have just the bare html and css in your hands, which doesn't change the fact that you are using non-free software that generates that html; still you wouldn't have a problem with that because "you're not running non-free js code on your browser". but instead they chose to split the software: they hand it to your browser a piece of the software in js so that you can have a more dynamic experience. As a plus your browser doesn't have to call the server all the time to generate an updated DOM. Now UI logic can be very hard and complex so instead of handing you a plain js file which can be many KBs long, they minify it, and maybe gzip it so they can better use the network resources, potentially saving energy for the benefit off all mankind. I see this way: It's just a website, but now some of the server's code is offloaded to the browser by means of js. But it is still a website. I don't think it is reasonable asking every website to stop minifying the js and to provide a way to submit a custom modified form of js client code that interacts with the website in a customized way. That would require to also release the server code, which would mean that to be free all websites that deliver js client code to web browsers would have to release their server code. Can you all see the problem here? js client code is not the same thing as regular installed on my pc software. I have to trust my libre browser, which is in fact installed on my local computer and which I can modify and inspect the source code. I trust that it is written in a way that stops client js code from doing harm to my privacy and freedom. We have different classes of software here. Software fully installed locally on my machine is one class of software. Server software, which is not running on my machine is a different kind of software. And software that is split between server software and client software *running in a libre sandboxed environment installed on my machine* is another class of software entirely. I would assert that each class of software described above brings about different philosophical and ethical questions and deserve to be differently treated. For starters, I would argue that a js client code, *running on my libre sandboxed browser environment*, which is really just a part of a much larger software, which is a website, does not harm my freedom and my privacy as long as the libre browser is properly constructed to properly handle js client code. Doesn't this proposition seem reasonable to you gentleman? Filipe On Fri, Feb 3, 2017 at 9:54 PM, Jean-Christophe Helary < jean.christophe.helary@gmail.com> wrote: > > 2017/02/04 8:38=E3=80=81Ted Zlatanov =E3=81=AE=E3=83= =A1=E3=83=BC=E3=83=AB: > > > Your implicit assumption here is that if any part of a service involves > > nonfree software (in this case, Docker Hub account registration and > > maintenance), then using any other part of the service (in this case, > > Docker Hub as an image repository) is against this purpose. > > > > That specific assumption, in my opinion, is overreaching and does not > > serve the original purpose you quoted, yet it has become an important > > argument for the FSF. > > Instead of arguing here, why don't you ask Docker Hub why they require > non-free software for such a trivial task and try to convince them to not > do that? > *That* would better promote free software than having Emacs hosted there > while ignoring the non-free aspects of the system. > A much better way to spend your energy in my opinion. > > Jean-Christophe Helary > --94eb2c095082067ef60547a99cc5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Sometimes people minify js to make better usage of the netwo= rk, not because they want to hide from you the js source code to gain more = power over you as a user. There's no practical way to run your specific= modified version of js in a browser to customize your own site experience = because the js code is just a tailor made client for the site's server = code.

Look this way: They could have rendered the whole html tha= t you see in the server side, and still there are tons of websites that do = that. and in that case you would have just the bare html and css in your ha= nds, which doesn't change the fact that you are using non-free software= that generates that html; still you wouldn't have a problem with that = because "you're not running non-free js code on your browser"= .=C2=A0

but instead they chose to split the software: they hand = it to your browser a piece of the software in js so that you can have a mor= e dynamic experience. As a plus your browser doesn't have to call the s= erver all the time to generate an updated DOM. Now UI logic can be very har= d and complex so instead of handing you a plain js file which can be many K= Bs long, they minify it, and maybe gzip it so they can better use the netwo= rk resources, potentially saving energy for the benefit off all mankind.

I see this way: It's just a website, but now some of the serve= r's code is offloaded to the browser by means of js. But it is still a = website.=C2=A0

I don't think it is reasonable asking every w= ebsite to stop minifying the js and to provide a way to submit a custom mod= ified form of js client code that interacts with the website in a customize= d way. That would require to also release the server code, which would mean= that to be free all websites that deliver js client code to web browsers w= ould have to release their server code.=C2=A0

Can you all see th= e problem here? js client code is not the same thing as regular installed o= n my pc software.

I have to trust my libre browser, which is in = fact installed on my local computer and which I can modify and inspect the = source code. I trust that it is written in a way that stops client js code = from doing harm to my privacy and freedom.=C2=A0

We have differe= nt classes of software here. Software fully installed locally on my machine= is one class of software. Server software, which is not running on my mach= ine is a different kind of software. And software that is split between ser= ver software and client software *running in a libre sandboxed environment = installed on my machine* is another class of software entirely.

= I would assert that each class of software described above brings about dif= ferent philosophical and ethical questions and deserve to be differently tr= eated.=C2=A0

For starters, I would argue that a js client code, = *running on my libre sandboxed browser environment*, which is really just a= part of a much larger software, which is a website, does not harm my freed= om and my privacy as long as the libre browser is properly constructed to p= roperly handle js client code.

Doesn't this proposition seem= reasonable to you gentleman?

Filipe


On Fri, Feb 3, 2017 at 9:= 54 PM, Jean-Christophe Helary <jean.christophe.helary@gmail= .com> wrote:
> 2017/02/0= 4 8:38=E3=80=81Ted Zlatanov <tzz@lif= elogs.com>=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB:

> Your implicit assumption here is that if any part of a service involve= s
> nonfree software (in this case, Docker Hub account registration and > maintenance), then using any other part of the service (in this case,<= br> > Docker Hub as an image repository) is against this purpose.
>
> That specific assumption, in my opinion, is overreaching and does not<= br> > serve the original purpose you quoted, yet it has become an important<= br> > argument for the FSF.

Instead of arguing here, why don't you ask Docker Hub why they r= equire non-free software for such a trivial task and try to convince them t= o not do that?
*That* would better promote free software than having Emacs hosted there wh= ile ignoring the non-free aspects of the system.
A much better way to spend your energy in my opinion.

Jean-Christophe Helary

--94eb2c095082067ef60547a99cc5--