From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: Lower all threads started by a particular tro... er, person?
Date: Mon, 11 Jan 2016 15:36:07 -0800 [thread overview]
Message-ID: <m2wprf6654.fsf@eno.apple.com> (raw)
In-Reply-To: <upzcmvsfvx2y.fsf@dod.no>
on Sat Jan 09 2016, Steinar Bang <sb-AT-dod.no> wrote:
>>>>>> asjo@koldfront.dk (Adam Sjøgren):
>
>> Does this hide the entire _thread_?
>
> No, just the troll in question.
Yeah, the problem here is that other people jump on the thread and waste
my bandwidth dealing with the unproductive input and I really want to
down-score the whole thing.
> There is a possibility to score down on both the subject,
Using the subject can lead to down-scoring too many articles.
In principle there should be no reason to do this based on subject,
since thread references are present in the message headers.
> and on that particular thread (using references (at least I _think_
> there is...)), but I don't know how to do this without looking it up.
I guess that would be `L r'. But I want to find messages from a
certain author and then programmatically down-score everything that
refers to that message. I suppose
[[info:gnus#Advanced%20Scoring][info:gnus#Advanced Scoring]] could be
used to write a sufficiently ugly rule, but I worry that it might take
too long to process. I wonder how hard it would be to extend that stuff
to allow for arbitrary ancestry searching, e.g. with ^*
-Dave
next prev parent reply other threads:[~2016-01-11 23:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 7:39 Dave Abrahams
2016-01-08 14:05 ` Dave Marquardt
2016-01-09 7:36 ` Steinar Bang
2016-01-09 9:45 ` Adam Sjøgren
2016-01-09 10:58 ` Steinar Bang
2016-01-11 23:36 ` Dave Abrahams [this message]
2016-02-06 6:04 ` Lars Ingebrigtsen
2016-02-07 15:58 ` Dave Abrahams
2016-02-07 16:43 ` Teemu Likonen
2016-02-07 17:22 ` Greg Troxel
2016-02-07 17:35 ` Greg Troxel
2016-02-08 5:20 ` Lars Ingebrigtsen
2016-02-07 20:21 ` Dave Abrahams
2016-02-08 5:20 ` Lars Ingebrigtsen
2016-02-07 16:56 ` Greg Troxel
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=m2wprf6654.fsf@eno.apple.com \
--to=dave@boostpro.com \
--cc=ding@gnus.org \
/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).