Re: bottom / top posting

From: "Basques, Bob (CI-StPaul)" <bob(dot)basques(at)ci(dot)stpaul(dot)mn(dot)us>
To: 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-10 16:08:14
Message-ID: 0D2D5F24-3A69-45ED-A101-BBEBA08A27D3@ci.stpaul.mn.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

All,

First, I AM an old-timer, and prefer the top posting for a number of reasons. I’ve tried the Digest versions of lists in the past and they didn’t quite work out (for me).

Top post, newest on top, older stuff indented, can be clipped wherever, although I prefer to see everything if I need to, below. Why should I need to scroll down to see the newest stuff, especially in long threads. Top posting is very easy to understand what’s what, always see the latest stuff first, no scrolling to get going, if I want to see history, I scroll down, I prefer to see the whole thread at once, even the really long ones, for the context. I tend to search for old stuff in the archives through Nabble which works great (for me).

Alternatively, where I deem appropriate I will do inline posting/clipping, but I always announce that at the top (posting) of the response.

My tarnished two cents worth . . . :c)

Bobb

P.S. BTW, I intentionally don’t use a big SIG in my Email because of my list participation. I have no control over my companies addition of those “Think Before You Click . . .” placards either. Only alternative there is to not use my Company account, which seems wrong to me for some reason . . . I could probably figure out some way to address those placards automatically, but haven’t tried as of yet. I wonder if I could do it with a rule/scripting . . . .

From: Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com>
Date: Monday, June 7, 2021 at 7:06 AM
To: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: bottom / top posting

Think Before You Click: This email originated outside our organization.

I hear a lot of suggestions wrt bottom / top posting.

only when i read this,
PostgreSQL - general - Top posting.... | Threaded View (postgresql-archive.org)<https://www.postgresql-archive.org/Top-posting-tt5961037.html#none>

I got a feeling it sounded rude to the top post, despite me not even having an iota of intention to think that way. I was mostly used to tickets or chat.
but as with chats, using CAPS was not known to me as shouting for a long time, when someone pointed out to me this is what others feel when they read.

Will keep this in mind, for me as well as others who are not aware of the same.

--
Thanks,
Vijay
Mumbai, India

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2021-06-10 16:30:16 Re: Logical Replication: SELECT pg_catalog.set_config Statement appears to be hanging
Previous Message Hannes Kühtreiber 2021-06-10 16:06:15 Re: Logical Replication: SELECT pg_catalog.set_config Statement