2.1M of the oldest Usenet posts are now online for anyone to read
vice.com
vice.com
https://usenetarchives.com/threads.php?id=rec.music.makers.p...
Google does have some from 1998. It is this weird mix of people from 2016 replying to threads from 1998. The organization is very confusing which I'm sure contributes to the low quality.
https://groups.google.com/g/rec.music.makers.percussion/c/rv...
And what's insane is that there appear to be some flames still going on from 20 years ago ???
I vaguely recall this dude's name from back in 2002 ... I guess he must have been a prolific poster / troll, but I don't remember. But there appear to be some people trolling him. I think he did sell drums or something.
https://groups.google.com/g/rec.music.makers.percussion/c/Nh...
Good ol' Usenet I guess ...
Yeah this is insane, I search for "Rob Schuh" and this flame war has been going on for decades !!!
https://groups.google.com/g/rec.music.makers.percussion/c/8Z...
hmm... here's a taste of it:
https://slashdot.org/story/00/08/27/1439247/usenet-archive-f...
EDIT:
Great Renaming: n.
The flag day in 1987 on which all of the non-local groups on the Usenet had their names changed from the net.- format to the current multiple-hierarchies scheme. Used esp. in discussing the history of newsgroup names. “The oldest sources group is comp.sources.misc; before the Great Renaming, it was net.sources.” There is a Great Renaming FAQ on the Web.
p293 " ! Should only be used when sending via UUCP. This should be the only special character in the address (called a path). The path indicates each site through which mail will be routed, starting at the left and going towards the right. Mixing ! with @ is not considered good. That is, use:
uunet!ucbvax.berkeley.edu.edu!smith
not:
uunet!smith@ucbvax.berkeley.edu.edu"
In other words because UUCP was dialup and long distance expensive, email was routed through specific known hosts, which is why sometimes people ended up with long bangpathed addresses.
https://www.phoenixnewtimes.com/news/drum-and-drummer-643105...
This guy was apparently a genius drummer as a young man -- jammed with Jaco Pastorius, and a friend of John Medeski.
Then a bodybuilder, steroid user (when it was legal), convicted felon, a sufferer of chronic illness, and epic Usenet flamewar participant.
And deceased since 2012, but people still flame him on Usenet.
https://www.drumforum.org/threads/r-i-p-rob-schuh.73509/
And on top of it he also made drums. I remember that from the newsgroup:
https://rec.music.makers.percussion.narkive.com/RqlLNCp4/pro...
I remember the flames but about drums and steroids, but I had no idea back then ...
It was drummed-up charges. :)
> jammed with Jaco Pastorius
Another tragic case, sadly.
‘alt’ groups typically were filtered heavily.
Does anybody remember who this is? I can’t find him, despite my efforts searching for what I just described.
He also got a guest appearance in Jagged Alliance 2. Or at least one of the characters (Calvin Barkmore) looks and sounds a lot like him.
For an archive this is a big no-no. Respect the source material!
Otherwise, thank you for the time spent doing this.
Also, it seems that your parsing process strips headers and that you don't keep the raw messages, however I remember that on some newsgroups people used to pass secret messages in headers that only those "in the know" would look for, it would be a shame to lose that. Access to posts in raw format would be nice in this scenario.
Its not a bad idea to filter content though, and/or have a flag button on threads/posts. 300 million articles from 40 years of an obscure and anarchic corner of the internet are bound to contain posts that are either potentially illegal or which you otherwise don't necessarily want to be publishing.
Though I'm also curious, that's perhaps not the tone I would have used when asking. After all, better a censored archive than no archive.
I'm just speculating, but it may be the policy of usenetarchives.com, in order to accept their upload.
Censoring seems to be done around email addresses, names, and offensive words. Perhaps, this is done to reduce the chances of people later asking for the posts to be taken down entirely.
For example, I believe the takedown by Google of comp.lang.lisp and comp.lang.forth commented elsewhere was done because there was offensive content present. The Google support request that mentioned that reason was taken down, but it's what I remember.
"Getting good FP performance from a micro seems to require pipelining. Keeping the p<asterisk><asterisk>e(s) full seems to require a certain amount of parallelism and regularity."
https://www.usenetarchives.com/view.php?id=comp.arch&g=14965...
Edit: Ah, the irony. HN markdown causes two consecutive asterisks to disappear.
A code block.
Two asterisks follow: **
This normally would be *italicised*.Actually, it's not that obvious. It censored "Dirty Sanchez". I'm thinking it thought it was a person's name, and censored it for privacy reasons?
> Keeping the p<asterisk><asterisk>e(s) full seems to
I suppose "pipe" can have an offensive/sexual connotation. Even if it doesn't so much today, perhaps it did back then.
(It isn’t: while “knob” can be translated as “Knopf”, the latter doesn’t have the anatomical meanings of the former).
> On Oct 13, 11:36 am, "Colin" <Co...@DirtySanchez.b••t> wrote:
Did you find additional utzoo material beyond what was already on archive.org in tarballs?
I do have one question. Those tapes...how old were they? Were they contemporary to the postings? (bonus question: if so wow, but under what justification?. tapes were expensive right and nobody valued archiving at the time (except maybe this guy)?) this individual you got the tapes from meticulously copy onto new media and all the overhead that entails?
Today I make personal backups of things I want to keep, whether local files or web snippets and burn 'em to a DVD , blu-ray, or optical disk of some kind with the justification of 'can't ransomware WORM media'.
However, I don't do the internet archiving guru stuff of '3 copies, 2 mediums, 1 routine' (or something like that) so in a sense my backups are cruising for a bruising in the case that optical disks could go bad, hard drives could die (these I do migrate to new media when I get around to it, CDs I just read and burn to a fresh one), house could burn down, etc.
Partially looking to see if I can get justification for my backup slovenliness ;)
It would take some engineering: I might store each optical disk image as a compressed image file, for example (zstd would be good for the large amount of data), to avoid metadata charges. Fun to think about.
I've frankly never trusted them as a steward for this and I'm glad to see someone stepping in.
Do you have any plans to team up with the Internet Archive on this?
It’s sadly not good enough.
How do you handle cross posting?
On one hand it’s nice that we can see all this old data. On the other hand, as far as I remember in the 90s you typically subscribed to a newsgroup and only then got recent posts. So the expectations was a limited life time of the post. Of course it would still be stored in thousands of readers.
Obviously the copyright of each post is with the author. You just assume that you have a right to redistribute.
I’m also happy if I get a pointer elsewhere if you have an url.
Probably by not being European.
Europe doesn't make laws for the whole world anymore. Colonialism is dead.
Fatal error: Uncaught Error: Call to a member function real_escape_string() on null in /var/www/html/usenetarchives.com/3.vars.php:80 Stack trace: #0 /var/www/html/usenetarchives.com/1.header.php(190): include() #1 /var/www/html/usenetarchives.com/view.php(22): include_once('/var/www/html/u...') #2 {main} thrown in /var/www/html/usenetarchives.com/3.vars.php on line 80
Pretty consistently.
As it exists right now, there are some glaring omissions. I would imagine that showing authors in the search results next to the titles would not be prohibitively difficult.
Proper threading of posts would probably be considerably harder, but would provide immense value IMHO.
DMCA took this incredible resource off line. Please don’t let this happen again, as even archive.org found it easier to destroy it all than to fight Marty.
Plus it allows all us little people build fun things with it, like my altavista based search of utzoo:
altavista.superglobalmegacorp.com
Thanks
Edit: I am now on a desktop, and confirm it's not a mobile glitch; the archives for comp.os.linux are imported back to 2003 only at this time. https://www.usenetarchives.com/threads.php?id=comp.os.linux&...
Suggestions:
* Forget about "SEO".
* Forget about running "analytics" surveillance for megacorps.
* Forget about "monetizing" "content".
Also, consider that the Usenet was more a private club, in a more innocent world, and posts were largely ephemeral. We should violate expectations with hesitation and care.
ihnp4!{cithep,wlbr!callan}!tim
What that meant was that to get an email to me, your computer should arrange to deliver it to ihnp4. That was the name of a machine at a Bell Labs office at a place named "Indian Hill" in Naperville, IL. It stood for "Indian Hill Network Processor 4".ihnp4 was very well connected, so it was reasonable for me to expect that you could find a way to get the email to it.
The rest of my email address is saying that ihnp4 should deliver the mail to cithep (Caltech High Energy Physics) or wlbr (a machine at the Westlake Village, CA offices of Bunker Ramo). If it goes to wlbr, wlbr should send it to callan (a machine at Callan Data Systems). I had accounts on cithep and callan, both with user name tim.
You didn't have to start at ihnp4, of course. As long as you could find a way to get it to one of {ihnp4, cithep, wlbr, callan} you could get it to me.
Periodically there was a posting on Usenet giving a list of machines that would publicly relay mail and their interconnections. (I want to say this was monthly and in net.general, but I'm not sure).
Given that and a list of machines that your site connected to, you could find a path from your site to me. Let's say you were in Boston, and you knew your company exchanged mail with decvax (a machine at Digital Equipment Corporation). You could see from the connection list that decvax connected to trwrb (a machine at TRW Redondo Beach, CA, I believe), and trwrb connected to wlbr, so from your machine the email address decvax!trwrb!wlbr!callan!tim would work to reach me.
Usenet is still around, I still read it most days, with trn.
Most newsgroups are either dead or pure spam, but some are active with real content.
I think this is what really did usenet in for me. I used to use newsgroups quite a bit in the early 2000s, then moved on to forums, and then of course social media took over (and now I'm substantially over that).
Given that usenet is now past its popular heyday, I thought it would also be past the peak of spam - and it probably is - but having just registered with eternal-september.org, I'm still pretty surprised by how much spam is in some of these groups. Granted a lot of it is old (because I told Thunderbird to just download all the headers), but there's loads of more recent stuff as well: e.g., crap about COVID in all kinds of groups, as if we're not hearing and reading enough about it already.
This is kind of a shame. If newsgroups had a viable mechanism for combating spam I think they'd still be a great place to hang out because they were and are a one-stop shop for such a wide range of activities and interests. In addition, and ignoring the spam, the reading and writing experience is still really pleasant.
> ...the executives of all these corporations who made the decision to fund these n*s all deserve to die in mass-shootings.
I loved USENET. Threaded discussion is intoxicating. I learned and shared a lot.
Came back after the spam waves to visit some retro computing groups. A few are active. Cool. Low spam.
It didn't seem to count towards our download limit either. Not sure why not, but that was awesome.
The basic concept is simply copying and forwarding email-like messages, grouped into a hierarchical set of newsgroup feeds. A host would subscribe to other hosts, and would allow other hosts to subscribe to their own feeds. And then just push/pull this through the network.
Originally, this was done all with shell scripts dialing up remote hosts by modem and copying compressed datasets nightly. This developed into a full suite of protocols called UUCP. Later, Internet protocols like the Network News Transfer Protocol started carrying some, then all, of the traffic.
In principle, it is unregistered, unpaid, and decentralized. You start exchanging with someone else who has the newsgroups you want to send and receive.
In practice, both in the past and now, you subscribe, usually commercially, to one of the services with the bandwidth and storage to host a reasonable portion of Usenet. ISPs often provided NNTP Usenet service into the early 2000s, along with SMTP/POP for email.
Back when UUCP was still around there wasn't much binary data in groups. It took a while to develop algorithms to encode binary data (uuencode, base64), the protocol was text only.
Your disk, however, would only have the messages you'd specifically requested and pulled down over your modem. (Or, if you went way back to the vt100 days, "your disk" was the central server which had it all.)
My 1M message Usenet archive is 5.6GiB of space, and I believe this covers ~30 days of non-alt.binaries messages. The data is a decade old, so I don't recall the exact details of collection anymore.
One can dial into your ISP, sync News (fetch new messages in groups one is subscribed to and send messages) and then go offline and read/answer the messages without paying per minute and without blocking ports for other dial-in customers.
This also worked between different news servers in distinct networks with unreliable connections.
For the how paid: In some regions it was part of the things a "good" ISP had to offer their clients. Also back in the days™ large parts of the internet was run on machines in some university labs.
I still don't quite get the user experience. What if you're subscribed to alt.binaries? Do you then sync all the binaries when you go online? That wouldn't make sense. Perhaps it only synchronizes on a level below that, alt.binaries.something.something? But that may still be too much.
And what if my ISP's server didn't have the newsgroup I was interested in? Is it like DNS, where it would then fetch it from somewhere else and then cache it? Or did most servers store the entire data? Or an ISP would just store the messages that at least one of their customers subscribe to?
If you were one of the fortunate ones to have a hard-wired connection, well, that happened a lot faster.
Newsreaders were awesome for reading newsgroups. You were able to add someone or a topic to a kill file for one group or all groups.
As binaries got bigger and bigger, the retention time for them on the remote system got shorter and shorter. You might have 7 days of binaries and 90 days of everything else.
For a while some forum software would be accessible via NNTP which was awesome. It let more people use the forums but gave more experienced users much better tools.
This was also where the term “spam” really got popularized (see https://en.wikipedia.org/wiki/Laurence_Canter_and_Martha_Sie...) so many things which we now take for granted were being tried at scale for the first time there. There was a [relatively weak] moderation system which could be used to restrict posting and there were bots which would retroactively cancel messages so you might not see so much junk if a group used such a bot and ruthlessly nuked spam.
Regarding ISPs, in many cases it worked like your last case: start storing anything that at least one client has asked for recently. This was a notorious source of disk space consumption if you ran a low-capacity server and then had someone fire up a client, request the world, and then stop reading it but your system was still downloading everything.
Yes. Your news reader (nee aggregator) would use the NNTP protocol to tell the server "please give me a list of articles in groups X, Y, and Z". Your reader would know you read up to article 234 in a group previously, but now there were 266, so there were 32 new ones. You'd tell the reader UI to go into that group, which would cause it to download the new articles (headers) and display them to you. If you saw a particular thread you liked you'd select that and the body of the article(s) would be downloaded.
If you wanted to do offline reading there was a file format call SOUP which would allow you to download it to your local machine (remember, this was often in the age of dial-up). There is no article on SOUP, but a similar idea was QWK for BBSes:
* https://en.wikipedia.org/wiki/QWK_(file_format)
To distribute articles/posts globally an NNTP server would talk to other NNTP servers: technically peer-to-peer was/is possible, but it was often hierarchical. One could also have site/local-only groups and global groups.
Typically you synced the equivalent of headers and bodies separately (for the groups you were interested in). This way you only grabbed what you wanted. For binary groups, people settled on patterns in subjects, etc so that clients could automate downloading of files (binaries had to be encoded and split into parts due to post length limits).
On regular text type newsgroups you might set your client to download headers+bodies in one shot for offline mode. With offline mode you would then just download what's new vs your cache. Then work against your local cache for reading/replying. Once online again, your batched replies could be sent.
If your ISP didn't have the newsgroup you wanted, you would have to point to another NTTP server. For a while there were public ones that anyone could use. Over time, those public ones went away or dropped problematic areas like alt.binaries.*. These days Usenet is available as a for-pay service.
For what you download in sync depends on your config. alt.binaries is special, I believe relatively young and many providers didn't offer them to begin with ...
When fetching you configured your client "please fetch all of comp.lang.cpp" and it would do. I believe you could also say "just give me the headers" and load only selected messages on next sync (i.e. for fetching only binaries from messages with interesting subjects)
If your ISP didn't have a server, there were multiple open ones in universities or other ISPs (not all locked down for their customers only but either didn't care or saw it as an ad for them), but they could be far away (modern cross ocean cables are younger ...) and busy/slow.
And yes, a server can decide which groups it syncs.
That's one of the reasons ISPs stopped offering them - they'd have to have the infrastructure for all of their customers to support something that perhaps only one person would actually read.
Universities would often not carry the complete alt.* heirachy for example (especially in later, post 2000 years where the binary groups started getting big).
Messages were transferred overnight by copying the latest changes between each uni, you could post to the use group of choice using a usenet client. I was very excited to have access to it at the time, it was rare to have a connection outside of a uni.
There were source code feeds to where you could download the latest sources and try to compile them yourself, I remember fiddling with things like flex and bison.
It was full nerd - pretty well everyone was an academic, student or worked at a uni or research lab, you'd have contact in almost real time with anyone - this was a new thing.
You'd interface with it using a glass tty - I had a vt52 which connected to a Sun 3 box, which was our development computer. I remember getting a 300 baud modem and connecting to it at night from home with my PC, or maybe it was my amstrad still, PC's were very expensive still. It was a fun time.
Edit: just remembered we only had one dial in modem to the uni, and I'd use it to dial in from home, I remember we used to fight over access to it - eventually they got a second one because the sys admin was sick of not being able to get access to the network at night. They to were very expensive, I think they were 2400 or maybe even 4800 bps - a crazy speed then.
What it was is basically a massive collection of discussion groups, organised hierarchically, hosted on local machines that exchanged these messages with other machines. There was a variety of newsreader programs available that you could use to read and post messages on these discussion groups.
Not every usenet host supports every group. There were a couple of top-level hierarchies, like rec.* for everything recreational, like hobbies and games (I was an avid reader of the rec.games.frp.* newsgroups, which were about roleplaying games); sci.* for everything science, comp.* for everything computer related (some of which was admittedly also recreational). There was also the alt.* hierarchy where literally anything goes. Many hosts only supported a limited selection of the alt.* newsgroups.
You'd post under your own email address, and most newsreaders also supported emailing people directly instead of responding in the group.
I believe there was a big revamp at the end of the 1980s where everything about usenet got changed. I only know the situation from after that reorganisation.
For anyone who doesn't want to sign up to try it, there's also:
news.aioe.org
I still use Thunderbird most often.
If you are an Emacs user, Gnus is another way to get the old school experience.
Another text one that was popular is tin, which I've never used but which, like slrn, is still maintained and updated.
https://archive.org/details/matrixcomputerne0000quar/mode/2u...
I lifted a copy off a friend who was thinning his book herd a decade or so back. The first edition, published in 1990, predates the commercial Internet, World Wide Web, Linux, and all of what's transpired since, though the introduction pressages much by noting the role of existing networks in the the then-fresh events of April 15 – June 4, 1989, known as the six-four incident, and culminating in the Tiananmen Square Massacre.
The book has a 15 page section describing Usenet, including user and traffic statistics from 1979--1988, mostly compiled by Gene Spafford and Brian Reid. Usenet is only one of numerous conferencing systems covered, others being BITNET, UUCP, FidoNET, VNET, and EASYnet
For April, 1988: 381 newsgroups, 57,979 messages, 130.949 MB, 4,152--7,810 hosts (depending on who counted and how), and an estimated 141,000 readers (people) from a total online population of 880,000.
Larry Wall, working at JPL, is named ... as the author of rn.
Much of the book, though, simply discusses the many many individual computer networks. The notion of a single global end-to-end interconnected inter-network was still very much a novelty.
In one section, the fact that the principle public interconnect between North America and Europe was a single 9600 Baud link is mentioned....
Originally, Usenet used UUCP for transport; later on NNTP was defined so Usenet could be shared via TCP/IP. In the early days, only DARPA contractors (which included many university computer science departments) could be on the Internet; second-class citizens could use UUCP and modems.
In the early there were only a few dozen to few hundred computers, mainly in universities and computer companies. You list all the networked computers in a single file called /etc/hosts.
In the late 1980s universal protocols and funding from Senator Al Gores 1991 Information Superhighway legislation allowed the computers anywhere in the world to interconnect.
My usenet email address from 1976 still works.
Jon Udell's 1999 book "Practical Internet Groupware" was an excellent resource on how to set up this sort of infrastructure by gluing together various protocols:
An NNTP server had a list of discussion forums: clients connected and got the list, and the user could selectively subscribe to the one's they were interested in. The client would keep track of which messages were read, and so when new ones were posted you'd only see new messages by default.
Each NNTP server could talk to other NNTP servers. They would exchange a list of forums each had, and then the articles had in each forum. Each article/post had a unique ID (basically like the Message-ID in e-mails), and so each could request articles from the other that they did not already have. New messages could be posted to either server and they would 'cross pollinate' (multi-master basically).
Each NNTP server could technically talk to multiple other NNTP servers, so cross-pollination could be very wide, but in the early days with low-kbps modems and expensive long distance, there was a lot of local hierarchical hubs.
There were a few key hubs that had fancy long-distance T1 and such that could transfer across continents and oceans as a bit of a service for the community.
One would "post" a message and periodically one or more systems would poll your system. Either over the ARPAnet or via an actual modem. It would fetch all of the posts that had been created on that system and add them to its list of new posts, and it would send you all of the posts you hadn't yet seen.
In a directory on your system would be all of the posts from everyone on Usenet for all of the groups you cared to "follow."
Back in the 80's I could read everything posted in a couple of hours in the morning. :-) That changed quickly.
Slight difference -- there would be no main "front page," -- only individual self-hosted hubs that could choose which "subreddits" (newsgroups) they would carry.
That meant that unlike with Reddit, an idiotic interface redesign only ruined it for users of one client, and only until they got time to switch to another client.
Typically the posting news server (i.e. your own news server) was responsible for validating that you used your real email address.
Originally there was no validation, but as spam rose validation became required.
News servers required you to login, originally they were open to anyone.
For example:
https://www.usenetarchives.com/view.php?id=comp.arch&g=14965...
Amazingly, you could replace most of the content of that post with "Star Trek Discovery" or "Star Trek Picard" and it'd be just like a recent post!
I think The Next Generation fared well despite the slow first series. Fascinating bit of internet history.
At least this "review" is worded better than many of the suspect (paid for?) reviews of films on IMDB these days.
He was more mature and could cope far better later on sites such as slashdot where he engaged, but landing a dream job, and being rejected by fellow nerds as well as “william fucking shatner” really did a number on him.
I suppose it must be a skill to learn that people dislike your character, not you personally.
Still you can always rely on your heroes:
Actually, it was the Security Officer's Wife, Keiko. :D
Someone should do this properly. Like the ArchiveTeam guys.
Assuming there's little in the way of moderation perhaps there's something to be said for small networks with a barrier to entry.
You have to remember this was before the web. There were ways to have FTP sites or other more permanent locations to share FAQs if you knew where to look, but for the most part someone new would show up on a newsgroup and start asking the same newbie questions all over again, or hit some hot-button issue for that group and re-start an epic flame war. So each September or so would be an influx of people who didn't understand or know the culture and it was uncomfortable for all the people who had been in the club prior to that year's new kids.
:)
Gen Z, woooooo. Woo.
I'm doomed.
Anyways, what can be done probabably will be done, for whichever reason because it's getting cheaper and cheaper.
And then the next leak happens.
And somewhere on some site like Have I been owned?, or in a torrent there is a comma separated list with many, or even all of your former pseudonyms connected with your current address, social security, drivers license, younameit.
Gotcha!
Point being a lot of us I think are really respective of privacy and the fact that people (even teachers and nurses!) have lives that don't revolve around work.
Even worse, there's a large chunk of millenials who don't even believe that Gen-X exists, and think that the generation above them are all boomers.
1; I’m a 34yo millennial, 2; my siblings are ~40ish yo gen-xers, 3; my parents are 65yo boomers.
My genx siblings all bought massive houses around 2008 when I was starting my career which in 2008 meant being lucky to make $40k as a sysadmin. Obama subsidies all over the place if you had 5-10 years to put together a downpayment, though. I don’t think my paycheck became NOT hand-to-face until I was in my mid-late 20s and making well into 6 figures. And I’m not eating avocado toast or buying starbucks.
This is my 2nd recession since I started my career. In the first I was a “JR” and couldn’t get a job. Now I’m a SR and overqualified at most places. I barely know any millenial colleagues of mine that are home owners. And once again, I’m in my mid 30s.
And no, I don’t have children along with half of my mid-30s friends because we can’t afford them along with the 70k+ Of college debt and $600k starter houses.
The truly sad part though, millennials actually remember and know what life was like starting out around ~2008. We’re very open to mentoring and hiring gen-z. Social media wasn’t what it was back in 2008, of course, but I don’t remember any genxers going out of their way to get us millennials hired, go over our resumes, refer us, etc. I luckily landed my first engineering job from another millennial over IRC. This goes into the culture of the company, interviewing, everything. The people bitching about having to describe how to throw a rock or explain why manholes are round? They’re millennials who got those stupid questions when we were JRs because of a horrible job market that Boomers/Genx allowed to continue as the status quo. Not all, of course, but there’s a lot.
Instead of working to make things better for those coming up behind you, you’re acting like the victim. We can all come up with reasons that things suck. Let’s try to improve things.
But yeah if youtube existed when I was young I would probably be internet famous in a bad way.
At least with my old embarrassing forum posts and such it was me actively sharing it :)
It was awesome. You had a good choice of clients to read and post (instead of a half-baked webapp), and everything was incredibly snappy.
We have fallen so far. There's no money in building protocols and money in apps, so people build apps instead.
You could use the same system to get software: I eventually got an entire GNU development system for my Atari ST from umich via archie. Usenet would have index updates broadcast so you knew when to download new files.
Also, the clarity of those Spectrum 512 files. You could almost see the texture of the skin.
Bit unreasonable to complain that Google is evil because they don't want to keep an archive of Usenet when the only reason this is an issue is because nobody else wanted to do that either. Every organization which ran an NNTP server had a copy of all messages because Usenet is decentralised, every single one could have kept an archive and didn't, it's not like websites where nobody but the webserver host has full access.
Not gonna go as far as saying "it cannot be evil to do what everyone else does", but if there is only one remaining archive on the planet and you desperately value it ... why are you shitting on the company which owns it?
* As long as they provide the service, it's difficult for any other competitors to get traction. Once upon a time, their Usenet archive was great, and gradually they eroded the search and the UI.
* As far as I know, they never offered their archive through NNTP or any open protocol. It seems to me that if they offered the archives now, a number of organizations might at least consider stepping up. Instead, they seem to operate as a data roach motel.
When it comes to usenet though...
https://www.usenetarchives.com/threads.php?id=comp.lang.smal...
I see the posts there are pretty interesting. This one led me to a bit of a rabbit hole:
https://www.usenetarchives.com/view.php?id=comp.lang.smallta...
Was really suprised to see this, a page an a half of posts and healthy replies from just this last month. I really wonder what type of people still hang out there.
comp.arch (1986-) easily has 10 times as much present day activity.
How active is another topic.
There are contributors from then still active now too.
It's a long shot since it would require Google to actually do something with a dataset they clearly don't care about, but they could get some good corporate PR points almost for free.
eg:
It's nice that this person/org is hosting these, but I'd feel more comfortable if archive.org (and perhaps another org or two) mirrored them as well. History shouldn't be dependent on some random person/org paying to host them. I thought things would be safe with Google and I was wrong. I'm definitely less confident that usenetarchives.com will be around forever.
I believe these were gatewayed with Usenet (so you could use NNTP to read and write), though they weren't actually part of Usenet proper.
I was an active participant back in the 1990s, but it disappeared when the web took over.
(.)(.)I hung out in talk.origins for a little bit. The usual practice of threads there was to have very, very deep threads with people quoting liberally (i.e., not bothering to trim messages, which is usual custom on Usenet) to reply with a short message. And talk.origins was consistently one of the highest post count groups. If alt.atheism was like talk.origins, then it's mostly the crowd of people it attracted rather than any accident of UI design.
Usenet culture and things like that group which was part of the empire of meow (http://xahlee.info/Netiquette_dir/_/meow_wars.html) are kind of interesting an represent a part of the Internet that seems lost, but probably still exists under all the shiney social media sites.
The main consequence of that flooding, disrupting and destroying of newsgroups is people moved on to the shiny social media sites, and Usenet was effectively killed off.
I shudder at a potential early Myspace/Facebook archive in 20-30 years.
Once you posted something, you had no real control over it being retained and archived. There was a message header you could set ("X-No-Archive: yes" IIRC), but it could not really be enforced.
For about the past 20 years you don't need an archive though, with some Usenet service providers having posts going back to at least 2003 (with people talking about 2003 being a cut off for this archive, I suspect that's where much of the content is coming from).
Major Usenet providers required/had so much space for binaries they just stopped expiring text posts, which are a drop in the ocean by comparison.
Ditto for old BITNET/LISTSERVs needing to be archived. A lot of my childhood is wrapped in up BBSes, BITNET/LISTSERVs/Majordomo lists, and USENET, and being able to see some of it on textfiles.com and Deja was a nostalgic joy ride down memory lane.
https://www.usenetarchives.com/view.php?id=comp.ai&g=4670&p=...
Common Lisp "Loop" flamewar must be older than 30 years.
> B-@yahoo.com
> 2004-04-25 16:47:31 EST
> I sure do
A simpler time.
(Sorry for the shallow comment, but it's my hot take on the title)
Is there a big gap in the 90s? Couldn't find anything from mid 90s.
reddit is owned by someone. it is censored periodically. it is monetized.
usenet was built up in a more grassroots peer-to-peer way.
Please comment as much as you like—and thanks for working on rectifying the lost-Usenet issue.
This is a bit like as a teenager going to a meeting in the 80's, having it recorded without you knowing and now it being on online.
There was no expectations usenet would be stored or be searchable back then.
That's also sort of public. Actually, it 100% is.
It's still not ethical by normal HN standards.
Expectations, right or wrong, for privacy are normally respected on HN. That's all my point is.
Soon using infrared and other techniques we'll be able to get pretty good naked images of people in public too. Every part of your body on a search engine. It's all... like it or not, I guess. But we should at least think about privacy.