Re: [tlug] Threaded email readers

[Scott Robbins <scottro@example.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Jan 17, 2006 at 04:29:49PM -0800, sjs@example.com wrote:
> If this goes wrong, sorry all over the place eat crow, etc...
> 
> I think my misunderstanding was was that the thread info was in the
> subject.  It looks like it is
> in the message header under references, right?  I was just hitting reply
> as a lazy way to pull in the address and assuming that would start a new
> thread.
> 
> This time I started from blank, so this is a new thread, right??

I'm sure this will be answered by the time I've replied, but yes, it's a
new thread.

As for thread hijacking by people who don't realize they're doing
it--don't let that scare you into lurking--I think most newcomers
learn about it the same way you did, doing it and then being told it's
wrong. 

Heh, to my chagrin, I was told about it by a Windows user with a proper
mail client.   

Thinking that the subject is all that determines the thread is the
intuitive way to think, but who ever said computers were intuitive?  It
reminds me when I was watching my wife take a ballet class, (at a high
level) and someone said in response to the teacher's request, "That
doesn't feel natural."  The teacher replied, "Since when is ballet
natural?"

Just in case, as I scroll down through the rest of the messages, no one
answered the question, yes, the thread is actually, in more RFC
compliant mail readers, determined by header information.  



- -- 

Scott Robbins

PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

Willow: The only solution is the final solution.
Xander: Nuke the school? I like that.
Willow: Not quite. Exorcism.
Cordelia: Are you crazy? I saw that movie. Even the priest died.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFDzZjM+lTVdes0Z9YRAg8XAKCkqb+v3l1ph18QFqxDB04HeBSqLwCcCsss
chJHcsTTFZLteLEtItAu+58=
=K0cw
-----END PGP SIGNATURE-----