From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Cheap way to check for new messages in a thread
Date: Tue, 28 Mar 2023 19:30:56 -0400 [thread overview]
Message-ID: <20230328-oppressed-almighty-61330f9dde22@meerkat> (raw)
In-Reply-To: <20230328220830.M352242@dcvr>
On Tue, Mar 28, 2023 at 10:08:30PM +0000, Eric Wong wrote:
> > I think this is a workable approach, but would require a reindex, right?
>
> Yes, it requires a reindex to take effect, which takes ~2 days
> on my lore mirror. The biggest problem is MUAs are likely to
> cull References: when threads get too long; so accuracy gets
> lost.
>
> Supporting /$MSGID/?q=... doesn't seem like the worst idea,
> actually; since I've seen some web forums (phpBB maybe?) have a
> "search in thread" function.
>
> thread:{sub-query} is ideal; and I wouldn't rule out doing any
> combination of the three (I don't like separating before/after).
I'm fine with either of these, and just to stress, it's not really blocking
anything I'm working on -- bugbot is in initial rollout stages, so while the
number of tracked bugs/threads remains low, even if we re-download a hundred
threads every 10 minutes, it's just internal churn between two adjacent VMs.
If it becomes heavy, I can always look into switching to lei and performing
local queries instead of doing external polling.
However, if you do want to add ability to cheaply do a "give me just the
newest messages in this thread since this datetime", that would be great for
my needs. :)
-K
next prev parent reply other threads:[~2023-03-28 23:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 15:08 Cheap way to check for new messages in a thread Konstantin Ryabitsev
2023-03-27 19:10 ` Eric Wong
2023-03-27 20:47 ` Konstantin Ryabitsev
2023-03-27 21:38 ` Eric Wong
2023-03-28 14:04 ` Konstantin Ryabitsev
2023-03-28 19:45 ` Eric Wong
2023-03-28 20:00 ` Konstantin Ryabitsev
2023-03-28 22:08 ` Eric Wong
2023-03-28 23:30 ` Konstantin Ryabitsev [this message]
2023-03-29 21:25 ` Eric Wong
2023-03-30 11:29 ` Eric Wong
2023-03-30 16:45 ` Konstantin Ryabitsev
2023-03-31 1:40 ` Eric Wong
2023-04-11 11:27 ` Eric Wong
2023-06-16 19:11 ` Konstantin Ryabitsev
2023-06-16 23:13 ` [PATCH] www: use correct threadid for per-thread search Eric Wong
2023-06-21 17:11 ` Konstantin Ryabitsev
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=20230328-oppressed-almighty-61330f9dde22@meerkat \
--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
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).