From: Al Dunbar on 22 Mar 2010 22:09 "Trevor Lawrence" <Trevor L.(a)Canberra> wrote in message news:#7bdvsgyKHA.2644(a)TK2MSFTNGP04.phx.gbl... > "Evertjan." <exjxw.hannivoort(a)interxnl.net> wrote in message > news:Xns9D437A5745B09eejj99(a)194.109.133.242... >>I myself wrote on 22 mrt 2010 in microsoft.public.scripting.jscript: >>> Trevor Lawrence wrote on 22 mrt 2010 in >>> microsoft.public.scripting.jscript: >>>> Is there a time lag >>> >>> It is the nature of Usenet that there are wildly varying posting >>> time-lags, and even absence of arrival on or early removal from a >>> specific news-server. >>> >>>> that means that replies don't always get read ? >>> >>> A time-lag is not even needed for that, >>> the fact itself being a fact in fact: >>> >>> Replies don't always get read. >> >> Which should not be an excuse for replying >> that you did not read the above. >> >> ;-) >> > > > LOL > > Re your reply > Thanks I have often noticed posts being completely ignored and wondered > why Another LOL. How can you observe something that does not happen? You cannot observe posts being completely ignored, as the lack of a reply does not mean the non-repliers paid no attention. They might have thought about it, for example, and realized they had nothing worth contributing. There are many reasons for not replying (thank goodness, otherwise each post would have at least X number of replies where X is the number of people following the newsgroup). One of these is that the question is vague, hard to understand, or identical to the last twenty posts a person has answered. But even if some posts actually were being completely ignored, you will likely be unable to find out why, mainly because those not answering are the ones that know why, and they are not telling you. Think about it for a minute... Of course, if you knew why and knew it in advance, you would know not to post, or to post something that would be replied to. /Al
From: "Trevor Lawrence" Trevor on 22 Mar 2010 23:55 Touch� -- Trevor Lawrence Canberra Web Site http://trevorl.mvps.org "Al Dunbar" <alandrub(a)hotmail.com> wrote in message news:1BC9DD21-746A-4526-848A-2432E5052505(a)microsoft.com... > > > "Trevor Lawrence" <Trevor L.(a)Canberra> wrote in message > news:#7bdvsgyKHA.2644(a)TK2MSFTNGP04.phx.gbl... >> "Evertjan." <exjxw.hannivoort(a)interxnl.net> wrote in message >> news:Xns9D437A5745B09eejj99(a)194.109.133.242... >>>I myself wrote on 22 mrt 2010 in microsoft.public.scripting.jscript: >>>> Trevor Lawrence wrote on 22 mrt 2010 in >>>> microsoft.public.scripting.jscript: >>>>> Is there a time lag >>>> >>>> It is the nature of Usenet that there are wildly varying posting >>>> time-lags, and even absence of arrival on or early removal from a >>>> specific news-server. >>>> >>>>> that means that replies don't always get read ? >>>> >>>> A time-lag is not even needed for that, >>>> the fact itself being a fact in fact: >>>> >>>> Replies don't always get read. >>> >>> Which should not be an excuse for replying >>> that you did not read the above. >>> >>> ;-) >>> >> >> >> LOL >> >> Re your reply >> Thanks I have often noticed posts being completely ignored and wondered >> why > > Another LOL. How can you observe something that does not happen? You > cannot observe posts being completely ignored, as the lack of a reply does > not mean the non-repliers paid no attention. They might have thought about > it, for example, and realized they had nothing worth contributing. There > are many reasons for not replying (thank goodness, otherwise each post > would have at least X number of replies where X is the number of people > following the newsgroup). One of these is that the question is vague, hard > to understand, or identical to the last twenty posts a person has > answered. > > But even if some posts actually were being completely ignored, you will > likely be unable to find out why, mainly because those not answering are > the ones that know why, and they are not telling you. Think about it for a > minute... > > Of course, if you knew why and knew it in advance, you would know not to > post, or to post something that would be replied to. > > /Al > >
First
|
Prev
|
Pages: 1 2 3 Prev: Create a folder structure path Next: Split function... popular topic today! |