From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id CCB7A1382C5 for ; Thu, 22 Mar 2018 06:31:51 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8F694E09A7; Thu, 22 Mar 2018 06:31:45 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 361D5E0961 for ; Thu, 22 Mar 2018 06:31:45 +0000 (UTC) Received: from proton (unknown [133.11.143.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: heroxbd) by smtp.gentoo.org (Postfix) with ESMTPSA id 9F168335C2E for ; Thu, 22 Mar 2018 06:31:43 +0000 (UTC) From: Benda Xu To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Mailing list moderation and community openness References: <4aab96fa-0edb-6a28-791e-28e2103f2a30@gentoo.org> <0818a5b0-cc1e-403f-6c08-1285999de30f@gentoo.org> <20180320160316.GA5785@whubbs1.gaikai.biz> <87605qs3pi.fsf@gentoo.org> Date: Thu, 22 Mar 2018 15:31:40 +0900 In-Reply-To: (Rich Freeman's message of "Tue, 20 Mar 2018 20:08:42 -0400") Message-ID: <87a7v0d3jn.fsf@proton.d.airelinux.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain X-Archives-Salt: 8b9d40cd-b70f-4593-8ebd-bf1268c520c1 X-Archives-Hash: de204f8986e66c0c68baffefa55114fa Hi Rich, Rich Freeman writes: > Actually, I think it is more of a technical constraint. It is > basically impossible to blacklist somebody on a mailing list, since > all they need to do is roll up a new email address. > I can think of various arguments for whitelisting or not whitelisting, > but it seems silly to blacklist. Okay, I see your argument. Just a random bikeshedding. We might be able to require GPG signed email to make a post. Then we can blacklist the GPG identity? To think of it further, the web of trust is basically a whitelist. But it has the flexibility to chain the trust from a Gentoo dev by several 'hops'. Benda