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.8 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-xf31.google.com (mail-qv1-xf31.google.com [IPv6:2607:f8b0:4864:20::f31]) (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 0BE5F1F41C for ; Mon, 27 Mar 2023 20:47:20 +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=YOInb/Xy; dkim-atps=neutral Received: by mail-qv1-xf31.google.com with SMTP id o44so7745736qvo.4 for ; Mon, 27 Mar 2023 13:47:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; t=1679950039; 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=MCRRdDxIovLZGAoG6Sw1D5S/msNdWxvN4B5Yfy2eAQE=; b=YOInb/XyyXwe2TBlX/1S0anL42jmrdNHfX05ft6FhwxYzP/O+6Yz0NZXbyBwZj1LN2 rUe7xsAsGkl8cxKlnUtuu0es0DJw9g4X9LEBrWI1xKf15gFXOLXMgy1wk8uDNj8oUpLt +K3lb+7fp73HdVNyukBnLZKl9x1d0VtNzgEJc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679950039; 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=MCRRdDxIovLZGAoG6Sw1D5S/msNdWxvN4B5Yfy2eAQE=; b=VwPDOC+/YD8YZqE4tuwR6C9vlDh1RJ0Z1Ap9VIsope3uCmZnOp8x6juHEaCuJ2u2+3 M/exKXi921LNycMeAiHtqsZyRDlbhGzRi5uq1wmO6o0lG297hMkJBDSHTwCQang4WHK3 Of0A37r9gdtAtfXdBWmHFBE34KJDkyWrmWXTF0Rk1bfzA/8yG9oVdWXMh1sSxbjiwjJq YiVHWy9J9xY2h375vZjSnrT9jNDwP7z2hnzK/88wQ9zgEjm7bPhXBOiWKoWe/JK9QiK5 KoZBERNkNN6KIb8Inn4DhNTxkTtJ6JO4/gj9e8QfW/hxOWOuL02CeB32YCKa92EUxoLU ArmA== X-Gm-Message-State: AAQBX9frAxyTUg0Hf7epXSimKQP4tHqzWKxO7jocCRQdF6dqg02SZ6lQ +gi45pggeuP/JyzdbhGDP8XDHH3FGr4h9L+1hBs= X-Google-Smtp-Source: AKy350Zlt/nuhws5bccVRqFsCXOSV5avyOy6uPPK4X5dZiKLr4EU/ugPNAgZKWCajR6+ReZXm6h4dw== X-Received: by 2002:a05:6214:248b:b0:5be:ec50:7358 with SMTP id gi11-20020a056214248b00b005beec507358mr25169450qvb.3.1679950038828; Mon, 27 Mar 2023 13:47:18 -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 r132-20020a37448a000000b007466432a559sm14948326qka.86.2023.03.27.13.47.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Mar 2023 13:47:18 -0700 (PDT) Date: Mon, 27 Mar 2023 16:47:16 -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: References: <20230327191049.M277377@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20230327191049.M277377@dcvr> List-Id: On Mon, Mar 27, 2023 at 07:10:49PM +0000, Eric Wong wrote: > > For the bugzilla integration work I'm doing, I need a way to check if there > > were any updates to a thread since the last check. Right now, I'm just > > grabbing the full thread, parsing it and seeing if there are any new > > message-IDs that we don't know about, but it's very wasteful. Any way to just > > issue something like "how many messages are in a thread with this message-id" > > or "are there any updates to a thread with this message-id since > > YYYYMMDDHHMMSS? > > lei q -t --only /path/to/(inbox|extindex) mid:$MSGID rt:APPROXIDATE.. > > Returns JSON and won't retrieve message bodies from git. Ah, I was hoping to have a fully remote way of doing this. > I wouldn't query down to the second due to propagation delays, > clock skew, etc, though. > > There might be a JMAP endpoint I can implement for WWW which > only retrieves that info, but getting backreferences (required > by the JMAP spec) to work properly seemed painful. What about a "bodiless" atom feed? It's already available per thread, so perhaps there could be a mode that skips the bodies or trims them after the first paragraph? -K