On Tue, 31 Oct 2023 17:32:11 -0500
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now read
only at google groups to stop the spam floods.
Same as comp.lang.c as has been mentioned elsewhere (<iMWdnVed06hwqtz4nZ2dnZfqn_GdnZ2d@brightview.co.uk> for example). Good. I wonder how that works. Was some algorithm at googlegroups triggered and automatically took the measure (or notified a human) or do they have some employee at Google regularly take a few minutes of their time once per several weeks to have a short look at googlegroups to see how things are working ? I will guess the latter because an algorithm would have acted much sooner.
On 01/11/2023 02:09, Spiros Bousbouras wrote:
On Tue, 31 Oct 2023 17:32:11 -0500
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now read
only at google groups to stop the spam floods.
Same as comp.lang.c as has been mentioned elsewhere
(<iMWdnVed06hwqtz4nZ2dnZfqn_GdnZ2d@brightview.co.uk> for example). Good. I >> wonder how that works. Was some algorithm at googlegroups triggered and
automatically took the measure (or notified a human) or do they have some
employee at Google regularly take a few minutes of their time once per
several weeks to have a short look at googlegroups to see how things are
working ? I will guess the latter because an algorithm would have acted much >> sooner.
What will Google do assuming the spammers just move on to another group?
They wouldn't want to make
ALL their groups read only, and it can't be hard for the spammers to
identify new target groups that
haven't been locked down yet?
Mike.
On 01/11/2023 02:09, Spiros Bousbouras wrote:
On Tue, 31 Oct 2023 17:32:11 -0500What will Google do assuming the spammers just move on to another group? They wouldn't want to make
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now readSame as comp.lang.c as has been mentioned elsewhere
only at google groups to stop the spam floods.
(<iMWdnVed06hwqtz4nZ2dnZfqn_GdnZ2d@brightview.co.uk> for example). Good. I >> wonder how that works. Was some algorithm at googlegroups triggered and
automatically took the measure (or notified a human) or do they have some
employee at Google regularly take a few minutes of their time once per
several weeks to have a short look at googlegroups to see how things are
working ? I will guess the latter because an algorithm would have acted much >> sooner.
ALL their groups read only, and it can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
On 01/11/2023 02:09, Spiros Bousbouras wrote:
On Tue, 31 Oct 2023 17:32:11 -0500
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now read
only at google groups to stop the spam floods.
Same as comp.lang.c as has been mentioned elsewhere
(<iMWdnVed06hwqtz4nZ2dnZfqn_GdnZ2d@brightview.co.uk> for example).
Good. I
wonder how that works. Was some algorithm at googlegroups triggered and
automatically took the measure (or notified a human) or do they have some
employee at Google regularly take a few minutes of their time once per
several weeks to have a short look at googlegroups to see how things are
working ? I will guess the latter because an algorithm would have
acted much
sooner.
What will Google do assuming the spammers just move on to another
group? They wouldn't want to make ALL their groups read only, and it
can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
Mike.
Mike Terry wrote:
On 01/11/2023 02:09, Spiros Bousbouras wrote:
On Tue, 31 Oct 2023 17:32:11 -0500
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now read >>>> only at google groups to stop the spam floods.
Same as comp.lang.c as has been mentioned elsewhere
(<iMWdnVed06hwqtz4nZ2dnZfqn_GdnZ2d@brightview.co.uk> for example).
Good. I
wonder how that works. Was some algorithm at googlegroups triggered and
automatically took the measure (or notified a human) or do they have some >>> employee at Google regularly take a few minutes of their time once per
several weeks to have a short look at googlegroups to see how things are >>> working ? I will guess the latter because an algorithm would have
acted much
sooner.
What will Google do assuming the spammers just move on to another
group? They wouldn't want to make ALL their groups read only, and it
can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
Mike.
What I'm hoping is that this is just a temporary measure while they work >something else out. Various admins needed several days - including
false starts - to develop working solutions, Google will have QA
measures in place so they won't be able to move that quickly.
Mike Terry wrote:
On 01/11/2023 02:09, Spiros Bousbouras wrote:
On Tue, 31 Oct 2023 17:32:11 -0500
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now read >>>> only at google groups to stop the spam floods.
Same as comp.lang.c as has been mentioned elsewhere
(<iMWdnVed06hwqtz4nZ2dnZfqn_GdnZ2d@brightview.co.uk>Â for example).
Good. I
wonder how that works. Was some algorithm at googlegroups triggered and
automatically took the measure (or notified a human) or do they have
some
employee at Google regularly take a few minutes of their time once per
several weeks to have a short look at googlegroups to see how things are >>> working ? I will guess the latter because an algorithm would have
acted much
sooner.
What will Google do assuming the spammers just move on to another
group? They wouldn't want to make ALL their groups read only, and it
can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
Mike.
What I'm hoping is that this is just a temporary measure while they work something else out. Various admins needed several days - including
false starts - to develop working solutions, Google will have QA
measures in place so they won't be able to move that quickly.
In article <uht2te$3me4m$1@paganini.bofh.team>,
Andrew <Doug@hyperspace.vogon.gov> wrote:
Mike Terry wrote:
On 01/11/2023 02:09, Spiros Bousbouras wrote:
On Tue, 31 Oct 2023 17:32:11 -0500
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now read >>>>> only at google groups to stop the spam floods.
Same as comp.lang.c as has been mentioned elsewhere
(<iMWdnVed06hwqtz4nZ2dnZfqn_GdnZ2d@brightview.co.uk>Â for example).
Good. I
wonder how that works. Was some algorithm at googlegroups triggered and >>>> automatically took the measure (or notified a human) or do they have some >>>> employee at Google regularly take a few minutes of their time once per >>>> several weeks to have a short look at googlegroups to see how things are >>>> working ? I will guess the latter because an algorithm would have
acted much
sooner.
What will Google do assuming the spammers just move on to another
group? They wouldn't want to make ALL their groups read only, and it
can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
Mike.
What I'm hoping is that this is just a temporary measure while they work
something else out. Various admins needed several days - including
false starts - to develop working solutions, Google will have QA
measures in place so they won't be able to move that quickly.
Google should be tossing abusers off!
On 11/1/23 03:40, Andrew wrote:
Mike Terry wrote:
On 01/11/2023 02:09, Spiros Bousbouras wrote:
On Tue, 31 Oct 2023 17:32:11 -0500
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now read >>>>> only at google groups to stop the spam floods.
Same as comp.lang.c as has been mentioned elsewhere
(<iMWdnVed06hwqtz4nZ2dnZfqn_GdnZ2d@brightview.co.uk>Â for example).
Good. I
wonder how that works. Was some algorithm at googlegroups triggered and >>>> automatically took the measure (or notified a human) or do they have
some
employee at Google regularly take a few minutes of their time once per >>>> several weeks to have a short look at googlegroups to see how things are >>>> working ? I will guess the latter because an algorithm would have
acted much
sooner.
What will Google do assuming the spammers just move on to another
group? They wouldn't want to make ALL their groups read only, and it
can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
Mike.
What I'm hoping is that this is just a temporary measure while they work
something else out. Various admins needed several days - including
false starts - to develop working solutions, Google will have QA
measures in place so they won't be able to move that quickly.
A man can dream. I'm betting this is a permanent "solution".
On 11/1/23 10:01, Andrew wrote:
If the tossers toss the abusers off, the abusive spammer tossers just
return with new email addresses (and they don't even need to be gmail)
and start tossing their spam around again.
I can't remember, does gmail get checked for spam on their servers? If
it does then they are 80% of the way there.
There is a spam folder. It's effectiveness is something I'm not sure of.
The Doctor wrote:
In article <uht2te$3me4m$1@paganini.bofh.team>,
Andrew <Doug@hyperspace.vogon.gov> wrote:
Mike Terry wrote:
On 01/11/2023 02:09, Spiros Bousbouras wrote:
On Tue, 31 Oct 2023 17:32:11 -0500
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now >>>>>> read
only at google groups to stop the spam floods.
Same as comp.lang.c as has been mentioned elsewhere
(<iMWdnVed06hwqtz4nZ2dnZfqn_GdnZ2d@brightview.co.uk>Â for example). >>>>> Good. I
wonder how that works. Was some algorithm at googlegroups triggered
and
automatically took the measure (or notified a human) or do they
have some
employee at Google regularly take a few minutes of their time once per >>>>> several weeks to have a short look at googlegroups to see how
things are
working ? I will guess the latter because an algorithm would have
acted much
sooner.
What will Google do assuming the spammers just move on to another
group? They wouldn't want to make ALL their groups read only, and it >>>> can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
Mike.
What I'm hoping is that this is just a temporary measure while they work >>> something else out. Various admins needed several days - including
false starts - to develop working solutions, Google will have QA
measures in place so they won't be able to move that quickly.
Google should be tossing abusers off!
If the tossers toss the abusers off, the abusive spammer tossers just
return with new email addresses (and they don't even need to be gmail)
and start tossing their spam around again.
I can't remember, does gmail get checked for spam on their servers? If
it does then they are 80% of the way there.
Le 01/11/2023 à 16:53, candycanearter07 a écrit :
There is a spam folder. It's effectiveness is something I'm not sure of.
Gmail filters a lot of spam, sometimes there is a false positive but it's rare.
Apparently they don't want to use that on Google Groups.
On Wed, 01 Nov 23 15:57:11 +0000
Eric M <conanospamic@gmail.com> wrote:
Le 01/11/2023 à 16:53, candycanearter07 a écrit :
There is a spam folder. It's effectiveness is something I'm not sure of.
Gmail filters a lot of spam, sometimes there is a false positive but it's rare.
This has been my experience too and I have been using a gmail address for
at least 15 years. It is very good at filtering incoming spam. Its filter also gets trained very quickly.
Apparently they don't want to use that on Google Groups.
Yes and this indicates that they don't give a damn about googlegroups , they just spend as little time on it as possible. I am guessing that the reason they haven't shut it down yet is because they don't want to devote the time to have a meeting of management who are high enough in the hierarchy to make the decision !
Spiros Bousbouras <spibou@gmail.com> wrote:
On Wed, 01 Nov 23 15:57:11 +0000
Eric M <conanospamic@gmail.com> wrote:
Le 01/11/2023 à 16:53, candycanearter07 a écrit :
There is a spam folder. It's effectiveness is something I'm not sure of. >>>Gmail filters a lot of spam, sometimes there is a false positive but it's >>> rare.
This has been my experience too and I have been using a gmail address for
at least 15 years. It is very good at filtering incoming spam. Its filter
also gets trained very quickly.
Apparently they don't want to use that on Google Groups.
Yes and this indicates that they don't give a damn about googlegroups , they >> just spend as little time on it as possible. I am guessing that the reason >> they haven't shut it down yet is because they don't want to devote the time >> to have a meeting of management who are high enough in the hierarchy to make >> the decision !
I think Gmail uses a different mechanism: every time a Gmail user marks
a junkmail as spam Google is aware of it and moves the spam to the
user's junk mailbox. That mechanism is not available to them for News because News users do not feed back real-time spam reports to them.
That is not intended to be an apologia for Google's neglectful pollution
of Usenet, only stating a view.
I think Gmail uses a different mechanism: every time a Gmail user marks
a junkmail as spam Google is aware of it and moves the spam to the
user's junk mailbox. That mechanism is not available to them for News because News users do not feed back real-time spam reports to them.
On 11/1/23 11:39, Sn!pe wrote:[...]
I think Gmail uses a different mechanism: every time a Gmail user marks
a junkmail as spam Google is aware of it and moves the spam to the
user's junk mailbox. That mechanism is not available to them for News because News users do not feed back real-time spam reports to them.
That is not intended to be an apologia for Google's neglectful pollution
of Usenet, only stating a view.
You could still have a "mark as spam" button and have them update the
filters and such. Maybe even have a local newsgroup for dealing with
spam (google-groups.spam or something).
Yes and this indicates that they don't give a damn about googlegroups ,
they just spend as little time on it as possible. I am guessing that
the reason they haven't shut it down yet is because they don't want to
devote the time to have a meeting of management who are high enough in
the hierarchy to make the decision !
I think Gmail uses a different mechanism: every time a Gmail user marks
a junkmail as spam Google is aware of it and moves the spam to the
user's junk mailbox. That mechanism is not available to them for News because News users do not feed back real-time spam reports to them.
That is not intended to be an apologia for Google's negligent pollution
of Usenet, only stating a view.
You could still have a "mark as spam" button and have them update the
filters and such. Maybe even have a local newsgroup for dealing with
spam (google-groups.spam or something).
I think Gmail uses a different mechanism: every time a Gmail user
marks a junkmail as spam Google is aware of it and moves the spam to
the user's junk mailbox. That mechanism is not available to them
for News because News users do not feed back real-time spam reports
to them.
What will Google do assuming the spammers just move on to another group? They wouldn't want to make
ALL their groups read only, and it can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday, 01 November 2023 16:39 -0000,
in article <1qjizbc.1d77w5nup213fN%snipeco.2@gmail.com>,
Sn!pe <snipeco.2@gmail.com> wrote:
I think Gmail uses a different mechanism: every time a Gmail user
marks a junkmail as spam Google is aware of it and moves the spam to
the user's junk mailbox. That mechanism is not available to them
for News because News users do not feed back real-time spam reports
to them.
This is not because the reporting mechanism does not exist, rather
those who are the noisiest regarding spam from, no by, Google Groups
are too lazy to go through Google's reporting process. After all,
taking this action behind the scenes does nothing to boost their quite meaningless post count.
In the past, sufficient jumping^W reporting through Google Groups
hoops has resulted in the removal of all access to the target groups.
I have not observed a single post in news.admin.net-abuse.email, via
Google Groups, since December, 2018, as this group is inaccessible
from GG.
BTW - Blocking posts based on the appearance of gmail.com or
googlemail.com in the Message-ID is a fools errand, as these do not
occur. M-IDs and References containg "googlegoups.com" should fit the
bill.
- --
David Ritz <dritz@mindspring.com>
"There will be more spam." -- Paul Vixie
Mike Terry <news.dead.person.stones@darjeeling.plus.com> wrote:
What will Google do assuming the spammers just move on to another group? They wouldn't want to make
ALL their groups read only, and it can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
That's basically the question.
And comp.os.vms is totally inundated now.
--scott
The Doctor wrote:
In article <uht2te$3me4m$1@paganini.bofh.team>,
Andrew <Doug@hyperspace.vogon.gov> wrote:
Mike Terry wrote:
On 01/11/2023 02:09, Spiros Bousbouras wrote:
On Tue, 31 Oct 2023 17:32:11 -0500
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now read >>>>>> only at google groups to stop the spam floods.
Same as comp.lang.c as has been mentioned elsewhere
(<iMWdnVed06hwqtz4nZ2dnZfqn_GdnZ2d@brightview.co.uk>Â for example). >>>>> Good. I
wonder how that works. Was some algorithm at googlegroups triggered and >>>>> automatically took the measure (or notified a human) or do they have some >>>>> employee at Google regularly take a few minutes of their time once per >>>>> several weeks to have a short look at googlegroups to see how things are >>>>> working ? I will guess the latter because an algorithm would have
acted much
sooner.
What will Google do assuming the spammers just move on to another
group? They wouldn't want to make ALL their groups read only, and it >>>> can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
Mike.
What I'm hoping is that this is just a temporary measure while they work >>> something else out. Various admins needed several days - including
false starts - to develop working solutions, Google will have QA
measures in place so they won't be able to move that quickly.
Google should be tossing abusers off!
If the tossers toss the abusers off, the abusive spammer tossers just
return with new email addresses (and they don't even need to be gmail)
and start tossing their spam around again.
I can't remember, does gmail get checked for spam on their servers? If
it does then they are 80% of the way there.
Le 01/11/2023 à 16:53, candycanearter07 a écrit :
On 11/1/23 10:01, Andrew wrote:
If the tossers toss the abusers off, the abusive spammer tossers just
return with new email addresses (and they don't even need to be gmail)
and start tossing their spam around again.
I can't remember, does gmail get checked for spam on their servers? If >>> it does then they are 80% of the way there.
There is a spam folder. It's effectiveness is something I'm not sure of.
Gmail filters a lot of spam, sometimes there is a false positive but it's >rare. Apparently they don't want to use that on Google Groups.
candycanearter07 wrote:
On 11/1/23 03:40, Andrew wrote:
Mike Terry wrote:
On 01/11/2023 02:09, Spiros Bousbouras wrote:
On Tue, 31 Oct 2023 17:32:11 -0500
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
Apparently comp.arch, comp.lang.c++, and comp.lang.fortran are now read >>>>>> only at google groups to stop the spam floods.
Same as comp.lang.c as has been mentioned elsewhere
(<iMWdnVed06hwqtz4nZ2dnZfqn_GdnZ2d@brightview.co.uk>Â for example). >>>>> Good. I
wonder how that works. Was some algorithm at googlegroups triggered and >>>>> automatically took the measure (or notified a human) or do they have >>>>> some
employee at Google regularly take a few minutes of their time once per >>>>> several weeks to have a short look at googlegroups to see how things are >>>>> working ? I will guess the latter because an algorithm would have
acted much
sooner.
What will Google do assuming the spammers just move on to another
group? They wouldn't want to make ALL their groups read only, and it >>>> can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
Mike.
What I'm hoping is that this is just a temporary measure while they work >>> something else out. Various admins needed several days - including
false starts - to develop working solutions, Google will have QA
measures in place so they won't be able to move that quickly.
A man can dream. I'm betting this is a permanent "solution".
I don't know if it is permanent, but it is lazy. If Ray, Adam, I and others >can filter spam, I would think Google could do it.
--
Retro Guy
Mike Terry <news.dead.person.stones@darjeeling.plus.com> wrote:
What will Google do assuming the spammers just move on to another group? They wouldn't want to make
ALL their groups read only, and it can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
That's basically the question.
And comp.os.vms is totally inundated now.
--scott
candycanearter07 <no@thanks.net> wrote:
[...]
Yes and this indicates that they don't give a damn about googlegroups , >>>> they just spend as little time on it as possible. I am guessing that
the reason they haven't shut it down yet is because they don't want to >>>> devote the time to have a meeting of management who are high enough in >>>> the hierarchy to make the decision !
I think Gmail uses a different mechanism: every time a Gmail user marks >>> a junkmail as spam Google is aware of it and moves the spam to the
user's junk mailbox. That mechanism is not available to them for News
because News users do not feed back real-time spam reports to them.
That is not intended to be an apologia for Google's negligent pollution
of Usenet, only stating a view.
You could still have a "mark as spam" button and have them update the
filters and such. Maybe even have a local newsgroup for dealing with
spam (google-groups.spam or something).
But, but, the author of my Newsreader has retired; who will program a
"mark as spam" button for it? I don't read News using a Google program
so there ~is no~ 'feedback to Google' mechanism.
It isn't as though Google have anything to do with Usenet anyway;
they've simply usurped the Usenet group namespace for their ersatz
"Google Groups" mailing list setup.
On 1 Nov 2023 21:51:38 -0000, kludge@panix.com (Scott Dorsey) wrote:
Mike Terry <news.dead.person.stones@darjeeling.plus.com> wrote:
What will Google do assuming the spammers just move on to another group? They wouldn't want to make
ALL their groups read only, and it can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
That's basically the question.
And comp.os.vms is totally inundated now.
--scott
p.s. has googlegroups ever been known to reinstate/reactivate posting
from a problematic group after they've locked down that group or
is it permanent?
And comp.os.vms is totally inundated now.
On 1 Nov 2023 21:51:38 -0000
kludge@panix.com (Scott Dorsey) wrote:
And comp.os.vms is totally inundated now.
Same for sci.lang.japan .
On 1 Nov 2023 21:51:38 -0000
kludge@panix.com (Scott Dorsey) wrote:
And comp.os.vms is totally inundated now.
Same for sci.lang.japan .
On 1 Nov 2023 21:51:38 -0000, kludge@panix.com (Scott Dorsey) wrote:
Mike Terry <news.dead.person.stones@darjeeling.plus.com> wrote:group? They wouldn't want to make
What will Google do assuming the spammers just move on to another
ALL their groups read only, and it can't be hard for the spammers to >identify new target groups that
haven't been locked down yet?
That's basically the question.
And comp.os.vms is totally inundated now.
--scott
p.s. has googlegroups ever been known to reinstate/reactivate posting
from a problematic group after they've locked down that group or
is it permanent? e.g., heavily googlespammed "alt.comp.freeware"
has gone over thirty (30) hours without a peep from headquarters;
perhaps they're simply reloading for the next barrage of possibly
heavier attacks than ever before (August logged 8218 googlespams),
or might it be that alt.comp.freeware has been put into lockdown?
On 11/1/23 13:59, Sn!pe wrote:
candycanearter07 <no@thanks.net> wrote:
[...]
Yes and this indicates that they don't give a damn about googlegroups , >>>>> they just spend as little time on it as possible. I am guessing that >>>>> the reason they haven't shut it down yet is because they don't want to >>>>> devote the time to have a meeting of management who are high enough in >>>>> the hierarchy to make the decision !
I think Gmail uses a different mechanism: every time a Gmail user marks >>>> a junkmail as spam Google is aware of it and moves the spam to the
user's junk mailbox. That mechanism is not available to them for News >>>> because News users do not feed back real-time spam reports to them.
That is not intended to be an apologia for Google's negligent pollution >>>> of Usenet, only stating a view.
You could still have a "mark as spam" button and have them update the
filters and such. Maybe even have a local newsgroup for dealing with
spam (google-groups.spam or something).
But, but, the author of my Newsreader has retired; who will program a
"mark as spam" button for it? I don't read News using a Google program
so there ~is no~ 'feedback to Google' mechanism.
It isn't as though Google have anything to do with Usenet anyway;
they've simply usurped the Usenet group namespace for their ersatz
"Google Groups" mailing list setup.
Maybe back in the day they did care about Usenet more?
also side note i love the word ersatz and wish ppl used it more last
time ive heard it was like in ASOUE.
--
user <candycane> is generated from /dev/urandom
On Thu, 2 Nov 2023 02:14:29 +0100 (CET) D <J@M> wrote:
On 1 Nov 2023 21:51:38 -0000, kludge@panix.com (Scott Dorsey) wrote:
Mike Terry <news.dead.person.stones@darjeeling.plus.com> wrote:p.s. has googlegroups ever been known to reinstate/reactivate posting
What will Google do assuming the spammers just move on to another group? They wouldn't want to makeThat's basically the question.
ALL their groups read only, and it can't be hard for the spammers to identify new target groups that
haven't been locked down yet?
And comp.os.vms is totally inundated now.
--scott
from a problematic group after they've locked down that group or
is it permanent?
Years ago they made unavailable comp.lang.c
From: RS Wood <rsw@therandymon.com>
Newsgroups: comp.misc
Subject: comp.lang.c banned from Google interface - hooray
Date: Sun, 14 Feb 2021 22:59:14 -0000 (UTC)
Message-ID: <s0ca02$5p9$1@solani.org>
[...]
Comments URL: https://news.ycombinator.com/item?id=26126455
and some other groups but they reinstated them later. On the other hand ,
I have been told (<BGlHbeAV7eBlFAX9@perry.uk>) that uk.railway has
been removed completely.
Comp.lang.c Google Group has been banned (groups.google.com)[end quoted excerpt . . . lots of interesting reading on that longer page]
347 points by veltas on Feb 13, 2021 | hide | past | favorite | 189 comments >...
zafiro17 on Feb 13, 2021 | prev | next [–]
On behalf of Usenet users everywhere, this is excellent news, and I wouldn't >be surprised if Usenetters begin stuffing other useful newsgroups with crap >in order to removed from Google as well.
Google's assimilation of Usenet content had promise at first but quickly >turned into a dystopia and the general consensus on Usenet is that Google
has been a disaster for Usenet.
_kst_ on Feb 13, 2021 | parent | next [–]
Google had the most complete archive of comp.lang.c (and the rest of Usenet). >That archive is now inaccessible.
Users posting to comp.lang.c through Google Groups were a problem -- >especially with the recent bug that caused GG posts to comp.lang.c++ to have >the "++" quietly dropped.
If Google made its archive of all Usenet newsgroups available, I'd be fine >with them dropping the posting interface. (And some users actually managed
to post to comp.lang.c through Google Groups without breaking things.)
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 49:58:58 |
| Calls: | 10,397 |
| Calls today: | 5 |
| Files: | 14,067 |
| Messages: | 6,417,314 |
| Posted today: | 1 |