all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Bastien <bzg@gnu.org>
Cc: kfogel@red-bean.com, mccracken.joel@gmail.com,
	monnier@iro.umontreal.ca, vibhavp@gmail.com, emacs-devel@gnu.org
Subject: Re: twitter.el, anyone?
Date: Tue, 21 Jan 2014 09:42:44 -0500	[thread overview]
Message-ID: <E1W5cXM-0000ji-Hz@fencepost.gnu.org> (raw)
In-Reply-To: <87y52agzel.fsf@bzg.ath.cx> (message from Bastien on Mon, 20 Jan 2014 21:40:34 +0100)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

Sorry, I can't concretely understand the information you sent.  Many
points are not clear to me.  For instance, is "CA certificate"
synonymous with "Symantec Root Certificate"?  I can't tell.

Does "Root Certificate" refer to private data that the server holds
(analogous to a GPG private key), or data that users should all have
(analogous to a GPG public key), or both, or what?

Does the Symantec license forbid everyone, even Twitter, from
redistributing the data that users need to run twittering mode?

Depending on the answers to these questions, that issue might be
a fatal problem or it might be no problem at all.

-- 
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
  Use Ekiga or an ordinary phone call.




  reply	other threads:[~2014-01-21 14:42 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15  4:04 twitter.el, anyone? Richard Stallman
2014-01-15  4:24 ` Joel Mccracken
2014-01-15  7:08   ` Karl Fogel
2014-01-15 14:53     ` Stefan Monnier
2014-01-15 16:31       ` Bastien
2014-01-16 17:56       ` Richard Stallman
2014-01-16 18:13         ` Vibhav Pant
2014-01-16 21:16           ` Joel Mccracken
2014-01-17  1:39             ` Stephen J. Turnbull
2014-01-17  5:48             ` chad
2014-01-17 14:10           ` Richard Stallman
2014-01-17 14:34             ` Bastien
2014-01-18 12:33               ` Richard Stallman
2014-01-18 13:17                 ` Vibhav Pant
2014-01-18 13:22                   ` Vibhav Pant
2014-01-19 12:12                   ` Richard Stallman
2014-01-19 13:25                     ` Vibhav Pant
2014-01-20  9:14                       ` Richard Stallman
2014-01-19 15:26                 ` Bastien
2014-01-19 17:54                   ` Achim Gratz
2014-01-20  9:32                     ` Bastien
2014-01-19 20:29                   ` Stefan Monnier
2014-01-20  9:46                     ` Bastien
2014-01-20 19:22                       ` Richard Stallman
2014-01-20 20:40                         ` Bastien
2014-01-21 14:42                           ` Richard Stallman
2014-01-21 15:10                             ` Bastien
2014-01-22 15:31                               ` Richard Stallman
2014-01-23  8:20                               ` Bastien
2014-01-23 17:18                                 ` Richard Stallman
2014-01-20 19:20                     ` Richard Stallman
2014-01-20 19:22                   ` Richard Stallman
2014-01-20 20:40                     ` Bastien
2014-01-21 14:42                       ` Richard Stallman [this message]
2014-01-21 15:26                         ` Bastien
2014-01-23 10:55                           ` Richard Stallman
2014-01-23 11:46                             ` Bastien
2014-01-15  7:08 ` David Kastrup
2014-01-15  7:42   ` Vibhav Pant
2014-01-15  8:53     ` chad
2014-01-16 17:53   ` Richard Stallman
2014-01-16 18:59     ` David Kastrup
2014-01-16 21:38     ` Sebastien Vauban
2014-01-17  1:14       ` Vibhav Pant
2014-03-07 10:59 ` Steinar Bang
2014-03-07 12:11   ` Matt Ford
2014-03-07 13:35     ` Tassilo Horn
2014-03-08  9:45       ` Grim Schjetne
2014-03-08 15:11         ` Lars Ingebrigtsen

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=E1W5cXM-0000ji-Hz@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=bzg@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.com \
    --cc=mccracken.joel@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=vibhavp@gmail.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 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.