From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,ff7d8060c8210f40 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!newsfeed.r-kom.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Alex R. Mosteo" Newsgroups: comp.lang.ada Subject: Re: [OT] Broken threading (was RE: real_time.clock is not monotonic) Date: Fri, 23 Feb 2007 11:11:14 +0100 Message-ID: <547stgF1vulshU1@mid.individual.net> References: <545blhF1ttrphU2@mid.individual.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Trace: individual.net PbK9dwm4GlrfzMdcaMHoOw7WPpx61XqtuRnXksMmflHIxZRQQ= User-Agent: KNode/0.10.4 Xref: g2news2.google.com comp.lang.ada:9451 Date: 2007-02-23T11:11:14+01:00 List-Id: Randy Brukardt wrote: > "Alex R. Mosteo" wrote in message > news:545blhF1ttrphU2@mid.individual.net... > ... >> Randy, all your posts break threading in my newsreader. I'm wondering in > whose >> end is the problem -- my knode or your newsreader. >> >> Curiosly, I'm not sure it has been always like this. I'd say it's since > some >> weeks ago. > > I started using the Ada-France e-mail service a couple of weeks ago after > changing ISPs (the new ISP doesn't have a news server, the installer said > that since they only support businesses, they don't support news, as "it's > more for home users". Uh-huh.) I'd expect that you'd see issues with other > people using that service (I doubt they're specially handling messages from > me... ;-) > > Anyway, someone offered to give me an account on their personal news server; > I posted this message with that account. Does this help?? Yes, this message appears properly threaded :) When digging for bugs in knode I found the one that's causing this: knode only relies on reference headers, and doesn't consider the subject in absence of references. Obviously, not being your fault, is very kind of you to use an alternative, but since I'll get the problem with other people until this is fixed in knode, you may as well use whatever is more comfortable for you. Thanks in any case, Alex.