From nobody Sun Jan 22 06:01:27 2023 X-Original-To: freebsd-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 4P02g13jq2z2tyl2 for ; Sun, 22 Jan 2023 06:01:33 +0000 (UTC) (envelope-from grog@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P02g13GMGz4Drr; Sun, 22 Jan 2023 06:01:33 +0000 (UTC) (envelope-from grog@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1674367293; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=E8NA1Mr21OL0NXXgYCNk7EypkZKkgfQm3RE0+4K4C+s=; b=BEpGmiw3JcFyqhmgktHt6pH0IS+sesSeUZer203KH8e5r775vlIes5wJzoR7uEmX1u7ZYx VLLRafZpQs7UpxXJEhxj7++NsHwdmItb1us5Upv6Jo8n3DBwpOdSoM2UPrxnuqK/kke/7f YZwtB/P2NedufzHDKnesAz5sVwFxkHwKOZJb5WxKh3woxDw1+YpisIw6hFNDWHC/CzvX7M avWQEhNBW8fB2blUponAJ9eQ4ePzlkNp8SQhSO3ecgXFV/NOyIh/4W1adWpexIzFA4UcpJ x17TjmKfz6d7kmxakyRHji0h3UyxoqlqjCeI20pJwsCkQe1YvhTmF3YOrOGVJg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1674367293; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=E8NA1Mr21OL0NXXgYCNk7EypkZKkgfQm3RE0+4K4C+s=; b=UHotWfYv2F02ZEQnRwJmH2scpBQdZokxSjAjjJF4SwCDv7kLHpdsjgIo8vB0xQxPZkavEc EOTFKWppw8IeIhmDQjoyRKWOIlFnt0bvMhuYtxM9aKYELMnUFUsr5PC5+qh0Y9vX1DIQb8 UkKRHPrdHKkH3HwhSTAVfXkSDrVHI0tZudOlcLMPlo2pZvjPI8Sm/Mmj/pFlvU77da1tfH TwY+z1SGwiJ830A+B25L6S+53vbWqJkeYg92LijLpUSbe4+S/7VAIpctNxP/1katr81oV2 Z6VmaKY+HRK5Oo5UvZP1gWFcflClyw9+6OCv3a59t9X+YzFMLqk2MggFxDSzog== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1674367293; a=rsa-sha256; cv=none; b=Dop+2pxbfs2dPUJknIQ0+Bb7P1/ZwpFuuXLn79oeMExBATju4O0cD/L/FLEdOwGZ4irlw6 mJ2swq13zimNpeAReOMqn7DKaIzRelBRWzyjLkQXvqkaDoXuao6EKGgZPHNk3pbjY8U4OR Jy9khz7Aol6lxD7+JVOwvKz6vU5njNXJVj9tBrF9uxUavgS1ObgT9oviQub6KcyG73p5A6 60028YjLAz+s/TfNwlQsCQxnKwJl/MEAAbSVxJDomd0gqSj6ikE56lA3L2hJ/4YyEoJrq2 xoTROqS68WEGFQvR8N56c/bdjiilvlVNJ80RIdO60Ogjigtc+qq9OhwND8mtnw== Received: from eureka.lemis.com (121-200-11-253.79c80b.mel.nbn.aussiebb.net [121.200.11.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: grog/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4P02g00cRxzgrs; Sun, 22 Jan 2023 06:01:31 +0000 (UTC) (envelope-from grog@FreeBSD.org) Date: Sun, 22 Jan 2023 17:01:27 +1100 From: Greg 'groggy' Lehey To: Paul Procacci Cc: Ian Smith , freebsd-questions@freebsd.org Subject: Out of order posting (was:: Load 0.20 on a freshly installed idle system) Message-ID: <20230122060127.GB8068@eureka.lemis.com> References: <1889CB4C-4B11-4178-8446-97DA9E5EC35A@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/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="s/l3CgOIzMHHjg/5" Content-Disposition: inline In-Reply-To: Organization: The FreeBSD Project Phone: +61-3-5309-0418 Mobile: +61-490-494-038. Use only as instructed. WWW-Home-Page: https://www.FreeBSD X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 User-Agent: Mutt/1.6.1 (2016-04-27) X-ThisMailContainsUnwantedMimeParts: N --s/l3CgOIzMHHjg/5 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [message rearranged and trimmed for compliance and legibility] On Saturday, 21 January 2023 at 1:38:12 -0500, Paul Procacci wrote: > On Fri, Jan 20, 2023 at 11:44 PM Ian Smith wrote: >> >> PS Also bugging me is dreadful endless top-posting, tail-quoting Microso= ft >> corporate-email-style mess. > > Sorry but blame google and/or gmail for the top posting. Why? Have you not read their instructions? At https://support.google.com/a/users/answer/9283192 under "Have better email conversations", there's the item "Reply inline to email". That seems to be exactly what we're asking for. > I use whatever their defaults are and that's not going to change > unless they change it. You can put your answer wherever you want, though they may not make it easy. But it's your choice to use Gmail. I'd suggest to put your answers: * Where it matches what you're answering. * Where it matches the project guidelines. Where are the project guidelines? Currently there's https://docs.freebsd.org/en/articles/freebsd-questions/, which contains: Include relevant text from the original message. Trim it to the minimum, but do not overdo it. It should still be possible for somebody who did not read the original message to understand what you are talking about. Use some technique to identify which text came from the original message, and which text you add. I personally find that prepending =E2=80=9C>=E2=80=9D to the original message works best. Leaving white spa= ce after the =E2=80=9C> ;=E2=80=9D and leave empty lines between your text and the= original text both make the result more readable. Put your response in the correct place (after the text to which it replies). It is very difficult to read a thread of responses where each reply comes before the text to which it replies. > RFC's surrounding usenet described this in pretty clear detail. (Just > looked it up: 1855). Thanks for the link, though I don't see anything that relates to the current discussion. About the only thing of relevance I see is: do not include the entire original! > At this point in my life all I would suggest to you is to either > suck it up or ban/ignore the messages from senders you don't want to > see. Mine included. This would be a rather drastic approach. Discussion is better. > I found this to be a better approach than attempting to correct > people on what is the proper `netiquette'. Whatever you want, of course. But if you're prepared to accept a supposed mandate by Gmail, I wonder how objective you're being. Greg -- Sent from my desktop computer. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php --s/l3CgOIzMHHjg/5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAmPM0TcACgkQIubykFB6QiONvwCgpllr/MNi/x+4ychETdpW3/CE vy4An2EgOAvv9PZm8FDbeaItBdDtufhO =4P1B -----END PGP SIGNATURE----- --s/l3CgOIzMHHjg/5--