• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Top-posting [ was Variable names]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Top-posting [ was Variable names]


  • Subject: Re: Top-posting [ was Variable names]
  • From: Joel Esler <email@hidden>
  • Date: Thu, 13 Jan 2011 19:33:35 -0500
  • Mail-followup-to: Joel Esler <email@hidden>, Nigel Garvey <email@hidden>, AppleScript Users <email@hidden>

On Thu, Jan 13, 2011 at 10:08:20PM +0000, Nigel Garvey wrote:
> Bruce Robertson top-posted on Thu, 13 Jan 2011 08:24:46 -0800:
>
> >And what exactly  is wrong with having immediate clarity about the new
> >message?
>
> It's only immediately clear to the person who sent the message.  :)
> Everyone else has to scroll down to see to what point, by which of the
> possibly many contributors to the thread so far, the new message refers.
> In a discussion forum, it's much clearer and more convenient for readers
> if the content of each message progresses in the normal reading order.
> That way, readers can be reminded of what's gone before and can read the
> new message in the context of what's been quoted. It also makes it
> easier for the new message to be quoted by others in the historical
> context. (With this post, I've had to insert what I'm writing now
> between your top-posting and the historical context — which is mixed up
> enough already!)
>
> As Robert and Yvan have already pointed out, top-posting also tends to
> foster the accumulation of unedited junk at the bottom of each message.
> (Your reply, for instance, quoted the entire Admin signature from the
> copy of my message you received.) Top-posters who receive individual
> messages from the server may not care about this, but to those of us who
> prefer to receive the digests, or who like to file discussions for their
> own reference, it's a real pain in the goodness-mes — almost as bad as
> when entire digests are quoted in replies.
>
> Top-posting's not the only thing which litters the digests. (They're
> also dotted with server messages that HTML or other attachments have
> been scrubbed — which leaves some postings with no content at all!) I
> only picked on top posting as a comment on Alex's overzealous views on
> clarity in scripts and his apparent disregard for it in his quoting on
> this list. (See below.) I've no wish to push the matter any further. I
> know from past experience it's a waste of time.  ;)


Top posting totally sucks.  I've ranted about this for years, and you
will find many of my emails Top Posted from hell.

I try to bottom post on lists, inline post where needed, and top post
for the rest.

(Totally going to post a link to my own blog right here:
http://blog.joelesler.net/2009/12/bottom-posting.html
)

Rant rant rant rant.

J
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users

This email sent to email@hidden

  • Follow-Ups:
    • Re: Top-posting [ was Variable names]
      • From: Ronald Hofmann <email@hidden>
References: 
 >Top-posting [ was Variable names] (From: "Nigel Garvey" <email@hidden>)

  • Prev by Date: Re: Top-posting [ was Variable names]
  • Next by Date: Re: Top-posting
  • Previous by thread: Re: Top-posting [ was Variable names]
  • Next by thread: Re: Top-posting [ was Variable names]
  • Index(es):
    • Date
    • Thread