From nobody Sat Jun 18 09:18:59 2022 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id EA3B286086A for ; Sat, 18 Jun 2022 09:19:26 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from cp160176.hpdns.net (cp160176.hpdns.net [91.238.160.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4LQ9My5NNcz4d2l; Sat, 18 Jun 2022 09:19:26 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=milibyte.co.uk; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=vC+O42iUJjLSiX8EzFdVsjuROddkcwt0LT1cU4l4Tjc=; b=Z2YmaGC2q67EA0Shrq+LTNvdsU J6s4fScjcVPX5O9+1g1ur/2nuRfhjN8o3JXX5lr4/C6HflyYkJtbK0tiKQbVjUhvgIzsLpdeFpjr/ lWcK38E0pG9HIqJHsB7sXRJDKH9nucICFn+G+z4XVDT4bfjmhIdpZk6zFXMT2WNb53dtBLWU1xj2i YTbH1fhsu4L2vxo+an3/kPZC3/K/bZElM08PGm0uFVuo81eY4xDmE4NU1naEsfQ0S4PhsUBI/j9EY q4lh7e+BzuywGhrg+667g1T6u7io8QI29vlModEDV9n6VjFTly15TdkGjOlADCyM/bGo3eb6XVWPv jXChGfxw==; Received: from 82-71-56-121.dsl.in-addr.zen.co.uk ([82.71.56.121]:27916 helo=curlew.milibyte.co.uk) by cp160176.hpdns.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1o2Ubg-001lAy-Jo; Sat, 18 Jun 2022 10:19:03 +0100 Received: from [127.0.0.1] (helo=curlew.localnet) by curlew.milibyte.co.uk with esmtp (Exim 4.95) (envelope-from ) id 1o2Uba-0001A3-KA; Sat, 18 Jun 2022 10:18:59 +0100 From: Mike Clarke To: questions@freebsd.org Cc: postmaster@freebsd.org, Ian Smith Subject: Re: Broken User Experience - online mailing list Date: Sat, 18 Jun 2022 10:18:59 +0100 Message-ID: <2882063.hHqAuc6tWs@curlew> In-Reply-To: <2E1B782A-DB40-41B1-A036-A790C4DCC409@nimnet.asn.au> References: <2E1B782A-DB40-41B1-A036-A790C4DCC409@nimnet.asn.au> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="nextPart2273836.THHZn3L5Ee" Content-Transfer-Encoding: 7Bit X-SA-Do-Not-Rej: Yes X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-SA-Exim-Scanned: No (on curlew.milibyte.co.uk); SAEximRunCond expanded to false X-YourOrg-MailScanner-Information: Please contact the ISP for more information X-YourOrg-MailScanner-ID: 1o2Ubg-001lAy-Jo X-YourOrg-MailScanner: Found to be clean X-YourOrg-MailScanner-SpamCheck: X-YourOrg-MailScanner-From: jmc-freebsd2@milibyte.co.uk X-Spam-Status: No X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cp160176.hpdns.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - milibyte.co.uk X-Get-Message-Sender-Via: cp160176.hpdns.net: authenticated_id: mailpool@milibyte.co.uk X-Authenticated-Sender: cp160176.hpdns.net: mailpool@milibyte.co.uk X-Source: X-Source-Args: X-Source-Dir: X-Rspamd-Queue-Id: 4LQ9My5NNcz4d2l X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --nextPart2273836.THHZn3L5Ee Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" On Saturday, 18 June 2022 06:15:15 BST Ian Smith wrote: > Instead of linking messages to next and previous messages in thread, there > are only (possibly multiple) Reply links, and Reply To links back, but no > "next / previous message in thread" links, which a) allowed full traversal > of all messages in the thread, and b) moving on to the next thread after > the last one. When faced with this type of problem with web based lists I generally open the message in a new tab so that I can quickly switch back to the list to read the next item. -- Mike Clarke --nextPart2273836.THHZn3L5Ee Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="UTF-8"

On Saturday, 18 June 2022 06:15:15 BST Ian Smith wrote:


> Instead of linking messages to next and previous messages in thread, there

> are only (possibly multiple) Reply links, and Reply To links back, but no

> "next / previous message in thread" links, which a) allowed full traversal

> of all messages in the thread, and b) moving on to the next thread after

> the last one.


When faced with this type of problem with web based lists I generally open the message in a new tab so that I can quickly switch back to the list to read the next item.


--

Mike Clarke

--nextPart2273836.THHZn3L5Ee--