-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> ** In newsreaders, I believe there is often some optionality about how the
> various methods of threading are used. I think, if attempting to thread
> email messages, an email client should allow the same.
News postings are not email, and the same rules cannot (thankfully,
in most cases) apply. The same basic rules of ettiquette, however.. do
apply.
News postings use the "References" header to thread postings, which
is a hash of the originating Message-Id header. The newsreader of choice can
thread based on many different parts of the headers, References, Message-Id
(for newsreaders who post without adhering to the References header), etc.
> It seems to me that using the subject heuristically should avoid the
> problem some are experiencing, given that some email clients don't even
> use in-reply-to, and that some people sometimes change the subject when
> replying (which is something humans do naturally in conversation anyway).
The fact that clients don't use In-Reply-To headers means nothing
when you are composing a message. If you hit "Reply" to a message, it will
be threaded by readers which treat it as such. The fact that those broken
mail clients can't properly thread them by using the proper In-Reply-To
header, means notihng to most of us. It's not our problem, and we shouldn't
be expected to change the rules of ettiquette, just because some mail
clients come broken by default.
Also, changing the subject is allowed, as long as it maintains the
same threading context, as a conversation.
Using one message in a thread, as a "template" for a new message on
a completely unrelated topic of discussion, is frowned upon, and annoying.
> Isn't this a better solution?
d.
perldoc -qa.j | perl -lpe '($_)=m("(.*)")'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.1.92 (GNU/Linux)
iD8DBQE9qfZ8kRQERnB1rkoRAjE1AJ9AEntvGgxlRu2/otcfRiQ05xBdbACfcusL
gBnn7k7zThBuRevAuDIQdpw=
=/Xak
-----END PGP SIGNATURE-----
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
