On Tue, 24 Mar 2009 03:46:05 -0800, JoeU2004 wrote:

"NormanM" wrote:

Google Groups isn't a news reader.

Of course, it is. It provides a browser interface to its news servers.

The fact that Google provides a web (HTTP) server interface to their archive
of news articles does not make it a "news reader". Specifically, a news
reader is a local application running on your computer. If you are using a
web browser to access information, you are access an HTTP server, with an
HTTP reader.

It isn't even an NNTP service.

That's a fairly narrow, and incorrect, definition of a news reader.

NNTP is a protocol. HTTP is a protocol. Providing NNTP service means just
that: Running an NNTP server which is accessed via an NNTP client. Yes, very
narrow. However, anything wider than that is highly inaccurate.

A news reader is any application or service that provides access to one or
more news servers.

And which "news servers" are Google providing? A news server provides data
via the NNTP protocol; Google groups only provides HTTP access. That is a
"web server", not a "news server".

There is no requirement that NNTP be used between news
readers and servers.

If you are reading articles using an HTTP client, you are accessing an HTTP
server. That is web service, not news service.

Even the Wikipedia explanation offers this point of
view ...

And who made Wikipedia an authoritative source for anything?

... although I take exception to the Usenet limitation, to wit: "A
newsreader is an application program that reads articles on Usenet
(generally known as newsgroup), either directly from the news server's disks
or via the Network News Transfer Protocol (NNTP)."

Why do you take exception? That is very accurate.

An __open__ news server must support NNTP between it and generic news
readers like OE, simply because that is the current standard. But the
Google news servers are not open, AFAIK. (Aside: If anyone knows an open
URL for the Google news servers, please let me know.)

Google is a web archive of Usenet articles. Web, not news. You can only use
a web client (HTTP) because that is all that they offer.

Also, a __public__ news server (i.e. Usenet server) must support NNTP at the
backend in order to receive and distribute postings in public newsgroups.
(Arguably, the news server itself does not need to support NNTP at the
"backend", as long as some other network application does.)

A completely private news server is not required to use NNTP for
distribution. Generally, it is unlikely that it doesn't, since there is no
point in reinventing the wheel. But there are reasons not to use NNTP (e.g.
security; see SNNTP).

NNTP, HTTP, FTP, SMTP, IMAP, SMTP: All are Internet protocols. You need the
appropriate servers and clients for access. If you are using an HTTP client
(web browser) for access, you are using a "web service", not a "news
service". What is going on at the back end is irrelevant. It is how you are
accessing the service which is relevant.

HTTP!=NNTP.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum