Gnus development mailing list
 help / color / mirror / Atom feed
From: Raja R Harinath <harinath@cs.umn.edu>
Subject: Re: GroupLens (gnus-gl.el)
Date: Sun, 02 Feb 2003 11:29:38 -0600	[thread overview]
Message-ID: <d98ywyoakd.fsf@bose.cs.umn.edu> (raw)
In-Reply-To: <m3fzr78r7l.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 02 Feb 2003 01:24:30 +0100")

Hi,

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Raja R Harinath <harinath@cs.umn.edu> writes:
>
>> But, GroupLens is not supposed to be a moderation system.  It is
>> supposed to find people who appear to have opinions similar to yours,
>> and weights the score based on that "closeness" criterion.
>>
>> It is thus less likely to be poisoned -- unless you are poisonous too :-)
>
> It's a more subtle tool than, er, "flat" moderation, but it's still
> pretty easy to poison 

But the subtlety is of the same kind that makes bayesian filtering
work.  The larger your corpus of ratings, the more resilient to
poisoning.  The poisoner has to put in more work to get to you, and
he'll only get a small payoff for all that effort (fewer people
reached for amount of effort expended).

> (unless you use some kind of authorization system, or keep it "in
> the family").  

I think the issues here are

  * make sure that submitted ratings are credited to right person
    (simple PGP signatures)
  * make sure that the database maintainer is trustworthy 
    (unlike Amazon.com ;-)

Bogus data will be easier to ignore, since it'll be hard for that data
to be "close to" good data.

> Hacking up a system that would inject a gazillion fake profiles that
> would make it likely that your important MAKE VIAGRA NOW messages
> rate highly isn't particularly difficult.  Probably.

But, if none of them is "close", that's not a problem.  And, each time
you come near a poisoned profile, you can distance yourself from it
with your own ratings.

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu



      parent reply	other threads:[~2003-02-02 17:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27 18:59 Ted Zlatanov
2003-01-28 22:11 ` three nnmaildir questions: naming, numbering, and splitting David Wuertele
2003-01-28 22:40   ` Paul Jarc
2003-01-28 23:26     ` David Wuertele
2003-01-29  0:31       ` Paul Jarc
2003-01-29  7:29   ` Kai Großjohann
2003-02-01 16:22 ` GroupLens (gnus-gl.el) Lars Magne Ingebrigtsen
2003-02-01 20:59   ` Kai Großjohann
2003-02-01 21:24     ` Lars Magne Ingebrigtsen
2003-02-02 12:20       ` Alex Schroeder
2003-02-02 12:25         ` Lars Magne Ingebrigtsen
2003-02-02 12:19     ` Alex Schroeder
2003-02-02  0:18   ` Raja R Harinath
2003-02-02  0:24     ` Lars Magne Ingebrigtsen
2003-02-02  1:34       ` Ted Zlatanov
2003-02-02  2:17         ` Simon Josefsson
2003-02-02  4:40           ` Ted Zlatanov
2003-02-02 17:29       ` Raja R Harinath [this message]

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=d98ywyoakd.fsf@bose.cs.umn.edu \
    --to=harinath@cs.umn.edu \
    /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).