From: Henry Bent <henry.r.bent@gmail.com>
To: Kurt H Maier <khm@sciops.net>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Steve Bellovin recounts the history of USENET
Date: Fri, 22 Nov 2019 17:21:20 -0500 [thread overview]
Message-ID: <CAEdTPBe=ebY6sFbMX7WRp9ZQJuC7Y_7rYACpi5gVt0xPKayjfw@mail.gmail.com> (raw)
In-Reply-To: <20191122210645.GB37773@wopr>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
On Fri, 22 Nov 2019 at 16:06, Kurt H Maier <khm@sciops.net> 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.
>
Why do you say that? I used a browser that was fully logged out of Google
and in paranoid/private settings mode and I could browse newsgroups, do
basic searching, etc. eg:
https://groups.google.com/forum/#!searchin/net.unix-wizards/iris%7Csort:date
> 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 alluded to this sort of problem in my previous email, but in my recent
experience the search results have been satisfactory and I consider the
degraded search problem resolved. I have been able to search for very
precise text strings with entirely satisfactory results over the last few
months.
-Henry
[-- Attachment #2: Type: text/html, Size: 1745 bytes --]
next prev parent reply other threads:[~2019-11-22 22:22 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
2019-11-23 3:45 ` Larry McVoy
2019-11-23 4:42 ` Warren Toomey
2019-11-22 22:21 ` Henry Bent [this message]
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='CAEdTPBe=ebY6sFbMX7WRp9ZQJuC7Y_7rYACpi5gVt0xPKayjfw@mail.gmail.com' \
--to=henry.r.bent@gmail.com \
--cc=khm@sciops.net \
--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).