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
Date: Fri, 1 Feb 2019 09:00:56 +0000 [thread overview]
Message-ID: <20190201090056.b5ait6ebaflz3tsq@dcvr> (raw)
In-Reply-To: <CAMwyc-TzobgiqvPSwX3HBwLXXmdWLLtJh=STmFrz57YoxXdRkA@mail.gmail.com>
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...
next prev parent reply other threads:[~2019-02-01 9:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 11:43 [RFC 0/2] support for /~/$MESSAGE_ID endpoint Eric Wong
2019-01-09 11:43 ` [RFC 1/2] config: inbox name checking matches git.git more closely Eric Wong
2019-01-09 11:43 ` [RFC 2/2] www: add /~/$MESSAGE_ID global redirector endpoint Eric Wong
2019-01-27 2:06 ` Eric Wong
2019-01-28 13:50 ` Konstantin Ryabitsev
2019-02-01 9:00 ` Eric Wong [this message]
2019-02-01 18:31 ` [PATCH v2] newswww: add /$MESSAGE_ID " Eric Wong
2019-02-04 11:11 ` [PATCH v2] examples/newswww.psgi: demonstrate standalone NewsWWW usage Eric Wong
2019-02-19 19:53 ` [RFC 2/2] www: add /~/$MESSAGE_ID global redirector endpoint Konstantin Ryabitsev
2019-02-19 22:55 ` Eric Wong
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: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190201090056.b5ait6ebaflz3tsq@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.org \
/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/public-inbox.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).