On Mon, 12 May 2008 04:40:11 +0100, Roy Schestowitz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> ____/ Kelsey Bjarnason on Monday 12 May 2008 00:45 : \____
>
>> [snips]
>>
>> On Sun, 11 May 2008 18:12:38 +0100, Roy Schestowitz wrote:
>>
>>> The reason for this is netiquette, I suspect. KNode warns if you
>>> crosspost widely (wildly) and probably crashes only if you are Gary
>>> Stewart. I've run KNode for months without a single glitch.
>>
>> Try this:
>>
>> Create a scoring rule, say on your own posts - makes it easy to keep
>> track of posts you've made and their responses. Colorize the header,
>> say in blue.
>>
>> Exit the app, re-run, load a newsgroup you know you've posted in
>> recently and... er... excuse? Where'd all my messages go? No
>> highlighting whatsoever!
>>
>> Oh, wait, yes there is. If you dick around hunting for them, you'll
>> find them, thoughtfully hidden in collapsed threads. Wasn't the whole
>> point of colorizing them to make them easier to spot? How about doing
>> what Pan does - if there's a colorization rule in place, actually
>> _colorize_ what's visible.
>>
>> Yeah, I know, you can still see the score, but when you're scrolling
>> down a largish selection of threads, it's not nearly as visible as it
>> should be, the whole point to colorizing it in the first place.
>>
>> This has been true of _every_ version of KNode I've tried since 2001.
>> It is, in fact, the sole reason I use Pan over KNode.
>>
>> One of these days I should get around to writing a patch for it. :)
>
> Don't you use vieweing filters? It's very handy. You can easily isolate
> threads where you posted.
I use every method known to man to sort news. As a result, I tend to get
annoyed when those methods stop working because of a bad design decision
on the part of an app developer. :)
|
|
