From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.2 required=3.0 tests=ALL_TRUSTED,BAYES_00,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no
	autolearn=ham autolearn_force=no version=3.4.6
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id B377C1F452;
	Wed, 29 Mar 2023 21:25:58 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=80x24.org;
	s=selector1; t=1680125158;
	bh=IqlGQbQhAA2otw7lLNl6Nm70yc+e891qblViKnHnIMM=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
	b=DPxsqovlv+xzWx8Um/l2IcMAZ1JyRCgPNw7uARkTuwkp3yqPprH+Anl2qesA90Tza
	 6qZCLWcUDW/bcqyv0rNdAG6LD/ogqqVYskAQL4ouyX9SCkcw+tRyvbL/3RE0cSq5Vs
	 Ln5TOlxJfG1gBbL7Xfo2XI6JaUNFEegHCL7Oz2zQ=
Date: Wed, 29 Mar 2023 21:25:58 +0000
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: Cheap way to check for new messages in a thread
Message-ID: <20230329212558.M622984@dcvr>
References: <aaniyhk7wfm4e6m5mbukcrhevzoc6ftctyrfwvmz4fkykwwtlj@mverfng6ytas>
 <20230327191049.M277377@dcvr>
 <tdgola6w5slak6y232ka4pryjvavi7jwgeqgwsbyvjhyuy3xir@a3777kv7imvz>
 <20230327213849.M743623@dcvr>
 <euqfjyjedoywqdcbldq23o3k3joewdmnx5j3tsjcu2dfx253uj@mzrjrpfy5nxv>
 <20230328194549.M808175@dcvr>
 <20230328-monsoon-charred-giver-91f26d3024fb@meerkat>
 <20230328220830.M352242@dcvr>
 <20230328-oppressed-almighty-61330f9dde22@meerkat>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20230328-oppressed-almighty-61330f9dde22@meerkat>
List-Id: <meta.public-inbox.org>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> 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.

Alright.

> 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. :)

Per-thread search is something I've wanted for a while, anyways,
so I think I'll do /$MSGID/?q= in between ongoing work for
codesearch and chasing down FreeBSD issues.

I may not expose /$MSGID/?q= it via HTML just yet since I find
<form> elements confusing as a user :x

Indexing References/IRT would be a waste of space and I/O due to
MUA truncations; so I'm hesitant to do it since we already index
THREADID.

thread:{sub-query} will be nice, but I'll get to it after I deal
with the lei FUSE stuff since I've already done most of the C
work from another project.  Normal FSes are so inefficient
for storing Maildir outputs.