From nobody Thu Jun 23 08:14:40 2022 X-Original-To: freebsd-current@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 06F4085E0D2; Thu, 23 Jun 2022 08:14:45 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LTChz3X64z4r0C; Thu, 23 Jun 2022 08:14:43 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by mail-ed1-x533.google.com with SMTP id eo8so27425273edb.0; Thu, 23 Jun 2022 01:14:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=K6xNzL0t1HmM3DCVYAA37mlpatRKNBDFMhseepUsbaM=; b=mhSYAsodirw0qiaDct2t3S2NASnFv0dLZGQ/Smcf2nxHXgCRxAq3JGgvXEXxgqg3w3 26eolkrgvFH3OpW8k77driN9AlHlihK9LM7BJldSyf3KZNnDT3oYWRijwsPLs7MBPFwS WuxGLZsw/XAAAc2sCHIJpMJub9is33ufmHtFYvwPbkIjcjwKm1O3uh7OfkchM/VBZOpj gzuzmWbV3q5yD8J48NAQ/ZDtVByOimb8Dx3zA1H9tvTSyjajMmpjAfy54huH7hG8aLS7 XfQh3WmAjjp1Ehp+TYWZr4D8SRO+8Rr8+nlzkqlrx9+AeevmGxZj2GWwe+l6QNrq/0uO lJAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=K6xNzL0t1HmM3DCVYAA37mlpatRKNBDFMhseepUsbaM=; b=kRgdoSN/b1aM21c7fjqCaL/Jys3SJpoqXe4UExFJn0aKERiGcTU6saGQK7r6PRvBwC EA0ZaOTjQDotC5oIEeqk3jgdINt8cZ6zYzL/lWfWU8wylmJxE+pnXfNE22TWBoIKdz9p XkqbwmqZxD0B75eRhu/NPwQ719eWPwQAdgV1T2GePMqyoe3NiMMkQs/q0+57EjN5VttN Wd+RRkJUaJqiVwE55GkXtOuSt+qpupRYPbAqs43NQGuwJyx1wRrquUPmeMREXBBFT4lG yIDtD7+8cWAarl2njaDqbijOB2mJXrtDd/qxx4/8/hKZFHKyft/slM+pRQ5MdSdiNSJW IRTQ== X-Gm-Message-State: AJIora9VtlPLNDZ257gY6ODQcoKcT+Rk+TxNUKNmTrDIM4w6XDzZbWQs kk3tG/j30DkJAmnURlQ0TXQPE/Gb4TlB6v01SO+s5XwgPQ0h0St9X8M= X-Google-Smtp-Source: AGRyM1slxuMSCQSYptUZOr4FovOyFY/TOnW3ZySO2RjA0fnXyFZp/EeOZChlTMcOPSHtqLef97BYiHTSylqK0d1iCJg= X-Received: by 2002:a05:6402:249e:b0:42d:bb88:865b with SMTP id q30-20020a056402249e00b0042dbb88865bmr8903818eda.141.1655972081375; Thu, 23 Jun 2022 01:14:41 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Received: by 2002:ab4:a183:0:0:0:0:0 with HTTP; Thu, 23 Jun 2022 01:14:40 -0700 (PDT) In-Reply-To: <20220623060320.aad6a631.freebsd@edvax.de> References: <20220623030118.GA59423@eureka.lemis.com> <20220623060320.aad6a631.freebsd@edvax.de> From: grarpamp Date: Thu, 23 Jun 2022 04:14:40 -0400 Message-ID: Subject: Re: Posting Netiquette [ref: Threads "look definitely like" unreadable mess. Handbook project.] To: freebsd-doc@freebsd.org Cc: postmaster@freebsd.org, freebsd-questions@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4LTChz3X64z4r0C X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=mhSYAsod; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of grarpamp@gmail.com designates 2a00:1450:4864:20::533 as permitted sender) smtp.mailfrom=grarpamp@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::533:from]; MLMMJ_DEST(0.00)[freebsd-doc,freebsd-questions,freebsd-current]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N >> the =C3=A2=E2=82=AC=C5=93> ;=C3=A2=E2=82=AC and leave empty lines betwe= en your text and the original > Seems there is a charset mismatch. > MUA displaying nonsense > Oh the joy of UTF-8... ;-) https://unicode-table.com/en/sets/quotation-marks/ The pages ... https://docs.freebsd.org/en/books/handbook/eresources/#eresources-mail https://docs.freebsd.org/en/articles/freebsd-questions/ https://docs.freebsd.org/en/articles/mailing-list-faq/ ... are intermixing standard ASCII double quotes with questionably gratuitous choice of using left and right double quotes via UTF-8, which then may get slaughtered by non UTF-8 enabled cut-paste, systems, lists, gui's, desktops, apps, and MUAs along the way. Perhaps smack the typeset within all pages back down to ASCII, except where no standard ASCII convention is available to substitute for symbols, ie: (c) is the fine sub for =C2=A9, and ASCII still fits within UTF-8 meta declarations, which may be needed for =E2=82=BF which has no ASCII substitute, and of course for presenting non ASCII languages. And perhaps systems can consider enabling UTF-8 if needed to render and handle things like =E2=82=BF, say for whenever foundation gets to accepting those easy donations and crowdfunding. No idea what the ';' in the '=E2=80=9C> ;=E2=80=9D' is doing there for. A proper page would need to add a number of the missing email formatting netiquettes (such as no HTML), and actual photo examples of former bad chaos and new good result, etc... to be considered a good format, subject, and addressing netiquette guide rule page. Consider if "FreeBSD Articles" is best hier for a page that may becoming more often directly linked or included into prospective list user's signup clickstream, quarterly admin, friendly cluebat hints, etc. And it's mostly written to apply only to -questions when it should be completely agnostic. So the pages may be currently serving lesser preventive or curative use as far as lists could go. > Unless there is a good reason to do otherwise, reply to the sender > and to FreeBSD-questions. Well for subscription-required-to-post lists, only list-reply is needed... which also follows address line bloat minimization, reduces personal reply issues, reduces "Stop copying me direct when I'm on list", etc. > Arguably these recommendations should be separated out into their own pag= e. Such soley dedicated content would make the page easier for people to link to wherever such reference is needed. The current pages don't, and they're bleeding [partially] duplicated and differing guidance content across each other. If the page was good enough, it would get picked up by search engines and other projects. [-current, and even -questions, could probably be dropped now, for -doc, or wherever else is best.]