Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: adapt in SCORE file does not work logicaly
Date: Mon, 20 Oct 2014 00:14:04 +0200	[thread overview]
Message-ID: <87a94raes3.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.11500.1413732756.1147.info-gnus-english@gnu.org>

Stefan Huchler <stefan.huchler@mail.de> writes:

> thx for an answer!

This answer doesn't answer any of your questions, but
you are welcome nonetheless :)

There is a huge section in the Gnus manual on
scoring. Did you check that out?

For what reason do you want scoring?

If it is to block spammers and perhaps (f)lamers in
general, for mail, I managed to do that with
splitting, just split them to a spam group, then give
that group low priority so it won't even show.

For news, I have a KILL file. I just add addresses to
both. But to KILL isn't as good as splitting because
the to-be killed posts still show up in the group
buffer. It'll say "some.group 6" and you think, cool,
some interesting discussion, hit RET, and... turns
out, all six were KILL-ed.

I just feel it would be better to have a common
interface for splitting both news and mails and also
to have the plonkies in a textfile, i.e., not hard
coded.

Now I have the splitting hard-coded in an Elisp (.el)
file and the killing in the KILL file that is sort of
a hybrid, with entries like

(gnus-kill "From" "Joe Flamer" '(gnus-summary-mark-as-read nil "X") t)

I do have an Elisp function and a shell script to
append automatically, but it is still suboptimal from
the scenario I describe - I don't know how other
people do it.

If you are interested in any of this, I'll be happy to
provide exact examples and the code itself - but
probably you know of this, right?

Anyway, as for scoring, I never got that to work but
it would be very interesting to have features like:

* threads where you are active, bring that to your
  attention
  
* people who quote you, even more so

* subjects that has been around for ages and you never
  participated, downgrade

* very short messages that contains +1, downgrade
  (ignore), as they don't bring anything in terms of
  thoughts or technology

* messages that contains insults ("idiot"), ignore
  (even when true, never pleasant to read, also
  doesn't bring anything)

I don't know if or to what extent that can be done
with scoring, but I would be very happy to learn.

At the very least, a common interface to killing
(common to mail and news) and a clear separation of
code and data should be very possible. I'd be
surprised if no one ever did anything to that extent,
if so, tell me and I'll se what I can do whenever I
get, eh, "time" (ha).

Keep Gnusing!
  
-- 
underground experts united

       reply	other threads:[~2014-10-19 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.11500.1413732756.1147.info-gnus-english@gnu.org>
2014-10-19 22:14 ` Emanuel Berg [this message]
2014-10-19 23:40   ` Ray
2014-10-20 21:35     ` Stefan Huchler
2014-10-20 21:38     ` Stefan Huchler
     [not found]     ` <mailman.11602.1413841225.1147.info-gnus-english@gnu.org>
2014-10-21  3:56       ` Emanuel Berg
2014-10-21 11:42         ` Stefan Huchler
2014-10-19 15:32 Stefan Huchler

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=87a94raes3.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=info-gnus-english@gnu.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).