From: Filipe Silva <filipe.silva@gmail.com>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Cc: Ted Zlatanov <tzz@lifelogs.com>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: official Emacs Docker image
Date: Fri, 3 Feb 2017 22:37:55 -0200 [thread overview]
Message-ID: <CAEwkUWNY_m2Cx8HJ=5K0Ug9bya_cvt7v_rMz3pPQ6BkWxnLYtw@mail.gmail.com> (raw)
In-Reply-To: <865B41B3-9001-4F4A-9CF2-0C648100E0B2@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4161 bytes --]
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、Ted Zlatanov <tzz@lifelogs.com>のメール:
>
> > 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
>
[-- Attachment #2: Type: text/html, Size: 6465 bytes --]
next prev parent reply other threads:[~2017-02-04 0:37 UTC|newest]
Thread overview: 126+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 13:57 Move to a cadence release model? John Yates
2015-11-10 14:28 ` John Wiegley
2015-11-10 16:42 ` Eli Zaretskii
2015-11-10 17:03 ` John Wiegley
2015-11-11 0:17 ` Release process (was Re: Move to a cadence release model?) Stephen Leake
2015-11-11 0:24 ` John Wiegley
2015-11-11 3:45 ` Eli Zaretskii
2015-11-11 10:45 ` Stephen Leake
2015-11-11 15:43 ` Eli Zaretskii
2015-11-11 23:06 ` bug policy (was Re: Release process) Stephen Leake
2015-11-12 16:12 ` Eli Zaretskii
2015-11-12 16:39 ` John Wiegley
2015-11-12 17:36 ` Eli Zaretskii
2015-11-12 17:50 ` John Wiegley
2015-11-12 18:04 ` Eli Zaretskii
2015-11-11 16:39 ` Release process (was Re: Move to a cadence release model?) John Wiegley
2015-11-12 8:19 ` Xue Fuqiao
2015-11-17 0:09 ` Xue Fuqiao
2015-11-12 8:15 ` Xue Fuqiao
2015-11-10 14:32 ` Move to a cadence release model? Alan Mackenzie
2015-11-10 17:13 ` Eli Zaretskii
2015-11-10 17:11 ` Eli Zaretskii
2015-11-10 17:37 ` Óscar Fuentes
2015-11-10 17:44 ` Automate Emacs UI testing? (was: Move to a cadence release model?) John Wiegley
2015-11-10 18:01 ` Automate Emacs UI testing? Ashton Kemerling
2015-11-10 18:02 ` Automate Emacs UI testing? (was: Move to a cadence release model?) Eli Zaretskii
2015-11-10 19:16 ` Automate Emacs UI testing? joakim
2015-11-10 19:37 ` John Wiegley
2015-11-11 16:59 ` Richard Stallman
2015-11-11 17:18 ` joakim
2015-11-11 23:27 ` Richard Stallman
2015-11-12 2:26 ` official Emacs Docker image (was: Automate Emacs UI testing?) Ted Zlatanov
2015-11-12 15:49 ` official Emacs Docker image Nic Ferrier
2015-11-12 21:01 ` Ricardo Wurmus
2015-11-12 22:31 ` official Emacs Docker image (was: Automate Emacs UI testing?) Richard Stallman
2015-11-12 23:32 ` official Emacs Docker image joakim
2016-07-06 15:22 ` Ted Zlatanov
2016-07-07 21:56 ` Richard Stallman
2016-07-08 13:36 ` Ted Zlatanov
2016-07-09 16:54 ` Richard Stallman
2016-07-09 23:04 ` Ted Zlatanov
2016-07-10 14:25 ` Richard Stallman
2016-07-12 22:45 ` John Wiegley
2016-07-13 13:12 ` Richard Stallman
2016-07-13 16:34 ` John Wiegley
2016-12-30 0:10 ` Richard Stallman
2016-12-30 0:53 ` John Wiegley
2016-12-30 21:36 ` Richard Stallman
2016-12-30 22:01 ` joakim
2016-12-30 22:08 ` John Wiegley
2016-12-31 18:25 ` Richard Stallman
2017-01-27 14:56 ` Ted Zlatanov
2017-01-27 19:45 ` Filipe Silva
2017-01-30 14:36 ` Ted Zlatanov
2017-01-30 17:10 ` Ricardo Wurmus
2017-01-30 17:44 ` Ted Zlatanov
2017-01-31 0:14 ` Filipe Silva
2017-01-31 14:32 ` Ted Zlatanov
2017-02-01 3:03 ` Richard Stallman
2017-02-01 15:25 ` Ted Zlatanov
2017-02-02 2:53 ` Richard Stallman
2017-02-02 5:13 ` Mike Gerwitz
2017-02-02 14:21 ` Ted Zlatanov
2017-02-03 7:00 ` Stefan Reichör
2017-02-03 11:18 ` Filipe Silva
2017-02-04 2:56 ` Mike Gerwitz
2017-02-03 13:45 ` Ted Zlatanov
2017-02-03 21:59 ` Richard Stallman
2017-02-03 23:38 ` Ted Zlatanov
2017-02-03 23:54 ` Jean-Christophe Helary
2017-02-04 0:37 ` Filipe Silva [this message]
2017-02-04 1:12 ` Jean-Christophe Helary
2017-02-04 1:32 ` Filipe Silva
2017-02-04 23:52 ` Richard Stallman
2017-02-05 0:24 ` Jean-Christophe Helary
2017-02-04 23:54 ` Richard Stallman
2017-02-04 3:11 ` Mike Gerwitz
2017-02-04 4:13 ` Ted Zlatanov
2017-02-04 4:47 ` Mike Gerwitz
2017-02-06 10:49 ` Giuseppe Scrivano
2017-02-13 8:37 ` Richard Stallman
2017-02-13 9:55 ` Giuseppe Scrivano
2017-02-14 0:48 ` Richard Stallman
2017-02-14 2:07 ` Mike Gerwitz
2017-02-14 2:04 ` Mike Gerwitz
2017-02-04 23:54 ` Richard Stallman
2017-02-05 0:47 ` Ted Zlatanov
2017-02-04 23:48 ` Richard Stallman
2017-01-28 2:18 ` Richard Stallman
2017-02-21 15:01 ` Philippe Vaucher
2017-03-02 15:03 ` Ted Zlatanov
2017-03-03 10:09 ` Philippe Vaucher
2017-03-03 10:15 ` Philippe Vaucher
2017-03-08 20:30 ` Philippe Vaucher
2017-03-13 10:03 ` Philippe Vaucher
2018-04-04 18:33 ` Philippe Vaucher
2016-12-31 22:04 ` Ricardo Wurmus
2017-01-01 5:39 ` Elias Mårtenson
2017-01-01 9:03 ` Ricardo Wurmus
2017-01-01 10:15 ` Elias Mårtenson
2017-01-06 15:56 ` Ricardo Wurmus
2017-01-07 23:19 ` Philippe Vaucher
2016-12-31 1:22 ` Yann Hodique
2016-12-31 2:08 ` John Wiegley
2017-01-28 11:06 ` Alex Bennée
2016-12-31 10:11 ` Philippe Vaucher
2016-07-13 14:41 ` Ted Zlatanov
2015-11-12 11:36 ` Automate Emacs UI testing? Mathieu Lirzin
2015-11-12 11:43 ` joakim
2015-11-10 18:20 ` Move to a cadence release model? Richard Stallman
2015-11-10 23:50 ` Xue Fuqiao
2015-11-10 23:58 ` John Wiegley
2015-11-11 1:55 ` John Yates
2015-11-11 9:02 ` Xue Fuqiao
2015-11-11 15:37 ` Eli Zaretskii
2015-11-12 22:35 ` Richard Stallman
2015-11-11 15:49 ` Eli Zaretskii
2015-11-12 11:27 ` Stelian Iancu
2015-11-12 16:22 ` Eli Zaretskii
2015-11-12 16:44 ` Stelian Iancu
2015-11-12 16:57 ` Eli Zaretskii
2015-11-11 15:48 ` Eli Zaretskii
2015-11-12 7:23 ` Xue Fuqiao
2015-11-12 7:37 ` Xue Fuqiao
2015-11-12 16:15 ` Eli Zaretskii
2015-11-20 3:02 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEwkUWNY_m2Cx8HJ=5K0Ug9bya_cvt7v_rMz3pPQ6BkWxnLYtw@mail.gmail.com' \
--to=filipe.silva@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@gmail.com \
--cc=tzz@lifelogs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).