Gnus development mailing list
 help / color / mirror / Atom feed
From: Brian Edmonds <edmonds@cs.ubc.ca>
Subject: red idea: ghettoize crossposts
Date: Sat, 1 Jun 1996 16:52:05 -0700	[thread overview]
Message-ID: <199606012352.QAA27821@edmonds.home.cs.ubc.ca> (raw)

I have quite a number of groups in which I would like to never see
crossposts from certain other groups.  Now I could just score them below
the expunge point and be done with it, but some of the time I actually
*do* want to read the same posts when they occur in the other group.

To give an example, we have a university-wide group here, ubc.general.
It tends to be pretty low traffic, so I just read it raw.  However,
people from van.general (city), bc.general (province), and some other
regional groups like to crosspost threads into it.  These other groups
have considerably higher volume and noise, so I adaptively score them
agressively.  I'd like to be able to kick crossposts to either out of
ubc.general, and bc.general crossposts out of van.general.

As a second example, I regularly follow alt.config and news.groups, but
I'd rather not see any crossposts to them from a number of other groups
that I might read first.  My news.groups adaptive scoring is tuned for
reorg discussions, and I'd rather not have to pointlessly do the same in
every group when a (crossposted) reorg discussion crops up.

Thus, I would like to see a new score file primative to "kill" posts
crossposted to certain groups (via Xref obviously), but not actually
mark them as read in all other groups too, just never display them in
that particular group.  Perhaps something in ubc.general like
  (hide-crosspost ("van.general" "bc.general"))
or even, if you're feeling more flowery
  (ghettoize ("van.general" "bc.general"))

The latter might avoid some confusion between hiding and killing...

Brian.


             reply	other threads:[~1996-06-01 23:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-01 23:52 Brian Edmonds [this message]
1996-06-02  0:42 ` Per Abrahamsen
1996-06-02 14:02   ` Brian Edmonds
1996-06-03  6:14     ` Lars Magne Ingebrigtsen

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=199606012352.QAA27821@edmonds.home.cs.ubc.ca \
    --to=edmonds@cs.ubc.ca \
    /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).