unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@80x24.org>, meta@public-inbox.org
Cc: Ihor Radchenko <yantar92@posteo.net>, Bastien Guerry <bzg@fsf.org>
Subject: future date in Date header pinning thread to top of $inbox/
Date: Sat, 04 Feb 2023 12:25:40 -0500	[thread overview]
Message-ID: <87edr5gx63.fsf@kyleam.com> (raw)

As noted by Ihor on the Org list (<87pmarnhlr.fsf@localhost>), Org's
public-inbox archive has a thread pinned to the top of the $inbox/
overview:

 * https://yhetil.org/orgmode/

That thread has a message where a sender set his Date to a future date:

  $ curl -fSsL https://yhetil.org/orgmode/ZT2vNKsf3Lp5xit3@protected.localdomain/raw | \
    grep Date:
  Date: Sun, 29 Oct 2023 04:02:44 +0300

Based on grepping around the public-inbox tree and Git history, I know
that there are spots in public-inbox that prefer a date from the
Received headers over the one from the Date header.  Would that make
sense to do here too to reduce the chances of a date from the future
pinning a thread?  (Or perhaps that's already the intention and
something's off here?)

Thanks.

             reply	other threads:[~2023-02-04 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-04 17:25 Kyle Meyer [this message]
2023-02-04 20:41 ` [PATCH] www: sort all /$INBOX/ topics by Received: timestamp Eric Wong
2023-02-04 21:16   ` Kyle Meyer
2023-02-05 19:30   ` Ihor Radchenko
2023-02-05 20:10     ` [PATCH] www: display Received: timestamp for dumped topics Kyle Meyer
2023-02-05 20:21       ` Eric Wong
2023-02-05 20:57         ` Kyle Meyer
2023-02-05 21:03         ` Ihor Radchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87edr5gx63.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=bzg@fsf.org \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.org \
    --cc=yantar92@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).