From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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=-3.7 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 5223F1F454 for ; Tue, 28 Mar 2023 23:31:00 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=google header.b=cYk0wzVD; dkim-atps=neutral Received: by mail-qv1-xf30.google.com with SMTP id m16so10382218qvi.12 for ; Tue, 28 Mar 2023 16:31:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; t=1680046259; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=jnGD2oI6OaC93B9TF/WT8YB0IdiEOUX5s0IChjlf+YM=; b=cYk0wzVDMjnYCQn/oz2Z7Ig5ddsjxQQApIxhp9alGCMbi+h2nQNxK4b8XgVUU7xHcR SCnuENDaAnQcjHD26fToMu6/SFOzRtMk3PXXBLhC3Ik8wXTrbJvxzAQLaKWg1W4Iyqx4 l+XEMdKE+FIHRzrCm8l+22V+FxnSqt5l20Y6U= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680046259; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=jnGD2oI6OaC93B9TF/WT8YB0IdiEOUX5s0IChjlf+YM=; b=eUiPGEJJiPFMM+m27LE3AvP8wQsQPsn4zjj/aSZyTSMG7R/s6tciIXx0eP38BspQDe aMolnthzf+rGSMwqFV5hoi80h6+8rdgMjHIypdDBBxJwTt9hWhoXAY8d4r3AXMWcKNRO nHn8qG4aCSaN4ix/yfKG3NVX52hc4WA7HDlBKylcwyp8VX9uEp1m97jE8qmVVstQnT3L ojhCrGwkn8zVuQN4AtsU8+9vKdhiMiLL3BW1h21a7UDILqX9jpjWYrI3AlIJvUiqxzMy oM6rB9boUWWY/5hOuZEiKDBqp8sf4RT0P4oA0N/epikxV50hd37j/5c0KY67+39Mw5Co JqKQ== X-Gm-Message-State: AAQBX9dOukpoKSUxZHaGNPO6CjfzbAwdVjTI/I5E96LSp709QA7JKnVP zTMDypDPbn2kRbk8mPHq/Zyyaw== X-Google-Smtp-Source: AKy350Y2zfbYWitp+GncLChSFVwuwW8MXn+dAyWJLhJYVqjplNFP6jxD/iL67qX2Sl0+8DwMx7NxCw== X-Received: by 2002:ad4:5fcd:0:b0:5a7:e9e4:5016 with SMTP id jq13-20020ad45fcd000000b005a7e9e45016mr28521707qvb.44.1680046258806; Tue, 28 Mar 2023 16:30:58 -0700 (PDT) Received: from meerkat.local (bras-base-mtrlpq5031w-grc-30-209-226-106-7.dsl.bell.ca. [209.226.106.7]) by smtp.gmail.com with ESMTPSA id g11-20020ad457ab000000b005dd8b9345c2sm4193388qvx.90.2023.03.28.16.30.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 28 Mar 2023 16:30:58 -0700 (PDT) Date: Tue, 28 Mar 2023 19:30:56 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: Cheap way to check for new messages in a thread Message-ID: <20230328-oppressed-almighty-61330f9dde22@meerkat> References: <20230327191049.M277377@dcvr> <20230327213849.M743623@dcvr> <20230328194549.M808175@dcvr> <20230328-monsoon-charred-giver-91f26d3024fb@meerkat> <20230328220830.M352242@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20230328220830.M352242@dcvr> List-Id: 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