From owner-freebsd-chat Tue Jul 27 4:43:22 1999 Delivered-To: freebsd-chat@freebsd.org Received: from vulcan.addy.com (vulcan.addy.com [207.239.68.7]) by hub.freebsd.org (Postfix) with ESMTP id 46965153B3 for ; Tue, 27 Jul 1999 04:43:19 -0700 (PDT) (envelope-from francisco@natserv.com) Received: from your-name (freyes.static.inch.com [207.240.212.43]) by vulcan.addy.com (8.8.5/8.6.12) with SMTP id HAA02529; Tue, 27 Jul 1999 07:42:12 -0400 (EDT) Message-Id: <199907271142.HAA02529@vulcan.addy.com> From: "Francisco Reyes" To: "Dag-Erling Smorgrav" , "Rod Taylor" Cc: "FreeBSd Chat list" Date: Tue, 27 Jul 1999 07:40:15 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows 98 (4.10.1998) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD essentials Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 27 Jul 1999 13:37:36 +0200, Dag-Erling Smorgrav wrote: >> Whelp... You could use the IP and block it from voting again for 2 >> hours or something. This would allow dynamic people to both vote >> (should they get the ip), and wouldn't allow one person to load it >> up very quickly. > >Consider how many -chat readers work for (or are) ISPs. The only thing I could think of was verifying a user by sending an email to which they need to reply and to verify this id is a valid user of one of the freebsd lists... but I can't remember if the lists currently allow to see members (which I actually hope they don't since this would allow spammers to get the names). Overall having people have to reply is one of the better methods I can think off.. although somewhat of an inconvinience. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message