From: Eric Wong <e@80x24.org>
To: Jeff King <peff@peff.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: Thank you for public-inbox!
Date: Thu, 30 Aug 2018 07:20:49 +0000 [thread overview]
Message-ID: <20180830072049.dgsjn3537xzo6qcm@dcvr> (raw)
In-Reply-To: <20180830033000.GD665@sigill.intra.peff.net>
Jeff King <peff@peff.net> wrote:
> On Wed, Aug 29, 2018 at 10:02:43AM +0000, Eric Wong wrote:
> > 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.
Heh, one of the (unstated?) goals of public-inbox is to educate
the users on how Message-IDs (and email in general) works.
And to that end...
> 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.
....More than dreaming, our goal should be to BUILD such a world :>
After all, it was my intense dislike of centralization which
drew me to DVCS and git in the first place.
> 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).
That would be awesome if somelike like <mid:ABC@XYZ> could be a
standard and adopted (likewise with <git:$object_id>).
I haven't checked, but are there existing/similar RFCs?
Surely somebody has tried to get <git:$object_id>
adopted by now, right?
next prev parent reply other threads:[~2018-08-30 7:20 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
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 [this message]
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:
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=20180830072049.dgsjn3537xzo6qcm@dcvr \
--to=e@80x24.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--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.
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).