wrote in message
...
I didn't *say* my problem was related to Google's...just that whatever
the problem *is* accessing Usenet in this past week or so, it isn't
"surely 100% Google's problem" or the rest of us wouldn't be
experiencing the same thing using other methods of accessing Usenet.

I don't see how you can avoid claiming that your problem is unrelated to
Google's, while at the same time claim that all concurrent problems related
to "accessing Usenet" must be related.

I've already explained that you, I, and every other end-user will *never*
see a general Usenet problem show up as a client-side error. A client-side
error is *always* going to be strictly between the user and their news
provider. As such, when people with different providers are having problems
at the same time, those problems are necessarily unrelated. It can be no
other way.

Your refusal to accept that it is just coincidence may make you feel better,
but it has absolutely zero basis in reality. There is no single "whatever
THE problem *is* accessing Usenet" that is affecting both you and people
going through Google.

Whatever errors Newswatcher is reporting to you, they are entirely
irrelevant to whatever errors someone using Google may have reported to
them. There is no single general problem affecting both you and Google
users.

(And frankly, I've never heard of a general "Usenet problem"...the very
design of Usenet means that problems are generally localized to individual
news providers, such as Cox or Google, and do not spread or are otherwise
shared by those providers).

Pete