From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: RFE: unified message-id lookup across all inboxes
Date: Wed, 9 Jan 2019 06:59:14 +0000 [thread overview]
Message-ID: <20190109065914.GA4688@dcvr> (raw)
In-Reply-To: <20190108150911.GB19908@pure.paranoia.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Tue, Jan 08, 2019 at 01:54:20AM +0000, Eric Wong wrote:
> > http://$HTTP_HOST/_/$MESSAGE_ID
> >
> > And 302 the user to the first message.
>
> That sounds good to me.
Alright. I think we can reserve '_' and some other punctuation
and make them invalid inbox names.
> I may be jaded from the times when Ruby's VM was really terrible, but
> I'm still harbouring deep aversion to Ruby. I'll take Perl over Ruby any
> day. :)
Heh, it was a large part of my full-time job for me to fix
RubyVM bugs for a few years. So it ought to be better, now; and
all the TLS termination for https://public-inbox.org/git/ since
2016 has been done by a Ruby server without nginx (or similar).
> I don't think this is something that needs fixing. I expect it's easier
> to just let people write custom web frontends to public-inbox
> repositories (I suspect that's what LWN has done). In fact, I pondered
> writing or commissioning a Django frontend if people needed more
> shiny whizbang stuff out of the web interface, but kernel devs are the
> kind of crowd that's served perfectly well by the current web frontend,
> so I don't have a strong enough need to do anything there.
Yeah, I was wondering when somebody would write a heavier one
with more whizbang features. But I also think
Thunderbird/sylpheed/... + NNTP (or POP3) could still do better.
I will certainly add user-customizable CSS for quote/diff
highlighting (and maybe code syntax highlighting, too).
At least I promised it last year to somebody privately.
But FWIW, I need to use giant fonts and can't deal with most
sites or UIs without "xrandr-invert-colors" (or "xcalib -i -a").
So UI is highly subjective and the only part of UI/UX I can
really understand are speed and stability. To that end, I think
the WWW code be made even faster (and eliminate Varnish/nginx
even for busy sites on cheap VPS). And the search queries +
mboxrd format won't change, so people can build on top of that
(but Xapian result sorting/accuracy may change).
V nyfb unir xvyyre srngher hc zl fyrrir juvpu V ubcr gb svavfu
vzcyrzragvat fbzrqnl...
prev parent reply other threads:[~2019-01-09 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 19:07 RFE: unified message-id lookup across all inboxes Konstantin Ryabitsev
2019-01-08 1:54 ` Eric Wong
2019-01-08 15:09 ` Konstantin Ryabitsev
2019-01-09 6:59 ` Eric Wong [this message]
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=20190109065914.GA4688@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.
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).