on a different "manners" topic, was Re: Phishing...

Edward Lewis Ed.Lewis at neustar.biz
Wed Jan 3 14:33:20 UTC 2007


I'm not going to pick on the "it's" (grammatically correct, but it 
refers the email disclaimers which I don't feel like commenting on) 
but I want to say that I've come to appreciate top-posting.  With 
top-posts, there is no need to scroll down the list, and it is more 
like a conversation than injecting comments in-line.

Some say that top-posting reverses the conversation, but if you are 
thumbing through the archives of top-posted threads, each 
contribution is on the first screen and you can navigate message to 
message in time-order.  In my personal opinion, reading through 
archives of in-lined threads is much more of a problem - for one 
because threads take off in other directions and an in-line 
conversation never stands alone.  Usually with a few nested in-lines 
I loose "who said what" context too.

(As an exercise, try to prepare a reply in-line and then as a 
top-post.  You will see that in-line means less typing, as you don't 
have to "rephrase the question."  In-line is less work to render, but 
I think it is a poor communication style.)

As far as the HTML, I don't think I use it, but I fail to see why 
it's rude.  Sorry, it is newer technology and it does screw up old 
tools.  (I do get bit by it - the hotels seem to love HTML 
confirmations that I can't read on my work mailer.)  It's my/reader's 
choice to not use newer tools.

I do agree that full quoting is a pain - especially when the message 
is less than 1% new content.  Especially when all them new headers 
(DKIM keys and what not) fill up my screen first anyway. Yeah, I 
know, "upgrade."

There.  I've said it...oh, and the disclaimers don't give me 
heartburn.  I just ignore them.

At 8:03 -0500 1/3/07, Rich Kulawiec wrote:

>Because it's very rude -- like top-posting, or full-quoting, or sending
>email marked up with HTML.  Because it's an unprovoked threat.  Because

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                +1-571-434-5468
NeuStar

Dessert - aka Service Pack 1 for lunch.



More information about the NANOG mailing list
https://mailman.nanog.org/pipermail/nanog/2007-January/197962.html
mailman.nanog.org
crawl=CC-MAIN-2022-49
5073
application/http; msgtype=response
sha1:T5PG4X4BZZ2ISTF2RG63MSORFDVZU3SP
<urn:uuid:7335c2ad-ee6e-4e1d-aeea-954b713fb5f4>
2022-12-08T09:56:54Z
172.67.18.15
text/html
sha1:5QFHNV6YM6MZUJMH5WVHUZC4A5WKOVPK
<urn:uuid:ac0dd0be-2599-4bc3-9272-6e3a9706f7f2>
https://mailman.nanog.org/pipermail/nanog/2007-January/197962.html
response
<urn:uuid:12ab831d-a9fa-4c75-aff6-3bc9b753d3c4>
isPartOf: CC-MAIN-2022-49
publisher: Common Crawl
description: Wide crawl of the web for November/December 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-8
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/