From: Jason Stevens <jsteve@superglobalmegacorp.com>
To: Kurt H Maier <khm@sciops.net>, Larry McVoy <lm@mcvoy.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Steve Bellovin recounts the history of USENET
Date: Sat, 23 Nov 2019 01:48:07 +0000 (UTC) [thread overview]
Message-ID: <ADFDF14544A65F35.9b4bc5f3-105c-4e58-8ebd-e2b835dfd175@mail.outlook.com> (raw)
In-Reply-To: <20191122213238.GC16255@mcvoy.com>
[-- Attachment #1: Type: text/plain, Size: 2190 bytes --]
I for one believe in duplication, and not relying on a single source.
All the artifacts survive today because they were scattered to the winds and found again.
Plus when building a database having 10gb of human entered data is invaluable.
I should add that the first public listing of hack on Google is missing the last part. But it's in the utzoo archive.
https://nethackwiki.com/wiki/Hack_1.0
So the google stuff is incomplete.
Besides it's fun to re-read the world when the rumours of Spocks iniment death in the next movie circulated, and fans petitioned to save him, or even the fallout of Tienemen square, and how it parallels in reddit.
I should also add now that Intel is purging all their old drivers and documents online, even a company with a vested interest in their own past doesn't care.
Google is sunsetting their cloud printing after being up for a decade. It's only a matter of time before they find past free speech inconvenient and problematic and terminate groups.
TLDR is that data needs to be shared, not made inaccessible by one company, and the Google usenet thing is incomplete.
On Sat, Nov 23, 2019 at 5:33 AM +0800, "Larry McVoy" <lm@mcvoy.com> wrote:
On Fri, Nov 22, 2019 at 01:06:45PM -0800, Kurt H Maier wrote:
> On Fri, Nov 22, 2019 at 03:49:58PM -0500, Henry Bent wrote:
> >
> > Has anyone definitely proven that any of the contents of these files are
> > not in the searchable Google Groups interface? I don't really see any need
> > to duplicate their efforts.
>
> That data is essentially unavailable to people without Google accounts.
> Even back when it was, the search had degraded to the point where you
> could paste explicit quotes from messages and those messages would not
> be in the results page.
>
> I wholeheartedly see a need to duplicate (and surpass) their efforts. The
> Deja News service was wonderful; Google's implementation is not. Even if
> someon were to convince them to improve it, they've demonstrated they're
> not a good company to rely on for long-term availability of services
> that are not active surveillance vehicles.
Amen.
[-- Attachment #2: Type: text/html, Size: 4416 bytes --]
next prev parent reply other threads:[~2019-11-23 1:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 12:46 Jason Stevens
2019-11-21 13:23 ` arnold
2019-11-21 13:31 ` Jason Stevens
2019-11-21 15:58 ` Leah Neukirchen
2019-11-22 20:18 ` Justin R. Andrusk
2019-11-22 20:49 ` Henry Bent
2019-11-22 21:06 ` Kurt H Maier
2019-11-22 21:32 ` Larry McVoy
2019-11-23 1:48 ` Jason Stevens [this message]
2019-11-23 3:45 ` Larry McVoy
2019-11-23 4:42 ` Warren Toomey
2019-11-22 22:21 ` Henry Bent
2019-11-23 0:00 ` Kurt H Maier
2019-11-23 1:36 ` Theodore Y. Ts'o
2019-11-22 23:21 ` Arthur Krewat
2019-11-23 1:32 ` Justin R. Andrusk
2019-11-23 22:25 ` Arthur Krewat
2019-11-21 17:22 ` Tomasz Rola
-- strict thread matches above, loose matches on Subject: below --
2019-11-19 19:01 Arnold Robbins
2019-11-21 3:14 ` Larry McVoy
2019-11-21 3:18 ` George Michaelson
2019-11-21 3:28 ` Larry McVoy
2019-11-21 8:56 ` George Michaelson
2019-11-21 9:40 ` Bakul Shah
2019-11-21 9:51 ` George Michaelson
2019-11-21 11:16 ` Arrigo Triulzi
2019-11-21 3:34 ` reed
2019-11-21 3:39 ` Larry McVoy
2019-11-21 3:40 ` Chet Ramey
2019-11-21 3:42 ` Larry McVoy
2019-11-21 3:50 ` Chet Ramey
2019-11-21 3:51 ` Larry McVoy
2019-11-21 3:58 ` Steve Nickolas
2019-11-21 3:50 ` Bakul Shah
2019-11-21 3:52 ` Larry McVoy
2019-11-21 3:58 ` Bakul Shah
2019-11-21 20:36 ` Dave Horsfall
2019-11-24 2:19 ` Michael Parson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ADFDF14544A65F35.9b4bc5f3-105c-4e58-8ebd-e2b835dfd175@mail.outlook.com \
--to=jsteve@superglobalmegacorp.com \
--cc=khm@sciops.net \
--cc=lm@mcvoy.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).