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_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-qv1-xf33.google.com (mail-qv1-xf33.google.com [IPv6:2607:f8b0:4864:20::f33]) (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 F08CE1F41C for ; Mon, 27 Mar 2023 15:08:59 +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=LDEGuVKn; dkim-atps=neutral Received: by mail-qv1-xf33.google.com with SMTP id o44so6949216qvo.4 for ; Mon, 27 Mar 2023 08:08:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; t=1679929738; h=content-disposition:mime-version:message-id:subject:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=+PlOx4iU0ttM5PZSIR5LzrCrEVuaADYIVgcS0RvB418=; b=LDEGuVKnaL5V8OFlMrQUDlAhk7yVwVthidqFe3kqONK2tluQrrK2XYoG/si77Y1Ppb Ti3f1AswFRwgEOeXPp3E6nCQV8KW/8NNna4VTq8XLTohWCJUwMnP4TqUoQIMKgPcPQ2/ wMNhOXGMQ5TyjofJ6MsTtFIA3viDlZEUVVJvw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679929738; h=content-disposition:mime-version:message-id:subject:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=+PlOx4iU0ttM5PZSIR5LzrCrEVuaADYIVgcS0RvB418=; b=IHW0ROuYyI7ysX9YvLNlCl6ptMjO1kGSw+qtHEXeJ8VGWblTBvZQKdCuaEuH0G9sz+ zvqbYUCrgiu+6ZioIhjAgIzgBWbzScjg/Tp9SJugtiSocDrxUYLYtVO4+uYyWFwUlgBG gk7Nwp1D6EfYwfvEF2JvUmWWfc/bSntt7MuCQ7nvlpTY8V1phCr4SbevFeMY97fLAx4b S92pffp/ywZ63qqJ3TiKJ6LUXccWpr+ayFqlEN0GZ/2QXYxgIYes89o883RTKLi4lsxs 71TeCHcvPYQEeR6sdkoj3EtVl9Bj2Hk6M2nobXydTxYjF1wRKqW1k2GNyD+6w+WC+W3x 86YA== X-Gm-Message-State: AAQBX9etm2pqYzTelwKd7oNdC3ufCtiMb4X8pqNvgjHTYxXReJLNyiCm cQWweX1CjMSMSt8muI+RruZ5hSUSJxowvCN7P/Q= X-Google-Smtp-Source: AKy350YdgFHnlHCAJQWf5sye//2Y4V3FaS0yTEbpPMs1mVjHD+FHCwSax1vbJ+txF2f34v7Hl/1CWQ== X-Received: by 2002:a05:6214:1304:b0:56f:52ba:ccf7 with SMTP id pn4-20020a056214130400b0056f52baccf7mr24959867qvb.14.1679929737984; Mon, 27 Mar 2023 08:08:57 -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 w19-20020ac86b13000000b003e38bae141dsm5627917qts.27.2023.03.27.08.08.56 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Mar 2023 08:08:57 -0700 (PDT) Date: Mon, 27 Mar 2023 11:08:55 -0400 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: Cheap way to check for new messages in a thread Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: Hello: 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? -K