List for cgit developers and users
 help / color / mirror / Atom feed
From: normalperson at yhbt.net (Eric Wong)
Subject: Spam on the mailingslist
Date: Sat, 17 Mar 2012 20:01:17 +0000	[thread overview]
Message-ID: <20120317200117.GA4719@dcvr.yhbt.net> (raw)
In-Reply-To: <20120317185337.GD11308@blizzard>

Lukas Fleischer <cgit at cryptocrack.de> wrote:
> On Sat, Mar 17, 2012 at 07:06:48PM +0100, Mariusz Wojcik wrote:
> >  >  This starts to get pretty annoying... About 25% of all mail on this
> >  >  mailing list is spam.
> >
> > Yes, they're really annoying for the archieve. The easiest solvation
> > would be move to Google Groups. It's quite nice and you have as the
> > same feature as a mailingslist. The other solvation would be you
> > have to register to the mailingslist to post on it.

NACK on Google Groups.  Their anti-spam measures are weak and
just recently I've heard of issues with their moderation notifications
not getting through (on the perlbal/mogilefs groups), so new posters
got silently ignored for a long time.

I also dislike user tracking/profiling done by Google, and it's
gotten worse now they're doing G+.

> Disabling posting for non-subscribers only shouldn't be too hard. Also,
> there should be some additional anti-spam measures, such as
> SpamAssassin.

Subscribers-only tends to isolate developers from users that
_occassionally_ find issues.  The git-ML (and LKML) culture favors lists
that allow unsubscribed users to post, and I think this does a lot to
encourage users to get involved.

SpamAssassin is great.  I use it on my own server, so it manages to
catch much of the spam that comes to this list.  Some spam will always
get through, but that's email.




  reply	other threads:[~2012-03-17 20:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-17 18:06 mdickie007
2012-03-17 18:43 ` mathstuf
2012-03-17 18:53 ` cgit
2012-03-17 20:01   ` normalperson [this message]
2012-03-18  9:00   ` hjemli
2012-03-17 20:40 ` mailings

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=20120317200117.GA4719@dcvr.yhbt.net \
    --to=cgit@lists.zx2c4.com \
    /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).