From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
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=-4.2 required=3.0 tests=ALL_TRUSTED,BAYES_00,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no
	autolearn=ham autolearn_force=no version=3.4.6
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id A022A1F5A0;
	Sun,  5 Feb 2023 20:21:59 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=80x24.org;
	s=selector1; t=1675628519;
	bh=PiPGysA4Q6TB/pudYSVredCI7s49CCsv11hxDYNEfAs=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
	b=zRdf0qWaMPkEyv0CG9/pqgSCxQwJh3edE6YMm2VvK4Y/oScuBIBHjDxw1WZHYytOK
	 OEHnE74uU0M3luqxi/VH6Foq6/vE7i5lBHDoJIvq6swfxdcr7cGOGG7tZfrLWn6vAi
	 6f91+tW/aPmqutAeidvDTgEBSmfmx5aGAHp+g2Zc=
Date: Sun, 5 Feb 2023 20:21:59 +0000
From: Eric Wong <e@80x24.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Ihor Radchenko <yantar92@posteo.net>, meta@public-inbox.org,
	Bastien Guerry <bzg@fsf.org>
Subject: Re: [PATCH] www: display Received: timestamp for dumped topics
Message-ID: <20230205202159.M111127@dcvr>
References: <87edr5gx63.fsf@kyleam.com>
 <20230204204110.M179231@dcvr>
 <87o7q7di5i.fsf@localhost>
 <87y1pb27r6.fsf@kyleam.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <87y1pb27r6.fsf@kyleam.com>
List-Id: <meta.public-inbox.org>

Kyle Meyer <kyle@kyleam.com> wrote:
> Ihor Radchenko writes:
> 
> > Eric Wong <e@80x24.org> writes:
> [...]
> >> 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.
> 
> The "it" that I reported is the sorting, so as far as I can see it's
> fixed.  With the "last update time", I suppose you're talking about the
> second line below:
> 
>   [FEATURE REQUEST] Timezone support in org-mode datestamps and org-agenda
>    2023-10-29  1:04 UTC  (110+ messages)
>                                         ` [POLL] Proposed syntax for [...]
> 
> I don't care too much one way or the other, but it makes sense to me for
> that to match the value that's actually used to sort the messages.
> Eric, what about something like this?

I'm slightly against it.  Date: is what's shown in every other
message view, and I think that's what most MUAs do, too.  I'm
fine with wrong dates being shown as long as it's not abusable
to pin a message to the top of /$INBOX/.

Aside from git-send-email behavior mentioned upthread, Date:
should also be favored in general because it's consistent across
recipients, and across independently-run archives w/o common
history.

I think the best we can do is point out to senders their clocks
are wrong, as this has been the case going back decades.