From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: thoughts improving duplicate message handling...
Date: Mon, 28 Dec 2020 21:41:46 +0000 [thread overview]
Message-ID: <20201228214146.GB17600@dcvr> (raw)
Spinning off of https://public-inbox.org/meta/20201228213139.GA17600@dcvr/
> (*) The downside to this approach is IMAP UIDs (NNTP article
> numbers) get changed, but I think I can workaround that. The
> workaround I'm thinking of involves capturing exact blob OIDs
> during the unindex phase to create an OID => UID mapping.
> reindex would reuse the OID => UID mapping to keep the same
> IMAP UID. It could be loosened to use ContentHash, or
> whatever combination of Message-ID/From/Date/etc, too.
I've noticed quite a few messages with identical Message-IDs,
especially with /all/ (*)
a) There are occasionally resent revisions of patches with the
same Message-ID
b) More often, a cross-posted message has different trailers
depending on which list it was posted to. (And the
PublicInbox::Filter::* API doesn't apply at indexing,
only at git injection time)
I'm thinking of two new features:
1) the WWW and lei UIs could have a "diff mode"
that clearly shows differences between rendered texts
This could be expensive with malicious inputs, but the
existing "limiter" infrastructure used for serving packs
should help, here.
2) support PublicInbox::Filter at index-time
(requires reindexing to take effect, will cause new IMAP
UIDs+NNTP article numbers to show up, possibly en-mass)
(*) https://public-inbox.org/meta/20201126194543.GA30337@dcvr/
next reply other threads:[~2020-12-28 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 21:41 Eric Wong [this message]
2020-12-29 15:50 ` thoughts improving duplicate message handling Konstantin Ryabitsev
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=20201228214146.GB17600@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/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).