Gnus development mailing list
 help / color / mirror / Atom feed
From: "St. Suika Fenderson Roberts" <wrobert2@mailhost.tcs.tulane.edu>
Subject: Re: OffGnus
Date: Wed, 22 Jan 1997 23:14:20 -0600	[thread overview]
Message-ID: <199701230514.XAA57074@rs5.tcs.tulane.edu> (raw)

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> Rich Pieri <rich.pieri@prescienttech.com> writes:
>> LMI> No -- nnagent will always download all the headers.  It's only the
>> LMI> article bodies that are interesting to decide whether should be
>> LMI> fetched or not.
>> 
>> You misunderstand.  If I score an article low based on how many lines it
>> contains, it will not appear in the summary buffer where I want it to

> I must be misunderstanding something basic here, because you and I
> seem to be saying the same things here.  Only we're disagreeing.  :-)

> 2) Uses a scoring scheme to say what articles to download, and
>    also downloads articles that have been manually marked for
>    download, no matter what their scores are.

The way I'm seeing this whole arguement is this:

Lars is saying that headers will be `scored' to determine if the article
will be auto-downloaded.

Rich is fearing that this means that the scoring to determine whether to
show an article in the summary will be affected by lowering the
auto-download score for articles that are too big, which could push
articles scores low enough that they are not displayed.

As long as the display scores affect the auto-download scores, and not
vice-versa, I don't see any problem with using scoring to determine
auto-downloadablity.  If the auto-download scores affect the summary
display scores one could well end up with problems . . .

hope this helps,
	Suika
--
		wrobert2@mailhost.tcs.tulane.edu
      No matter how big a pair she's got, an enemy is an enemy.
      							--Moroboshi Ataru


             reply	other threads:[~1997-01-23  5:14 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-01-23  5:14 St. Suika Fenderson Roberts [this message]
1997-01-23 17:19 ` OffGnus Rich Pieri
  -- strict thread matches above, loose matches on Subject: below --
1997-01-16  1:10 OffGnus Lars Magne Ingebrigtsen
1997-01-20 15:17 ` OffGnus Rich Pieri
1997-01-20 19:24   ` OffGnus Rich Pieri
1997-01-21  8:38     ` OffGnus Lars Magne Ingebrigtsen
1997-01-20 19:29   ` OffGnus Rich Pieri
1997-01-21  8:39     ` OffGnus Lars Magne Ingebrigtsen
1997-01-21 15:07       ` OffGnus Rich Pieri
1997-01-21 20:27         ` OffGnus Lars Magne Ingebrigtsen
1997-01-21 22:47           ` OffGnus Rich Pieri
1997-01-21 23:14             ` OffGnus Lars Magne Ingebrigtsen
1997-01-22 15:12               ` OffGnus Rich Pieri
1997-01-23  2:50                 ` OffGnus Lars Magne Ingebrigtsen
1997-01-23  5:29                   ` OffGnus David Moore
1997-01-23  9:19                     ` OffGnus Lars Magne Ingebrigtsen
1997-01-23 17:03                   ` OffGnus Rich Pieri
1997-01-24  9:25                     ` OffGnus Lars Magne Ingebrigtsen
1997-01-24 13:57                       ` OffGnus Rich Pieri
1997-01-24 21:03                         ` OffGnus Per Abrahamsen
1997-01-21 10:21     ` OffGnus dave edmondson
1997-01-21  8:37   ` OffGnus Lars Magne Ingebrigtsen
1997-01-21 15:26     ` OffGnus Rich Pieri
1997-01-21 22:52       ` OffGnus Lars Magne Ingebrigtsen
1997-01-22 15:24         ` OffGnus Rich Pieri
1997-01-22 16:44           ` OffGnus Justin Sheehy
1997-01-22 20:28             ` OffGnus Rich Pieri
1997-01-23  2:53           ` OffGnus Lars Magne Ingebrigtsen
1997-01-23 17:12             ` OffGnus Rich Pieri
1997-01-24  9:28               ` OffGnus Lars Magne Ingebrigtsen
1997-01-22 12:59 ` OffGnus Kai Grossjohann
1997-01-23  0:46   ` OffGnus Patrick Audley
1997-01-23  2:45   ` OffGnus Lars Magne Ingebrigtsen
1997-01-25 10:17     ` OffGnus Darren/Torin/Who Ever...

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=199701230514.XAA57074@rs5.tcs.tulane.edu \
    --to=wrobert2@mailhost.tcs.tulane.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).