From: Lars Ingebrigtsen <larsi@gnus.org>
To: Russ Allbery <rra@stanford.edu>
Cc: ding@gnus.org
Subject: Re: Repost: Time to revisit the message id generation algorithm?
Date: Thu, 02 Feb 2012 11:10:09 +0100 [thread overview]
Message-ID: <87boph5ywu.fsf@gnus.org> (raw)
In-Reply-To: <87zkd2yvx3.fsf@windlord.stanford.edu> (Russ Allbery's message of "Wed, 01 Feb 2012 15:29:44 -0800")
Russ Allbery <rra@stanford.edu> writes:
> One thing that I'd like to request, though, is that if this changes it
> would be nice to have an option to keep the current message ID behavior or
> something like it.
The privacy leak is pretty minor, I think. And while it's true that
collisions are more likely to occur than if Gnus were using a more
"random" algo, in practice I don't think anybody has ever reported Gnus
generating a duplicate.
--
(domestic pets only, the antidote for overdose, milk.)
http://lars.ingebrigtsen.no * Sent from my Rome
prev parent reply other threads:[~2012-02-02 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 18:18 Johann 'Myrkraverk' Oskarsson
2012-02-01 23:29 ` Russ Allbery
2012-02-02 10:10 ` Lars Ingebrigtsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87boph5ywu.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=rra@stanford.edu \
/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 NNTP newsgroup(s).