Re: GNOME discussions

On 3 November 2022 3:04:13 am AEDT, Graham Perrin <grahamperrin@freebsd.org> wrote:
 > On 02/11/2022 14:29, void wrote:
 > > On Wed, Nov 02, 2022 at 06:52:31AM +0000, Graham Perrin wrote:
 > >
 > >> E-mail too often fails.
 > >>
 > >> You can't fix this 
 > >>
 > <https://wiki.freebsd.org/GrahamPerrin/email#Broken_threading.2C_disconnections>,
 > 
 > >> for example.
 > 
 > …
 > 
 > > … The actual threading of an email conversation was (or at least I 
 > > thought it was)
 > > an email client competency, exclusively. …
 > 
 > I mean, whatever the cause of the mess, the end result (a mess of 
 > apparently disconnected threads) can not be fixed:
 > 
 > <https://wiki.freebsd.org/GrahamPerrin/email?action=AttachFile&do=get&target=2022-11-02+06.27+freebsd-questions.png>


With reference to:

https://lists.freebsd.org/archives/freebsd-questions/2022-June/index.html

my OP message to the list "Broken User Experience - online mailing list"

https://lists.freebsd.org/archives/freebsd-questions/2022-June/001397.html

about this very issue, the subsequent equally messy set of detached groups of responses, and including notably from Baptiste Daroussin (bapt@) who them indicated desire to help fix the problem.

The threading issues appear entirely related to the new list software, which apart from broken ability to traverse the lists properly by browser, may also be messing with the thread linkages in distributed raw emails?

Again, looking at the previous pipermail archives and browsing threads there shows how it used to be properly done for many years.

Of course people - as well as the list software - were more disciplined in keeping messages free of html attachments, wrapping lines at lengths suitable for text email clients etc.  The messier it gets, the messier people seem to want to make it :(

Whether "it can not be fixed" is out of our hands, I don't know.  I do know that it (thread linking and traversal) was ok for the first few months on the new list software, but that when it changed to how it is now, that change applied retrospectively to previous months ... which seems to indicate that if fixed, that may also retrospectively repair the damage? 

cheers anyway, Ian