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.
--
Some people say that it's cheating to just transfer the contents of your dreams
into a novel. But I say that transcribing what occurs in reality is cheating.
Yasutaka Tsutsui , author of "Paprika".
On Tue, 31 Oct 2023 13:04:15 -0000 (UTC), Spiros Bousbouras ><spibou@gmail.com> 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.
and what percentage are ghoul goo . . . ninety-eight . . . ninety-nine ?
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.
Le 31/10/2023 à 14:04, Spiros Bousbouras a écrit :
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 keep reporting spam on this groups, maybe it works only if many people
do it. You can select up to 30 threads in a page so it's easy to report a
few thousand messages (takes 2 minutes a day).
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.
In article <6b6bc8ee5d2588a14f752bf700322a9b@dizum.com>, D <J@M> wrote:
On Tue, 31 Oct 2023 13:04:15 -0000 (UTC), Spiros Bousbouras >><spibou@gmail.com> 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.
and what percentage are ghoul goo . . . ninety-eight . . . ninety-nine ?
Good one GG is Ghoul Goo!
On Tue, 31 Oct 2023 13:04:15 -0000 (UTC), Spiros Bousbouras <spibou@gmail.com> 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.
and what percentage are ghoul goo . . . ninety-eight . . . ninety-nine ?
In article <EvJxBywITbfdDd2ZG@bongo-ra.co>,
Spiros Bousbouras <spibou@gmail.com> 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.
Check!
comp.lang.fortran , comp.arch , sci.lang.japan : a lot.
GG ban justified
comp.lang.cobol : spam has stopped , there was a lot until October 25th.
All right.
comp.lang.forth : a bit of spam.
bit?
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.
The best solution: Depeer Google GRoups from Usenet
and teach Google a Lesson in Manners!
Le 31/10/2023 14:04, Spiros Bousbouras a écrit :
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 keep reporting spam on this groups, maybe it works only if many people
do it. You can select up to 30 threads in a page so it's easy to report a
few thousand messages (takes 2 minutes a day).
I keep reporting spam on this groups, maybe it works only if many people
do it. You can select up to 30 threads in a page so it's easy to report a
few thousand messages (takes 2 minutes a day).
Reporting it where ? If you mean reporting it through the googlegroups interface , it's a waste of time as the experience of many people over
many years (and also in the last few weeks) has shown. It only affects
what is shown to the person who did the reporting when they are logged
in to their Google account , nothing more than that.
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.
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.
On Tue, 31 Oct 2023 14:33:04 +0100 (CET)
D <J@M> wrote:
On Tue, 31 Oct 2023 13:04:15 -0000 (UTC), Spiros Bousbouras <spibou@gmail.com> 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.
and what percentage are ghoul goo . . . ninety-eight . . . ninety-nine ?
Taking a random sample and also taking into account recent experience ,
I would say 100% .
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.
On Tue, 31 Oct 2023 13:54:34 -0000 (UTC)
doctor@doctor.nl2k.ab.ca (The Doctor) wrote:
In article <EvJxBywITbfdDd2ZG@bongo-ra.co>,For today (October 31st) I only see 2 spam posts. There are a few others >where someone is trying to convince people to continue Forth discussion
Spiros Bousbouras <spibou@gmail.com> wrote:
Checking on news.cyber23.de which I don't think does any filtering :Check!
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.GG ban justified
comp.lang.cobol : spam has stopped , there was a lot until October 25th.All right.
comp.lang.forth : a bit of spam.bit?
on facebook (oh dear) but these are from a legitimate poster in general.
Also deapple , dewatermelon and , ideally , de<all other fruit> .comp.misc : never got any spam with the recent flood.The best solution: Depeer Google GRoups from Usenet
I wonder if the spammers have a plan or it's random to a large extent.
and teach Google a Lesson in Manners!
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.
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...)
On Tue, 31 Oct 2023 14:33:04 +0100 (CET)
D <J@M> wrote:
On Tue, 31 Oct 2023 13:04:15 -0000 (UTC), Spiros Bousbouras ><spibou@gmail.com> 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.
and what percentage are ghoul goo . . . ninety-eight . . . ninety-nine ?
Taking a random sample and also taking into account recent experience ,
I would say 100% .
On Tue, 31 Oct 2023 13:54:58 -0000 (UTC), doctor@doctor.nl2k.ab.ca (The >Doctor) wrote:
In article <6b6bc8ee5d2588a14f752bf700322a9b@dizum.com>, D <J@M> wrote: >>>On Tue, 31 Oct 2023 13:04:15 -0000 (UTC), Spiros Bousbouras >>><spibou@gmail.com> 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.
and what percentage are ghoul goo . . . ninety-eight . . . ninety-nine ?
Good one GG is Ghoul Goo!
Noun: ghoul goo(-u)l
1. Someone who takes bodies from graves and sells them for
anatomical dissection
2. An evil spirit or ghost
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.
On Tue, 31 Oct 2023 15:43:47 -0000 (UTC), Spiros Bousbouras ><spibou@gmail.com> wrote:
On Tue, 31 Oct 2023 14:33:04 +0100 (CET)
D <J@M> wrote:
On Tue, 31 Oct 2023 13:04:15 -0000 (UTC), Spiros Bousbouras ><spibou@gmail.com> 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.
and what percentage are ghoul goo . . . ninety-eight . . . ninety-nine ?
Taking a random sample and also taking into account recent experience ,
I would say 100% .
even that seems unusual, compared with other popular newsgroups that
have been routinely infiltrated and occupied by recurring troll farm >characters posting from non-google servers . . . but 100% seems like
a waste of google's inexhaustible resources to flood dead newsgroups,
unless part of their apparently top-secret mission is to burden nntp
news servers along with those subscribing to newsgroups with as much
ugliness as they can possibly muster . . . and nobody does that like
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.
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.
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 : >>>>>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...)
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. >>>>
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.
Checking on news.cyber23.de which I don't think does any filtering :
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!
Checking on news.cyber23.de which I don't think does any filtering :
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.
= 66322 . . . not sure if this is in reference/message id headers
containing "googlegroups.com" . . .
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.
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]
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
I just went to Google Groups in my browser and was able to read ACF's[end quote]
current posts without any problem. Looks to me that there isn't any
lockdown.
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:| awk '{print $2}' | sort | uniq -c | sort -gr
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'
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>
50656 [comp.cad.cadence]
Scary.
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>
Spiros Bousbouras <spibou@gmail.com> wrote:
50656 [comp.cad.cadence]
Scary.
It is indeed...
Content-Type: text/plain; charset="UTF-8"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.
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.
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[end quote]
current posts without any problem. Looks to me that there isn't any
lockdown.
seems google is in "regroup" mode, with occasional "lockdowns" just to
be on the safe side . . .
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
Content-Type: text/plain; charset="UTF-8"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>
"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[end quote]
current posts without any problem. Looks to me that there isn't any
lockdown.
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 <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!
<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.
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
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!
So they can do something to improve Google Groups, if a certain number of
people ask them to.
If anyone is listening!
Le 06/11/2023 a 17:22, doctor@doctor.nl2k.ab.ca (The Doctor) a ecrit :
So they can do something to improve Google Groups, if a certain number of >>> people ask them to.
If anyone is listening!
I'm not totally against your idea of depeering Google but I'm afraid they >will always find a feed, so we need to live with them. And if we can >collectively talk to them, maybe they will listen more than if it's a
single user.
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
Le 06/11/2023 à 17:22, doctor@doctor.nl2k.ab.ca (The Doctor) a écrit :
So they can do something to improve Google Groups, if a certain number of >>> people ask them to.
If anyone is listening!
I'm not totally against your idea of depeering Google but I'm afraid they >will always find a feed, so we need to live with them. And if we can >collectively talk to them, maybe they will listen more than if it's a
single user.
On Mon, 06 Nov 23 20:32:39 +0000, Eric M <conanospamic@gmail.com> wrote:
Le 06/11/2023 a 17:22, doctor@doctor.nl2k.ab.ca (The Doctor) a ecrit :
So they can do something to improve Google Groups, if a certain number of >>>> people ask them to.
If anyone is listening!
I'm not totally against your idea of depeering Google but I'm afraid they >>will always find a feed, so we need to live with them. And if we can >>collectively talk to them, maybe they will listen more than if it's a >>single user.
a group seance might work better if everyone is holding hands while
the medium makes tries to make contact, which almost never actually
occurs, but who knows . . . one out of a googol of tries might work?
On Mon, 06 Nov 23 20:32:39 +0000, Eric M <conanospamic@gmail.com> wrote:
Le 06/11/2023 a 17:22, doctor@doctor.nl2k.ab.ca (The Doctor) a ecrit :
So they can do something to improve Google Groups, if a certain number of >>>> people ask them to.
If anyone is listening!
I'm not totally against your idea of depeering Google but I'm afraid they
will always find a feed, so we need to live with them. And if we can
collectively talk to them, maybe they will listen more than if it's a
single user.
a group seance might work better if everyone is holding hands while
the medium makes tries to make contact, which almost never actually
occurs, but who knows . . . one out of a googol of tries might work?
On 11/6/23 15:19, D wrote:
On Mon, 06 Nov 23 20:32:39 +0000, Eric M <conanospamic@gmail.com> wrote:
Le 06/11/2023 a 17:22, doctor@doctor.nl2k.ab.ca (The Doctor) a ecrit : >>>>> So they can do something to improve Google Groups, if a certain number of >>>>> people ask them to.
If anyone is listening!I'm not totally against your idea of depeering Google but I'm afraid they >>> will always find a feed, so we need to live with them. And if we can
collectively talk to them, maybe they will listen more than if it's a
single user.
a group seance might work better if everyone is holding hands while
the medium makes tries to make contact, which almost never actually
occurs, but who knows . . . one out of a googol of tries might work?
HA, 1/googol chance. Good pun.
On 11/6/23 15:19, D wrote:
On Mon, 06 Nov 23 20:32:39 +0000, Eric M <conanospamic@gmail.com> wrote:
Le 06/11/2023 a 17:22, doctor@doctor.nl2k.ab.ca (The Doctor) a ecrit :
So they can do something to improve Google Groups, if a certain number of >>>>> people ask them to.
If anyone is listening!
I'm not totally against your idea of depeering Google but I'm afraid they >>> will always find a feed, so we need to live with them. And if we can
collectively talk to them, maybe they will listen more than if it's a
single user.
a group seance might work better if everyone is holding hands while
the medium makes tries to make contact, which almost never actually
occurs, but who knows . . . one out of a googol of tries might work?
HA, 1/googol chance. Good pun.
--
user <candycane> is generated from /dev/urandom
On Tue, 7 Nov 2023 03:16:18 -0600, candycanearter07 <no@thanks.net> wrote:
On 11/6/23 15:19, D wrote:
On Mon, 06 Nov 23 20:32:39 +0000, Eric M <conanospamic@gmail.com> wrote: >>>> Le 06/11/2023 a 17:22, doctor@doctor.nl2k.ab.ca (The Doctor) a ecrit : >>>>>> So they can do something to improve Google Groups, if a certain number of
I'm not totally against your idea of depeering Google but I'm afraid they >>>> will always find a feed, so we need to live with them. And if we canpeople ask them to.If anyone is listening!
collectively talk to them, maybe they will listen more than if it's a
single user.
a group seance might work better if everyone is holding hands while
the medium makes tries to make contact, which almost never actually
occurs, but who knows . . . one out of a googol of tries might work?
HA, 1/googol chance. Good pun.
maybe, but then again . . . what are the real chances of mere mortals conversing with the gods? like the old wailing wall joke "oy vey it's
like talking to a brick wall!" but the seance was en vogue in the 20s
when the namesake "google" already had his character in the limelight
On 11/7/23 07:54, D wrote:
On Tue, 7 Nov 2023 03:16:18 -0600, candycanearter07 <no@thanks.net> wrote: >>> On 11/6/23 15:19, D wrote:
On Mon, 06 Nov 23 20:32:39 +0000, Eric M <conanospamic@gmail.com> wrote: >>>>> Le 06/11/2023 a 17:22, doctor@doctor.nl2k.ab.ca (The Doctor) a ecrit : >>>>>>> So they can do something to improve Google Groups, if a certain number ofHA, 1/googol chance. Good pun.
a group seance might work better if everyone is holding hands whileI'm not totally against your idea of depeering Google but I'm afraid they >>>>> will always find a feed, so we need to live with them. And if we can >>>>> collectively talk to them, maybe they will listen more than if it's a >>>>> single user.people ask them to.If anyone is listening!
the medium makes tries to make contact, which almost never actually
occurs, but who knows . . . one out of a googol of tries might work?
maybe, but then again . . . what are the real chances of mere mortals
conversing with the gods? like the old wailing wall joke "oy vey it's
like talking to a brick wall!" but the seance was en vogue in the 20s
when the namesake "google" already had his character in the limelight
True, there's no chance of talking with the higher ups.
BUT, maybe with
enough activism, you could get some kinda response..
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 49:59:29 |
| Calls: | 10,397 |
| Calls today: | 5 |
| Files: | 14,067 |
| Messages: | 6,417,314 |
| Posted today: | 1 |
