| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 27 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 40:23:58 |
| Calls: | 631 |
| Calls today: | 2 |
| Files: | 1,187 |
| D/L today: |
24 files (29,813K bytes) |
| Messages: | 174,391 |
Index of /usenet/CONFIG(45186 lines / 2172252 bytes / 2.17 megabytes) . . . >https://downloads.isc.org/usenet/CONFIG/active
[ICO] Name Last modified Size Description
[ ] Parent Directory -
[TXT] HIERARCHY-NOTES 2010-01-18 03:50 27K
[DIR] LOGS/ 2025-10-01 01:00 -
[TXT] README 2019-01-07 02:58 14K
[ ] active 2025-10-08 20:00 2.0M >https://downloads.isc.org/usenet/CONFIG/active
[ ] active.bz2 2025-10-08 20:00 263K
[ ] active.gz 2025-10-08 20:00 292K
[TXT] control.ctl 2023-08-05 15:57 104K
[ ] newsgroups 2025-10-08 20:00 2.3M
[ ] newsgroups.bz2 2025-10-08 20:00 620K
[ ] newsgroups.gz 2025-10-08 20:00 685K
...
aaa.inu-chan 0000000000 0000000001 m<snipped 45184 lines>
...
...[end quoted plain text]
zippo.spamhippo.top100 0000000000 0000000001 m
Index of /usenet/CONFIG(45186 lines / 2172252 bytes / 2.17 megabytes) . . . >https://downloads.isc.org/usenet/CONFIG/active
[ICO] Name Last modified Size Description
[ ] Parent Directory -
[TXT] HIERARCHY-NOTES 2010-01-18 03:50 27K
[DIR] LOGS/ 2025-10-01 01:00 -
[TXT] README 2019-01-07 02:58 14K
[ ] active 2025-10-08 20:00 2.0M >https://downloads.isc.org/usenet/CONFIG/active
[ ] active.bz2 2025-10-08 20:00 263K
[ ] active.gz 2025-10-08 20:00 292K
[TXT] control.ctl 2023-08-05 15:57 104K
[ ] newsgroups 2025-10-08 20:00 2.3M
[ ] newsgroups.bz2 2025-10-08 20:00 620K
[ ] newsgroups.gz 2025-10-08 20:00 685K
...
aaa.inu-chan 0000000000 0000000001 m<snipped 45184 lines>
...
...[end quoted plain text]
zippo.spamhippo.top100 0000000000 0000000001 m
browse any currently or previously active newsgroup in usenet archives
using any newsreader (40tude dialog, t-bird, etc,) and search overview (xover) headers, e.g., nntp <lux-feed1.newsdeef.eu:119 usenet archive>,
but for complete search of body text content, non-overview headers etc. requires downloading articles individually or in filtered groups, such
as by thread, date or other xover search criteria, it definitely works
but is not for "one-click" researchers accustomed to dead googlegroups
websites with current usenet access do not search articles for content,
but for newsgroup browsing, message id searches, they're helpful, e.g.:
https://pugleaf.net/
https://newsgrouper.org/
https://al.howardknight.net/
some of these web-to-usenet sites could eventually expand their search features to include full content searches, not yet, it's a possibility
there are about ~36,800 currently active unmoderated plain text groups,
with a total of ~45,186 active newsgroups (39369 y / 5811 m / 6 n) ...
(using Tor Browser 14.5.8)
https://downloads.isc.org/usenet/CONFIG/
Index of /usenet/CONFIG [ICO] Name Last modified Size Description [(45186 lines / 2172252 bytes / 2.17 megabytes) . . .
] Parent Directory -
[TXT] HIERARCHY-NOTES 2010-01-18 03:50 27K [DIR] LOGS/ >>2025-10-01 01:00 - [TXT] README 2019-01-07 02:58 14K [ ] >>active 2025-10-08 20:00 2.0M >>https://downloads.isc.org/usenet/CONFIG/active [ ] active.bz2 >>2025-10-08 20:00 263K [ ] active.gz 2025-10-08 20:00 292K
[TXT] control.ctl 2023-08-05 15:57 104K [ ] newsgroups >>2025-10-08 20:00 2.3M [ ] newsgroups.bz2 2025-10-08 20:00 620K [ ]
newsgroups.gz 2025-10-08 20:00 685K ...
https://downloads.isc.org/usenet/CONFIG/active aaa.inu-chan 0000000000 >>0000000001 m ...<snipped 45184 lines>
...[end quoted plain text]
zippo.spamhippo.top100 0000000000 0000000001 m
*.*
39369 y
5811 m
6 n
_______ 45186 total
alt.binaries.*
2569 y
50 m
_______
2619 b
recommend: newsdeef, blueworld, csiph, paganini, netfront, etc.
for reliable servers with longer and complete article retention
On Thu, 9 Oct 2025 06:33:26 +0200, D wrote:
browse any currently or previously active newsgroup in usenet archives
using any newsreader (40tude dialog, t-bird, etc,) and search overview
(xover) headers, e.g., nntp <lux-feed1.newsdeef.eu:119 usenet archive>,
but for complete search of body text content, non-overview headers etc.
requires downloading articles individually or in filtered groups, such
as by thread, date or other xover search criteria, it definitely works
but is not for "one-click" researchers accustomed to dead googlegroups
websites with current usenet access do not search articles for content,
but for newsgroup browsing, message id searches, they're helpful, e.g.:
https://pugleaf.net/
https://newsgrouper.org/
https://al.howardknight.net/
some of these web-to-usenet sites could eventually expand their search
features to include full content searches, not yet, it's a possibility
there are about ~36,800 currently active unmoderated plain text groups,
with a total of ~45,186 active newsgroups (39369 y / 5811 m / 6 n) ...
(using Tor Browser 14.5.8)
https://downloads.isc.org/usenet/CONFIG/
Index of /usenet/CONFIG [ICO] Name Last modified Size Description [(45186 lines / 2172252 bytes / 2.17 megabytes) . . . >>>https://downloads.isc.org/usenet/CONFIG/active aaa.inu-chan 0000000000 >>>0000000001 m ...
] Parent Directory -
[TXT] HIERARCHY-NOTES 2010-01-18 03:50 27K [DIR] LOGS/
2025-10-01 01:00 - [TXT] README 2019-01-07 02:58 14K [ ] >>>active 2025-10-08 20:00 2.0M >>>https://downloads.isc.org/usenet/CONFIG/active [ ] active.bz2 >>>2025-10-08 20:00 263K [ ] active.gz 2025-10-08 20:00 292K >>>[TXT] control.ctl 2023-08-05 15:57 104K [ ] newsgroups >>>2025-10-08 20:00 2.3M [ ] newsgroups.bz2 2025-10-08 20:00 620K [ ]
newsgroups.gz 2025-10-08 20:00 685K ...
<snipped 45184 lines>
...[end quoted plain text]
zippo.spamhippo.top100 0000000000 0000000001 m
*.*
39369 y
5811 m
6 n
_______ 45186 total
alt.binaries.*
2569 y
50 m
_______
2619 b
recommend: newsdeef, blueworld, csiph, paganini, netfront, etc.
for reliable servers with longer and complete article retention
These numbers are incorrect and way too low. It varys with server and >backbone. My newsreader has 111275 text and binary groups on a server on
one backbone and 138712 a different server on another backbone. Not all
of these groups are currently active but they all contain articles. Of
the active groups, some are more active than others but this is the total >number of groups on two different servers. In general, text retention
goes back to 2003 on most servers and binary retention can go to 2008 if >you're willing to pay a premium for long retetention.
...[end quoted excerpt]
(read only) lux-feed1.newsdeef.eu :119 :563
* Text retention: 198x - 2025
+ TOR1: pp55dzqem2eufe2wst2u7lunqhs3pkryzrleikrixl2xuvblyeqyg4qd.onion:119
+ TOR2: 3nxvtk6l6fvjel6egccgo5zcerivvvz27ahsdjthvxc7focidpr2xlyd.onion:119
+ username: usenet
+ password: archive
+ Update: 2025-09-03 :: Rate Limits applied.
+ Do not open more than 3 connections.
(read only) 81-171-22-215.pugleaf.net :119 :563
* Text retention: 198x - 2025
+ username: usenet
+ password: archive
. . . 1371 headers in alt.fan.usenet from lux-feed1.newsdeef.eu (0-1370)the oldest article: <35244fde.88725954@news.loop.com> is dated 1998-04-03
On 10 Oct 2025 22:23:21 GMT, Alterego <al@alt.org> wrote:
On Thu, 9 Oct 2025 06:33:26 +0200, D wrote:[end quoted excerpt]
.....
(read only) lux-feed1.newsdeef.eu :119 :563
* Text retention: 198x - 2025
+ TOR1: pp55dzqem2eufe2wst2u7lunqhs3pkryzrleikrixl2xuvblyeqyg4qd.onion:119
+ TOR2: 3nxvtk6l6fvjel6egccgo5zcerivvvz27ahsdjthvxc7focidpr2xlyd.onion:119
+ username: usenet
+ password: archive
+ Update: 2025-09-03 :: Rate Limits applied.
+ Do not open more than 3 connections.
(read only) 81-171-22-215.pugleaf.net :119 :563
* Text retention: 198x - 2025
+ username: usenet
+ password: archive
e.g., i just sampled this newsgroup news:alt.fan.usenet (w/40tude dialog)
. . . 1371 headers in alt.fan.usenet from lux-feed1.newsdeef.eu (0-1370)the oldest article: <35244fde.88725954@news.loop.com> is dated 1998-04-03
other servers with complete and long retention, nntp.csiph.com (~9 years), paganini.bofh.team (~5 years), freenews.netfront.net (~4 years) . . . and
for shorter retention servers there are dozens, including some with onion addresses that work with tor on port 563, but most of these are read-only
On 10/11/25 00:12, D wrote:
On 10 Oct 2025 22:23:21 GMT, Alterego <al@alt.org> wrote:
On Thu, 9 Oct 2025 06:33:26 +0200, D wrote:[end quoted excerpt]
.....
(read only) lux-feed1.newsdeef.eu :119 :563
* Text retention: 198x - 2025
+ TOR1: pp55dzqem2eufe2wst2u7lunqhs3pkryzrleikrixl2xuvblyeqyg4qd.onion:119
+ TOR2: 3nxvtk6l6fvjel6egccgo5zcerivvvz27ahsdjthvxc7focidpr2xlyd.onion:119
+ username: usenet
+ password: archive
+ Update: 2025-09-03 :: Rate Limits applied.
+ Do not open more than 3 connections.
(read only) 81-171-22-215.pugleaf.net :119 :563
* Text retention: 198x - 2025
+ username: usenet
+ password: archive
e.g., i just sampled this newsgroup news:alt.fan.usenet (w/40tude dialog) >>> . . . 1371 headers in alt.fan.usenet from lux-feed1.newsdeef.eu (0-1370)
the oldest article: <35244fde.88725954@news.loop.com> is dated 1998-04-03
other servers with complete and long retention, nntp.csiph.com (~9 years), >> paganini.bofh.team (~5 years), freenews.netfront.net (~4 years) . . . and
for shorter retention servers there are dozens, including some with onion
addresses that work with tor on port 563, but most of these are read-only
1981
net.bugs.2bsd >https://rocksolid-us.pugleaf.net/groups/net.bugs.2bsd/threads?page=5
1983
net.crypt
https://rocksolid-us.pugleaf.net/groups/net.crypt/threads?page=7
...snip
"holes" in directories
By: pur-eebruner on Fri, 11 Dec 1981 21:19 43 Years 10 Months ago >https://rocksolid-us.pugleaf.net/groups/net.bugs.2bsd/thread/1
"holes" in directories
#1
Author: pur-eebruner
Date: Fri, 11 Dec 1981 21:19
55 lines
2279 bytes
We discovered a particularly nasty problem with the way that UNIX
handles directories when cleaning up a bad system crash. A "hole"
(region where no blocks are allocated) was created in /usr/tmp.
"fsck" reported no unusual errors, but when we attempted to touch
the inside of this directory (e.g. with "ls") we had all sorts of
errors from our disc driver.
--John Bruner[end quoted excerpt]
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads. >...
...[end quoted excerpt]
Digram statistics question
By: psuvaxsibley on Fri, 13 May 1983 21:49 42 Years 5 Months ago
The Early History of Usenet, Part II: The Technological Setting[end quoted plain text]
14 November 2019
Usenet--Netnews--was conceived almost exactly 40 years ago this month.
To understand where it came from and why certain decisions were made
the way they were, it's important to understand the technological
constraints of the time.
Metanote: this is a personal history as I remember it. None of us were
taking notes at the time; it's entirely possible that errors have crept
in, especially since my brain cells do not even have parity checking,
let alone ECC. Please send any corrections.
In 1979, mainframes still walked the earth. In fact, they were the
dominant form of computing. The IBM PC was about two years in the
future; the microcomputers of the time, as they were known, had too
little capability for more or less anything serious. For some purposes, >especially in research labs and process control systems, so-called >minicomputers--which were small, only the size of one or two full-size >refrigerators--were used. So-called "super-minis", which had the raw
CPU power of a mainframe though not the I/O bandwidth, were starting
to become available.
At the time, Unix ran on a popular line of minicomputers, the Digital >Equipment Corporation (DEC) PDP-11. The PDP-11 had a 16-bit address
space (though with the right OS, you could quasi-double that by using
one 16-bit address space for instructions and a separate one for data); >depending on the model, memory was limited to the 10s of kilobytes
(yes, kilobytes) to a very few megabytes. No one program could access
more than 64K at a time, but the extra physical memory meant that a
context switch could often be done without swapping, since other
processes might still be memory-resident. (Note well: I said "swapping",
not "paging"; the Unix of the time did not implement paging. There was
too little memory per process to make it worthwhile; it was easier to
just write the whole thing out to disk...)
For most people, networking was non-existent. The ARPANET existed (and
I had used it by then), but to be on it you had be a defense contractor
or a university with a research contract from DARPA. IBM had assorted
forms of networking based on leased synchronous communications lines
(plus some older mechanisms for dial-up batch remote job entry), and
there was at least one public packet-switched network, but very, very
few places had connections to it. The only thing that was halfway
common was the dial-up modem, which ran at 300 bps. The Bell 212A full- >duplex, dial-up modem had just been introduced but it was rare. Why?
Because you more or less had to lease it from the phone company: Ma
Bell, more formally known as AT&T. It was technically legal to buy your
own modems, but to hardwire them to the phone network required going
through a leased adapter known as a DAA (data access arrangement) to
"protect the phone network". (Explaining that would take a far deeper
dive into telephony regulation than I have the energy for tonight.)
Usenet originated in a slightly different regulatory environment,
though: Duke University was served by Duke Telecom, a university entity
(and Durham was GTE territory), while UNC Chapel Hill, where I was a
student, was served by Chapel Hill Telephone-the university owned the
phone, power, water, and sewer systems, though around this time the
state legislature ordered that the utilities be divested.
There was one more piece to the puzzle: the computing environments at
UNC and Duke computer science. Duke had a PDP-11/70, then the high-end
model, running Unix. We had a PDP-11/45 intended as a dedicated machine
for molecular graphics modeling; it ran DOS, a minor DEC operating
system. It had a few extra terminal ports, but these didn't even have
modem control lines, i.e., the ports couldn't tell if the line had
dropped. We hooked these to the university computer center's Gandalf
port selector. With assistance from Duke, I and a few others brought up
6th Edition Unix on our PDP-11, as a part-time OS. Some of the faculty
were interested enough that they scrounged enough money to buy a better >8-port terminal adapter and some more RAM (which might have been core >storage, though around that time semiconductor RAM was starting to
become affordable). We got a pair of VAX-11/780s soon afterwards, but
Usenet originated on this small, slow 11/45.
The immediate impetus for Usenet was the desire to upgrade to 7th
Edition Unix. On 6th Edition Unix, Duke had used a modification they
got from elsewhere to provide an announcement facility to send messages
to users when they logged in. It wasn't desirable to always send such >messages; at 300 bps--30 characters a second--a five-line message took >annoying long to print (and yes, I do mean "print" and not "display"; >hardcopy terminals were still very, very common). This modification was
not even vaguely compatible with the login command on 7th Edition; a >completely new implementation was necessary. And 7th Edition had uucp >(Unix-to-Unix Copy), a dial-up networking facility. This set the stage
for Usenet.
To be continued...
...
https://www.cs.columbia.edu/~smb/blog/2019-11/2019-11-14.html
The Early History of Usenet, Part I: Prologue >https://www.cs.columbia.edu/~smb/blog/2019-11/2019-11-14a.html
The Early History of Usenet, Part II: The Technological Setting >https://www.cs.columbia.edu/~smb/blog/2019-11/2019-11-15.html
The Early History of Usenet, Part III: Hardware and Economics >https://www.cs.columbia.edu/~smb/blog/2019-11/2019-11-17.html
The Early History of Usenet, Part IV: File Format >https://www.cs.columbia.edu/~smb/blog/2019-11/2019-11-21.html
The Early History of Usenet, Part V: Implementation and User Experience >https://www.cs.columbia.edu/~smb/blog/2019-11/2019-11-22.html
The Early History of Usenet, Part VI: Authentication and Norms >https://www.cs.columbia.edu/~smb/blog/2019-11/2019-11-25.html
The Early History of Usenet, Part VII: The Public Announcement >https://www.cs.columbia.edu/~smb/blog/2019-11/2019-11-30.html
The Early History of Usenet, Part VIII: Usenet Growth and B-news >https://www.cs.columbia.edu/~smb/blog/2019-12/2019-12-26.html
The Early History of Usenet, Part IX: The Great Renaming >https://www.cs.columbia.edu/~smb/blog/2020-01/2020-01-09.html
The Early History of Usenet, Part X: Retrospective Thoughts >https://www.cs.columbia.edu/~smb/blog/2020-01/2020-01-09a.html
The Early History of Usenet, Part XI: Errata >https://www.cs.columbia.edu/~smb/blog/control/tag_index.html#TH_Usenet_history >The tag URL ...#TH_Usenet_history will always take you to an index of all >blog posts on this topic.
...
(seems "pugleaf" is really webifying the usenet...it's truly excellent)
p.s. here's a fine article that was posted here in alt.fan.usenet back
in 2023-12-03, <ukhsg9$sqh$1@reader2.panix.com> about usenet's genesis:
On 10/11/25 04:04, D wrote:
...
(seems "pugleaf" is really webifying the usenet...it's truly excellent)
p.s. here's a fine article that was posted here in alt.fan.usenet back
in 2023-12-03, <ukhsg9$sqh$1@reader2.panix.com> about usenet's genesis:
http://rocksolid-us.pugleaf.net/groups/alt.fan.usenet/message/<Cukhsg9$sqh$1@reader2.panix.com>
;)
On 10/11/25 04:30, Billy G. wrote:
On 10/11/25 04:04, D wrote:
...
(seems "pugleaf" is really webifying the usenet...it's truly excellent)
p.s. here's a fine article that was posted here in alt.fan.usenet back
in 2023-12-03, <ukhsg9$sqh$1@reader2.panix.com> about usenet's genesis: snip
https://rocksolid-us.pugleaf.net/groups/alt.fan.usenet/message/<ukhsg9$sqh$1@reader2.panix.com>
The Early History of Usenetsnip
#834
From: pschleckpanix.c
Date: Sun, 03 Dec 2023 12:32
25 lines
788 bytes
"November 2019 is, as best I can recall, the 40th anniversary of the >conception of Usenet.
...[end quoted excerpt]
Technical Details
Message-ID: <ukhsg9$sqh$1@reader2.panix.com>
Path: i2pn2.pugleaf.net!archive.newsdeef.eu!apf1.newsdeef.eu!not-for-mail
Show Full Headers
Complete Article Headers
Path: archive.newsdeef.eu!apf1.newsdeef.eu!not-for-mail
From: pschleck@panix.com (Paul W. Schleck)
Newsgroups: alt.fan.usenet,alt.culture.usenet,news.groups
Subject: The Early History of Usenet
Date: Sun, 3 Dec 2023 12:32:09 -0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Message-Id: <ukhsg9$sqh$1@reader2.panix.com>
Injection-Date: Sun, 3 Dec 2023 12:32:09 -0000 (UTC)
Injection-Info: reader2.panix.com; posting-host="panix2.panix.com:166.84.1.2";
logging-data="29521"; mail-complaints-to="abuse@panix.com"
User-Agent: nn/6.7.3
User Registration[end quoted excerpt]
Username 3-20 characters, letters, numbers, and underscores only
Email Address Valid email address required for password recovery *
* password recovery is still work in progress!
Password At least 12 characters
Confirm Password
Sign Up
Already have an account?
Usenet Article Lookup
Please provide an exact Message-ID, angle brackets included, to look up:
<105oldi$2ede$1@dont-email.me>[end quote]
View for Bookmarking (what is this?)
Look up another Usenet article
Path: nntp.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Invalid <invalid@invalid.invalid>
Newsgroups: alt.obituaries
Subject: Ozzie Osbourne, 76
Date: Tue, 22 Jul 2025 18:31:16 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 1
Message-ID: <105oldi$2ede$1@dont-email.me>
Injection-Date: Tue, 22 Jul 2025 18:31:16 +0000 (UTC)
Injection-Info: dont-email.me; posting-host="be6113b6302b35f816d6925dc394d076";
logging-data="80302"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+XKIJO3qxbXvAC0j5aWrV0OjOcNRijveI="
User-Agent: tin/2.6.5-20250209 ("Helmsdale") (Linux/6.14.0-24-generic (x86_64))
Cancel-Lock: sha1:xom/jbXOHoe4hMS9fDbyf9tsdyg=
Per multiple sources.
Article View: net.bugs.2bsd[end quoted excerpt]
"holes" in directories