I don't expect anybody to do anything. If you were going to do
something, I have no idea what it might be.
I've pointed out in other threads that Giganews does not prevent one of
its users from committing a specific type of abuse. The user is Ubi the
shithead. The abuse involves re-injection of an article written by
someone else with all headers intact but with a change in crosspost. The
article is re-injected with a new Message-ID but it's always a variation
on the original Message-ID.
Because the headers are intact, the injection headers the orginal
article are preloaded. This is nonstandard but Giganews does not prevent
this.
Path is a real header from Giganews. Comparing to the Path header, it's
quite obvious that the injection headers were preloaded.
I didn't write these.
Message-ID: <Upeapd$1m4u2$
1...@dont-email.me>
Message-ID: <Upb4un$11qrb$
1...@dont-email.me>
Note that the Message-IDs created by Ubi the shithead use Ray's domain
name without permission.
In recent past, one of you had to adjust filters because Ubi the
shitheads antics versus another user lead to a false positive NoCeM,
given two articles with identical bodies but different Message-IDs.
I have had zero success over the years trying to get Giganews to TOS
their user committing abuse through their News site. I've filed abuse
reports when other people were forged. I've filed abuse reports when
I've been forged. Giganews will not crack down on this kind of targeted
abuse committed through their News site.
I've never noticed that Giganews was any major source of spam, so I
don't expect the Google Groups spammers to pay for Giganews accounts to
substitute for the loss of Google Groups.
This is a different kind of abuse.