From: Eric Wong <e@80x24.org>
To: Jeff King <peff@peff.net>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Subject: Re: git-scm.com status report
Date: Thu, 9 Feb 2017 04:30:34 +0000 [thread overview]
Message-ID: <20170209043034.GA30409@dcvr.yhbt.net> (raw)
In-Reply-To: <20170209025030.52frbjekatebjoii@sigill.intra.peff.net>
Jeff King <peff@peff.net> wrote:
> I agree we should continue to serve HTTPS. The usual solution for our
> use case is to stick a CDN like Cloudflare in front of GitHub Pages (and
> I think we'd want to do that anyway for performance).
>
> I haven't done it, but there are various guides. Here's the one from
> Cloudflare:
>
> https://blog.cloudflare.com/secure-and-fast-github-pages-with-cloudflare/
AFAIK, there's a way to keep CloudFlare stuff accessible to Tor
users. If there is, please do so. As a Tor user, it's been
disappointing to see so much of the web walled off by CAPTCHAs.
Thank you.
Heck, maybe a .onion mirror would be nice :)
I wouldn't mind hosting one myself if it's static.
next prev parent reply other threads:[~2017-02-09 4:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 2:33 git-scm.com status report Jeff King
2017-02-02 4:36 ` Eric Wong
2017-02-02 6:54 ` Samuel Lijin
2017-02-03 11:58 ` Jeff King
2017-02-03 20:56 ` Samuel Lijin
2017-02-05 20:11 ` Pranit Bauva
2017-02-06 16:24 ` Jeff King
2017-02-06 18:27 ` Jeff King
2017-02-09 2:12 ` brian m. carlson
2017-02-09 2:50 ` Jeff King
2017-02-09 4:30 ` Eric Wong [this message]
2017-05-17 1:56 ` Samuel Lijin
2017-05-17 2:03 ` Jeff King
2017-05-18 12:06 ` Lars Schneider
2017-05-18 15:42 ` Jeff King
[not found] <16F9F83D-5A7F-4059-9A27-DB25A8FB1E99@gmail.com>
2017-02-02 22:51 ` Samuel Lijin
2017-02-03 12:08 ` Jeff King
[not found] ` <CAPMsMoAUcVteJGfyYrL1ZkNLnoRES0yZxkMZeL347Q_1Kx5VBQ@mail.gmail.com>
2017-02-03 22:24 ` Jeff King
[not found] ` <CAPMsMoDpAeD0hpPuLeWO2T1VoEZDf_hD2gA2GDBqypMF9V6gAw@mail.gmail.com>
2017-02-20 7:53 ` Jeff King
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170209043034.GA30409@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.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://80x24.org/mirrors/git.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).