No more Google Groups search?

[RayLopez99]

jamesjaddah1755 gmail.com wrote:







Not perfect is a gross understatement. See if you can find Linus

Torvalds talking about his Linux kernel project...

I ignore/block most threads when the original post is improperly

formatted by Google Groups users.

I for one kind of like Google Groups and I also like the idea of getting rid of old messages from years ago. Do you really want everybody to read some flamebait you wrote a decade ago? Pretty soon, as storage gets cheaper, everything you ever wrote, bought or said will be archived for some government or organization to use against you and/or data mine. Is this the future we want?

If you have something important to say, there should of course be some freeonline depository or self-publishing website that archives for eternity, but otherwise not.

RL

 

[Jon Danniken]

I for one kind of like Google Groups and I also like the idea of
getting rid of old messages from years ago. Do you really want
everybody to read some flamebait you wrote a decade ago? Pretty
soon, as storage gets cheaper, everything you ever wrote, bought or
said will be archived for some government or organization to use
against you and/or data mine. Is this the future we want?

If you have something important to say, there should of course be
some free online depository or self-publishing website that archives
for eternity, but otherwise not.

It's all still there, Ray, and accessible to any who do a standard
g**gle search. The issue is that the advanced search is gone, so you
can't specify the parameters of what you are looking for when you search
old usenet posts.

And trim your damn posts, ya noobie.

Jon

 

[John Doe]

And someday, this thing will be dead.
And hopefully take its Google Groups formatting with it...

 

[RayLopez99]

And someday, this thing will be dead.
I ignore/block most threads when the original post is improperly formatted, like Google Groups users.

Killfile me then, John Doe! LOL

RL

 

[Paul]

Killfile me then, John Doe! LOL

RL

You realize there are free USENET servers available.
And proper clients that do quoting.

A free USENET news server will protect your IP
address, unlike Google Groups leaving the IP
in the header.

There really is no desirable aspect to using
Google Groups. Bad quoting, formatting (double spacing),
and exposing the IP are the reasons why you should
avoid it and go elsewhere. AIOE and E-S are
available options.

Paul

 

[John Doe]

RayLopez99 wrote:

Kill files are for newbies. Content filtering by ignoring a thread
branch is almost all I need.

Needs to remove the comedian lodged in the vacant area between its
ears.

You realize there are free USENET servers available. And proper
clients that do quoting.

A free USENET news server will protect your IP address, unlike
Google Groups leaving the IP in the header.

Like Eternal September. As of course you know, it is free and
allows reconstructing a thread. That is something some pay servers
don't even allow.

There really is no desirable aspect to using Google Groups. Bad
quoting, formatting (double spacing),

Some groups are chock-full of Google Groups users. Google has
become a blight on USENET, worse than AOL was.

 

[John Doe]

There really is no desirable aspect to using Google Groups. Bad
quoting, formatting (double spacing), and exposing the IP

That IP thing is amusing.

 

[RayLopez99]

There really is no desirable aspect to using

Google Groups. Bad quoting, formatting (double spacing),

and exposing the IP are the reasons why you should

avoid it and go elsewhere. AIOE and E-S are

available options.

I found that to set up a newsreader, and do a test post, and all that sort of stuff, is at least a full day's work, maybe two, and there's no guarantee it will even work the first time.

Thanks however for the information.

RL

 

[John Doe]

I found that to set up a newsreader, and do a test post, and all
that sort of stuff, is at least a full day's work, maybe two,

If it's your precious time… Then confine your posts to Google Groups groups.
Or just go away. Problem solved.

 

[Paul]

I found that to set up a newsreader, and do a test post, and all that sort of stuff, is at least a full day's work, maybe two, and there's no guarantee it will even work the first time.

Thanks however for the information.

RL

Five minutes, tops.

I bet if someone made a bar bet with you, you
could do it in five minutes

There are tutorial pages available, for specific USENET
News Readers. Some university web pages have such info.

The only sticking point, is when using an authenticating
USENET server like Eternal September (where you sign up
for an account), you need to tick the "send authentication"
box. As authentication protocol is optional, and the user
is expected to turn on authentication, if the server uses
a username and password.

This is why, for a noobie, I'd start them off with nntp.aioe.org.
Since no authentication tick box is needed, and you only
need to type into four lines of text boxes, to set it
up. And if you can't type stuff into four lines in five
minutes, you're busy eating too many donuts

Paul

 

[Flasherly]

I found

that to set up a newsreader, and do a test post, and all that sort of
stuff, is at least a full day's work, maybe two, and there's no
guarantee it will even work the first time.

-
I never encountered that with FORTE for the reader/writer and AIOE.
True, I may not have utilized all it's many options, and certainly
wouldn't understand all it's aspects. Basically I just got it
functionally working. For me, that would be in a semi-standalone or
portable configuration (for backup purposes). Within the FORTE
directory the actual messages are kept, while, on C drive, Forte keeps
its configuration under typical user profiles;- find that C directory
and copy it over the main program for the next time C is restored. It
contains only the basics, what groups, AIOE's address.

"Seeing" how _everything_ works in relation to the options is another
story I haven't even started. Put it this way: I didn't at all mind
posting through Google until the GOOGLE BullShit got too thick
(identity challenges and Google's trying to screw with browser
updates).