nanog mailing list archives
Re: Diversity of MUAs (was Re: How threading works (was Re: Root Cause Re: 202401102221.AYC ...))
From: Peter Potvin via NANOG <nanog () nanog org>
Date: Sun, 14 Jan 2024 01:46:06 -0500
*audible sigh* Yet another useless thread added to my Gmail inbox because of a changed subject line. Can we please stop doing this for conversations that are about the same topic? Numerous users on this list have clearly shown they are annoyed by this, and frankly is something that the list admins should be looking into - it spams everyone’s inboxes and makes conversations harder to follow. Kind regards, Peter On Sun, Jan 14, 2024 at 01:34 Ellenor Bjornsdottir via NANOG < nanog () nanog org> wrote:
On Sunday, January 14, 2024 6:01:45 AM UTC William Herrin wrote:On Sat, Jan 13, 2024 at 12:58 PM Bryan Fields <Bryan () bryanfields net>wrote:On 1/12/24 3:04 PM, Mu wrote:Would it be possible for you to reply in-thread, rather thancreating a new thread with a new subject line every time you reply to someone?Trying to follow the conversation becomes very difficult for noreason.Threading has nothing to do with subject lines. RFC822 (now 5822)specifieshow this works based on message ID. This thread displays fine inthreadedmode in my MUA and in the archives.Hi Bryan, Respectfully, your MUA is not the only MUA. Others work differently. GMail, for example, follows the message IDs as you say but assumes that if you change the subject line in your reply (more than adding "Re:") then you intend to start a new thread from that point in the discussion. It groups messages accordingly. This is not an unreasonable expectation: if you merely want to continue the current conversation without going off on a new tangent then there's no need for a different subject line. Regards, Bill HerrinI have been using KMail to read this list. Just thought I'd throw my hat in the ring there, I guess!
Current thread:
- 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block, (continued)
- 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block Abraham Y. Chen (Jan 10)
- RE: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block Tony Wicks (Jan 10)
- Root Cause Re: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block Abraham Y. Chen (Jan 12)
- Re: Root Cause Re: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block Mu (Jan 12)
- How threading works (was Re: Root Cause Re: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block) Bryan Fields (Jan 13)
- Re: How threading works (was Re: Root Cause Re: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block) Abraham Y. Chen (Jan 13)
- Re: How threading works (was Re: Root Cause Re: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block) Joel Esler (Jan 13)
- Re: How threading works (was Re: Root Cause Re: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block) Jay R. Ashworth (Jan 14)
- Re: How threading works (was Re: Root Cause Re: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block) William Herrin (Jan 13)
- Re: Diversity of MUAs (was Re: How threading works (was Re: Root Cause Re: 202401102221.AYC ...)) Ellenor Bjornsdottir via NANOG (Jan 13)
- Re: Diversity of MUAs (was Re: How threading works (was Re: Root Cause Re: 202401102221.AYC ...)) Peter Potvin via NANOG (Jan 13)
- Re: Diversity in threading, Diversity of MUAs (was Re: How threading works John Levine (Jan 14)
- Re: Diversity in threading, Diversity of MUAs (was Re: How threading works William Herrin (Jan 14)
- Re: Diversity in threading, Diversity of MUAs (was Re: How threading works Andy Smith (Jan 14)
- Re: [External] Re: Diversity in threading, Diversity of MUAs (was Re: How threading works Hunter Fuller via NANOG (Jan 15)
- Re: How threading works (was Re: Root Cause Re: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block) Bryan Fields (Jan 14)
- Re: How threading works (was Re: Root Cause Re: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block) Abraham Y. Chen (Jan 14)
- Re: How threading works (was Re: Root Cause Re: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block) Giorgio Bonfiglio via NANOG (Jan 14)
- Re: How threading works (was Re: Root Cause Re: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block) Christopher Hawker (Jan 14)
- Re: How threading works (was Re: Root Cause Re: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block) Tom Beecher (Jan 14)
- Re: How threading works (was Re: Root Cause Re: 202401102221.AYC Re: Streamline The CG-NAT Re: 202401100645.AYC Re: IPv4 address block) Jay R. Ashworth (Jan 14)