Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: nocem in Gnus: should it go away?
Date: Thu, 14 Dec 2006 19:24:09 +0000	[thread overview]
Message-ID: <g69r6v2ffhi.fsf@lifelogs.com> (raw)
In-Reply-To: <y68u00f4eaz.fsf@contents-vnder-pressvre.mit.edu> (David Z. Maze's message of "Fri\, 01 Dec 2006 14\:16\:36 -0500")

On  1 Dec 2006, dmaze@mit.edu wrote:

> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> /gnus/lisp> grep -i nocem *.el|wc
>> 165     754    9124
>>
>> That's a lot of code for a feature no one uses.  Should it go away?
>> Or should it be revisited, updated, and made useful?  Maybe it can
>> integrate with spam.el for instance.
>
> My $0.02 is that "classic" Usenet spam has practically vanished (for
> the...five? public NNTP groups I read, three of which are
> moderated).

It's terrible on Gmane, though, and I use that for many lists :)

> I tried using NoCeM for a bit but the overhead of running it was just
> insane, even given a news server pretty close to me on the network.
> Setting gnus-spam-autodetect to scan NNTP groups too seems to give
> pretty good results at a much lower performance overhead.

Yes, I like it too.  Very fast on Gmane because of their anti-spam
system.

> If you were trying to read "most" of Usenet using Gnus, it might still
> be useful to you.  But that's an awful lot of traffic.  Personally, I
> wouldn't miss nocem if it vanished, and I could see it wanting to
> vanish if the code maintenance issues are starting to stack up.

I'll see what Katsumi Yamaoka says.  My feeling is that it could be
useful, but not too many care.

Ted



  reply	other threads:[~2006-12-14 19:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-01 18:11 Ted Zlatanov
2006-12-01 19:16 ` David Z Maze
2006-12-14 19:24   ` Ted Zlatanov [this message]
2006-12-03 23:37 ` Katsumi Yamaoka
2006-12-14 19:21   ` Ted Zlatanov
2006-12-15  5:05     ` Katsumi Yamaoka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=g69r6v2ffhi.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).