Killfiling Google Groups (was: ???????? ?????????? ?????????????? ??????????????)



[I thought we might as well have a meaningful Subject line]

In comp.os.linux.misc on Sun, 6 May 2007 22:46:12 +0200, Michael
Heiming <michael+USENET@xxxxxxxxxxxxxx> wrote:

In comp.os.linux.misc Peter J Ross <pjr@xxxxxxxxxxxxxxx>:
In comp.os.linux.misc on Sun, 06 May 2007 13:54:55 -0500, Moe Trin
<ibuprofin@xxxxxxxxxxxxxxxxxxxxxx> wrote:

On Sun, 6 May 2007, in the Usenet newsgroup comp.os.linux.misc, in article
<2251h4-08a.ln1@xxxxxxxxxxxxxxx>, Michael Heiming wrote:

this looks like asking for a permanent entry in the lines off:

^User-Agent:[ ]G2/1.0*$

I'd like to avoid, but the permanent abuse makes one think about it...

Depends on where you put it - if done in leafnode, you'll have to stop
posting your newsgroup stats, as google is (unfortunately) used by many
posters whose ISPs are either so cheap, or so stupid as to not have a
news service.

In addition to users not knowing what usenet is at all, since
they use groups.google and might not be aware what the fuzz is
about?

On the other hand, some helpful people may use Google Gropes when they
temporarily lack access to a real news server. Any system of
killfiling Gropers has to be flexible enough to allow the useful
minority not to be killfiled.

<...>

Tin can't score on User-Agent (yet), but this would work:

msgid_only=\.googlegroups\.com>

Might do the trick, though I have never put much work into tin
kill filling, leafnode does all I need at a more centralized
point.

Leafnode can only choose between retrieving or killing an article. Tin
can also give it a score for sorting purposes, and the article will
still be available from Leafnode if follow-ups suggest that it's worth
reading.

E.g., I'm currently experimenting with these rules in Slrn, which I'm
sure could be adapted for Tin:

% Google Gropers
[*comp*, news.*]
Score: -100
Message-Id: \.googlegroups\.com>
~From: poster@example\.com
~From: poster@example\.net
Score: -200
Message-ID: \googlegroups\.com>
~From: poster@example\.com
~From: poster@example\.net
{::
Xref: :.*:
~References: .
}

The effect with my current settings is that all Gropers not
individually excluded are scored down and sorted towards the bottom of
the list of articles, while all non-excluded Gropers who start new
threads or who participate in crossposts are marked read.

--
PJR :-)
.



Relevant Pages

  • Re: More bad news: Motorola cuts 4000 jobs
    ... Ba ca'i tin kie^?u ddo' la` tin ddo^`n ra(`ng, ... "SAN FRANCISCO - Google Inc said on Wednesday it was laying ... some benefits for employees in its New York office cafeteria, ... most of its engineers to other offices, ...
    (soc.culture.vietnamese)
  • Re: iPods and Brasso
    ... >> some sort of pink compound in a small tin - Duraglit? ... though now I google for it the wadding stuff's some ...
    (uk.comp.sys.mac)
  • Re: Where does Firefox stores its cache?
    ... And this is while set 50Mb cache size! ... A very quick Google took me to about:cache, ... james | "Does exactly what it says on the tin." ...
    (Fedora)
  • Re: Why dont my posts show up under the poster I am replying to?
    ... A good message sent via google is just as good as if it ... was sent from Outlook Express, Thunderbird, tin, or nn. ... sent via google is just as dumb as if it was sent from Outlook Express, ...
    (rec.outdoors.rv-travel)
  • Re: Addition to my FAQ - re NSP shut downs
    ... hate activities against what they term "google gropers". ... Are you really this fucking stupid, ...
    (news.software.readers)