Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114354 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 47052 invoked from network); 10 May 2021 21:44:26 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 10 May 2021 21:44:26 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 3E71E1804DA for ; Mon, 10 May 2021 14:52:04 -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=0.9 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-qk1-f170.google.com (mail-qk1-f170.google.com [209.85.222.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 ; Mon, 10 May 2021 14:52:03 -0700 (PDT) Received: by mail-qk1-f170.google.com with SMTP id 197so16911325qkl.12 for ; Mon, 10 May 2021 14:52:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=e87ODN70Eyxdbk1QgmE+097tnAQfEITcwm5yq2yg02A=; b=emVbKTKUrs5D8K370sJuxRchA0ZDFrryOtSCp9Jf8ae3dyVucVfm6pZENsVJP3X0eg 6GXNxeAsyaadfTvj1jk5lLxsKp2WumMz1rU8Y3k9wtiAuP7i49Z7/Dby6UTYb/wjtCXg oq3K7VltJog/fW1EuSLpxP4XBucs3Or+sUa/Lu84T7ii/zln819me/9D4gMMclbZjfFt Y36b9HztMvVvUVsHEH3mwWgFCtotBKnQx4wj0WGFWLj3telbSe3DabMOQUxtlg0oiKgK AHvPcDfFPX5I3quVszwIIyvyAKBoie3xt4CXnBeNNVLmFaMNMK2oyLp8eKlMp7WmHlKj P2jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=e87ODN70Eyxdbk1QgmE+097tnAQfEITcwm5yq2yg02A=; b=nhsIP4NF3TqnuAGwEQ6iJPir0bxrdUPDg6r2OdMoFhbNNInLoD7HjbH6dDnaHR9YGF sDTyA75oz8KBc6q0rjTZyzAHHe/0YiDRWmgi00AE7OuL/50h0XoAVtyRSF11yfXKq3J3 9fLym0gJ1qs4MsYiLzSfeIMLsRdf0JqvfDVpk6eCR2hHaMjB4T2VemdH5xoZRkXY4EMb EECP+aeoJ0oN3jrhEjemxZuJe6VszwteUwbrSIFzZADOSzFlp/8EspQ82xNArUHrMbdB O8YLEhlH1Zg0bOGZaDxvYdnVgZNPBJAtczasIVH7VSe0/6rJYmlSBEAFEaim5ZND8yz0 ZQzA== X-Gm-Message-State: AOAM533uk+KxxWsxZBP/XY1g6AO0IrT6JPx3jNbF9nRtKLVlrEk+gSaF r0sfUbtXL/noZdRejfyo00FJzxgokuiHWnat2TKgzcayGaoadA== X-Google-Smtp-Source: ABdhPJxlSlqViFmRwGItxZBFuppdtdVXhbX11PDZe/J7MHpdpiXiBEVBW6qZod+0dT8nHuW3MBIAbqwyjIx0gqh/es0= X-Received: by 2002:a37:7c83:: with SMTP id x125mr26588256qkc.222.1620683519830; Mon, 10 May 2021 14:51:59 -0700 (PDT) MIME-Version: 1.0 Date: Mon, 10 May 2021 22:51:49 +0100 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary="0000000000007e2e6905c200c984" Subject: Could we drop the bottom-posting rule? From: tekiela246@gmail.com (Kamil Tekiela) --0000000000007e2e6905c200c984 Content-Type: text/plain; charset="UTF-8" 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 --0000000000007e2e6905c200c984--