mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Nieder <>
To: Jeff King <>
Cc: Eric Wong <>,
	Johannes Schindelin <>,
Subject: Re: Thank you for public-inbox!
Date: Wed, 29 Aug 2018 20:56:09 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Jeff King wrote:

> I guess I just wonder if I set up a mirror on another domain, would
> anybody actually _use_ it? I'd think most people would just go to
> as the de facto URL.

If it's faster than and you don't mind the traffic I
would send, then I'll use it. :)

> That would be neat, but I think it actually makes references less useful
> in a lot of cases. URLs are universally understood, which means:
>  - people who don't know about public-inbox can just follow the link
>    (and in fact, that's how they learn how useful it is!)

I agree: please don't stop using URLs.

Having the message-id in the URL is very useful for being able to
migrate to another server.

In an ideal world, we'd be habitually using URLs that reference a
redirector, in the same spirit as
That way, there is a very restricted syntax to use (e.g. just
message-ids) that is stable and can be reconfigured to redirect to
another service as appropriate.  In principle it also allows tricks
like redirecting based on geography or making the redirector go to the
user's preferred archive interface based on a cookie.


  reply	other threads:[~2018-08-30  3:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-27 14:25 Thank you for public-inbox! Johannes Schindelin
2018-08-27 17:31 ` Eric Wong
2018-08-29  5:07 ` Jeff King
2018-08-29 10:02   ` Eric Wong
2018-08-29 15:43     ` Andrei Rybak
2018-08-29 16:30       ` Ævar Arnfjörð Bjarmason
2018-08-30  3:30     ` Jeff King
2018-08-30  3:56       ` Jonathan Nieder [this message]
2018-08-30  7:20         ` Eric Wong
2018-08-31  1:14           ` Jonathan Nieder
2018-08-31 11:01             ` Eric Wong
2018-08-30  7:20       ` Eric Wong
2018-08-30  8:19         ` 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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

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).