Date: Mon, 23 Jan 2023 02:49:24 +0100 From: Tomasz Rola <rtomek@ceti.pl> To: Paul Procacci <pprocacci@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Out of order posting (was:: Load 0.20 on a freshly installed idle system) Message-ID: <Y83npFPuiqj2KeB9@tau1.ceti.pl> In-Reply-To: <CAFbbPui=zc5-ERz06gr1nLFy_SWuOZ67ubvoKiT2kPSubHy7bw@mail.gmail.com> References: <CAGAKwcgFWukBrB_6SZVAoC4YKyPVhVMGED4aB6Z4E1fwZAO6mg@mail.gmail.com> <CAFbbPuhyJDewvE_a6MQpiGrpUew7EtxZKwt_=RHODNUyCYNduw@mail.gmail.com> <CAGAKwcghHH5t1_dtWPkOCwxPvDra%2BmgNFTQsG65i1_7pzTDkug@mail.gmail.com> <CAFbbPujMDQgo=zvSc5orcT=v3ftrVPXDjZE-D%2BUxt3%2BdOjFmUA@mail.gmail.com> <CAGAKwcid8j3C28wiypO87X9HT9Wq8cfTNHWnOQvcQgAcWrFuLw@mail.gmail.com> <CAGAKwcgZz8gujtd8gPBoC5nKxE00q1Pau6%2BiOUjxBR-UMMNpKw@mail.gmail.com> <1889CB4C-4B11-4178-8446-97DA9E5EC35A@nimnet.asn.au> <CAFbbPui=uPmKoKYo2t2KaXu=yWUT%2Ba4wksqnwvCjJpBsaALcpQ@mail.gmail.com> <20230122060127.GB8068@eureka.lemis.com> <CAFbbPui=zc5-ERz06gr1nLFy_SWuOZ67ubvoKiT2kPSubHy7bw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Those who could most probably already did it and know how it is going to end. I hope you have enough free time to match my answer with exact part of your message(s). I start to like top posting, seems like quite a fun. On Sun, Jan 22, 2023 at 01:36:27AM -0500, Paul Procacci wrote: > Thanks for your insight. Here's the fact of the matter. > Unless I'm using an email client where I can move a cursor to the position > needed to tip me off what kind of posting is required for said email (like > Mutt), then the steps necessary to conform to various `rules' on various > forms/lists/work emails/etc is simply too much work. > Also a fact: not once has anyone complained to me about top posting until > now. > Also a fact: I was asked not to bottom post elsewhere albeit quite a long > time ago. > I'm not an advocate of either method, just don't have the time to conform. > Not only do I use gmail as is evident by this email, but I use other email > clients as well. All their defaults are top posting oriented. > This is what led me to state to either ignore my messages or block me. I > certainly won't be offended and have better things to worry about other > than posting methodology on various lists. > > ~Paul > > > On Sun, Jan 22, 2023 at 1:01 AM Greg 'groggy' Lehey <grog@freebsd.org> > wrote: > > > [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 <smithi@nimnet.asn.au> wrote: > > >> > > >> PS Also bugging me is dreadful endless top-posting, tail-quoting > > Microsoft > > >> 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 > > “>” to the original message works best. Leaving white space after > > the “> ;” 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 > > > > > -- > __________________ > > :(){ :|:& };: -- Regards, Tomasz Rola -- ** A C programmer asked whether computer had Buddha's nature. ** ** As the answer, master did "rm -rif" on the programmer's home ** ** directory. And then the C programmer became enlightened... ** ** ** ** Tomasz Rola mailto:tomasz_rola@bigfoot.com **
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Y83npFPuiqj2KeB9>