From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <yantar92@posteo.net>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS8495 185.67.36.0/23
X-Spam-Status: No, score=-3.4 required=3.0 tests=BAYES_00,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 mout01.posteo.de (mout01.posteo.de [185.67.36.65])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 D30B21F5A0
	for <meta@public-inbox.org>; Sun,  5 Feb 2023 19:30:01 +0000 (UTC)
Authentication-Results: dcvr.yhbt.net;
	dkim=pass (2048-bit key; secure) header.d=posteo.net header.i=@posteo.net header.a=rsa-sha256 header.s=2017 header.b=VxtBi2U7;
	dkim-atps=neutral
Received: from submission (posteo.de [185.67.36.169]) 
	by mout01.posteo.de (Postfix) with ESMTPS id 618B8240079
	for <meta@public-inbox.org>; Sun,  5 Feb 2023 20:29:59 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017;
	t=1675625399; bh=qICouNQfAs8qvIzdN8asVDMejHCJ+Yo6nqL00Dr59X0=;
	h=From:To:Cc:Subject:Date:From;
	b=VxtBi2U7QF78rppfUcjcNxOsgGKSLzL0QSz6BdDMZLZuDWqWShBObgY9xK9krjQLW
	 EAkhpCJAG5Q0G4pi0OU6FVktJ0NvlmLjzl88Ax6y2jAP8mrJY/kVI5oScuW3gLn6qx
	 C/5Vw8EnXYGo9mGmKPBA80mfE15iQDlxeIefL0gZKwg5OFacYkqPAlsfJ4fYJ1ZU33
	 lKj5zwVjt0toghpRirqGSaz2d+Xayuujnw74eLbL5nIz2M9hhJJ89oAkhO6nswqOvi
	 TWyoqTyfgQkET4aRTWnWdhqIdxMvt7f3qaxIXtJiDwh03FqiuzH40u8r6Td9TcDw0K
	 aEadEJTLhXTcg==
Received: from customer (localhost [127.0.0.1])
	by submission (posteo.de) with ESMTPSA id 4P8zxL440jz9rxR;
	Sun,  5 Feb 2023 20:29:58 +0100 (CET)
From: Ihor Radchenko <yantar92@posteo.net>
To: Eric Wong <e@80x24.org>
Cc: Kyle Meyer <kyle@kyleam.com>, meta@public-inbox.org, Bastien Guerry
 <bzg@fsf.org>
Subject: Re: [PATCH] www: sort all /$INBOX/ topics by Received: timestamp
In-Reply-To: <20230204204110.M179231@dcvr>
References: <87edr5gx63.fsf@kyleam.com> <20230204204110.M179231@dcvr>
Date: Sun, 05 Feb 2023 19:30:33 +0000
Message-ID: <87o7q7di5i.fsf@localhost>
MIME-Version: 1.0
Content-Type: text/plain
List-Id: <meta.public-inbox.org>

Eric Wong <e@80x24.org> writes:

> Thanks for the report.  The previous pinning prevention only
> prevented older messages from being pinned to the /$INBOX/ landing
> page.  It didn't prevent recent, future-looking messages from
> being pinned to the landing page, which seems to be what
> happened in your case.
>
> Does this untested patch fix it?

I am looking at https://list.orgmode.org/ and the thread still displays
the future date "2023-10-29  1:04 UTC" as the last update time. Though
ordering suggests that the future time was ignored when building recent
thread list.


-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>