Sun Feb 04 23:48:42 2001
To: Yogi Bear
From: {cherish} <anon-20042@anon.twwells.com>
Subject: Usenet
Dear Yogi,
Could you write me a brief explanation about usenet?
What is it?
How does it work?
What's a post?
Whatever you want to add... sorta a compilation of all the computer questions you've answered at asdis over the years.
I would like such an article to put at cherish institute with credit being given to Yogi Bear who is known to have "all the answer" about the Net. *grin*
The name of the article would be
Usenet 101 (u101.html)
Useful Information about Usenet
Pleeeeeeeeeeease.
N Q,
cherish ppls (the committee to organize the institute) c.o.t.i.
p.s.
Other information in this group will be:
- FAQ link
- SYSK
- astri's how to use twwells
- Coney silences post
- Maybe a list of /or links to lists of jargon on the Net
like LOL and YMMV (I lean toward a new list because
links become outdated and also links can lead to stuff
that triggers)
edited to here
Mon, 5 Feb 2001 06:16:37
From: Yogi Bear
To: {cherish} <anon-20042@anon.twwells.com>
Subject: Re: Usenet
On Sun, 4 Feb 2001, {cherish} wrote:
> Dear Yogi,
>
> Could you write me a brief explanation about usenet?
I think this is a FAQ.
I'm pretty sure that I've seen an intro for beginners in the usenet FAQ
files.
> What is it?
Usenet is a distributed messaging system that lets users put in a
message at one point and have that message gradually flow over the
entire network of news servers (provided everything works!) at extremely
low cost. The advantage of low cost is balanced by the disadvantages
that not every message makes it to every news server and that because of
the topology of news servers, replies often get distributed before the
message that they reply to!
> How does it work?
The Net News Transport Protocol governs how usenet works so that people
can design programs for news servers and news clients that all can
'talk' with each other. I don't recall the RFC number that does this &
I don't know whether there have been additional RFCs that add to usenet.
The important question is "who makes it work?" and that's the newsadmins
or news administrators. Those are the people who determine what
newsgroups to carry/add/delete, and who determine for each newsgroup how
long to retain articles on their news server.
> What's a post?
uhoh ;)
> Whatever you want to add... sorta a compilation of all the computer
> questions you've answered at asdis over the years.
Things like the purists not regarding the alt.* hierarchy as part of
usenet? LOLOL
> I would like such an article to put at cherish institute with credit being
> given to Yogi Bear who is known to have "all the answer" about the Net.
> *grin*
aw
It also means that you could make it asd/asdis specific! And include
links to other important stuff (like a Jell-O room? that has a rack of
German socks for ppls to wear.)
Mon, 5 Feb 2001 12:56:57
From: Yogi Bear
To: {cherish} <anon-20042@anon.twwells.com>
Subject: Re: Usenet
>>I think this is a FAQ.
>
> Yes.
http://www.faqs.org/faqs/news-newusers-intro/
(a bit dense, but it conveys that usenet is *not a website, and that
it's extensive and chaotically organized ;)
> Can I use what you wrote in your message?
Yes. Please use what you think will meet the needs of your readers.
Mon, 5 Feb 2001 13:08:36
From: Yogi Bear
To: {cherish} <anon-20042@anon.twwells.com>
Subject: Re: Usenet -- have you asked RC?
On Mon, 5 Feb 2001, {cherish} wrote:
> At 06:16 am 2/5/01, you wrote:
>>On Sun, 4 Feb 2001, {cherish} wrote:
>>
>>
> Dear Yogi,
>>
>
>>
> Could you write me a brief explanation about usenet?
FWIW, I think Jill-RC understands this stuff pretty well since her husband
runs a news server on their host (as I understand it anyway.) She might
have some ideas about how to present the essentials in a way that will
help asd-ers make best use of newsgroups (and still protect themselves
against stuff like deja.com archiving etc.)
eg: It's not obvious on the surface that a simple post to a newsgroup can
result in spam coming for months!
Mon Feb 05 14:14:15 2001
To: Yogi Bear
From: {cherish} <anon-20042@anon.twwells.com>
Subject: Re: Usenet
At 12:56 pm 2/5/01 , you wrote:
>On Mon, 5 Feb 2001, {cherish} wrote:
>
>
> Can I use what you wrote in your message?
>
>Yes. Please use what you think will meet the needs of your readers.
Thank you, and I hope that you'll proof read the page when I'm done in case I've made aany errors.
I want a simple explanation. Short. Concise.
Mon Feb 05 14:17:05 2001
To: Yogi Bear
From: {cherish} <anon-20042@anon.twwells.com>
Subject: Re: Usenet -- have you asked RC?
Passing the buck, eh?
I'd like to get something online before I start asking for suggestions.
I do not want any [1] links on the page.
Just a meaningful, useful definition/explanation of Usenet.
[1] outside cherish institute
> Mon, 5 Feb 2001 19:13:50
From: Yogi Bear
To: {cherish} <anon-20042@anon.twwells.com>
Subject: Re: Usenet
On Mon, 5 Feb 2001, {cherish} wrote:
> At 12:56 pm 2/5/01 , you wrote:
>>On Mon, 5 Feb 2001, {cherish} wrote:
>>
>>
> Can I use what you wrote in your message?
>>
>>Yes. Please use what you think will meet the needs of your readers.
>
> Thank you, and I hope that you'll proof read the page when I'm done in case
> I've made aany errors.
>
> I want a simple explanation. Short. Concise.
Ah, I forgot to add to the explanation of newsgroups/usenet that now
there are sites that provide HTML access to messages and/or archive them
-- deja.com, newsguy.com, etc, to let people use browsers to read
newsgroups.
RFC (Request For Comment) 977 defined the original standard. I went to
http://www.faqs.org and searched RFCs -- results appended.
----------------8<-------------------------------
RFC Archive Search
Results for query "nntp"
-------
File name (modification date), and list of matched lines
_________________________________________________________________
1. rfc3023.html, ( Jan 13 2001)
* (e.g., 8BITMIME[RFC1652] ESMTP or NNTP[RFC0977]), UTF-8 does not
* clean transport (e.g., 8BITMIME[RFC1652] ESMTP or NNTP[RFC0977]),
* ESMTP or NNTP), or a binary clean transport (e.g., HTTP), no
* transport (e.g., 8BITMIME ESMTP or NNTP), the XML MIME entity MUST
be
* base64. For an 8-bit clean transport (e.g., 8BITMIME ESMTP or
NNTP),
* transport (e.g., 8BITMIME ESMTP or NNTP), the XML MIME entity MUST
be
_________________________________________________________________
2. rfc3017.html, ( Dec 7 2000)
* 6.2.2. NNTP Server Name .................................. 18
* 6.2.2. NNTP Server Name
* (FQDN) of the Network News Transfer Protocol (NNTP) server which
* <!-- Name of an NNTP server --
>
_________________________________________________________________
3. fyi/fyi35.html, ( Nov 14 2000)
* that itself contains an NNTP server, ensure that it is configured
so
* that it does not accept NNTP connections other than from your
* in NNTP servers. This can lead to denial of service, either from
the
* naive news forgeries, the "NNTP-Posting-Host:" header shows the
_________________________________________________________________
4. fyi/fyi32.html, ( Nov 14 2000)
* Network News Transfer Protocol (NNTP) designed to enhance Usenet
_________________________________________________________________
5. fyi/fyi31.html, ( Nov 14 2000)
* nntp: the Network News Transfer Protocol. NNTP specifies how
_________________________________________________________________
6. fyi/fyi25.html, ( Nov 14 2000)
* NNTP via NNTP gateway
* existing protocols (FTP, NNTP) or via HTTP and a gateway. In this
* NNTP
* understands Gopher, HTTP, WAIS, FTP, NNTP (USENET NEWS) and
_________________________________________________________________
7. fyi/fyi23.html, ( Nov 14 2000)
* a local news spool, or use the Network News Transfer Protocol
(NNTP)
* RFC 977 specifies NNTP, the Network News Transfer Protocol,
_________________________________________________________________
8. fyi/fyi18.html, ( Nov 14 2000)
* Network News Transfer Protocol (NNTP)
* NNTP
_________________________________________________________________
9. bcp/bcp17.html, ( Nov 14 2000)
* news Usenet News via NNTP [RFC-977]
_________________________________________________________________
10. rfc2980.html, ( Oct 18 2000)
* rfc2980 - Common NNTP Extensions
*
* Common NNTP Extensions
* Transfer Protocol (NNTP) protocol defined in RFC 977 are
documented
* for future implementers of the NNTP protocol. In the role, this
* RFC 977 [1] defines the NNTP protocol and was released over a
decade
* ago. Since then, NNTP has become one of the most popular protocols
* the growth in use of the protocol, work began on a revision to
NNTP
* their way into many implementations of NNTP. Additionally, many
* NNTP available in official NNTP server releases of some type as of
* of the IETF NNTP-EXT working group chaired by Ned Freed and Stan
* are NOT part of any current standard for NNTP. In fact, some of
the
* ones listed in this document should not be included in new NNTP
* implementations as they should no longer be used modern NNTP
* other. Transport extensions are additions to the NNTP
specification
* another server. Newsreader extensions are additions to the NNTP
* specification that were made to assist NNTP clients in selecting
and
* retrieving news articles from servers. Other extensions to the
NNTP
* ignored in the interpretation of commands by the NNTP server. Any
* like to suspend the lock step conversational nature of NNTP and
send
* ignored in the interpretation of commands by the NNTP server. Any
* NNTP newsreaders. There may be other extensions to the LIST
command
* This extension first appeared in ANU-NEWS, an NNTP implementation
for
* NNTP v2 revision called AUTHINFO SIMPLE and a more recent version
* This version of AUTHINFO was part of a proposed NNTP V2
* Note that the response codes used here were part of the proposed
NNTP
* the NNTP sockets (if appropriate for that authentication
protocol),
* The first NNTP working group discussed and proposed a syntax for
this
* Many NNTP implementations add headers to Usenet articles when then
Limit of 30 matched lines per file exceeded...
_________________________________________________________________
11. std/std01.html, ( Oct 6 2000)
* NNTP Network News Transfer Protocol 977
_________________________________________________________________
12. rfc2924.html, ( Sep 27 2000)
* Examples of fully-specified protocols are NTP [NTP], NNTP [NNTP],
* HTTP/1.1 [HTTP] is somewhat similar to NNTP in that it is designed
to
_________________________________________________________________
13. rfc2896.html, ( Sep 1 2000)
* nntp PROTOCOL-IDENTIFIER
_________________________________________________________________
14. rfc2700.html, ( Aug 31 2000)
* NNTP Network News Transfer Protocol 977
_________________________________________________________________
15. std/std1.html, ( Mar 18 2000)
* NNTP Network News Transfer Protocol 977
_________________________________________________________________
16. rfc2600.html, ( Mar 18 2000)
* NNTP Network News Transfer Protocol 977
_________________________________________________________________
17. rfc2782.html, ( Feb 24 2000)
* suboptimal) fallback hosts for Telnet, NNTP and other protocols
_________________________________________________________________
18. std/std2.html, ( Aug 2 1999)
* nntp 119/tcp Network News Transfer Protocol
* nntp 119/udp Network News Transfer Protocol
* NNTP 0001 (minimize monetary cost)
* NNTP - Network News Transfer Protocol
* NNTP - Network News Transfer Protocol
_________________________________________________________________
19. rfc999.html, ( Aug 2 1999)
* NNTP specifies a protocol for the distribution, inquiry,
retrieval, and
* news among the ARPA-Internet community. NNTP is designed so that
news
_________________________________________________________________
20. rfc991.html, ( Aug 2 1999)
* Network News Transfer Protocol ------------------------------
(NNTP)
* NNTP specifies a protocol for the distribution, inquiry,
* community. NNTP is designed so that news articles are stored
_________________________________________________________________
21. rfc990.html, ( Aug 2 1999)
* 119 NNTP Network News Transfer Protocol [66,PL4]
* NNTP - Network News Transfer Protocol
_________________________________________________________________
22. rfc977.html, ( Aug 2 1999)
* NNTP specifies a protocol for the distribution, inquiry,
retrieval,
* transmission of news among the ARPA-Internet community. NNTP is
* NNTP specifies a protocol for the distribution, inquiry,
retrieval,
* server-client model. NNTP is designed so that news articles need
only
* NNTP is modelled upon the news article specifications in RFC 850,
* which describes the USENET news system. However, NNTP makes few
* Typically, the NNTP server runs as a background process on one
host,
* This specification does not cover the operation of slave NNTP
* to NNTP server usage which would enhance operation on large local
* NNTP has commands which provide a straightforward method of
* find NNTP to be a more efficient way to distribute news than more
* Using NNTP, hosts exchanging news articles have an interactive
* contact one or more of its neighbors using NNTP. First it will
* 2. The NNTP Specification
* the NNTP server. These are not specific to any one command, but
may
* 200 or 201 is sent upon initial connection to the NNTP server
* NNTP server discontinues service (by operator request, for
example);
* the NNTP server and the responses which will be returned by those
* ignored in the interpretation of commands by the NNTP server. Any
* NNTP servers.
* software and not necessarily the NNTP server itself.
* of the posting permission granted to a client by the NNTP server.
* to indicate that it has finished all its transactions with the
NNTP
* NNTP servers which do not give priority to slave servers, this
* S: 201 Foobar NNTP server ready (no posting)
* S: 205 Foobar NNTP server bids you farewell.
* the NNTP server.
_________________________________________________________________
23. rfc2635.html, ( Aug 2 1999)
* that itself contains an NNTP server, ensure that it is configured
so
* that it does not accept NNTP connections other than from your
* in NNTP servers. This can lead to denial of service, either from
the
* naive news forgeries, the "NNTP-Posting-Host:" header shows the
_________________________________________________________________
24. rfc2626.html, ( Aug 2 1999)
* There does exist a problem in both NNTP, RFC 977, and the Usenet
News
* Network News Protocol (NNTP).
* There does exist a problem in both NNTP, RFC 977, and the Usenet
News
* The NNTP transfer protocols defined in RFC 977. Sections 3.7.1,
the
_________________________________________________________________
25. rfc2616.html, ( Aug 2 1999)
* those supported by the SMTP [16], NNTP [13], FTP [18], Gopher [2],
* messages via proxies/gateways to SMTP or NNTP.
_________________________________________________________________
26. rfc2595.html, ( Aug 2 1999)
* forgery when transmitted through SMTP or NNTP. TLS is no
substitute
_________________________________________________________________
27. rfc2594.html, ( Aug 2 1999)
* protocols, like NNTP [25] or WebNFS [26,27] might be defined in
the
_________________________________________________________________
28. rfc2577.html, ( Aug 2 1999)
* commands relevant to the service being attacked (SMTP, NNTP,
etc.).
_________________________________________________________________
29. rfc2500.html, ( Aug 2 1999)
* NNTP Network News Transfer Protocol 977
_________________________________________________________________
30. rfc2400.html, ( Aug 2 1999)
* NNTP Network News Transfer Protocol Elective 977
_________________________________________________________________
31. rfc2376.html, ( Aug 2 1999)
* 8BITMIME, or NNTP), UTF-8 is not encoded, but UTF-16 is base64
* 8BITMIME, or NNTP), UTF-8 is not encoded, but UTF-16 is base64
* For an 8-bit clean transport (e.g., ESMTP, 8BITMIME, or NNTP), or
a
* transport (e.g., ESMTP, 8BITMIME, or NNTP), the XML entity must be
_________________________________________________________________
32. rfc2300.html, ( Aug 2 1999)
* NNTP Network News Transfer Protocol Elective 977
_________________________________________________________________
33. rfc2235.html, ( Aug 2 1999)
* Network News Transfer Protocol (NNTP) designed to enhance Usenet
_________________________________________________________________
34. rfc2219.html, ( Aug 2 1999)
* news Usenet News via NNTP [RFC-977]
_________________________________________________________________
35. rfc2200.html, ( Aug 2 1999)
* NNTP Network News Transfer Protocol Elective 977
_________________________________________________________________
36. rfc2150.html, ( Aug 2 1999)
* nntp: the Network News Transfer Protocol. NNTP specifies how
_________________________________________________________________
37. rfc2142.html, ( Aug 2 1999)
* NNTP (see [RFC977]), and > for HTTP (see [HTTP]).
* example, if an NNTP server's host name is DATA.RAMONA.VIX.COM yet
it
* does not support the associated service. So, for example, if an
NNTP
* do not, themselves, serve the NNTP protocol.
* USENET NNTP [RFC977]
* NEWS NNTP Synonym for USENET
_________________________________________________________________
38. rfc2132.html, ( Aug 2 1999)
* 8.16. Network News Transport Protocol (NNTP) Server Option
* The NNTP server option specifies a list of NNTP available to the
* The code for the NNTP server option is 71. The minimum length for
_________________________________________________________________
39. rfc2130.html, ( Aug 2 1999)
* NNTP
* See 8.2. No strong tradition for negotiation of encoding in NNTP
* Email. One difference is that nearly all NNTP channels are 8-
* bit clean; some NNTP newsgroups have a tradition of using 8-bit
* NNTP Net News Transfer Protocol
_________________________________________________________________
40. rfc2129.html, ( Aug 2 1999)
* ftp and nntp. Future implementation will include other triggers
_________________________________________________________________
41. rfc2098.html, ( Aug 2 1999)
* ftp, nntp, http, etc.
_________________________________________________________________
42. rfc2076.html, ( Aug 2 1999)
* This means that attributes from SMTP [1], UUCP [18] and NNTP [15]
are
_________________________________________________________________
43. rfc2068.html, ( Aug 2 1999)
* those supported by the SMTP [16], NNTP [13], FTP [18], Gopher [2],
* messages via proxies/gateways to SMTP or NNTP.
_________________________________________________________________
44. rfc2052.html, ( Aug 2 1999)
* suboptimal) fallback hosts for Telnet, NNTP and other protocols
* ; NNTP - use the IP providers's NNTP server
* nntp.tcp SRV 0 0 119 nntphost.ip-provider.net.
_________________________________________________________________
45. rfc2039.html, ( Aug 2 1999)
* WWW proxies, NNTP, GOPHER, FTP and WAIS. The focus of this
document
* considerable overlap with other types of servers like (FTP, NNTP,
* NNTP, GOPHER and WAIS) as well as client and proxy management.
* services (like NNTP, FTP, GOPHER and WAIS).
* NNTP) as well.
_________________________________________________________________
46. rfc2010.html, ( Aug 2 1999)
* name server host (e.g., SMTP, NNTP, FTP, et al). If login is
_________________________________________________________________
47. rfc2000.html, ( Aug 2 1999)
* NNTP Network News Transfer Protocol Elective 977
_________________________________________________________________
48. rfc1983.html, ( Aug 2 1999)
* Network News Transfer Protocol (NNTP)
* NNTP
_________________________________________________________________
49. rfc1945.html, ( Aug 2 1999)
* SMTP [12], NNTP [11], FTP [14], Gopher [1], and WAIS [8], allowing
* messages via proxies/gateways to SMTP or NNTP.
_________________________________________________________________
50. rfc1920.html, ( Aug 2 1999)
* NNTP Network News Transfer Protocol Elective 977
_________________________________________________________________
... Limit of 50 files exceeded ...
-------
Results Summary for query "nntp":
at least 166 matches in at least 50 files
(Some matches may be to HTML tags which may not be shown.)
Your search allowed NO spelling errors, with up to 30 matches per
RFC and was limited to only the first 50 RFCs encountered.
The search did not care about 'case'. Meta character intrepretation
was enabled in your search string and only whole words were
searched.
-------
Back To RFCs - Usenet References - Usenet FAQs - HTML RFC Search
Engine
© Copyright The Internet FAQ Consortium, 1996
All rights reserved
> Mon, 5 Feb 2001 19:19:23
From: Yogi Bear
To: {cherish} <anon-20042@anon.twwells.com>
Subject: Re: Usenet -- have you asked RC?
On Mon, 5 Feb 2001, {cherish} wrote:
> Passing the buck, eh?
Just that once you get something that fits your needs, you might pass it
by RC for both DID and tekkie viewpoints.
> I'd like to get something online before I start asking for suggestions.
>
> I do not want any [1] links on the page.
Ah. That's a useful constraint to know. *sigh*
A comment about things that people can plug into search engines that
will turn up further references might be useful then.
> Just a meaningful, useful definition/explanation of Usenet.
Usenet is great! What more do they gotta know????
Where else can you find Jell-O parties and hospital watches taken with
the seriousness they deserve!
>
> [1] outside cherish institute
>
> Tue, 6 Feb 2001 08:09:02
From: Yogi Bear
To: {cherish} <anon-20042@anon.twwells.com>
Subject: usenet --
> FAQ files!
It was usenet communities of interest who started the construction and
maintenance of FAQ files (Frequently Asked Questions with
commonly-accepted Answers) when the 'regulars' to the newsgroups got
tired of answering the same questions over and over! Because it was
individual members of the groups who volunteered for the tasks, the FAQs
are a wonderful mix that somewhat depends on the dedication and
interests of the various communities. Most are posted periodically to
the newsgroups which evolved them.
>
Tue Feb 06 13:03:08 2001
To: Yogi Bear
From: {cherish} <anon-20042@anon.twwells.com>
Subject: Re: Usenet ?
At 07:13 pm 2/5/01 , you wrote:
>On Mon, 5 Feb 2001, {cherish} wrote:
>
> I want a simple explanation. Short. Concise.
Uh... *eyes darting from side to side*
Maybe I should say, "In a nutshell . . ."
What's nntp?
>Ah, I forgot to add to the explanation of newsgroups/usenet that now
>there are sites that provide HTML access to messages and/or archive them
>-- deja.com, newsguy.com, etc, to let people use browsers to read
>newsgroups.
>
>RFC (Request For Comment) 977 defined the original standard. I went to
>http://www.faqs.org and searched RFCs -- results appended.
>----------------8<-------------------------------
>
> RFC Archive Search
>
> Results for query "nntp"
Tue Feb 06 13:07:55 2001
To: Yogi Bear
From: {cherish}
Subject: Re: Usenet -- things to plug into
At 07:19 pm 2/5/01 , you wrote:
>On Mon, 5 Feb 2001, {cherish} wrote:
>
> I do not want any [1] links on the page.
>
>Ah. That's a useful constraint to know. *sigh*
>
>A comment about things that people can plug into search engines that
>will turn up further references might be useful then.
Like what things?
What things can people plug into search engines that wil turn up further references that might be useful?
>
> Just a meaningful, useful definition/explanation of Usenet.
>
>Usenet is great! What more do they gotta know????
Uh... what is it?
|
c h e r i s h
