From: Rene Herman <rene.herman@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net, perex@suse.cz
Subject: Re: Broken moderation
Date: Tue, 20 Mar 2007 13:57:21 +0100 [thread overview]
Message-ID: <45FFDA31.8000106@gmail.com> (raw)
In-Reply-To: <s5hvegwccug.wl%tiwai@suse.de>
On 03/20/2007 01:35 PM, Takashi Iwai wrote:
> The last post went through without moderation.
> Really puzzling. Did someone approve manually?
That last one, not me. This one I'm now replying to (from within my
inbox), yes, me. But yes, something is rotten here. As I said in a later
message (which you hadn't seen at the time you wrote this due to the
massive delay of some messages showing up on list even after manual
moderator acceptance) I even have a message in my inbox from yesterday
that hasn't made it yet.
My conclusion for the time being -- sourceforge sucks so bad that things
are unsalvageable as long as the list is on there. linux-kernel is an
open list and almost completely spam-free, so if vger is willing to host
the list(s) I don't believe the alsa-project.org forwards would need to
be disabled (although having a functional spamfilter on alsa-project.org
directly will ofcourse also be good).
As to the difference with alsa-user -- as far as I'm aware, alsa-user is
a subscriber-only list which makes all the difference. Personally I
wouldn't terribly mind having alsa-devel subscriber-only as well but the
list would then recieve major flack from linux-kernel posters who want
to cross-post without needing to subscribe. I've personally long since
concluded that although subscriber only lists may suck, the spam problem
is just too big if you don't have a few full-time admins to throw at it
and thereby sucks worse (vger does have those full-time admins).
Rene.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-20 12:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 23:24 [RFC][RFT] Adding support for Jazz16 based sound cards Rask Ingemann Lambertsen
2007-03-12 11:28 ` Takashi Iwai
2007-03-12 23:23 ` Rask Ingemann Lambertsen
2007-03-13 9:34 ` Takashi Iwai
2007-03-19 0:32 ` Rene Herman
2007-03-19 20:52 ` Rene Herman
2007-03-19 21:06 ` Rene Herman
2007-03-19 21:22 ` Rene Herman
2007-03-19 21:40 ` Rene Herman
2007-03-20 12:12 ` Takashi Iwai
2007-03-20 12:28 ` Broken moderation Takashi Iwai
2007-03-20 12:35 ` Takashi Iwai
2007-03-20 12:57 ` Rene Herman [this message]
2007-03-20 14:58 ` RESUBSCRIBE - New alsa-devel mailing list Jaroslav Kysela
2007-03-20 15:09 ` Benoit Fouet
2007-03-20 15:38 ` Jaroslav Kysela
2007-03-20 15:21 ` Tobin Davis
2007-03-20 15:35 ` Ingo Müller
2007-03-20 16:18 ` Rene Herman
2007-03-20 17:25 ` Jaroslav Kysela
2007-03-21 0:49 ` [Alsa-devel] " Ed Wright
2007-03-21 9:10 ` Rene Herman
2007-03-19 22:46 ` [RFC][RFT] Adding support for Jazz16 based sound cards Rask Ingemann Lambertsen
2007-03-20 21:23 ` [Alsa-devel] " Rene Herman
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=45FFDA31.8000106@gmail.com \
--to=rene.herman@gmail.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
--cc=tiwai@suse.de \
/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