user/dev discussion of public-inbox itself
 help / color / Atom feed
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: Mon, 28 Jan 2019 18:50:11 +0500
Message-ID: <CAMwyc-TzobgiqvPSwX3HBwLXXmdWLLtJh=STmFrz57YoxXdRkA@mail.gmail.com> (raw)
In-Reply-To: <20190127020608.f6yu2j3w4mfcc75b@dcvr>

On Sun, 27 Jan 2019 at 07:06, Eric Wong <e@80x24.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.

-K

  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 [this message]
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         ` [RFC 2/2] www: add /~/$MESSAGE_ID global redirector endpoint Konstantin Ryabitsev
2019-02-19 22:55           ` Eric Wong

Reply instructions:

You may reply publically 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='CAMwyc-TzobgiqvPSwX3HBwLXXmdWLLtJh=STmFrz57YoxXdRkA@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

user/dev discussion of public-inbox itself

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

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
	nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
	nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
	nntp://news.gmane.org/gmane.mail.public-inbox.general

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox