From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id BD4C21F453;
	Fri,  1 Feb 2019 09:00:56 +0000 (UTC)
Date: Fri, 1 Feb 2019 09:00:56 +0000
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: [RFC 2/2] www: add /~/$MESSAGE_ID global redirector endpoint
Message-ID: <20190201090056.b5ait6ebaflz3tsq@dcvr>
References: <20190109114327.1901-1-e@80x24.org>
 <20190109114327.1901-3-e@80x24.org>
 <20190127020608.f6yu2j3w4mfcc75b@dcvr>
 <CAMwyc-TzobgiqvPSwX3HBwLXXmdWLLtJh=STmFrz57YoxXdRkA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAMwyc-TzobgiqvPSwX3HBwLXXmdWLLtJh=STmFrz57YoxXdRkA@mail.gmail.com>
List-Id: <meta.public-inbox.org>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> > Eric Wong <e@80x24.org> wrote:
> > > The "/~/" is not finalized, yet.  Initially I chose "/_/", but
> > > it could conflict with valid git remote names.
> >
> > Any thoughts on the use of "~"?  Thinking about combining this
> > with the "solver" feature for blob recreation...
> 
> I don't really have a strong opinion on this one -- it's purely
> cosmetics. I'm wondering if it will be confusing to some folks due to
> ~ usually denoting $HOME. I would opt for /_mid/ to indicate that it's
> a special message-id lookup URL. Maybe marry the two and call it
> /~mid/? That would avoid clashing with potentially valid mailbox
> names.

Both "_mid" and "~mid" can cause usability problems and
work badly when people try to select part of the URL using
a pointing device.  But I guess "/-/" or "/_/" are safe-enough
choices and we can disallow them as inbox names...

However, my screwing up solver hrefs in the Atom feeds got me
thinking this can even be a 404 handler at the top level
(similar to how PublicInbox::NewsWWW works).  That would allow
it to be mapped to any path (or domain) via the PSGI builder
file...