Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <hardaker@ece.ucdavis.edu>
Cc: ding@ifi.uio.no
Subject: Re: new feature for Red - adaptive scoring
Date: Mon, 29 Jan 1996 08:53:06 -0800	[thread overview]
Message-ID: <199601291653.AA282914387@teal.ece.ucdavis.edu> (raw)
In-Reply-To: Your message of "27 Jan 1996 21:33:07 PST." <w8s68dxml8c.fsf@surt.ifi.uio.no>


larsi@ifi.uio.no (Lars Magne Ingebrigtsen) writes:

|> Score rules that haven't been used for 7 days (or so) are removed, so
|> that shouldn't really be a problem, I would think...  The point of the
|> decay thing is to avoid having all the things you like reach posinf
|> while the things you don't like would reach neginf, isn't it?

True, however in some cases you want to come close.  Take for
instance, really annoying threads that have gone on way too long you
actually want to make sure that it makes it below the 'mark' or
'expunge' values.  This will become increasingly hard to do if you
have a percentile based system.  The other problem is that it greatly
depends on the frequency with which you use gnus.  For instance, if
you read gnus 2-3 times a day, then every time you load the score file
your scores drop by a percentage.  Now, since very few articles will
get posted during that time, your scores will be aftected drasticlaly.
Then there is the guy that reads articles gnus once in a blue moon.
He'll barely decrease his scores upon load and then read, say, 100
articles with the same subject which will greatly increase the score
for that subject.  The guy that read the gnus 3 times a day probably
entered the group and had no articles with the subject in question,
and thereby only decreased his score.  I've certainly rambled about
this far long enough for even the most basic of infants could
understand my thoughts...  err, I could have written this so
incoherently that no-one will understand it either I suppose.  Wow.
Monday mornings.

Anyway, I like the suggestion at the end of the week about have a
variable that is a list contains the rules to use and when.  IE,

if abs(score) < 50 then decrease by 5 pts
if abs(score) >= 50 then decrease by 5%

or something of that nature.



  parent reply	other threads:[~1996-01-29 16:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-01-25 17:13 Jack Vinson
1996-01-25 21:33 ` Jason L Tibbitts III
1996-01-26 16:46   ` Lars Magne Ingebrigtsen
1996-01-26 17:18     ` Joe Hildebrand
1996-01-26 16:46 ` Lars Magne Ingebrigtsen
1996-01-26 17:52   ` Wes Hardaker
1996-01-26 22:10     ` Sean Lynch
1996-01-27 20:33       ` Lars Magne Ingebrigtsen
1996-01-29 16:55         ` Wes Hardaker
1996-01-29 19:07       ` Edward J. Sabol
1996-01-27 20:33     ` Lars Magne Ingebrigtsen
1996-01-28 20:05       ` Brian Edmonds
1996-01-29 16:53       ` Wes Hardaker [this message]
1996-01-26 18:55   ` Steven L Baur

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=199601291653.AA282914387@teal.ece.ucdavis.edu \
    --to=hardaker@ece.ucdavis.edu \
    --cc=ding@ifi.uio.no \
    /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 NNTP newsgroup(s).