From: Eric Wong <email@example.com> To: Konstantin Ryabitsev <firstname.lastname@example.org> Cc: email@example.com Subject: Re: RFE: unified message-id lookup across all inboxes Date: Tue, 8 Jan 2019 01:54:20 +0000 Message-ID: <20190108015420.GA28903@dcvr> (raw) In-Reply-To: <20190107190719.GE9442@pure.paranoia.local> Konstantin Ryabitsev <firstname.lastname@example.org> 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 > access: > https://email@example.com 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): http://$HTTP_HOST/_/$MESSAGE_ID 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 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
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=20190108015420.GA28903@dcvr \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: RFE: unified message-id lookup across all inboxes' \ /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 This inbox may be cloned and mirrored by anyone: 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 # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 meta meta/ https://public-inbox.org/meta \ email@example.com public-inbox-index meta Example config snippet for mirrors. 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.io/gmane.mail.public-inbox.general note: .onion URLs require Tor: https://www.torproject.org/ code repositories for project(s) associated with this inbox: https://80x24.org/public-inbox.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git