Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114382 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 47408 invoked from network); 11 May 2021 14:09:50 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 May 2021 14:09:50 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id A19171804DB for ; Tue, 11 May 2021 07:17:37 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: **** X-Spam-Status: No, score=4.0 required=5.0 tests=BAYES_50, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com [209.85.208.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 11 May 2021 07:17:37 -0700 (PDT) Received: by mail-lj1-f170.google.com with SMTP id w15so25292369ljo.10 for ; Tue, 11 May 2021 07:17:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XIRB0rMCB1az6rcRWBKaErJyRIz6b1Py63iIdPT2pOo=; b=UGeKq4tRVWLPSahFqJL7nHmhSH8KIwf2Ecrfo9Rn9CmoU6zeYpDLiihR2URZZGVVla yGqDQIEAE+lKK5wqK6E592CKolICvNMT2moZBVYsB5VyP/tZvU8jQr7p7Sra2xpBrEZb db4mLjUKKvjw5tTmMBbahohwj0HstcgiYrZWZSjwx/shyUVcrxEfgpRnCKpPuvUvIl7Z 38Uz5yD2FC2r2E8YTgVxczA6YBcIokPezPxQXQwpBiWuqyWWPDPaUG/IdE0lqnwuN3Hw 9+7GqTvaYGSL3pZE+0EQM7moV3ME4djDoC3BlUDYz80umb7zZIljxVyMXvWfC9ZihFvV SNsw== X-Gm-Message-State: AOAM5321/9ciaiV4BilZo5JqbT/QKE7PyFYL1DqPoW0eMFtuINqA69hI 4/ANc8FVAdKnWaDNR7xdCSvLqD7S7IO4ZWm2/O0UKA== X-Google-Smtp-Source: ABdhPJz4piDrwZFL9PNN8BT44sM8c89fMiLLPH96iryhpmbdSolAAYq4wnDdrcRwbjpMBR7BF9Ue01iONuCdYptyqOk= X-Received: by 2002:a2e:a379:: with SMTP id i25mr24850227ljn.365.1620742654966; Tue, 11 May 2021 07:17:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 11 May 2021 09:17:24 -0500 Message-ID: To: Kamil Tekiela Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000038cf2e05c20e8e46" Subject: Re: [PHP-DEV] Could we drop the bottom-posting rule? From: pollita@php.net (Sara Golemon) --00000000000038cf2e05c20e8e46 Content-Type: text/plain; charset="UTF-8" -1. Top posting encourages lazy email composition. One should put an ounce of thought into how one organizes a response. On Mon, May 10, 2021 at 4:52 PM Kamil Tekiela wrote: > > Hi Internals, > > Could we drop the bottom-posting rule? > > Almost all new contributors fall into this trap and reply to a thread by > top-posting, only to get chastised by someone else on the list. It's really > difficult to remember to delete the default reply. Mail clients don't make > it easy for us; it's hidden by default. Bottom-posting makes reading the > thread much more difficult too. The actual reply gets lost in between the > quoted content. I often get confused about what is new and what was > quoted. Many modern clients are designed to handle top-posting and don't > handle bottom-posting well. People are usually used to it and they read > from top to bottom. I don't know if in the past some mail clients defaulted > to bottom-posting but right now it just seems like an unnecessary > annoyance. > > If you want to quote someone then it makes sense to copy a part of the > message and then add a reply below, but forcing people to remove the > default reply from the mail client and then add the whole previous message > on top of your own reply isn't very productive. It wastes time and screen > space. > > Could we please change this rule or at least stop enforcing it? > Do people actually have mail clients that don't automatically hide the > previous conversation? If not, then I think we can let people top-post. > > Regards, > Kamil --00000000000038cf2e05c20e8e46--