31–40 of 127 posts
What's the end game of the Spanish org? What are they trying to achieve with this?
Earlier quoted context omitted.
Email has had threading since before I was born.
Email has never had explicit threading - email has a bunch of usage habits that many clients interpret as attempted threading (which often results in threads of steam receipts in my gmail webview FYI). There are a number of clients that are particularly good at respecting the specific approaches to threading used by mailing lists and that come with a plethora of powerful keyboard interactions to make browsing a whole…
edit: I see now in the RFC that there is a description.
Earlier quoted context omitted.
Email has had threading since before I was born.
Email has never had explicit threading - email has a bunch of usage habits that many clients interpret as attempted threading (which often results in threads of steam receipts in my gmail webview FYI). There are a number of clients that are particularly good at respecting the specific approaches to threading used by mailing lists and that come with a plethora of powerful keyboard interactions to make browsing a whole…
The "In-Reply-To" header is described in rfc2822. It is an explicit header in the RFC that is how you create threads.
Every mail client I've used correctly understands how to thread reply-chains using In-Reply-To.
The thing you're talking about, steam receipts grouping, is not a feature of email, but a specific feature of gmail's web view which is not mandated by any RFC and indeed is not explicit threading...
But there is a real way to thread which is defined in the RFC, and if you use a reasonable email client (aka not gmail), every mailing list's threading will work for you.
Earlier quoted context omitted.
Perhaps I am alone is this (based on the votes) but when I go to https://www.postgresql.org/list/ it requires a great deal of clicking to drill down and lets say I eventually end up some where like https://www.postgresql.org/list/pgsql-general/2021-09/ I am greeted with a lot "Re:" "No subject" etc. Perhaps what is comes down to is I am trying to interact with a mailing list using a browser which is perhaps unfair. I…
So the downvotes on your perfectly legitimate comment are absurd, but here we are. To get technical, the problem that you're having isn't that interacting with mailing lists is cumbersome, but rather, interacting with mailing list archives is cumbersome. You're not wrong. Web interfaces for mailing list archives haven't really changed in yonks, and there's little incentive to do so. The only people who use the archiv…
https://www3.wipo.int/madrid/monitor/en/showData.jsp?ID=ROM.... -> Real-time Status and then -> Documents -> United States of America -> (PDF link) https://madrid.wipo.int/documentaccess/documentAccess?docid=...
Earlier quoted context omitted.
Linux has had the LKML for almost three decades. It still works well for them. https://en.wikipedia.org/wiki/Linux_kernel_mailing_list
Does it? I find it really cumbersome. We were just interacting with it the other day and found it annoyingly baroque. There's a lot of assumed knowledge and I've read a fair bit of documentation and have been following Kernel development since before my career. It "works" for the people who it works for and that's it.
Earlier quoted context omitted.
Does it? I find it really cumbersome. We were just interacting with it the other day and found it annoyingly baroque. There's a lot of assumed knowledge and I've read a fair bit of documentation and have been following Kernel development since before my career. It "works" for the people who it works for and that's it.
Ok, what would you suggest in it's place?
At this point I might suggest Gitlab, but I don't really feel like having a back and forth about what may or may not be ideal about that.
This is the guy in question: https://twitter.com/ahachete