From: Eric Wong <e@80x24.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jeff King <peff@peff.net>,
Emily Shaffer <emilyshaffer@google.com>,
git@vger.kernel.org
Subject: Re: GitGitGadget on git/git, was Re: Should we auto-close PRs on git/git?
Date: Wed, 27 Nov 2019 02:37:45 +0000 [thread overview]
Message-ID: <20191127023745.GA15031@dcvr> (raw)
In-Reply-To: <xmqqa78iw0f8.fsf@gitster-ct.c.googlers.com>
Junio C Hamano <gitster@pobox.com> wrote:
> Eric Wong <e@80x24.org> writes:
>
> > (and I'm not going to pay extortionist .org fees to keep
> > public-inbox.org when it comes up for renewal in 2023,
> > maybe everyone can use Tor .onions by then :> )
>
> Just on this tangent. Would you be willing to keep the domain and
> keep the service running, if Git Project Leadership Committee pays
> the fee out of the funds we keep at Software Freedom Conservancy?
Maybe... I'm against the *principle* of paying extortionists;
and I don't think the Git project should encourage them, either.
Promoting + developing a Distributed Hash Table (DHT) for
Message-ID (and git OID) lookups to fight against centralization
would be a better use of time and funds :>
However, if EFF and other .orgs prove effective in keeping
prices reasonable then that's fine, I guess. I personally
expect to be financially worse off in 2023 than I was in 2013
when I bought the domain, so some help there could be nice :)
The actual cost of running a service is only $20/month in VPS
hosting. It's a business expense at the moment as I hack on
that machine for clients, and I'm trying to make public-inbox
cheaper and easier to host, too.
But, https://lore.kernel.org/git/ has professionals behind it
and is more scalable. It's currently missing syntax
highlighting and blob regeneration because that's a PITA to
configure, though...
next prev parent reply other threads:[~2019-11-27 2:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 2:00 Should we auto-close PRs on git/git? Emily Shaffer
2019-11-09 4:55 ` Junio C Hamano
2019-11-13 5:29 ` Stephen Smith
2019-11-12 19:11 ` Johannes Schindelin
2019-11-13 1:10 ` Jeff King
2019-11-13 12:04 ` Johannes Schindelin
2019-11-14 7:41 ` Jeff King
2019-11-14 23:03 ` Johannes Schindelin
2019-11-18 18:37 ` GitGitGadget on git/git, was " Johannes Schindelin
2019-11-21 10:54 ` Jeff King
2019-11-22 13:50 ` Johannes Schindelin
2019-11-22 14:43 ` Johannes Schindelin
2019-11-25 14:30 ` Jeff King
2019-11-26 20:55 ` Johannes Schindelin
2019-11-26 21:56 ` Eric Wong
2019-11-26 22:22 ` Johannes Schindelin
2019-11-26 22:40 ` Eric Wong
2019-11-26 22:52 ` Johannes Schindelin
2019-11-26 23:58 ` Eric Wong
2019-11-27 1:52 ` Junio C Hamano
2019-11-27 2:37 ` Eric Wong [this message]
2019-11-13 21:09 ` Emily Shaffer
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=20191127023745.GA15031@dcvr \
--to=e@80x24.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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.
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.