unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Petton <nicolas@petton.fr>
To: Yoni Rabkin <yoni@rabkins.net>
Cc: bug-gnu-emacs@gnu.org, emacs-devel <emacs-devel@gnu.org>
Subject: Re: New iteration on the Emacs homepage
Date: Wed, 30 Mar 2016 10:08:16 +0200	[thread overview]
Message-ID: <87k2kks80f.fsf@petton.fr> (raw)
In-Reply-To: <878u11uqh0.fsf@rabkins.net>

[-- Attachment #1: Type: text/plain, Size: 767 bytes --]

Yoni Rabkin <yoni@rabkins.net> writes:

> As long as we are on this topic, someone has just pointed out to me (on
> #fsf IRC) that the CSS files are being served from third-party servers,
> namely:
>
> https://code.cdn.mozilla.net/fonts/fira.css
> https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css

I removed the second one (it was unused).

> I feel like it would be better if those CSS files would be served from
> fsf-controlled URLs like static.fsf.org, so that the FSF has control
> over them.

I can do that.

> This would have the additional benefit of not leaking information about
> anyone visiting fsf.org to third-parties.

But it has a cost too: it won't be served by the Mozilla CDN, and we'll
have to maintain this file.

Nico

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

  reply	other threads:[~2016-03-30  8:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y4c1f6tl.fsf@petton.fr>
2016-03-29 17:06 ` New iteration on the Emacs homepage Yoni Rabkin
2016-03-29 17:22   ` Nicolas Petton
2016-03-29 17:30     ` Yoni Rabkin
2016-03-29 17:46     ` Yoni Rabkin
2016-03-30  8:08       ` Nicolas Petton [this message]
2016-03-30 11:40         ` Yoni Rabkin
2016-03-31  7:56         ` Richard Stallman
2016-03-31  8:02           ` Nicolas Petton
2016-04-06 13:09             ` Yoni Rabkin
2016-04-06 13:31               ` Nicolas Petton
2016-03-30 12:11       ` bug#23152: " Richard Stallman
2016-03-30 12:10     ` 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

  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=87k2kks80f.fsf@petton.fr \
    --to=nicolas@petton.fr \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=yoni@rabkins.net \
    /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).