|Dave Fawthrop wrote: | |> On Sat, 18 Mar 2006 01:58:29 +1300, Nick wrote: |> |> |Guy King wrote: |> | |> |> The message |> |> from snipped-for-privacy@gmail.com contains these words: |> |> |> |> |> |>>Ask them if it's standard or if it's just particular to your place |> |>>because it's in a poor state. |> |> |> |> |> |> You're at it again - starting a new thread to answer a question instead |> |> of doing it under the one you're replying to. |> |> |> |> Are you aware you're doing it? |> |> |> |> If so, why do you do it? |> |> |> |> If not, then "You're starting a new thread to answer each question". |> |> Please stop it! |> | |> |Can you explain what you are talking about? |> |daddyfreddy's post contains nige's name and text, and nige's |> |original message ID. |> |> You are posting to usenet which has a very useful method of keeping track |> of who is replying to which post, called threading. This is automatically |> kept track of by the header line: |> References: |> |> |> |> This *essential* when threads get to hundreds of posts, dozens of layers |> deep.
|If you actually had a look at the headers, you will see that |daddyfreddy's post contained that reference line perfectly. |Please go and look now. | |> I note that you are using Mozilla/5.0 |> User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007 |> Perhaps someone using Mozilla could explain which wrong button you are |> hitting. | |As I have already explained in this thread, the problem is |occurring because Google removes superfluous blanks from the |subject line, and some deficient newsreaders interpret that as a |change of thread. |I hope you will all have the decency to apologise to daddyfreddy.
Your explanation came after my post :-( The usenet propagation system is and always was cr*p.