Kaz Kylheku
7/10/2015 3:37:00 PM
On 2015-07-10, CAI GENGYANG <gengyangcai@gmail.com> wrote:
> On Friday, July 10, 2015 at 3:51:08 AM UTC+8, Kaz Kylheku wrote:
>> On 2015-07-09, CAI GENGYANG <gengyangcai@gmail.com> wrote:
>> > There seems to be a lot of spam in comp.lang.lisp
>>
>> I explained that it only *looks* that way because you use Google Groups.
>>
>> Google Groups isn't Usenet; it's a Google service which participats
>> in the Usenet network.
>>
>> I'm currently using the "news.aioe.org" server (to which I connect using the
>> SLRN newsreader.) I cannot remember the last time I saw a spam in comp.lang.c
>> through this setup.
>>
>> The spam you're seeing is largely from your fellow Google Groups users,
>> and other sources that better run news servers filter out.
>>
>> Please do not bother discussing it. Nobody cares; if you don't like it,
>> stop using Google Groups. Get a real newsreader and connect to an NNTP server.
>>
>> If you reply to spam and quote all of it, that's when it spreads outside
>> of Google Groups. Your posting looks legitimate and so it reaches servers on
>> Usenet where the original spam never reached.
>
> Ok ... I am not replying to spam or quoting it. I am simply saying that it
> might be possible to write a program to stop ANY spam from entering
> comp.lang.lisp at all, which would be the best solution for everyone so we
> don't even have to see it ...
comp.lang.lisp is not an object; it is just a tag in the Newsgroups: line of
articles that are distributed through Usenet.
Since comp.lang.lisp it is not an object, it doesn't have borders that you can
defend.
Before proposing anti-spam solutions for Usenet, you should
understand what it is and how it works.
Spam must be fought at entry points into Usenet: numerous servers world-wide
which accept posting from users. (In many cases, anonymous users.)
(Servers are objects with borders!)
It also must be fought at the connection points between servers: one server
defending itself against spam relayed by a connecting server which itself
didn't do an adequate job of spam rejection.
As a user, what you can do is use a good server (not Google Groups), plus local
filtering in your news user agent, if necessary.
(Your news agent *can* treat comp.lang.lisp as a virtual object; it has
a representation of that newsgroup which it can associate with filters and
whatnot, and even maintain a local cache of it and so on.)
I repeat myself: I hardly see any spam from the server that I use. I can't
remember the last time I saw a spam message in comp.lang.lisp from where
I'm reading.
This is your problem caused by using Google Groups; it is already solved for
other people by not using Google Groups.