- From: David Poehlman <poehlman1@comcast.net>
- Date: Sat, 28 Feb 2004 23:38:10 -0500
- To: "Derek Featherstone" <feather@wats.ca>, <w3c-wai-ig@w3.org>
Oh, I'm not upset and I am not aiming my comments at anyone either but the message below is a good example of something painfully difficult to go through. If you want to read it now and then come back to the next line, that will be fine. I'll conseed the point that I didn't read all the email when the net was young so top posting might not have been the norm. I too have a life <grin> and it takes a lot of time for me to go through posts and intersperce comments but I will often do this if the message is in a series of questions or points to respond to for one reason or another. So far, this thread seems to me to beliy that format but as with everything else, there are many ways of doing things. There are some ood points in your message below about digest mode and busy people coming into a thread somewhere in the middle and I grant that I have struggled with this issue quite a bit. Since though I cannot figure out a way to have my posts sent in formats that work for everyone, I take the simplest approach possible for me. I do a lot of posting and this saves time. Archiving is another matter. I usually use archives as a search engine so may not spend a lot of time reading messages but if I do read a thread, I begin from its beginning and when I see a lot of complex posting, it becomes quite difficult to follow. Where I see top posting, it is fairly simple for me to read the new information and skip the message that I have already read or read it if I have not and wish to after reading the top. The logic of reading from beginning to end comes from the book world where there is a page one through the end in increasing numbers. In conversation though, It's the newest information that is most needed in most instances but then we are also dealing with a plethora of ways to approach the situation that people take for which I respect every one. ----- Original Message ----- From: "Derek Featherstone" <feather@wats.ca> To: <w3c-wai-ig@w3.org> Sent: Saturday, February 28, 2004 11:14 PM Subject: RE: [WAI-IG] list policies (top posting for vision impairments) David Poehlman wrote: > Top posting is the most intelegent way to go but it must be done > intelegently. Derek's response (warning - this gets long): I don't see this as being the case at all -- to me it doesn't make sense to top post. This message isn't personally directed at you David, so please don't take offence to what I'm writing. I believe in *not* top-posting passionately, so I'm sure to get quite excited as I'm writing this. I could be wrong, but I'd hazard a guess that the main reason top posting occurs is use of email clients that don't allow you to fully configure your replies, or that just top post by default (i.e., Outlook). Outlook also includes all of the email message by default. Generally when people take the time to quote first, respond next, they also tend to trim their posts to only include relevant material from the previous message, keeping things nice and to the point. > I've studied a lot of different methods > of communicating, and I've seen a lot of them and when email was yong, > all we saw was top posting. Anything else is scrambled eggs no matter > how good you are at searching or scrolling. I'll be honest with you - when email was young, my recollection is that top posting was *never* the norm. Certainly not on email, and definitely not on Usenet. And that is part of the point really. Interspersing your comments with my responses to your comments helps to establish context for what I am saying. It allows me to respond to points one by one, providing a quoted reference and indicating that I am specifically responding to this point of your post. Interspersing your comments with my responses means that people don't *have* to scroll or search because the response is done in a logical order. By quoting you before my words, it is very clear to what I am responding. In addition, while you may know what you said, others may not. Again, its about context. > The advantages to top posting are that you will usually already know > what is in the previous message and if not, you can read the response > first or skip down to the original post. I have to disagree here as well. This thread is a case in point -- I saw your post, without reading previous posts. I couldn't establish coherence between posts because there was none. To what, precisely, were you responding? Your post included one message below it, but it could have been much worse. We also have to remember context and user preference. Some people may choose not to read messages in their email client. Many lists have digest mode where they receive one post a day. Not everyone will use things the same way we do -- this is a philosophy we are all familiar with on this list, right? (grin) We can't assume that people are always going to keep up with the posting and responses, so why not make it easier for all users that don't use the mailing lists in the same ways that we do? One of the powers of the Internet is that we have access to vast sources of information, and much of that is found in discussion lists such as this one. The discussion is important -- if it wasn't we wouldn't likely have web based archives of them. We use the web based archives as references in articles as we refer to discussions that shape our thinking, or that provide evidence to support or refute points. Saying that top posting is fine because "usually you already know what is in the previous message" only takes into account one scenario where you are actively following a conversation to know what specific authors have written. In my opinion, this neglects people in digest mode, people who are busy and haven't been able to keep up with the list, people that come up on our conversations through specific references and links to the web based archives, and doesn't take into account people that arrive in the web based archives from search engines. Some of the worst cases of this that I've seen are over on the Wrox forums. As an example, when searching for solutions to programming problems, I regularly come across messages in my search results that are top posted where the final post is along the lines of "Thanks Ian, that solved it for me..." with a string of countless top posted messages after it. Then I have to wade through the multiple nested originals that all include top posting to find one of Ian's specific posts, where he suggested a solution, and hope that I find the one that worked. If however, the last person had included a simple quote above his thank you message that said "Ian wrote: Make sure you check your configuration file is pointing at the correct path to the widget script.", then I or anyone else coming across that specific message would have a much clearer picture, and would know if the problem was the same, applied to their situation and if the answer was of any use at all. We need to make it easier for people to find information, and make that information more usable and easier for anyone to understand. > Interleaving stuff is sort of ok, but jumping through the hoops that > must be jumpped through in order to pick out the new bits after you > have already read the old bits can be tricky I'd suggest that if everyone top posted, we'd have more hoops to jump through to determine context. Again, we have to think beyond our own individual email clients here. Just like our web content, we don't know where our email messages will be used. They have a life beyond our email clients. > often, there is a lot of message with no comment that you have to wade > through and often, that is at the end of the message so a lot of time > gets waisted that way. Which is why trimming the message to leave just the important bits in is important. It shows that you've taken the care and the time to consider everyone that is potentially using your response message in any number of possible ways. Just like the work we do with accessibility, right? (grin) I've now just realized that this message has gone on far too long, so I'm about to head back to the top, and put in a warning to others at the top that this message is a long response. Why? So that they know that up front, and they can choose how they want to use the message -- they can read it now, read it later, or just trash it because they see its "another long-winded response from Derek". Provide as much context as possible to our readers (users) so they can make informed decisions about how to proceed based on their preferences and habits. Phew. I'm done now. BTW -- for those that are interested, there is a great tool for fixing quotes in Outlook at http://home.in.tum.de/~jain/software/outlook-quotefix/ Best regards, Derek. -- Derek Featherstone feather@wats.ca Web Accessibility Specialist / Co-founder of WATS.ca Web Accessibility Testing and Services http://www.wats.ca 1.866.932.4878 (North America)
Received on Saturday, 28 February 2004 23:38:12 UTC