Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

Re: [spam-stopper] A Thought on the Name

  • To: spam-stopper@xxxxxxxxxxxxxxxxxxxx
  • Subject: Re: [spam-stopper] A Thought on the Name
  • From: Roy Schestowitz <r@xxxxxxxxxxxxxxx>
  • Date: Mon, 03 Oct 2005 05:59:01 +0100
  • Delivery-date: Mon, 03 Oct 2005 05:59:03 +0100
  • Envelope-to: s@schestowitz.com
  • In-reply-to: <4340B432.8000303@mullenweg.com>
  • References: <20051001160535.E40C06097@comox.textdrive.com> <4340AFC7.1080802@mullenweg.com> <20051003053316.kxbpr0zfxnuo00sg@banana.catalyst2.com> <4340B432.8000303@mullenweg.com>
  • User-agent: Internet Messaging Program (IMP) H3 (4.0.3)
_____/ On Mon 03 Oct 2005 05:31:46 BST, [Matt Mullenweg] wrote : \_____

Roy Schestowitz wrote:
How about exchanging "stopper" with "barrier" or "filter"? If automattic is a
must due to the domain name, how about spam.automattic (pronounced
spamotomatic). It sounds malevolent, much like some illicit tools, but given
context, I think it's catchy.

It doesn't need "automattic" or any particular domain in there at all, that's all flexible.

It is definitely /comment/ (broadly contribution) spam that's targeted. Perhaps
it can be emphasised, assuming non-WordPress prospective users, by choosing
names that reflect on that very fact and are self-contained or
self-explanatory. Something global or already familiar (e.g. Apache's
SpammerAssassin) would have it pros. I can't think of something simple, but
CommentStrainer and CommentSieve are ones that distinguish ASS (dear gracious!)
from a typical spam prevention mechanism/service.


Roy

--
Roy S. Schestowitz
http://Schestowitz.com


[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index