MTNW and unread counts

In article <gkreme-C3631C.06522026022008.TakeThisOut@news.giganews.com>,
Lewis <gkreme.TakeThisOut@gmail.com> wrote:

> In article <paul.sture.nospam-BC0CD4.10334926022008.TakeThisOut@mac.sture.ch>,
> "P. Sture" <paul.sture.nospam.TakeThisOut@hispeed.ch> wrote:
>
> > In article <gkreme-E15A3F.10435416022008.TakeThisOut@news.giganews.com>,
> > Lewis <gkreme.TakeThisOut@gmail.com> wrote:
> >
> > > I have MTNW set to show killed threads, and yet when I see the unread
> > > count in the group list, and then open the group, the count drops by
> > > some number.
> > >
> > > For example, there were 5 messages in csmm and when I opened the group
> > > there were only 2 messages. 32 messages in csms, but only 23 when I
> > > actually opened the group.
> > >
> > > And I am seeing the killed messages.
> >
> > But aren't the killed messages already marked as read? They are here.
>
> Yes, they are marked as read, but in the specific example I gave there
> were 5 messages in csmm, but only 2 when I opened the group. Not of
> these were killed messages. Just the count is wrong.
>
> Turning on the slow article count seemed to alleviate this, but it is
> *very* slow, so I turned it off again. Now I just live with the
> incorrect article counts, or rather I ignore them.

In the documentation that is what is said. I believe the host does the
counting, in which case it is good to have the option.

--
What is done in the heat of battle is (normatively) judged
by different standards than what is leisurely planned in
comfortable conference rooms.