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.6 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-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 EFDD41F452 for ; Thu, 30 Mar 2023 16:45:10 +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=K5URrOx1; dkim-atps=neutral Received: by mail-qt1-x835.google.com with SMTP id cj15so11573916qtb.5 for ; Thu, 30 Mar 2023 09:45:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; t=1680194710; 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=eKMdEe1xMbtEY+3/cnk4HDyM5lyjwxjs5CA8Tl909IU=; b=K5URrOx1OK+wpdD6ftHYtrnAodlMbxOLVWosQjpayvNDU0dQYlYv1eCy/E7tUsxc2F v3jruZjwjlSb0jtVqvF2/ZHaqlRDE8gZBgKnmZ0EQrRJW18dLoN712EpRMxqkDSiEoAP e+Aypehbm6K7SmLf6uUrRDz83mMa90IlFDwyM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680194710; 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=eKMdEe1xMbtEY+3/cnk4HDyM5lyjwxjs5CA8Tl909IU=; b=vX4wL044/54XFR+rW3vUBH78C2lKX/bwkkdFItQpgJprNA/dnpH8icw2RXWXYinyPE QNWyMOWhDLBChrZZRn0HrR42M72D5x9C3dU+1Tv/4jHtHexgl1IcAzjkubltaaFNJ2wC 2RTAOU1Je0xjLg8eXSMsOeAF0FTy/G2ThoAZDRvE9R1GWLlWjT2W22uay5bg9ggGb04M jVB5ZxIQlAIdrzjGglgrjJ2emf7nrlCXOVF0Ei2+uSFeTQg8EtH3PIT1xl08ZnU4EFDL gH528woiu7NI0Ibm/6cvFtUKtZJSpnppM0S2z2hx5XixUi7Lh9I+i5CBDtsjcj/wMRUB HNrQ== X-Gm-Message-State: AO0yUKX37ZQUoqwTcmZKJLdiALpBALOjv8qmQ3bXClfdEUgszpMa6yP2 /tvj3HgiLLC7dkABJ6H9X1dVwUPRhqAxovcf0IM= X-Google-Smtp-Source: AKy350ZtF3Ht4HtNSB20rur8HIfe0iwwNuNvWp3xWgPX2cVa1ym3q0/vvVDL0gLZX9JTMR4bftN1EA== X-Received: by 2002:a05:622a:178a:b0:3e1:9557:123c with SMTP id s10-20020a05622a178a00b003e19557123cmr32153822qtk.52.1680194709824; Thu, 30 Mar 2023 09:45:09 -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 d202-20020ae9efd3000000b007468db93fd8sm13520540qkg.84.2023.03.30.09.45.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 30 Mar 2023 09:45:09 -0700 (PDT) Date: Thu, 30 Mar 2023 12:45:07 -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: <20230330-service-handmade-0295eec6336f@meerkat> References: <20230327191049.M277377@dcvr> <20230327213849.M743623@dcvr> <20230328194549.M808175@dcvr> <20230328-monsoon-charred-giver-91f26d3024fb@meerkat> <20230328220830.M352242@dcvr> <20230328-oppressed-almighty-61330f9dde22@meerkat> <20230329212558.M622984@dcvr> <20230330112951.M493025@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20230330112951.M493025@dcvr> List-Id: On Thu, Mar 30, 2023 at 11:29:51AM +0000, Eric Wong wrote: > > 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 > > This implements the mbox.gz retrieval. I didn't want to deal > with HTML nor figuring out how to expose more
elements, > yet; but I figure mbox.gz is the most important. Nice, thanks! I can't easily test this, because lore is currently mostly on 1.9 and the patch doesn't cleanly apply to that tree. However, I will be happy to test it out once 2.0 is out and we've updated to it on our systems. Cheers, -K