From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [RFC 2/2] www: add /~/$MESSAGE_ID global redirector endpoint
Date: Tue, 19 Feb 2019 14:53:13 -0500 [thread overview]
Message-ID: <CAMwyc-TMm5No0f1rYSY4j2mbCtvkpmpS+WCP8XCE4zT+LUUqYg@mail.gmail.com> (raw)
In-Reply-To: <20190201090056.b5ait6ebaflz3tsq@dcvr>
On Fri, 1 Feb 2019 at 04:00, Eric Wong <e@80x24.org> wrote:
> 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...
So, what's the latest decision at this point? I got a little lost
looking through the latest commit messages. :) Is the feature going to
be supported through toplevel /message_id URL, or am I misreading the
code?
-K
next prev parent reply other threads:[~2019-02-19 19:53 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
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 ` Konstantin Ryabitsev [this message]
2019-02-19 22:55 ` [RFC 2/2] www: add /~/$MESSAGE_ID global redirector endpoint 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: http://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=CAMwyc-TMm5No0f1rYSY4j2mbCtvkpmpS+WCP8XCE4zT+LUUqYg@mail.gmail.com \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.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).