#2 Leafnode Xref: problem

[Dâniel Fraga]

Hi, I think I found a bug. My setup:

Leafnode 1.9.45.rel
knews 1.0b.1 (newsreader)
inn 2.4.0 (server used for this example)

1) Suppose I post a crossposted message to three groups named
group.a, group.b, group.c

2) fetchnews sends the message and retrieves it

3) when I open knews, I see 1 message in each group. Anyway, knews
is configured to mark the article read based on the Xref: field, so the
right thing to happen if I click on the message in group.a (for instance)
is that knews will mark read the same message in group.b and group.c.

But, this doesn't happen with leafnode. I tested the behaviour directly
accessing inn and it works correctly, so it isn't knews' fault.

Well, I found the problem: knews with leafnode will only mark the same
crossposted message *read* in all groups, if I access the last group
before the others. In this example, for knews work with leafnode, I
must access group.c, so it can mark read the same message in group.b
and group.a.

The Xref: would be something like this:

Xref: abusar.abusar.org group.a:4 group.b:40 group.c:34

So it's like leafnode works on the Xref: field from right to left. In other
words (using the Xref: above), if I'm reading group.a, knews will mark
read this message only in group.a. If I'm start reading group.b, knews
will mark read this messagen only in group.b and group.a. Finally, if I'm
reading group.c, it works as it should work and knews can mark read in
all crossposted groups.

On the above Xref: example, I must access group.c first. If Xref: would
be something like:

Xref: abusar.abusar.org group.c:34 group🅱️40 group🅰️4

I must access group.a (the last one in Xref: line) first, so knews would
kill correctly the same article in the 2 crossposted remaining groups.

I think it's leafnode's problem, because with INN it doesn't happen. So
knews depends on the news server to do this.

Sorry for the long bug report, I hope I can help you figure it out.

Thanks!

[Matthias Andree]

Logged In: YES
user_id=2788

Not a leafnode bug. The "group:number" pairs on the Xref: line are
unordered. knews bug?