From: Eric Wong <email@example.com>
To: Konstantin Ryabitsev <firstname.lastname@example.org>
Subject: Re: RFE: unified message-id lookup across all inboxes
Date: Tue, 8 Jan 2019 01:54:20 +0000 [thread overview]
Message-ID: <20190108015420.GA28903@dcvr> (raw)
Konstantin Ryabitsev <email@example.com> wrote:
> Hello, all:
> One of the features lore.kernel.org users have been asking for is
> ability to retrieve a message based on its message-id regardless of
> which inbox it's in. Perhaps look them up in the order they are listed
> in the config file and display the first found?
Right, the NNTP interface already does that. Ordering in NNTP
is random (because Perl hash order is random), but I guess there
could be an option to control sorting in the config.
There'll be another sorting-related config option for a feature
on the horizon...
> The way it works currently is *almost* already what we want. E.g. if you
sidenote: I've been fighting memory use and that RFC is frightening :x
> It will tell you that the message is in another inbox (it was sent to
> linux-arm-kernel and not cc'd to linux-kernel). The users don't like
> that extra click, so they really just want a "show me the message if
> it's anywhere on lore, and give me a link to marc.info, etc if not in
> any of them).
Right. I wanted to make it obvious to the user the message was
in a different inbox. So I think the new endpoint would be
(without /$INBOX/ name):
And 302 the user to the first message.
> It's been way too long since I've done Perl, which is why I'm not
> offering patches, sorry! :)
No worries; I've got a bunch of other RFEs to take care of, too.
Also, I've been wondering if Ruby would have been a better
language for this project?
Python doesn't fit my brain, Xapian bindings for Lua aren't yet
in Debian, yet (RFP filed), but they're packaged for Ruby. But
I've been hacking on the Ruby VM for nearly a decade... I just
never get to use Ruby for development because I'm constantly
side-tracked into fixing and attempting to improve the VM and
language. But VM hacking isn't really rewarding anymore, so I'm
taking a break from that.
next prev parent reply other threads:[~2019-01-08 1:54 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 [this message]
2019-01-08 15:09 ` Konstantin Ryabitsev
2019-01-09 6:59 ` Eric Wong
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: https://public-inbox.org/README
* 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
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
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).