From: Christopher Allan Webber <cwebber@dustycloud.org>
To: rms@gnu.org
Cc: Bastien Guerry <bzg@gnu.org>, lokedhs@gmail.com, emacs-devel@gnu.org
Subject: Re: Condition to link to javascript code?
Date: Wed, 21 Dec 2016 21:13:53 -0600 [thread overview]
Message-ID: <87fulgveoe.fsf@dustycloud.org> (raw)
In-Reply-To: <E1cJOwU-0000w4-77@fencepost.gnu.org>
Richard Stallman writes:
> If it's a choice between linking to klipse.js on the same server
> and linking to klipse.js on the Google server, I see no particular
> ethical reason to prefer one or the other.
There's one reason at least; using content from Google's servers can
result in Google collecting information about what web pages people are
visiting.
next prev parent reply other threads:[~2016-12-22 3:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 3:01 Condition to link to javascript code? Bastien
2016-12-15 3:41 ` Clément Pit--Claudel
2016-12-15 12:12 ` Bastien
2016-12-17 15:47 ` Richard Stallman
2016-12-18 17:47 ` Bastien Guerry
2016-12-19 7:20 ` Elias Mårtenson
2016-12-19 8:06 ` Bastien Guerry
2016-12-19 8:46 ` Elias Mårtenson
2016-12-19 16:32 ` Bastien Guerry
2016-12-19 16:52 ` Clément Pit--Claudel
2016-12-20 18:15 ` Richard Stallman
2016-12-20 19:10 ` Davis Herring
2016-12-21 17:14 ` Richard Stallman
2016-12-21 11:28 ` Rasmus
2016-12-21 17:18 ` Richard Stallman
2016-12-22 10:24 ` Rasmus
2016-12-22 19:56 ` Richard Stallman
2016-12-23 13:40 ` Achim Gratz
2016-12-23 16:18 ` Richard Stallman
2016-12-24 11:41 ` Achim Gratz
2016-12-24 18:55 ` Richard Stallman
2016-12-25 10:04 ` Achim Gratz
2016-12-25 20:43 ` Richard Stallman
2016-12-22 3:13 ` Christopher Allan Webber [this message]
2016-12-22 19:54 ` Richard Stallman
2016-12-23 13:33 ` Achim Gratz
2016-12-23 16:18 ` Richard Stallman
2016-12-19 13:44 ` Stefan Monnier
2016-12-19 13:07 ` Richard Stallman
2016-12-19 17:01 ` Bastien Guerry
2016-12-20 18:16 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fulgveoe.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lokedhs@gmail.com \
--cc=rms@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.