Steve Clark wrote: > On 05/16/2014 12:52 PM, Joseph.Spenner at netwolves.securence.com wrote: >>> From: Wes James <comptekki at icloud.com> >>> To: centos at centos.org >>> Sent: Friday, May 16, 2014 9:42 AM >>> Subject: [CentOS] Sorry >> >>> Sorry for the messed up replies. The web based icloud interface forces >>> the writer to reply at the top of the email >>> and if you try to write at the bottom by deleting a few lines of the >>> message or selecting the whole message, >>> deleting it, adding some spaces and then pasting back and go to the end >>> it and adding a reply, it kills the >>> indentation. >>> >> A lot of the "new improved" email web interfaces do this, including >> yahoo. I SO miss the more simple clients.. >> >> (Hold on while I manually put > in the thread above me, so people know >> where the reply starts.) >> > Could someone explain again why we are not suppose to top post? > > I have heard that is so when people come in late they can just read from > top to bottom and find out what is going on. The only problem I have with that argument is > most times people snip large parts of the thread so you don't have all the info anyway. And > If I pick up a thread late I don't have any problem with reading someone's reply on top > and then reading on to find out what the thread is about. Read my previous post on this. And add to it that a lot of us snip, so that we don't have 150 lines to reply to one sentence in the middle. However, we *DO* leave in the stuff that makes that response comprehensible. However, top posting has ZERO relationship to somewhere in those 200 lines of post, complete with many sigs, that you're responding to. How do I have a *clue*, without reading down, up up down, and on and on? This was a M$ "innovation", just like, oh, IE6.... mark