In article <uhrl9n$3fjpb$1@paganini.bofh.team>,
Andrew <Doug@hyperspace.vogon.gov> wrote:
>Frank Slootweg wrote:
>> Richard Harnden <richard.nospam@gmail.invalid> wrote:
>>> On 31/10/2023 17:22, Mike Terry wrote:
>>>> On 31/10/2023 13:04, Spiros Bousbouras wrote:
>>>>> Checking on  news.cyber23.de  which I don't think does any filtering :
>>>>>
>>>>> comp.lang.c : spam has stopped , latest date for which I see spam is
>>>>> October 27th.
>>>>>
>>>>> comp.lang.fortran , comp.arch , sci.lang.japan : a lot.
>>>>>
>>>>> comp.lang.cobol : spam has stopped , there was a lot until October 25th.
>>>>>
>>>>> comp.lang.forth : a bit of spam.
>>>>>
>>>>> comp.misc : never got any spam with the recent flood.
>>>>>
>>>>> I wonder if the spammers have a plan or it's random to a large extent.
>>>>
>>>> I believe Google has acted on comp.lang.c by blocking all new posts from
>>>> GG.  (When I tried posting it told me I didn't have permission to post
>>>> for that group, but I don't usually use GG, so I'm not sure...)
>>>>
>>>> Mike.
>>>
>>> They have greyed-out the '+ New conversation' button, and attempting to
>>> reply to an existing thread says 'You do not have permission to post to
>>> this group', as Mike said.
>>>
>>> I guess it means that someone a google has finally gotten off their fat
>>> lazy arse.
>>
>> Yes, they seem to have blocked all new posts from GG in comp.lang.c,
>> both new threads (+ New conversation') and responses to existing
>> threads, because I *can* still post from GG in another comp.* group
>> (which also has some, but not immense amounts of, Thai/<whatever> spam),
>> but *not* in comp.lang.c ('You don't have permission to post to this
>> group').
>>
>> But AFAICT, this doesn't really solve anything, because now legit
>> Google Groups posters can no longer post in comp.lang.c (and probably
>> neither in some other closed groups, if any) either.
>>
>> AFAIK, the original intent was to not block/filter legit Google Groups
>> posters.
>>
>> So while the burden of GG spam filtering has been shifted from the
>> user to the news admins (much appreciated), we lost the legit Google
>> Groups posters.
>>
>
>Well maybe someone should post an explanation to affected groups, along
>with a suggestion of alternatives to GG. After recent events this is
>pretty much the best outcome we could hope for, the GG archives are
>still there but nothing new can be posted.
>Maybe the GG admins can come up with a better solution in a week or so.
>
>Ideally the spam would all be retrospectively deleted (by GG), giving us
>access to the older non-spam messages, that is probably too much to hope
>for. I am subscribed to one of the affected groups and I "cleaned
>things up" by deleting all Message-IDs from @gmail.com and
>@googlemail.com, obviously there were a lot of false-positives there but
>I did not have the time, inclination (or the technical possibilities) to
>implement more sophisticated solutions.

Too bad GG doesn ot cancelbot itself!
--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
Today is not tomorrow, and this world provides no guarantees. -unknown https://mindspring.com

Spiros Bousbouras <spibou@gmail.com> wrote:

> Checking on news.cyber23.de which I don't think does any filtering :

Let's try my spam group for comp.* for November...

It looks they moved mostly to comp.cad.cadence.

[news@kvm ~]$ tdx-util -o -n chmurka.spam.comp.thai | grep 'Nov 2023' | awk '{print $2}' | sort | uniq -c | sort -gr
50656 [comp.cad.cadence]
5517 [comp.ai.neural-nets]
4694 [comp.text.tex]
2608 [comp.theory]
813 [comp.databases]
794 [comp.protocols.time.ntp]
575 [comp.programming.threads]
286 [comp.lang.xharbour]
121 [comp.os.linux.misc]
99 [comp.lang.clipper.visual-objects]
33 [comp.lang.cobol]
25 [comp.lang.forth]
25 [comp.dcom.sys.cisco]
19 [comp.lang.python]
15 [comp.lang.verilog]
6 [comp.sys.acorn.misc]
5 [comp.software.testing]
5 [comp.security.ssh]
5 [comp.os.msdos.djgpp]
4 [comp.lang.fortran]
3 [comp.os.vms]
2 [comp.protocols.tcp-ip]
2 [comp.protocols.kerberos]
2 [comp.editors]
1 [comp.text.pdf]
1 [comp.protocols.tcp-ip.domains]
1 [comp.protocols.nfs]
1 [comp.protocols.dicom]
1 [comp.mobile.android]
1 [comp.mail.sendmail]
1 [comp.lang.c++]
1 [comp.arch.embedded]

In article <ui2nsq$aob$2$arnold@news.chmurka.net>,
Adam W. <gof-cut-this-news@cut-this-chmurka.net.invalid> wrote:
>Spiros Bousbouras <spibou@gmail.com> wrote:
>
>> Checking on news.cyber23.de which I don't think does any filtering :
>
>Let's try my spam group for comp.* for November...
>
>It looks they moved mostly to comp.cad.cadence.
>
>[news@kvm ~]$ tdx-util -o -n chmurka.spam.comp.thai | grep 'Nov 2023' |
>awk '{print $2}' | sort | uniq -c | sort -gr
> 50656 [comp.cad.cadence]
> 5517 [comp.ai.neural-nets]
> 4694 [comp.text.tex]
> 2608 [comp.theory]
> 813 [comp.databases]
> 794 [comp.protocols.time.ntp]
> 575 [comp.programming.threads]
> 286 [comp.lang.xharbour]
> 121 [comp.os.linux.misc]
> 99 [comp.lang.clipper.visual-objects]
> 33 [comp.lang.cobol]
> 25 [comp.lang.forth]
> 25 [comp.dcom.sys.cisco]
> 19 [comp.lang.python]
> 15 [comp.lang.verilog]
> 6 [comp.sys.acorn.misc]
> 5 [comp.software.testing]
> 5 [comp.security.ssh]
> 5 [comp.os.msdos.djgpp]
> 4 [comp.lang.fortran]
> 3 [comp.os.vms]
> 2 [comp.protocols.tcp-ip]
> 2 [comp.protocols.kerberos]
> 2 [comp.editors]
> 1 [comp.text.pdf]
> 1 [comp.protocols.tcp-ip.domains]
> 1 [comp.protocols.nfs]
> 1 [comp.protocols.dicom]
> 1 [comp.mobile.android]
> 1 [comp.mail.sendmail]
> 1 [comp.lang.c++]
> 1 [comp.arch.embedded]

Sad idiots!
--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
If we are running from truth, we cannot be approaching God. -unknown Beware https://mindspring.com

On Fri, 3 Nov 2023 14:30:47 -0000 (UTC), doctor@doctor.nl2k.ab.ca (The Doctor) wrote:
>In article <ui2nsq$aob$2$arnold@news.chmurka.net>,
>Adam W. <gof-cut-this-news@cut-this-chmurka.net.invalid> wrote:
>>Spiros Bousbouras <spibou@gmail.com> wrote:
>>> Checking on news.cyber23.de which I don't think does any filtering :
>>Let's try my spam group for comp.* for November...
>>It looks they moved mostly to comp.cad.cadence.
>>[news@kvm ~]$ tdx-util -o -n chmurka.spam.comp.thai | grep 'Nov 2023' |
>>awk '{print $2}' | sort | uniq -c | sort -gr
>> 50656 [comp.cad.cadence]
>> 5517 [comp.ai.neural-nets]
>> 4694 [comp.text.tex]
>> 2608 [comp.theory]
>> 813 [comp.databases]
>> 794 [comp.protocols.time.ntp]
>> 575 [comp.programming.threads]
>> 286 [comp.lang.xharbour]
>> 121 [comp.os.linux.misc]
>> 99 [comp.lang.clipper.visual-objects]
>> 33 [comp.lang.cobol]
>> 25 [comp.lang.forth]
>> 25 [comp.dcom.sys.cisco]
>> 19 [comp.lang.python]
>> 15 [comp.lang.verilog]
>> 6 [comp.sys.acorn.misc]
>> 5 [comp.software.testing]
>> 5 [comp.security.ssh]
>> 5 [comp.os.msdos.djgpp]
>> 4 [comp.lang.fortran]
>> 3 [comp.os.vms]
>> 2 [comp.protocols.tcp-ip]
>> 2 [comp.protocols.kerberos]
>> 2 [comp.editors]
>> 1 [comp.text.pdf]
>> 1 [comp.protocols.tcp-ip.domains]
>> 1 [comp.protocols.nfs]
>> 1 [comp.protocols.dicom]
>> 1 [comp.mobile.android]
>> 1 [comp.mail.sendmail]
>> 1 [comp.lang.c++]
>> 1 [comp.arch.embedded]
>
>Sad idiots!

= 66322 . . . not sure if this is in reference/message id headers
containing "googlegroups.com" . . . but it would be
very interesting to see aggregate (sum) totals for all unmoderated
usenet newsgroups since 1 January 2023, probably millions of these;

*notably, the popular "alt.comp.freeware" newsgroup has apparently
been blocked by googlegroups for three straight days and counting,
for a sum total of 29976 (nearly thirty thousand) since 1 January

On 31/10/2023 13:04, Spiros Bousbouras wrote:
> Checking on news.cyber23.de which I don't think does any filtering :
>
>
>
They have taken a pragmatic approach. Filtering should be done by users
on their own machines; It should not be imposed from the top!! what is
spam to one person is not necessarily spam to another.

On Fri, 3 Nov 2023 16:10:00 +0000, Serial Spammer <invalid@invalid.net> wrote:
>On 31/10/2023 13:04, Spiros Bousbouras wrote:
>> Checking on news.cyber23.de which I don't think does any filtering :
>>
>They have taken a pragmatic approach. Filtering should be done by users
>on their own machines; It should not be imposed from the top!! what is
>spam to one person is not necessarily spam to another.

google should do the right thing and pull the plug . . . but they won't,
or at least not yet until they've finished with their newsgroup-shifting

D <J@m> wrote:

> = 66322 . . . not sure if this is in reference/message id headers
> containing "googlegroups.com" . . .

It's only Thai spam, not everything from Google Groups. I keep two buffers
for them, one 1 GiB and one 3 GiB, it's around 8 days.

Class SPAM for groups matching "chmurka.spam.*"
Buffer SPAM1, size: 1.00 GBytes, position: 581 MBytes 3.57 cycles
Newest: 2023-11-03 22:46:01, 0 days, 0:01:37 ago
Oldest: 2023-10-27 1:25:04, 7 days, 22:22:34 ago
Buffer SPAM2, size: 3.00 GBytes, position: 112 kBytes 1.00 cycles
Newest: 2023-11-02 7:39:04, 1 days, 15:08:34 ago
Oldest: 2023-10-26 18:43:02, 8 days, 5:04:36 ago

On Fri, 3 Nov 2023 12:08:59 -0000 (UTC)
gof-cut-this-news@cut-this-chmurka.net.invalid (Adam W.) wrote:
> Spiros Bousbouras <spibou@gmail.com> wrote:
>
> > Checking on news.cyber23.de which I don't think does any filtering :
>
> Let's try my spam group for comp.* for November...
>
> It looks they moved mostly to comp.cad.cadence.
>
> [news@kvm ~]$ tdx-util -o -n chmurka.spam.comp.thai | grep 'Nov 2023' | awk '{print $2}' | sort | uniq -c | sort -gr
> 50656 [comp.cad.cadence]

Scary.

> 5517 [comp.ai.neural-nets]
> 4694 [comp.text.tex]
> 2608 [comp.theory]
> 813 [comp.databases]
> 794 [comp.protocols.time.ntp]
> 575 [comp.programming.threads]
> 286 [comp.lang.xharbour]
> 121 [comp.os.linux.misc]
> 99 [comp.lang.clipper.visual-objects]
> 33 [comp.lang.cobol]
> 25 [comp.lang.forth]
> 25 [comp.dcom.sys.cisco]
> 19 [comp.lang.python]
> 15 [comp.lang.verilog]
> 6 [comp.sys.acorn.misc]
> 5 [comp.software.testing]
> 5 [comp.security.ssh]
> 5 [comp.os.msdos.djgpp]
> 4 [comp.lang.fortran]
> 3 [comp.os.vms]
> 2 [comp.protocols.tcp-ip]
> 2 [comp.protocols.kerberos]
> 2 [comp.editors]
> 1 [comp.text.pdf]
> 1 [comp.protocols.tcp-ip.domains]
> 1 [comp.protocols.nfs]
> 1 [comp.protocols.dicom]
> 1 [comp.mobile.android]
> 1 [comp.mail.sendmail]
> 1 [comp.lang.c++]
> 1 [comp.arch.embedded]

No comp.lang.lisp on your list. Accessing the group through news.cyber23.de
I see more than 100 spam posts for November. For example

<a2f6538f-c5de-4ea6-84e3-90dcb1c697fen@googlegroups.com>
<def987bb-dc46-4013-90cc-5acc5059dd2fn@googlegroups.com>
<239ec4f4-db6e-49b0-9eeb-20ea96555d24n@googlegroups.com>
<9e94afea-d3da-4769-9275-39d63ebf52a1n@googlegroups.com>
<aba4a884-d027-4350-9790-b1ceb11b7fecn@googlegroups.com>
<827b9b4a-083c-488e-8a83-8d1cb9b21bdcn@googlegroups.com>
<8669b073-56ff-4ce1-a14e-7c6fa6878d92n@googlegroups.com>
<5037d60d-018a-4b02-b66d-92fcb68fa481n@googlegroups.com>

On Fri, 3 Nov 2023 16:10:00 +0000
Serial Spammer <invalid@invalid.net> wrote:
> On 31/10/2023 13:04, Spiros Bousbouras wrote:
> > Checking on news.cyber23.de which I don't think does any filtering :
> They have taken a pragmatic approach.

Perhaps they have taken a conscious approach or perhaps they're not paying
attention.

> Filtering should be done by users on their own machines; It should not be
> imposed from the top!!

It's best to have choice i.e. some servers doing filtering and some servers
not and the users can access what they prefer.

> what is spam to one person is not necessarily spam to another.

On the other hand , some posts would be considered spam by everyone ; I give
some examples in <+hh3PVV=lTGp=902p@bongo-ra.co> .

On Fri, 3 Nov 2023 21:48:59 -0000 (UTC), gof-cut-this-news@cut-this-chmurka.net.invalid (Adam W.) wrote:
>D <J@m> wrote:
>
>> = 66322 . . . not sure if this is in reference/message id headers
>> containing "googlegroups.com" . . .
>
>It's only Thai spam, not everything from Google Groups. I keep two buffers
>for them, one 1 GiB and one 3 GiB, it's around 8 days.
>
>Class SPAM for groups matching "chmurka.spam.*"
> Buffer SPAM1, size: 1.00 GBytes, position: 581 MBytes 3.57 cycles
> Newest: 2023-11-03 22:46:01, 0 days, 0:01:37 ago
> Oldest: 2023-10-27 1:25:04, 7 days, 22:22:34 ago
> Buffer SPAM2, size: 3.00 GBytes, position: 112 kBytes 1.00 cycles
> Newest: 2023-11-02 7:39:04, 1 days, 15:08:34 ago
> Oldest: 2023-10-26 18:43:02, 8 days, 5:04:36 ago

a contributor to alt.comp.freeware <ui55ib$3ap9c$2@dont-email.me> wrote:
> I just went to Google Groups in my browser and was able to read ACF's
> current posts without any problem. Looks to me that there isn't any
> lockdown.
[end quote]

seems google is in "regroup" mode, with occasional "lockdowns" just to
be on the safe side . . .

In article <+hh3PVV=lTGp=902p@bongo-ra.co>,
Spiros Bousbouras <spibou@gmail.com> wrote:
>On Fri, 3 Nov 2023 12:08:59 -0000 (UTC)
>gof-cut-this-news@cut-this-chmurka.net.invalid (Adam W.) wrote:
>> Spiros Bousbouras <spibou@gmail.com> wrote:
>>
>> > Checking on news.cyber23.de which I don't think does any filtering :
>>
>> Let's try my spam group for comp.* for November...
>>
>> It looks they moved mostly to comp.cad.cadence.
>>
>> [news@kvm ~]$ tdx-util -o -n chmurka.spam.comp.thai | grep 'Nov 2023'
>| awk '{print $2}' | sort | uniq -c | sort -gr
>> 50656 [comp.cad.cadence]
>
>Scary.
>
>> 5517 [comp.ai.neural-nets]
>> 4694 [comp.text.tex]
>> 2608 [comp.theory]
>> 813 [comp.databases]
>> 794 [comp.protocols.time.ntp]
>> 575 [comp.programming.threads]
>> 286 [comp.lang.xharbour]
>> 121 [comp.os.linux.misc]
>> 99 [comp.lang.clipper.visual-objects]
>> 33 [comp.lang.cobol]
>> 25 [comp.lang.forth]
>> 25 [comp.dcom.sys.cisco]
>> 19 [comp.lang.python]
>> 15 [comp.lang.verilog]
>> 6 [comp.sys.acorn.misc]
>> 5 [comp.software.testing]
>> 5 [comp.security.ssh]
>> 5 [comp.os.msdos.djgpp]
>> 4 [comp.lang.fortran]
>> 3 [comp.os.vms]
>> 2 [comp.protocols.tcp-ip]
>> 2 [comp.protocols.kerberos]
>> 2 [comp.editors]
>> 1 [comp.text.pdf]
>> 1 [comp.protocols.tcp-ip.domains]
>> 1 [comp.protocols.nfs]
>> 1 [comp.protocols.dicom]
>> 1 [comp.mobile.android]
>> 1 [comp.mail.sendmail]
>> 1 [comp.lang.c++]
>> 1 [comp.arch.embedded]
>
>No comp.lang.lisp on your list. Accessing the group through news.cyber23.de
>I see more than 100 spam posts for November. For example
>
><a2f6538f-c5de-4ea6-84e3-90dcb1c697fen@googlegroups.com>
><def987bb-dc46-4013-90cc-5acc5059dd2fn@googlegroups.com>
><239ec4f4-db6e-49b0-9eeb-20ea96555d24n@googlegroups.com>
><9e94afea-d3da-4769-9275-39d63ebf52a1n@googlegroups.com>
><aba4a884-d027-4350-9790-b1ceb11b7fecn@googlegroups.com>
><827b9b4a-083c-488e-8a83-8d1cb9b21bdcn@googlegroups.com>
><8669b073-56ff-4ce1-a14e-7c6fa6878d92n@googlegroups.com>
><5037d60d-018a-4b02-b66d-92fcb68fa481n@googlegroups.com>

More reason to depeer Google GRoups now!
--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
If we are running from truth, we cannot be approaching God. -unknown Beware https://mindspring.com

Spiros Bousbouras <spibou@gmail.com> wrote:

>> 50656 [comp.cad.cadence]
>
> Scary.

It is indeed...

> No comp.lang.lisp on your list. Accessing the group through news.cyber23.de
> I see more than 100 spam posts for November. For example
>
> <a2f6538f-c5de-4ea6-84e3-90dcb1c697fen@googlegroups.com>
> <def987bb-dc46-4013-90cc-5acc5059dd2fn@googlegroups.com>
> <239ec4f4-db6e-49b0-9eeb-20ea96555d24n@googlegroups.com>
> <9e94afea-d3da-4769-9275-39d63ebf52a1n@googlegroups.com>
> <aba4a884-d027-4350-9790-b1ceb11b7fecn@googlegroups.com>
> <827b9b4a-083c-488e-8a83-8d1cb9b21bdcn@googlegroups.com>
> <8669b073-56ff-4ce1-a14e-7c6fa6878d92n@googlegroups.com>
> <5037d60d-018a-4b02-b66d-92fcb68fa481n@googlegroups.com>

This is a different kind of spam than the one my filter catches. It might
be good to add it as well (but to a different filter) though...

<ui8tcr$4epd$1@dont-email.me> : "in addition, now Google Groups is requiring
a CAPTCHA to post to any other group." .

This is good news , I hope they keep this measure.

On Mon, 6 Nov 2023 11:50:49 -0000 (UTC), gof-cut-this-news@cut-this-chmurka.net.invalid (Adam W.) wrote:
>Spiros Bousbouras <spibou@gmail.com> wrote:
>>> 50656 [comp.cad.cadence]
>>
>> Scary.
>
>It is indeed...

one hundred thirty thousand (130054) googlespams inundating
<comp.cad.cadence> since 6 Oct 2023 (within the past month)
and counting . . . so what's new? such is normal for google
because they know that no one in the universe has the power
to stop them . . . thus power and corruption are synonymous

>> No comp.lang.lisp on your list. Accessing the group through news.cyber23.de
>> I see more than 100 spam posts for November. For example
>>
>> <a2f6538f-c5de-4ea6-84e3-90dcb1c697fen@googlegroups.com>
Content-Type: text/plain; charset="UTF-8"
"Indonsian - Detected
Link Mudah Akses Terpercaya :"
(followed by 11 "https://..." links; repeats 22 times)
Kekayaan alat musik tradisional Israel adalah cerminan..."
ditto . . .
>> <def987bb-dc46-4013-90cc-5acc5059dd2fn@googlegroups.com>
>> <239ec4f4-db6e-49b0-9eeb-20ea96555d24n@googlegroups.com>
>> <9e94afea-d3da-4769-9275-39d63ebf52a1n@googlegroups.com>
>> <aba4a884-d027-4350-9790-b1ceb11b7fecn@googlegroups.com>
>> <827b9b4a-083c-488e-8a83-8d1cb9b21bdcn@googlegroups.com>
>> <8669b073-56ff-4ce1-a14e-7c6fa6878d92n@googlegroups.com>
>> <5037d60d-018a-4b02-b66d-92fcb68fa481n@googlegroups.com>
>
>This is a different kind of spam than the one my filter catches. It might
>be good to add it as well (but to a different filter) though...

google admins should do the right thing and pull the plug

Le 06/11/2023 à 14:38, Spiros Bousbouras a écrit :

> <ui8tcr$4epd$1@dont-email.me> : "in addition, now Google Groups is requiring
> a CAPTCHA to post to any other group." .

> This is good news , I hope they keep this measure.

So they can do something to improve Google Groups, if a certain number of
people ask them to.

On 11/4/23 08:46, D wrote:
> On Fri, 3 Nov 2023 21:48:59 -0000 (UTC), gof-cut-this-news@cut-this-chmurka.net.invalid (Adam W.) wrote:
>> D <J@m> wrote:
>>
>>> = 66322 . . . not sure if this is in reference/message id headers
>>> containing "googlegroups.com" . . .
>>
>> It's only Thai spam, not everything from Google Groups. I keep two buffers
>> for them, one 1 GiB and one 3 GiB, it's around 8 days.
>>
>> Class SPAM for groups matching "chmurka.spam.*"
>> Buffer SPAM1, size: 1.00 GBytes, position: 581 MBytes 3.57 cycles
>> Newest: 2023-11-03 22:46:01, 0 days, 0:01:37 ago
>> Oldest: 2023-10-27 1:25:04, 7 days, 22:22:34 ago
>> Buffer SPAM2, size: 3.00 GBytes, position: 112 kBytes 1.00 cycles
>> Newest: 2023-11-02 7:39:04, 1 days, 15:08:34 ago
>> Oldest: 2023-10-26 18:43:02, 8 days, 5:04:36 ago
>
> a contributor to alt.comp.freeware <ui55ib$3ap9c$2@dont-email.me> wrote:
>> I just went to Google Groups in my browser and was able to read ACF's
>> current posts without any problem. Looks to me that there isn't any
>> lockdown.
> [end quote]
>
> seems google is in "regroup" mode, with occasional "lockdowns" just to
> be on the safe side . . .
>

They're probably going to continue to lock down groups at random.
--
user <candycane> is generated from /dev/urandom

On Mon, 06 Nov 23 14:37:46 +0000, Eric M <conanospamic@gmail.com> wrote:
>Le 06/11/2023 a 14:38, Spiros Bousbouras a ecrit :
>> <ui8tcr$4epd$1@dont-email.me> : "in addition, now Google Groups is requiring
>> a CAPTCHA to post to any other group." .
>
>> This is good news , I hope they keep this measure.
>
>So they can do something to improve Google Groups, if a certain number of
>people ask them to.

when the universal googlespam flood stops permanently never to be
seen nor heard from again, then and only then shall everyone know
for a fact that this news is more than gossip or wishful thinking;
but to be pollyannaish and google does summarily cease and desist
from their reign of terror, then that could set the precedent for
other violators to more strictly limit posting or else, read-only;
of course the psyops troll farms can't be stopped, but then again . . .

In article <YXVdbZTgPvu83LftE@bongo-ra.co>,
Spiros Bousbouras <spibou@gmail.com> wrote:
><ui8tcr$4epd$1@dont-email.me> : "in addition, now Google Groups is requiring
>a CAPTCHA to post to any other group." .
>
>This is good news , I hope they keep this measure.

They should make every post a captcha!
--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
Suffering will continue until we stop believing lies. -unknown Beware https://mindspring.com

In article <dbb94f49eb30ce8b0e04ccd607ee138b@dizum.com>, D <J@M> wrote:
>On Mon, 6 Nov 2023 11:50:49 -0000 (UTC),
>gof-cut-this-news@cut-this-chmurka.net.invalid (Adam W.) wrote:
>>Spiros Bousbouras <spibou@gmail.com> wrote:
>>>> 50656 [comp.cad.cadence]
>>>
>>> Scary.
>>
>>It is indeed...
>
>one hundred thirty thousand (130054) googlespams inundating
><comp.cad.cadence> since 6 Oct 2023 (within the past month)
>and counting . . . so what's new? such is normal for google
>because they know that no one in the universe has the power
>to stop them . . . thus power and corruption are synonymous
>
>>> No comp.lang.lisp on your list. Accessing the group through
>news.cyber23.de
>>> I see more than 100 spam posts for November. For example
>>>
>>> <a2f6538f-c5de-4ea6-84e3-90dcb1c697fen@googlegroups.com>
> Content-Type: text/plain; charset="UTF-8"
> "Indonsian - Detected
> Link Mudah Akses Terpercaya :"
> (followed by 11 "https://..." links; repeats 22 times)
> Kekayaan alat musik tradisional Israel adalah cerminan..."
>ditto . . .
>>> <def987bb-dc46-4013-90cc-5acc5059dd2fn@googlegroups.com>
>>> <239ec4f4-db6e-49b0-9eeb-20ea96555d24n@googlegroups.com>
>>> <9e94afea-d3da-4769-9275-39d63ebf52a1n@googlegroups.com>
>>> <aba4a884-d027-4350-9790-b1ceb11b7fecn@googlegroups.com>
>>> <827b9b4a-083c-488e-8a83-8d1cb9b21bdcn@googlegroups.com>
>>> <8669b073-56ff-4ce1-a14e-7c6fa6878d92n@googlegroups.com>
>>> <5037d60d-018a-4b02-b66d-92fcb68fa481n@googlegroups.com>
>>
>>This is a different kind of spam than the one my filter catches. It might
>>be good to add it as well (but to a different filter) though...
>
>google admins should do the right thing and pull the plug
>

Depeer Google Groups now!
--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
Suffering will continue until we stop believing lies. -unknown Beware https://mindspring.com

In article <Wv33_1awwf_k-ZbUkYdot0APVUg@jntp>,
Eric M <conanospamic@gmail.com> wrote:
>Le 06/11/2023 à 14:38, Spiros Bousbouras a écrit :
>
>> <ui8tcr$4epd$1@dont-email.me> : "in addition, now Google Groups is requiring
>> a CAPTCHA to post to any other group." .
>
>> This is good news , I hope they keep this measure.
>
>So they can do something to improve Google Groups, if a certain number of
>people ask them to.

If anyone is listening!
--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
Suffering will continue until we stop believing lies. -unknown Beware https://mindspring.com

In article <uib1co$gukb$2@dont-email.me>,
candycanearter07 <no@thanks.net> wrote:
>On 11/4/23 08:46, D wrote:
>> On Fri, 3 Nov 2023 21:48:59 -0000 (UTC),
>gof-cut-this-news@cut-this-chmurka.net.invalid (Adam W.) wrote:
>>> D <J@m> wrote:
>>>
>>>> = 66322 . . . not sure if this is in reference/message id headers
>>>> containing "googlegroups.com" . . .
>>>
>>> It's only Thai spam, not everything from Google Groups. I keep two buffers
>>> for them, one 1 GiB and one 3 GiB, it's around 8 days.
>>>
>>> Class SPAM for groups matching "chmurka.spam.*"
>>> Buffer SPAM1, size: 1.00 GBytes, position: 581 MBytes 3.57 cycles
>>> Newest: 2023-11-03 22:46:01, 0 days, 0:01:37 ago
>>> Oldest: 2023-10-27 1:25:04, 7 days, 22:22:34 ago
>>> Buffer SPAM2, size: 3.00 GBytes, position: 112 kBytes 1.00 cycles
>>> Newest: 2023-11-02 7:39:04, 1 days, 15:08:34 ago
>>> Oldest: 2023-10-26 18:43:02, 8 days, 5:04:36 ago
>>
>> a contributor to alt.comp.freeware <ui55ib$3ap9c$2@dont-email.me> wrote:
>>> I just went to Google Groups in my browser and was able to read ACF's
>>> current posts without any problem. Looks to me that there isn't any
>>> lockdown.
>> [end quote]
>>
>> seems google is in "regroup" mode, with occasional "lockdowns" just to
>> be on the safe side . . .
>>
>
>They're probably going to continue to lock down groups at random.
>--
>user <candycane> is generated from /dev/urandom
>

GG should be read-only on the USEnet side!
--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
Suffering will continue until we stop believing lies. -unknown Beware https://mindspring.com

In article <36998a8b33db23ec53ea67da8f2ec2e7@dizum.com>, D <J@M> wrote:
>On Mon, 06 Nov 23 14:37:46 +0000, Eric M <conanospamic@gmail.com> wrote:
>>Le 06/11/2023 a 14:38, Spiros Bousbouras a ecrit :
>>> <ui8tcr$4epd$1@dont-email.me> : "in addition, now Google Groups is requiring
>>> a CAPTCHA to post to any other group." .
>>
>>> This is good news , I hope they keep this measure.
>>
>>So they can do something to improve Google Groups, if a certain number of
>>people ask them to.
>
>when the universal googlespam flood stops permanently never to be
>seen nor heard from again, then and only then shall everyone know
>for a fact that this news is more than gossip or wishful thinking;
>but to be pollyannaish and google does summarily cease and desist
>from their reign of terror, then that could set the precedent for
>other violators to more strictly limit posting or else, read-only;
>of course the psyops troll farms can't be stopped, but then again . . .
>

Given this from my innreports

Unwanted sites in Path header field [Top 20]:
Site Count
google-groups.googlegroups.com 51525
news.neodome.net 1472
news.mixmin.net 1180
news.newsdemon.com 426
TOTAL: 4 54603

Source https://ns2.nk.ca/news-notice.2023.11.05-01.00.00.html
--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
Suffering will continue until we stop believing lies. -unknown Beware https://mindspring.com

On 11/6/23 10:22, The Doctor wrote:
> In article <uib1co$gukb$2@dont-email.me>,
> candycanearter07 <no@thanks.net> wrote:
>> On 11/4/23 08:46, D wrote:
>>> seems google is in "regroup" mode, with occasional "lockdowns" just to
>>> be on the safe side . . .
>>>
>>
>> They're probably going to continue to lock down groups at random.
>> --
>> user <candycane> is generated from /dev/urandom
>>
>
> GG should be read-only on the USEnet side!

I agree, but this halfhearted attempt is worse than just leaving it all
unlocked.
--
user <candycane> is generated from /dev/urandom

On Mon, 6 Nov 2023 16:21:24 -0000 (UTC), doctor@doctor.nl2k.ab.ca (The Doctor) wrote:
>In article <YXVdbZTgPvu83LftE@bongo-ra.co>,
>Spiros Bousbouras <spibou@gmail.com> wrote:
>><ui8tcr$4epd$1@dont-email.me> : "in addition, now Google Groups is requiring
>>a CAPTCHA to post to any other group." .
>>
>>This is good news , I hope they keep this measure.
>
>They should make every post a captcha!

+1 . . . but could that work without overloading the gigantic google
server systems with untold myriads, maybe millions of daily requests?

On Mon, 6 Nov 2023 16:23:52 -0000 (UTC), doctor@doctor.nl2k.ab.ca (The Doctor) wrote:
>In article <36998a8b33db23ec53ea67da8f2ec2e7@dizum.com>, D <J@M> wrote:
>>On Mon, 06 Nov 23 14:37:46 +0000, Eric M <conanospamic@gmail.com> wrote:
>>>Le 06/11/2023 a 14:38, Spiros Bousbouras a ecrit :
>>>> <ui8tcr$4epd$1@dont-email.me> : "in addition, now Google Groups is requiring
>>>> a CAPTCHA to post to any other group." .
>>>
>>>> This is good news , I hope they keep this measure.
>>>
>>>So they can do something to improve Google Groups, if a certain number of
>>>people ask them to.
>>
>>when the universal googlespam flood stops permanently never to be
>>seen nor heard from again, then and only then shall everyone know
>>for a fact that this news is more than gossip or wishful thinking;
>>but to be pollyannaish and google does summarily cease and desist
>>from their reign of terror, then that could set the precedent for
>>other violators to more strictly limit posting or else, read-only;
>>of course the psyops troll farms can't be stopped, but then again . . .
>
>Given this from my innreports
>Unwanted sites in Path header field [Top 20]:
>Site Count
>google-groups.googlegroups.com 51525
>news.neodome.net 1472
>news.mixmin.net 1180
>news.newsdemon.com 426
>TOTAL: 4 54603
>
>Source https://ns2.nk.ca/news-notice.2023.11.05-01.00.00.html

only four "unwanted sites"? four dozen would make better sense in
whatever context (they) (https://www.whois.com/whois/nk.ca) might
be interested in . . . at least the gold medal was awarded google