Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Scrambled Threads - Usenet

0 views
Skip to first unread message

tbl

unread,
May 18, 2007, 4:39:51 PM5/18/07
to
Every great once-in-a-while, while following a given thread,
the thread seems to get hijacked. The subject changes to
something not at all related, and that may be the only topic
from there on, or it may just be another topic inside that
thread.

This happened again, recently, so I made some notes on it.

Here are some headers from the OP:

Path: news.grc.com!.
From: Acc7 <Ac...@xxx.xxx> [munged]
Newsgroups: grc.techtalk
Subject: Curiosity or Fraud ??? Trying to buy Grisoft AVG
Date: Thu, 17 May 2007 22:41:05 -0400
Lines: 42
Message-ID: <1t3q431lcqo4n5888...@4ax.com>


The next message seems normal:

Path: news.grc.com!.
From: Jimmy <Ji...@disposable.invalid>
Newsgroups: grc.techtalk
Subject: Re: Curiosity or Fraud ??? Trying to buy Grisoft
AVG
Date: Thu, 17 May 2007 22:02:59 -0700
Organization: PC Repair
Lines: 16
Message-ID: <f2jc25$an0$1...@news.grc.com>
References: <1t3q431lcqo4n5888...@4ax.com>


But then:

Path: news.grc.com!.
From: "Dave Rodgers" <drod...@xxx.xxx> [munged]
Newsgroups: grc.techtalk
Subject: Linux Distro Question
Date: Fri, 18 May 2007 02:01:23 -0500
Lines: 18
Message-ID: <f2jkkd$gjm$1...@news.grc.com>
References: <1t3q431lcqo4n5888...@4ax.com>
<f2jc25$an0$1...@news.grc.com>


Any thoughts?

--
Thanks,
tbl

tbl

unread,
May 18, 2007, 4:44:52 PM5/18/07
to
On Fri, 18 May 2007 20:39:51 GMT, tbl <ha...@ThatSpam.net>
wrote:

Forgot to mention: Agent 4.2. But I have had this happen
in earlier versions, as well.

--
tbl

jo

unread,
May 18, 2007, 5:04:46 PM5/18/07
to

tbl wrote:

>Every great once-in-a-while, while following a given thread,
>the thread seems to get hijacked. The subject changes to
>something not at all related, and that may be the only topic
>from there on, or it may just be another topic inside that
>thread.

>Any thoughts?

Check your settings at Tools / Options / Display / Message List Pane /
Threading (this is where they are in 4.1)
And have a look at how many messages you have in the group. If above
20 or 30 thousand or so, you might be hitting the hash collision bug
and should move at least half to an archive folder.

Carroll Robbins

unread,
May 18, 2007, 5:19:59 PM5/18/07
to
tbl <ha...@ThatSpam.net> wrote in
<4s2s43ljmj5hkcjes...@4ax.com> on Fri, 18 May 2007 20:39:51
GMT:

>Every great once-in-a-while, while following a given thread,
>the thread seems to get hijacked. The subject changes to
>something not at all related, and that may be the only topic
>from there on, or it may just be another topic inside that
>thread.

The headers for these messages show they all belong to the same thread.
Dave Rodgers changed the subject but posted a reply not a new thread. He
apparently doesn't know how to post correctly. You can have Agent start a
new thread when the subject changes. Examine the Threading settings at
"Tools -> Options -> Display -> Message List Pane".
--
Carroll Robbins

Ralph Fox

unread,
May 18, 2007, 11:59:35 PM5/18/07
to

The "References" header indicates that this was posted as a reply
to the first message. Compare the "References" header of the
second message with the "Message-ID" header of the first message.


> But then:
>
> Path: news.grc.com!.
> From: "Dave Rodgers" <drod...@xxx.xxx> [munged]
> Newsgroups: grc.techtalk
> Subject: Linux Distro Question
> Date: Fri, 18 May 2007 02:01:23 -0500
> Lines: 18
> Message-ID: <f2jkkd$gjm$1...@news.grc.com>
> References: <1t3q431lcqo4n5888...@4ax.com>
> <f2jc25$an0$1...@news.grc.com>


The "References" header indicates that this was posted as a reply
to the first two messages. Compare the "References" header of the
third message with the "Message-ID" headers of the first two messages.

Dave has clicked the "Reply" button to start a reply message in the
same thread -- and then Dave has edited the subject line.

Dave did not click the "New usenet post" button to start a new thread.


> Any thoughts?

Dave needs to be educated. It's Dave who has done the hijacking.


–––––====oooOooo====–––––


Agent has another problem where, very occasionally, a follow-up
message gets threaded into the wrong thread even though the
follow-up's References header does not match any of the other
messages' "Message-ID" headers. The case which you posted here
is *NOT* an example of this.

If you want to read more about the other problem, Google this
group for "hash collision".


--
Cheers,
Ralph

Nick Spalding

unread,
May 19, 2007, 2:37:38 AM5/19/07
to
jo wrote, in <b3cb15d57284ff6a5...@me.getting.bored.now>
on Fri, 18 May 2007 21:04:46 GMT:

I don't think this is the problem here (Mr Fox has as usual done the
leg-work) but the message count doesn't have to be anywhere near as much
as that to get hash collisions.
--
Nick Spalding

Vista Home Premium, Intel Viiv dual core E6300 (1.86Ghz, 1066MHz FSB),
2GB RAM, 320GB NTFS HD, Video Nvidia GeForce 7900GS LCD 1280x1024x60Hz

tbl

unread,
May 23, 2007, 1:56:03 PM5/23/07
to
On Fri, 18 May 2007 21:04:46 GMT, jo <ki...@lineone.net>
wrote:

>
>tbl wrote:
>
>>Every great once-in-a-while, while following a given thread,
>>the thread seems to get hijacked. The subject changes to
>>something not at all related, and that may be the only topic
>>from there on, or it may just be another topic inside that
>>thread.
>
>>Any thoughts?


>Check your settings at Tools / Options / Display / Message List Pane /
>Threading (this is where they are in 4.1)


"Enable Threading by Subject" is checked, but
"Start a new thread when followup subject changes" is not.


>And have a look at how many messages you have in the group. If above
>20 or 30 thousand or so, you might be hitting the hash collision bug
>and should move at least half to an archive folder.


For the group that I investigated, 166k+ (!) Guess I need
to do some archiving.


Thanks for the good info.

--
tbl

tbl

unread,
May 23, 2007, 2:00:26 PM5/23/07
to
On Sat, 19 May 2007 07:37:38 +0100, Nick Spalding
<spal...@iol.ie> wrote:

>jo wrote, in <b3cb15d57284ff6a5...@me.getting.bored.now>
> on Fri, 18 May 2007 21:04:46 GMT:
>
>>
>> tbl wrote:
>>
>> >Every great once-in-a-while, while following a given thread,
>> >the thread seems to get hijacked. The subject changes to
>> >something not at all related, and that may be the only topic
>> >from there on, or it may just be another topic inside that
>> >thread.
>>
>> >Any thoughts?
>>
>> Check your settings at Tools / Options / Display / Message List Pane /
>> Threading (this is where they are in 4.1)
>> And have a look at how many messages you have in the group. If above
>> 20 or 30 thousand or so, you might be hitting the hash collision bug
>> and should move at least half to an archive folder.
>
>I don't think this is the problem here (Mr Fox has as usual done the
>leg-work) but the message count doesn't have to be anywhere near as much
>as that to get hash collisions.


The group that message came from has 166k+ messages... Looks
like I'm a little behind the curve, here!

Also contemplating checking the box for "Start a new thread
when a followup subject changes".

Thanks Nick.

--
tbl

tbl

unread,
May 23, 2007, 2:01:58 PM5/23/07
to


Looks like I should check the box for "Start a new thread
when a followup subject changes", eh?

Thanks for the help.

--
tbl

tbl

unread,
May 23, 2007, 2:07:25 PM5/23/07
to
On Sat, 19 May 2007 03:59:35 +0000, Ralph Fox <-...@-.invalid>
wrote:


Hehe. Thanks for the education, Ralph.


>Agent has another problem where, very occasionally, a follow-up
>message gets threaded into the wrong thread even though the
>follow-up's References header does not match any of the other
>messages' "Message-ID" headers. The case which you posted here
>is *NOT* an example of this.


There are over 166k messages in that group, so apparently
the bug seldom bites. But certainly something to be aware
of. Do you know if the Forte code-mongers have stated any
intentions toward fixing this, or are there bigger fish to
fry?


>If you want to read more about the other problem, Google this
>group for "hash collision".


Ahhh. Thanks. Forget that last question above, if it's not
too late...

--
tbl

0 new messages