On Thu, 5 Oct 2023 00:02:47 +0200, Opus <ifonly@youknew.org> wrote:

>On 04/10/2023 22:22, Joe Pfeiffer wrote:
>> Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> writes:
>>
>>> "luke.l...@gmail.com" <luke.leighton@gmail.com> writes:
>>>
>>>> awesome. does anyone know a "free" nntp server that's still
>>>> operational and not itself overloaded by spam?
>>>> (oh and as an added bonus, actually provides comp.arch
>>>> *and* allows postings?)
>>>
>>> news.eternal-september.org
>>>
>>> You may need to create an account to post.
>>
>> Sadly, no. That's the one I'm using, and I'm also getting Thaidal wave.
>
>Same here. Actually, since I switched to ES, the amount of spam I have
>run into has been much higher than what I had before. So I'm not sure ES
>is particularly good at filtering it. But certainly this recent Thai
>flood has been literally killing several newsgroups, which is why I
>wondered whether this was not the goal, as the potential revenue from
>this spam looks excessively questionable particularly on Usenet. Unless
>of course the idiocy factor is at play here and they are just spamming
>newsgroups not knowing what they are and what kind of people read them.
>
>So is that idiocy or malevolence? Bets are open.

Never ascribe to malice, that which can be explained by stupidity.
-- Robert J. Hanlon

Personally, I /always/ suspect malice when humans are involved.

George Neuner wrote:
> On Thu, 5 Oct 2023 00:02:47 +0200, Opus <ifonly@youknew.org> wrote:
>
>> On 04/10/2023 22:22, Joe Pfeiffer wrote:
>>> Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> writes:
>>>
>>>> "luke.l...@gmail.com" <luke.leighton@gmail.com> writes:
>>>>
>>>>> awesome. does anyone know a "free" nntp server that's still
>>>>> operational and not itself overloaded by spam?
>>>>> (oh and as an added bonus, actually provides comp.arch
>>>>> *and* allows postings?)
>>>>
>>>> news.eternal-september.org
>>>>
>>>> You may need to create an account to post.
>>>
>>> Sadly, no. That's the one I'm using, and I'm also getting Thaidal wave.
>>
>> Same here. Actually, since I switched to ES, the amount of spam I have
>> run into has been much higher than what I had before. So I'm not sure ES
>> is particularly good at filtering it. But certainly this recent Thai
>> flood has been literally killing several newsgroups, which is why I
>> wondered whether this was not the goal, as the potential revenue from
>> this spam looks excessively questionable particularly on Usenet. Unless
>> of course the idiocy factor is at play here and they are just spamming
>> newsgroups not knowing what they are and what kind of people read them.
>>
>> So is that idiocy or malevolence? Bets are open.
>
> Never ascribe to malice, that which can be explained by stupidity.
> -- Robert J. Hanlon
>
>
> Personally, I /always/ suspect malice when humans are involved.
>
I suspect malice, so that I can be positively surprised when it turns
out simple stupidity was the root cause.

Terje

--
- <Terje.Mathisen at tmsw.no>
"almost all programming can be viewed as an exercise in caching"

On 05/10/2023 00:02, Opus wrote:
> On 04/10/2023 22:22, Joe Pfeiffer wrote:
>> Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> writes:
>>
>>> "luke.l...@gmail.com" <luke.leighton@gmail.com> writes:
>>>
>>>> awesome. does anyone know a "free" nntp server that's still
>>>> operational and not itself overloaded by spam?
>>>> (oh and as an added bonus, actually provides comp.arch
>>>>   *and* allows postings?)
>>>
>>> news.eternal-september.org
>>>
>>> You may need to create an account to post.
>>
>> Sadly, no. That's the one I'm using, and I'm also getting Thaidal wave.
>
> Same here. Actually, since I switched to ES, the amount of spam I have
> run into has been much higher than what I had before. So I'm not sure ES
> is particularly good at filtering it.

eternal-september is a small operation - as far as I know, the server is
run primarily by one person, and there is no income from it other than
voluntary donations. They do have spam filters, but I suppose it
sometimes takes time to react if there is some new spamming variant or
method.

The level of spam I see on eternal-september has dropped off today. I
don't know if it is the filtering at the newserver that has been
updated, or if google has actually taken complaints seriously, or if the
spammers have moved on. I hope that it is gone for now.

> But certainly this recent Thai
> flood has been literally killing several newsgroups, which is why I
> wondered whether this was not the goal, as the potential revenue from
> this spam looks excessively questionable particularly on Usenet.

There is basically no potential revenue for this kind of spam in comp.*
groups. But there is also no financial incentive for destroying Usenet
groups - it is not as if killing comp.arch means we are all going to
move to Facebook, watch adverts and click on links for Thai language
betting sites.

Rumours of Usenet's death are greatly exaggerated - groups like these
will last as long as the people posting here. The real group killers
are always particular people, not spammers.

> Unless
> of course the idiocy factor is at play here and they are just spamming
> newsgroups not knowing what they are and what kind of people read them.
>
> So is that idiocy or malevolence? Bets are open.
>

My vote is for idiocy.

On Thursday, October 5, 2023 at 11:21:47 AM UTC+3, David Brown wrote:
>
> The level of spam I see on eternal-september has dropped off today. I
> don't know if it is the filtering at the newserver that has been
> updated, or if google has actually taken complaints seriously, or if the
> spammers have moved on. I hope that it is gone for now.

The level of spam I see on google groups today is low on comp.arch
(4 spam threads) but very high on comp.lang.c - approximately 70
spam messages per hour non-stop.

On 05/10/2023 11:52, Michael S wrote:
> On Thursday, October 5, 2023 at 11:21:47 AM UTC+3, David Brown wrote:
>>
>> The level of spam I see on eternal-september has dropped off today. I
>> don't know if it is the filtering at the newserver that has been
>> updated, or if google has actually taken complaints seriously, or if the
>> spammers have moved on. I hope that it is gone for now.
>
> The level of spam I see on google groups today is low on comp.arch
> (4 spam threads) but very high on comp.lang.c - approximately 70
> spam messages per hour non-stop.

On news.eternal-september.org, the spam is gone from comp.lang.c as well
as from comp.arch. If you are seeing it on google groups, and I am not
seeing it on news.eternal-september.org, then I guess that newsserver
has updating their filter rules.

(I suppose it's always possible that my Thunderbird message filters have
blocked it all, but I doubt it - it can filter based on particular words
in the subject or senders, but not on the content or the language. So
while the spam was at its worst, they only cut out about 30-50% of the
messages.)

On Thursday, October 5, 2023 at 3:54:40 PM UTC+3, David Brown wrote:
> On 05/10/2023 11:52, Michael S wrote:
> > On Thursday, October 5, 2023 at 11:21:47 AM UTC+3, David Brown wrote:
> >>
> >> The level of spam I see on eternal-september has dropped off today. I
> >> don't know if it is the filtering at the newserver that has been
> >> updated, or if google has actually taken complaints seriously, or if the
> >> spammers have moved on. I hope that it is gone for now.
> >
> > The level of spam I see on google groups today is low on comp.arch
> > (4 spam threads) but very high on comp.lang.c - approximately 70
> > spam messages per hour non-stop.
> On news.eternal-september.org, the spam is gone from comp.lang.c as well
> as from comp.arch. If you are seeing it on google groups, and I am not
> seeing it on news.eternal-september.org, then I guess that newsserver
> has updating their filter rules.
>
> (I suppose it's always possible that my Thunderbird message filters have
> blocked it all, but I doubt it - it can filter based on particular words
> in the subject or senders, but not on the content or the language. So
> while the spam was at its worst, they only cut out about 30-50% of the
> messages.)

Last spam message seen via GG on c.lang.c is from 40 minutes ago

Michael S <already5chosen@yahoo.com> writes:
>
> Last spam message seen via GG on c.lang.c is from 40 minutes ago

Another good reason to use e-s and not GG, apparently.

On Thursday, October 5, 2023 at 5:44:16 PM UTC+3, Joe Pfeiffer wrote:
> Michael S <already...@yahoo.com> writes:
> >
> > Last spam message seen via GG on c.lang.c is from 40 minutes ago
> Another good reason to use e-s and not GG, apparently.

What I see now on c.lang.c at much reduced rate of approximately 5 spam
messages per hour mostly is not a Thai UFABET spam, but mushroom spam.
UFABET spam did not disappear completely, but reduced to less than 1 message
per hour.

On Thursday, October 5, 2023 at 5:55:44 PM UTC+3, Michael S wrote:
> On Thursday, October 5, 2023 at 5:44:16 PM UTC+3, Joe Pfeiffer wrote:
> > Michael S <already...@yahoo.com> writes:
> > >
> > > Last spam message seen via GG on c.lang.c is from 40 minutes ago
> > Another good reason to use e-s and not GG, apparently.
> What I see now on c.lang.c at much reduced rate of approximately 5 spam
> messages per hour mostly is not a Thai UFABET spam, but mushroom spam.
> UFABET spam did not disappear completely, but reduced to less than 1 message
> per hour.

Few minutes after my previous post Thai UFABET spam at comp.lang.c
came back at highest rate ever.

David Brown <david.brown@hesbynett.no> schrieb:

> The level of spam I see on eternal-september has dropped off today. I
> don't know if it is the filtering at the newserver that has been
> updated, or if google has actually taken complaints seriously, or if the
> spammers have moved on. I hope that it is gone for now.

Usenet works differently.

It is possible to cancel or supersede an article, given its ID.
The cancel message will then be distributed across the network the
same way as a normal message. If a news server has the original
message, then it will be deleted; if it does not have it, it will
be marked as already present in the database, effectively limiting
its distribution. These will be distributed in the pseudo-newsgroup
"control".

Without safeguards in place, this system is prone to abuse,
people might want to (and did!) win an argument by cancelling
their opponent's article, so safeguards such as a signed cancel
can be used (but I never looked at the details, this was introduced
after I lost interest in Usenet administration).

It is generally considered to be OK to allow spam cancels, which
are then signed by people generally agreed not to abuse that power,
usually newsadmins. There is an objective metric, the Breidbart
index, for this.

So, all that news admins need to do is to allow the right spam cancels,
and things will be OK for them.

Google Groups probably disregards all that, as they disregard all
almost all things that make USENET a useful medium.

Michael S <already5chosen@yahoo.com> writes:
>On Thursday, October 5, 2023 at 5:55:44=E2=80=AFPM UTC+3, Michael S wrote:
>> On Thursday, October 5, 2023 at 5:44:16=E2=80=AFPM UTC+3, Joe Pfeiffer wr=
>ote:=20
>> > Michael S <already...@yahoo.com> writes:=20
>> > >=20
>> > > Last spam message seen via GG on c.lang.c is from 40 minutes ago=20
>> > Another good reason to use e-s and not GG, apparently.
>> What I see now on c.lang.c at much reduced rate of approximately 5 spam=
>=20
>> messages per hour mostly is not a Thai UFABET spam, but mushroom spam.=20
>> UFABET spam did not disappear completely, but reduced to less than 1 mess=
>age=20
>> per hour.
>
>Few minutes after my previous post Thai UFABET spam at comp.lang.c=20
>came back at highest rate ever.

It seems to be some attempt at SEO.

Still, since it seems since they did not quit, that we should do something
proactive to all the involved computers. Anyone have a DDS attack sitting
around ready to go ??

On Thursday, October 5, 2023 at 5:44:16 PM UTC+3, Joe Pfeiffer wrote:
> Michael S <already...@yahoo.com> writes:
> >
> > Last spam message seen via GG on c.lang.c is from 40 minutes ago
> Another good reason to use e-s and not GG, apparently.

Now on GG I see comp.arch not just without new spam, but with
old spam cleaned.
That's far better than I expected.

comp.lang.c continues to be bombed from both directions.

On Friday, October 6, 2023 at 12:53:38 PM UTC+1, Michael S wrote:

> Now on GG I see comp.arch not just without new spam, but with
> old spam cleaned.

awesome!

> That's far better than I expected.

ah jolly good, chrome stops asking "do i wish to translate thai" now.
> comp.lang.c continues to be bombed from both directions.

same trick would be interesting: ask multiple people to
run "report spam".

small favour to ask of the person who recommended xrn
(great to see athena widget toolkit still around, loved it
esp. the fact that you could run on *16* MB SunOS 4.1.3
workstations)

do you have a config setup (env vars, command-line options)
that successfully connects to eternal-september with a
registered user/pass?

i am trying "-authenticate user/pass lkcl/blahblah" and it's
not having any of it. if i connect with a GTK2-based nntp
client it works fine (i get the full uunet list)

tia,

l.

On Thu, 5 Oct 2023 16:03:15 -0000 (UTC), Thomas Koenig
<tkoenig@netcologne.de> wrote:

>David Brown <david.brown@hesbynett.no> schrieb:
>
>> The level of spam I see on eternal-september has dropped off today. I
>> don't know if it is the filtering at the newserver that has been
>> updated, or if google has actually taken complaints seriously, or if the
>> spammers have moved on. I hope that it is gone for now.
>
>Usenet works differently.
>
>It is possible to cancel or supersede an article, given its ID.
>The cancel message will then be distributed across the network the
>same way as a normal message. If a news server has the original
>message, then it will be deleted; if it does not have it, it will
>be marked as already present in the database, effectively limiting
>its distribution. These will be distributed in the pseudo-newsgroup
>"control".

Just a note pertaining to Eternal September because it has been
discussed here.

From their FAQ:

"
In general, our server does not execute Cancels and Supersedes. An
article stored on our server can neither be deleted by a Cancel nor be
overwritten by a Supersedes which means that an article deleted by a
Cancel message on other servers is still available on our server
(article is not deleted) and an article overwritten by a Supersedes
elsewhere is available on our server in more than one instance
(different versions of the article are not replaced).

But our server does honour the article headers "Cancel-Lock:" and
"Cancel-Key:" that create a verifiable connection between an article
and a corresponding Cancel/Supersedes. Users who add Cancel-Lock to
their articles and Cancel-Key to their Cancels/Supersedes can still
delete and replace articles on our server. For our own users, our
server automatically creates Cancel-Lock at posting time; a
Cancel-Lock already present at posting time (added by the user
himself) will be extended according to the technical specifications of
the system. Cancels and Supersedes through our server will
automatically get the corresponding Cancel-Key after verification and
will be executed.

Additionally, we maintain a whitelist of senders that contains
well-known Despammers ("professional" Spam Cancellers) so that we can
honour their desirable Spam Cancels and NoCeM Notices.
"

>Without safeguards in place, this system is prone to abuse,
>people might want to (and did!) win an argument by cancelling
>their opponent's article, so safeguards such as a signed cancel
>can be used (but I never looked at the details, this was introduced
>after I lost interest in Usenet administration).
>
>It is generally considered to be OK to allow spam cancels, which
>are then signed by people generally agreed not to abuse that power,
>usually newsadmins. There is an objective metric, the Breidbart
>index, for this.
>
>So, all that news admins need to do is to allow the right spam cancels,
>and things will be OK for them.
>
>Google Groups probably disregards all that, as they disregard all
>almost all things that make USENET a useful medium.

https://groups.google.com/g/eternal-september.support/c/n6YOor7dF0s/m/By89ZJcn5R0J

ah HA! advice on putting xrn*authenticateOnConnect: true in .Xdefaults.
awesome.

l.

"luke.l...@gmail.com" <luke.leighton@gmail.com> writes:
>small favour to ask of the person who recommended xrn
>(great to see athena widget toolkit still around, loved it
>esp. the fact that you could run on *16* MB SunOS 4.1.3
>workstations)

I use the following X resources (typically in ~/.Xresources,
use "xrdb -merge ~/.Xresources" after changing it):

XRn.authenticateOnConnect: true
XRn.authenticator: user/pass <user>/<password>
XRn.geometry: 880x1180
XRn*Command.font: -misc-fixed-medium-r-normal-*-15-*-*-*-*-*-iso8859-1
XRn.editorCommand: emacsclient %s
XRn.savePostings: ~/Articles
XRn.saveSentPostings: ~/Articles
XRn.saveSentMail: ~/Articles
XRn.sortedSubjects: thread,subject,date
XRn*printCommand: a2ps
XRn*artButtonList: artMarkUnread artMarkRead artCatchUp artQuit \
artThreadParent artNextUnread artNext artPrev artLast \
artNextGroup artFedUp artGotoArticle \
artUnsub artSubNext artSubPrev artThreadParent \
artListOld artResort artKillSubject artKillAuthor \
artKillThread artKillSubthread artSubSearch \
artContinue artPost artPostAndMail artExit artCheckPoint
XRn*artSpecButtonList: artSave artReply artForward artFollowup \
artCancel artRot13 artXlate artHeader \
artPrint
XRn*ngButtonList: ngCheckPoint ngRescan ngQuit ngRead ngNext ngPrev ngCatchUp ngSubscribe \
ngUnsub ngGoto ngAllGroups ngPrevGroup ngListOld \
ngSelect ngMove ngExit ngGripe ngPost \
ngPostAndMail
XRn.nntpServer: news.eternal-september.org
XRn.leaveHeaders: Message-ID, From, Subject, Reply-To, Date, Followup-To, Newsgroups

Replace <user> and <password>, and adjust the rest as desired.

- anton
--
'Anyone trying for "industrial quality" ISA should avoid undefined behavior.'
Mitch Alsup, <c17fcd89-f024-40e7-a594-88a85ac10d20o@googlegroups.com>

anton@mips.complang.tuwien.ac.at (Anton Ertl) writes:
>"luke.l...@gmail.com" <luke.leighton@gmail.com> writes:
>>small favour to ask of the person who recommended xrn
>>(great to see athena widget toolkit still around, loved it
>>esp. the fact that you could run on *16* MB SunOS 4.1.3
>>workstations)
>
>I use the following X resources (typically in ~/.Xresources,
>use "xrdb -merge ~/.Xresources" after changing it):
>
>XRn.authenticateOnConnect: true
>XRn.authenticator: user/pass <user>/<password>
>XRn.geometry: 880x1180
>XRn*Command.font: -misc-fixed-medium-r-normal-*-15-*-*-*-*-*-iso8859-1
>XRn.editorCommand: emacsclient %s
>XRn.savePostings: ~/Articles
>XRn.saveSentPostings: ~/Articles
>XRn.saveSentMail: ~/Articles
>XRn.sortedSubjects: thread,subject,date
>XRn*printCommand: a2ps
>XRn*artButtonList: artMarkUnread artMarkRead artCatchUp artQuit \
> artThreadParent artNextUnread artNext artPrev artLast \
> artNextGroup artFedUp artGotoArticle \
> artUnsub artSubNext artSubPrev artThreadParent \
> artListOld artResort artKillSubject artKillAuthor \
> artKillThread artKillSubthread artSubSearch \
> artContinue artPost artPostAndMail artExit artCheckPoint
>XRn*artSpecButtonList: artSave artReply artForward artFollowup \
> artCancel artRot13 artXlate artHeader \
> artPrint
>XRn*ngButtonList: ngCheckPoint ngRescan ngQuit ngRead ngNext ngPrev ngCatchUp ngSubscribe \
> ngUnsub ngGoto ngAllGroups ngPrevGroup ngListOld \
> ngSelect ngMove ngExit ngGripe ngPost \
> ngPostAndMail
>XRn.nntpServer: news.eternal-september.org
>XRn.leaveHeaders: Message-ID, From, Subject, Reply-To, Date, Followup-To, Newsgroups
>
>Replace <user> and <password>, and adjust the rest as desired.

Here's the set I've been using since 1989. Note that these override the
application defaults (/usr/share/X11/app-defaults/XRn).

XRn*iconGeometry: +4+186
XRn.geometry: 930x1000+100+-10
XRn*Composition.geometry: 887x684+134+82
XRn*verifyFrom: false
XRn.topLines: 10
XRn.stripHeaders: Path,Message-ID,References
XRn.saveMode: noheaders,subdir
XRn.sortedSubjects: thread,subject,date
XRn.rescanTime: 3600
XRn.updateNewsrc: on
XRn.pageArticles: on
XRn.defaultsFound: on
XRn*Geometry: +0+0
XRn.Geometry: 1024x800
XRn*font: -adobe-courier-medium-r-normal--14-140-75-75-m-90-iso8859-1
XRn*Label.font: 8x13
XRn*Command.font: 8x13
XRn*Dialog.borderWidth: 1
XRn.replyTo: user@domain.example
XRn*index*cursor: left_ptr
XRn.artButtonList: artQuit,artNextUnread,artNextGroup,artCatchUp,artFedUp,artGotoArticle,artMarkRead,artMarkUnread,artPost,artExit,artListOld,artThreadParent,artResort,artSubSearch,artContinue
XRn*cacheActive: true
XRn*cacheFilesMaxFiles: 100
XRn*articleText*foreground: #ffff00
XRn*articleText*background: #000040
XRn*index*font: 8x13
XRn*index*foreground: #ffff00
XRn*index*background: #040480
XRn*addQuit.foreground: white
XRn*addQuit.background: #00A000
XRn*ngQuit.foreground: white
XRn*ngQuit.background: #00A000
XRn*ngRead.background: #d09020
XRn*ngNext.background: #d09020
XRn*ngPrev.background: #d09020
XRn*ngCatchUp.background: #d09020
XRn*ngSubscribe.background: #d09020
XRn*ngUnsub.background: #d09020
XRn*ngGoto.background: #d09020
XRn*ngAllGroups.background: #d09020
XRn*ngRescan.background: #d09020
XRn*ngPrevGroup.background: #d09020
XRn*ngSelect.background: #d09020
XRn*ngMove.background: #d09020
XRn*ngExit.background: #8889ff
XRn*ngCheckPoint.background: #00c000
XRn*ngPost.background: #d09020
XRn*ngGripe.background: #8889ff
XRn*ngListOld.background: #8889ff
XRn*allQuit.foreground: white
XRn*allQuit.background: #00a000
XRn*artQuit.foreground: white
XRn*artQuit.background: #00A000
XRn*artNext.background: #00c000
XRn*artScroll.foreground: #000000
XRn*artScroll.background: #00c900
XRn*artScrollBack.foreground: #000000
XRn*artScrollBack.background: #fa6464
XRn*artListOld.foreground: #000000
XRn*artListOld.background: #8889ff
XRn*artCheckPoint.background: #00c000
XRn*artNextUnread.foreground: #000000
XRn*artNextUnread.background: #00c900
XRn*artPrev.foreground: #000000
XRn*artPrev.background: #fa6464
XRn*artLast.background: #90a090
XRn*artNextGroup.foreground: #000000
XRn*artNextGroup.background: #00c900
XRn*artGotoArticle.background: #90a090
XRn*artCatchUp.background: red
XRn*artCatchUp.foreground: black
XRn*artFedUp.background: #004000
XRn*artFedUp.foreground: white
XRn*artMarkRead.background: #90a090
XRn*artMarkUnread.background: #90a090
XRn*artUnsub.background: #90a090
XRn*artSubNext.foreground: #000000
XRn*artSubNext.background: #00c900
XRn*artSubPrev.foreground: #000000
XRn*artSubPrev.background: #fa6464
XRn*artKillSession.foreground: #00ffff
XRn*artKillSession.background: #a02030
XRn*artKillLocal.foreground: #00ffff
XRn*artKillLocal.background: #a02030
XRn*artKillGlobal.foreground: #00ffff
XRn*artKillGlobal.background: #a02030
XRn*artKillAuthor.foreground: #00ffff
XRn*artKillAuthor.background: #a02030
XRn*artSubSearch.background: #90a090
XRn*artContinue.background: #90a090
XRn*artPost.background: #90a090
XRn*artExit.background: #8889ff
XRn*artGripe.background: #8889ff
XRn*artSave.foreground: #400040
XRn*artSave.background: #00e000
XRn*artReply.foreground: #0000ff
XRn*artReply.background: #e06060
XRn*artForward.foreground: #0000ff
XRn*artForward.background: #e06060
XRn*artFollowup.foreground: #ffff00
XRn*artFollowup.background: #000080
XRn*artCancel.foreground: #0000ff
XRn*artCancel.background: #e06060
XRn*artRot13.foreground: #000000
XRn*artRot13.background: #ff00ff
XRn*artHeader.foreground: #000000
XRn*artHeader.background: #ff00ff
XRn*artPrint.foreground: #ffffff
XRn*artPrint.background: #000000
XRn*artAction.foreground: #000000
XRn*artAction.background: #ff00ff

>
>- anton
>--
>'Anyone trying for "industrial quality" ISA should avoid undefined behavior.'
> Mitch Alsup, <c17fcd89-f024-40e7-a594-88a85ac10d20o@googlegroups.com>

On Tue, 3 Oct 2023 18:06:21 -0700 (PDT), MitchAlsup
<MitchAlsup@aol.com> wrote:

>It appears that this N.G. has been killed

50 more Thai language messages about lottery / betting sites in this
group today. Eternal September seems to have blocked them, but they
showed up in Google.

Sigh!

Reported them all as spam.

On Wednesday, October 11, 2023 at 5:59:12 PM UTC+3, George Neuner wrote:
> On Tue, 3 Oct 2023 18:06:21 -0700 (PDT), MitchAlsup
> <Mitch...@aol.com> wrote:
>
> >It appears that this N.G. has been killed
>
> 50 more Thai language messages about lottery / betting sites in this
> group today. Eternal September seems to have blocked them, but they
> showed up in Google.
>
> Sigh!
>
> Reported them all as spam.

~3 spam messages per hour. comp.lang.c got 700 in last hour.

Someone needs to do a 1B logins per hour to that/those spamming websites.

On Monday, October 16, 2023 at 10:19:05 PM UTC+3, MitchAlsup wrote:
> Someone needs to do a 1B logins per hour to that/those spamming websites.

Website? Which website?
As far as I understand it, the only website involved is groups.google.com.
The rest is done from by scripts running on either client computers or
on non-web servers.
And you likely know that but prefer to be emotional rather than thinking.

On Monday, October 16, 2023 at 3:06:27 PM UTC-5, Michael S wrote:
> On Monday, October 16, 2023 at 10:19:05 PM UTC+3, MitchAlsup wrote:
> > Someone needs to do a 1B logins per hour to that/those spamming websites.
> Website? Which website?
<
There are a limited number of URLs from the massive spam we are getting.
Send 1B login requests to each of those sites per hour. for 365 days in a row.
<
> As far as I understand it, the only website involved is groups.google.com..
<
You idiot that is the good web site not the bad one.
<
> The rest is done from by scripts running on either client computers or
> on non-web servers.
<
Then bomb every return URL you find.
<
> And you likely know that but prefer to be emotional rather than thinking.
<
If I was in charge they would have already been nuked.

On Tuesday, October 17, 2023 at 5:04:51 AM UTC+3, MitchAlsup wrote:
> On Monday, October 16, 2023 at 3:06:27 PM UTC-5, Michael S wrote:
> > On Monday, October 16, 2023 at 10:19:05 PM UTC+3, MitchAlsup wrote:
> > > Someone needs to do a 1B logins per hour to that/those spamming websites.
> > Website? Which website?
> <
> There are a limited number of URLs from the massive spam we are getting.
> Send 1B login requests to each of those sites per hour. for 365 days in a row.
> <
> > As far as I understand it, the only website involved is groups.google.com.
> <
> You idiot that is the good web site not the bad one.

As far as the rest of the Usenet is concerned, groups.google.com are bad guys.
Al current wave of spam arrives through their interface. They are getting
getting 1000s of reports of abuse every day and do approximately nothing about
it except one-time incomplete cleanup that they did two weeks ago.

> <
> > The rest is done from by scripts running on either client computers or
> > on non-web servers.
> <
> Then bomb every return URL you find.

What "URL" are you talking about? Posting via Google Groups is pure
client activity. No Web Servers involved except Google's server, so, naturally,
there are no URLs.

> <
> > And you likely know that but prefer to be emotional rather than thinking.
> <
> If I was in charge they would have already been nuked.

It seems, I overestimated your knowledge of Usenet. You use it for decades,
but still appear to have no idea about what it is and how it works.

Michael S <already5chosen@yahoo.com> writes:
>On Tuesday, October 17, 2023 at 5:04:51=E2=80=AFAM UTC+3, MitchAlsup wrote:
>> On Monday, October 16, 2023 at 3:06:27=E2=80=AFPM UTC-5, Michael S wrote:=
>=20
>> > On Monday, October 16, 2023 at 10:19:05=E2=80=AFPM UTC+3, MitchAlsup wr=
>ote:=20
>> > > Someone needs to do a 1B logins per hour to that/those spamming websi=
>tes.=20
>> > Website? Which website?=20
>> <
>> There are a limited number of URLs from the massive spam we are getting.=
>=20
>> Send 1B login requests to each of those sites per hour. for 365 days in a=
> row.
>> <=20
>> > As far as I understand it, the only website involved is groups.google.c=
>om.=20
>> <
>> You idiot that is the good web site not the bad one.
>
>As far as the rest of the Usenet is concerned, groups.google.com are bad gu=
>ys.
>Al current wave of spam arrives through their interface. They are getting
>getting 1000s of reports of abuse every day and do approximately nothing ab=
>out
>it except one-time incomplete cleanup that they did two weeks ago.
>
>> <=20
>> > The rest is done from by scripts running on either client computers or=
>=20
>> > on non-web servers.=20
>> <
>> Then bomb every return URL you find.
>
>What "URL" are you talking about? Posting via Google Groups is pure
>client activity. No Web Servers involved except Google's server, so, natura=
>lly,
>there are no URLs.

There are, presumably, URLs in the body of the spam messages. I wouldn't
know because xrn does not display UTF-8.

However, it is likely those URLs refer to hacked legitimate websites
(e.g. wordpress) rather than something associated with the idiots doing
the spamming.