public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Owen Rees <owen.rees@hp.com>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Cc: Bruce Wehr <bruce@wehrhere.com>
Subject: RE: No postnews or other Usenet news utilities?
Date: Thu, 25 May 2006 09:23:00 -0000	[thread overview]
Message-ID: <3C908ED9C33B3D8EE1E4ABFF@orees.hpl.hp.com> (raw)
In-Reply-To: <007c01c67f9e$1eef7e10$3100000a@microline.mtc>

--On Wednesday, May 24, 2006 21:54:12 -0400 Bruce Wehr wrote:

> No, I am not a spammer.

--On Wednesday, May 24, 2006 13:38:22 -0400 Bruce Wehr wrote:

> Anyway, Xnews has an arbitrary limit on cross posting to 20 groups at a
> time.  Yesterday, I spent quite a bit of time going through all the
> *.forsale groups, selecting 20 at a time, excluding item specific ones
> (like computers or homes) and sending my ad.  It took quite a bit of time
> and was insanely repetitive.  Imagine my surprise when I used Google
> Groups today to search Usenet, only to find that my articles never made
> it out!  <ARRGH!>

Whatever definitions you or I may have for 'spam' and 'spammer' are 
irrelevant. What matters is the definition used by those who cancel spam. 
Dave Korn mentioned "the BI>20 definition of spam" presumably assuming that 
everyone knows that BI stands for "Breidbart Index", knows how it is 
calculated, and knows that 20 is the threshold generally accepted by those 
who actively cancel spam.

BI is the sum of the square roots of the number crossposts of messages 
similar enough to be considered equivalent. "insanely repetitive" suggests 
more than 5 posts to 20 groups and since 5*sqrt(20)>22 that has exceeded 
the threshold used as the definition of cancellable spam by those who 
actively cancel spam.


  parent reply	other threads:[~2006-05-25  9:23 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <052b01c67f5b$d74ce490$a501a8c0@CAM.ARTIMI.COM>
     [not found] ` <002701c67f73$625804e0$3100000a@microline.mtc>
2006-05-24 22:03   ` mwoehlke
2006-05-25  1:48     ` Bruce Wehr
2006-05-25  3:04       ` Gary R. Van Sickle
2006-05-25 11:24         ` bruce@wehrhere.com
2006-05-26  2:22           ` Gary R. Van Sickle
2006-05-26 22:03             ` Bruce Wehr
2006-05-25 15:20         ` mwoehlke
2006-05-26  2:36           ` Gary R. Van Sickle
2006-05-26  9:27             ` Dave Korn
2006-05-26 16:07             ` mwoehlke
2006-05-26 16:20               ` Igor Peshansky
2006-05-26 18:38                 ` mwoehlke
2006-05-26 22:54                 ` Bruce Wehr
2006-05-26 23:17                   ` Igor Peshansky
2006-05-26 23:22                   ` Brian Dessent
2006-05-26 23:41                     ` Bruce Wehr
2006-05-27  0:03                       ` Gary R. Van Sickle
2006-05-27  0:07                         ` Igor Peshansky
2006-05-27  0:00                     ` Gary R. Van Sickle
2006-05-26 16:25               ` Dave Korn
2006-05-26 16:43                 ` Dave Korn
2006-05-26 18:54                 ` mwoehlke
2006-05-26 22:44             ` Bruce Wehr
2006-05-25  9:23       ` Owen Rees [this message]
2006-05-25  9:44       ` Dave Korn
2006-05-25 15:19       ` mwoehlke
2006-05-25 15:52         ` One Angry User
2006-05-25  2:32 Gary R. Van Sickle
     [not found] <004c01c67fdc$1b0a9990$a501a8c0@CAM.ARTIMI.COM>
2006-05-25 11:10 ` bruce@wehrhere.com
2006-05-25 12:07   ` Dave Korn
2006-05-25 14:31     ` Christopher Faylor
2006-05-26  2:29       ` Gary R. Van Sickle
2006-05-26 22:30     ` Bruce Wehr
2006-05-27  0:22       ` Gary R. Van Sickle
     [not found] <4475E97D.2070204@ateb.com>
2006-05-25 19:20 ` Bruce Wehr

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=3C908ED9C33B3D8EE1E4ABFF@orees.hpl.hp.com \
    --to=owen.rees@hp.com \
    --cc=bruce@wehrhere.com \
    --cc=cygwin-talk@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).