mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <>
To: Eric Wong <>
Cc: Johannes Schindelin <>,
Subject: Re: Thank you for public-inbox!
Date: Wed, 29 Aug 2018 23:30:00 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20180829100243.GA28180@dcvr>

On Wed, Aug 29, 2018 at 10:02:43AM +0000, Eric Wong wrote:

> Jeff King <> wrote:
> > I've thought about mirroring it to a public server as well, just for
> > redundancy. But without the same domain, I'm not sure it would be all
> > that useful as a community resource.
> I wouldn't get too attached to the domain, "" is
> too long for my tastes anyways.  "$MESSAGE_ID"
> would actually be more user-friendly :>
> A generic Message-ID redirection/finding service would be good,
> (maybe some DHT thing, but... has that taken off for git blobs, yet?)

Yes, and I agree that the URL portability is one of the things I really
love about public-inbox (after all, I do have my own archive and now I
can follow people's public-inbox links into my very-fast local copy).

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.

> Anyways I hope to teach public-inbox to auto-linkify Message-ID-looking
> strings "<XXXXXXXXXXX@XXXXXXXX>" into URLs for domain-portability,
> (but it's ambiguous with email addresses).  But yeah, I don't
> like things being tied to domain names.

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

 - even for people who do know about it, they are likely to read mails
   in their MUA. And most MUAs have some mechanism for easily following
   a URL, but won't know how to auto-linkify a message-id.

So I too dream of a world where I can say "give me more information on
this identifier" and my tools search a peer to peer distributed hash
table for it. But I don't think we live in that world yet.

At the very least, I think if we plan to reference without an http URL
that we would use something like URI-ish, like <mid:ABC@XYZ>. That gives
tools a better chance to say "OK, I know how to find message-ids"
(though I still think that it's much less helpful out of the box
compared to an http URL).


  parent reply	other threads:[~2018-08-30  3:30 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 [this message]
2018-08-30  3:56       ` Jonathan Nieder
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).