Re: [Asrg] Adding a spam button to MUAs

Nathaniel Borenstein <nsb@guppylake.com> Thu, 17 December 2009 17:34 UTC

Return-Path: <nsb@guppylake.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 21A173A68B4 for <asrg@core3.amsl.com>; Thu, 17 Dec 2009 09:34:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.028
X-Spam-Level:
X-Spam-Status: No, score=-0.028 tagged_above=-999 required=5 tests=[AWL=-0.185, BAYES_50=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yupfN8yo6Gry for <asrg@core3.amsl.com>; Thu, 17 Dec 2009 09:34:17 -0800 (PST)
Received: from server1.netnutz.com (server1.netnutz.com [72.233.90.3]) by core3.amsl.com (Postfix) with ESMTP id 6F6943A68A2 for <asrg@irtf.org>; Thu, 17 Dec 2009 09:34:17 -0800 (PST)
Received: from c-67-173-1-117.hsd1.il.comcast.net ([67.173.1.117] helo=[192.168.1.4]) by server1.netnutz.com with esmtpa (Exim 4.69) (envelope-from <nsb@guppylake.com>) id 1NLKF1-0000x9-C2 for asrg@irtf.org; Thu, 17 Dec 2009 12:34:19 -0500
References: <alpine.BSF.2.00.0912082138050.20682@simone.lan> <20091216014800.GA29103@gsp.org> <DBF77720-200E-4846-949F-924388F9CC15@blighty.com> <20091216120742.GA28622@gsp.org> <20091216185904.3B9032421D@panix5.panix.com> <4B296458.5070603@mail-abuse.org> <16C1C8A4-D223-435B-93BC-A9D44F5965A1@guppylake.com> <B14EC7430355853625D0D4EA@lewes.staff.uscs.susx.ac.uk>
In-Reply-To: <B14EC7430355853625D0D4EA@lewes.staff.uscs.susx.ac.uk>
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
Message-Id: <BBF2AC03-3C88-4557-9346-343347C196A9@guppylake.com>
Content-Transfer-Encoding: quoted-printable
From: Nathaniel Borenstein <nsb@guppylake.com>
Date: Thu, 17 Dec 2009 12:33:59 -0500
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Mailer: Apple Mail (2.1077)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server1.netnutz.com
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - guppylake.com
Subject: Re: [Asrg] Adding a spam button to MUAs
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Dec 2009 17:34:18 -0000

On Dec 17, 2009, at 11:27 AM, Ian Eiloart wrote:

> Twitter seems to think that users are smart enough to distinguish between "unwanted" and "spam". They give you a button for each. It's an important distinction that most people can make. 

Twitter isn't always right, and my intuition differs from yours on this one.  Fortunately it's something that could be resolved empirically.  I'd like to see such a study, because it wouldn't take very many users who *can't* properly make that distinction to render the two-button solution counterproductive.  I'd rather have one bit of meaningful data than two bits of muddled data.  -- Nathaniel