X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f996b,aaba0d0b6dc1b0b5 X-Google-Attributes: gidf996b,public X-Google-ArrivalTime: 2003-06-02 04:29:04 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!fu-berlin.de!uni-berlin.de!h180n1fls34o1115.telia.COM!not-for-mail From: Veronica Karlsson Newsgroups: alt.ascii-art Subject: Re: ASCII Stuff Date: Mon, 02 Jun 2003 11:41:25 +0000 Lines: 61 Message-ID: <3EDB37E5.66D7292A@hotbrev.com> References: <1103_1053199699@news.kolumbus.fi> <3ec7046b$0$3540$626a54ce@news.free.fr> <1105_1053360226@news.kolumbus.fi> <3ED7994D.31F94B1F@hotbrev.com> <3ed7edaa$0$4585$626a54ce@news.free.fr> <3ED86D0F.545656B7@hotbrev.com> <3ed8b88a$0$11565$626a54ce@news.free.fr> NNTP-Posting-Host: h180n1fls34o1115.telia.com (213.67.71.180) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: fu-berlin.de 1054553341 9371720 213.67.71.180 (16 [58193]) X-Mailer: Mozilla 3.04 (X11; I; Linux 2.2.22-6.2.3 i586) Xref: archiver1.google.com alt.ascii-art:23414 BoD wrote: > Veronica Karlsson wrote: > > If article n+1 is a response to article n then it often does not make > > sense if the reader has not already read article n (or has not read it > > very recently). In email you can assume that the reader has done that. > > On usenet you cannot. > > That's why article n can be included (as a reference) in the end of the > message. Why? It certainly won't remove the need to scroll (because you still have to scroll past it to get to the next message). If it's already available in the group then it's completely redundant. If it's not then a short quote should be enough to not lose the context. Most of the time there is no need to quote the entire thing. > Of course, if you want to answer to a particular idea of the article, you > should quote it before your answer, and I think nobody disagrees with > that... But then it's not bottom-posting it would be middle-posting or > center-posting (?). Of course. (Who said anything about "bottom-posting"?) > But if you want to answer the whole article, I say you should either not > quote it at all, or quote it at the END so readers do not have to scroll > down to read it. This is where I disagree with you. If your response "carries its own context" (i.e. can be understood on its own) then, sure, go ahead, remove the quote. If it doesn't, then cut out everything except that little bit of it that you are responding to. If you are responding to more than one point, please do the "middle-posting" (normal) style. > Now of course this may or may NOT be what netiquette says. But hey, some > things have to evolve ;) And we must consider the new parameters (for > example useragents become more and more 'intelligent', They do? > bandwidth is less and less a problem, ...) Computer bandwidth maybe, but not "human bandwidth". Our eyes and brains and fingers still work the same way they did thousands of years ago. Example: these days many (most?) computers can show text that's more than 80 characters wide, but such text is not comfortable for the human eye to read. It still makes sense to keep your text under 80 columns, not because of how computer screens looked 20 years ago but because of how the human eye works. Also, when you put more "capacity" into a computer (or a freezer, or a cupboard, or a drawer, ...) you tend to fill it up. Keeping messages (or web pages or images) lean still helps. -- ##### c ^ OO /\\\\ ##### | /|\ `^^^^^^^%-- '||` | \\\\ ####-[.]\ / \ " " \ ha ha ha dd /[.]-\\\| ### _| |_ \\| ### (_ http://www.ludd.luth.se/~vk/cgi/asciichat/ _)} == \ / A S C I I A R T C H A T # ||\