Re: bottom / top posting

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Francisco Olarte <folarte(at)peoplecall(dot)com>
Cc: Sam Gendler <sgendler(at)ideasculptor(dot)com>, Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: bottom / top posting
Date: 2021-06-08 21:56:11
Message-ID: 20210608215611.GA26045@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jun 7, 2021 at 07:53:30PM +0200, Francisco Olarte wrote:
> message like yours in 5-10 seconds, properly scanning a top posted one
> takes much longer. So normally I stop reading at the quote and discard
> the message if I have not understood with what I have read UNLESS it's
> from my mother or I'm been paid to read it.
>
> I find top-posting moderately offensive, like saying "I am not going
> to waste time to make your reading experience better".

Yes, that is basically it, and if you are only communicating with one
other person, maybe that is reasonable. However, since our emails are
read by thousands, we have a responsibility to make them as clear as
possible, and that includes trimming and quoting relevant parts of
messages. However, as much as I try, I still regularly have typos in my
emails. :-(

And you are right in your earlier email in saying that "don't top-post"
or "bottom-post" is not clear enough in explaining how to properly
"trim-post", as you stated. Some people trim-post automatically, while
others have never thought about it since their communication is almost
always informal.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

If only the physical world exists, free will is an illusion.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ignacio Rey 2021-06-09 12:48:14 JDBC error: Unexpected packet type: 25
Previous Message Thomas Kellerer 2021-06-08 20:50:48 Re: index unique