user/dev discussion of public-inbox itself
 help / color / Atom feed
From: Konstantin Ryabitsev <>
To: Eric Wong <>
Subject: Re: [RFC 2/2] www: add /~/$MESSAGE_ID global redirector endpoint
Date: Tue, 19 Feb 2019 14:53:13 -0500
Message-ID: <> (raw)
In-Reply-To: <20190201090056.b5ait6ebaflz3tsq@dcvr>

On Fri, 1 Feb 2019 at 04:00, Eric Wong <> 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


  parent reply index

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:

  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

user/dev discussion of public-inbox itself

Archives are clonable:
	git clone --mirror
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

Example config snippet for mirrors

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone