info-gnus-english
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Workarounds for replies from nntp breaking thread references


From: Björn Bidar
Subject: Re: Workarounds for replies from nntp breaking thread references
Date: Sun, 29 Dec 2024 16:31:17 +0200
User-agent: Gnus/5.13 (Gnus v5.13)

James Thomas <jimjoe@gmx.net> writes:

> Björn Bidar wrote:
>
>> James Thomas writes:
>>
>>> Björn Bidar wrote:
>>>
>>>> Currently I'm building threads by reference
>>>> (gnus-gather-threads-by-references). But I noticed that replies from
>>>> those that read from nntp and reply via nntp/Gmane break the threading
>>>> as the reference to the original threat seems to be missing or
>>>> different.
>>>>
> ...
>>>
>>> gnus-fetch-old-headers?
>>
>> I have set that variable to 'some should that be enough?
>> The issue is that the Gmane bridge does not keep references intact.
>
> Oh sorry; I misunderstood your question.
>
>> IMHO since Gmane replies are send as a email a direct reply by email to
>> the thread would be the the best but I'm not sure either if in this
>> context the thread references would be resolved.
>
> I don't fully follow, but maybe try nntp-xref-number-is-evil?

A user reads with nntp and replies.
The reply is send to Gmane which then goes a head and replies with an
email from nntp to the list. If the user directly replies to the message
using their own email with the references intact the issue wouldn't exist.

>>>> Did anyone found any workaround for this kind of situation besides
>>>> gathering threads by subject?
>
> Is this really a bother?

For all groups yes but for these kinds of groups it might not be that
bad.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]