penney dot org | a little knowledge is a dangerous thing

Apr/06

24

Google Groups KillFile Released

The Google Groups KillFile is a very simple, but useful script for those folk that use Google Groups to access Usenet. In normal client side newsreaders there is the concept of a killfile that allows you to filter out posts based on subject or author which allows you to cut through some of the noise. Unfortunately if you have to use a web based client, namely Google Groups this feature is sadly missing which is where the Google Groups KillFile GreaseMonkey script fits in. Once you install the script it will add a small X next to each authors name. If you click the X then you will no longer see any posts by that user.You will need the following..

If you are in the titles only view you will see an X next to the user’s name, clicking this places the author in the killfile. If you are in the other view with Message Text view you will see a link that says Ignore User, again clicking this places the user in the killfile.

At the top right there is a new menu option Kill File, that when clicked displays the current killfile where you can remove people you have previously placed on the list.

You should realise that if someone replies to the troll the message will no longer be blocked as the authors name will change. So as always don’t feed the trolls :)

Hope this proves useful; the usual it’s not my fault if it breaks disclaimer applies.

– Damian

RSS Feed

71 Comments for Google Groups KillFile Released

Chris Dubea | May 15, 2006 at 9:40 am

Hey Damian,

Thanks for this, but I think it has a bug. There doesn’t seem to be an X for the poster of the initial message in a thread. Because of this if the poster is killfiled, his original message still appears. All his other messages go away, but not the first in the thread.

Thanks for the neat tool.

Chris

Desertphile | May 19, 2006 at 7:26 pm

I have been advertising this extension / script in various much-abused newsgroups (I wrote a version for Microsoft’s Internet Explorer.). However, several people have told me this Java script does not always work. I have zero knowledge of Java so I cannot say where the problem is.

ChiyoDad | June 23, 2006 at 7:48 am

It seems to work fine when one is viewing “titles” or “titles with message text”. Sadly, it doesn’t seem to work in the “topic” view; the messages still appear in the topic tree and in the topic texts.
:(

I’ll admit that it’s a good start, though!
:)

drahcir | August 10, 2006 at 8:31 am

Really cool!!

drahcir | August 10, 2006 at 12:34 pm

THis is really great, but sometimes it works and sometimes doesn’t work for me. I can’t figure out why.

jbrill | August 18, 2006 at 10:01 am

This is great start. One problem I’m finding is if that the script seems to block the entire thread and not just the postings made by the “killfiled” individual.

Keep up the good work and looking forward to the updated version.

Author comment by Damian | September 27, 2006 at 6:43 am

I’ve gone ahead and updated the script, works a lot better now, give it a whirl http://www.penney.org/ggkiller.html

nexibello | September 28, 2006 at 10:35 am

wonderful, works a lot better and I don’t have to use all my “work-arounds” anymore :)

but I have a new problem:

My work mode is:
“view titles only”
“Sorted by date of most recent message”
“view as a tree”

Since I have updated the killfile script:

Messages posted by killfiled authors are not visible. Instead of 30 messages a may see only 20. 10 are not visible because the authors are killfiled.
This has not changed.

If I *open* a *thread*, the name of a killfiled author is not listed in the thread-tree anymore and the message of the killfiled author is not displayed anymore.
This has changed.

Before, as soon as I opened a thread I could also see the killfiled authors and their messages.

My problem is:

I want to *unkillfile* an author.

My killfile contains about 300 names, they are listed in no specific order.

I can’t find the killfiled author in the list !?!
(I already copied the list to excel, sorted it alphabetically, but I still can’t find neither the name nor the e-mail-address)

and the 2nd possibility to unkillfile an author is not possible anymore:

If greasymonkey is switched on, the killfiled author is not (no more) visible and I cannot unkillfile him.

If greasymonkey is switched off, I can see the killfiled author but I can’t killfile him because the killfile option (no cross to click on) is gone, too.

Do you (anybody) have a work-around ?

Sorry for the long explanation….

Thanks and kind regards,
Nexibello

Author comment by Damian | September 28, 2006 at 11:07 am

To unkillfile someone you should be able to just click the KillFile link in the nav bar (when you are browsing a group)

emailaddr@gmail.com | My Groups | Help | My Account | Sign out | Kill File

That brings up the list of everyone in your killfile and you should be able to remove them from there. I haven’t tested it with 300 names, but I don’t see why it wouldn’t work.

Author comment by Damian | September 28, 2006 at 11:12 am

I just added a bunch of folks and you are right, the Killfile window that pops up isn’t displaying them all, I’ll find out why and update the script in the next day or so.

nexibello | September 29, 2006 at 12:40 am

*sigh of relief*
thanks :) so it was not me suffering of even poorer eyesight after all…

nexibello | October 6, 2006 at 6:40 am

Hi Damian

If threads are “viewed as a tree”, not all the dates of the messages are displayed in the tree.

It looks to me like this happens as soon there is one killfiled poster in the thread. If the killfiled author is the *first* in the thread (he started it), there is no date in the tree at all. If it’s the 40th, the date will be visible for authors 1 to 39, but not from the 40th onwards.

If the tree is sorted by date, all the dates are there again.

And *in* the message, the dates are there, too.

Greetings,
nexibello

P.S.:
I tried the new Google Group Beta version and realized that the killfile script doesn’t work there. But I suppose the “old” Google Group version will still be available for some time.

Dead Dave | November 22, 2006 at 2:34 am

http://groups.google.co.uk/group/rec.music.classical.recordings/browse_frm/thread/3c0914eff136298d/9a6c4a9ce43016aa?hl=en#9a6c4a9ce43016aa

Contains a poster who cannot be blocked – perhaps because there’s a single quote in the name?

Thanks, though – this is a great script!

Dead Dave | November 22, 2006 at 2:47 am

I just added the poster’s name manually to the scriptval thingy (using about:config) so it can be done! I know nothing about javascript though.

rekkidbraka | November 28, 2006 at 11:19 am

THANK you! I downloaded the new Firefox, GreaseMonkey and Google Groups KillFile script you posted and was able to zap some of the most annoying people on my favorite Google newsgroup. I reallyREALLYreally am grateful for you figuring out a way to killfile the folks who ruin certain usenet groups for the rest of us with their “You’re wrong, I’m always right” posts and I *highly* recommend your three-step killfile download to everyone who can get these scripts and programs onto their hard drives. This is an excellent script and it’s so cool to be able to filter Google Groups.

Again, thanks so much. I got my newsgroup back! :-)

S.P. | January 5, 2007 at 7:26 am

Stupid question, but how do I download/use the killfile. I click on the link on this page, and I just get a page full of meaningless technobabble stuff. What do I do with it? Am I supposed to understand it? What should I do to make it work? Answers in plain English please, not meaningless technobabble stuff.

Damian | January 5, 2007 at 7:56 am

S.P, you need to be using Firefox, and Firefox needs to have GreaseMonkey installed. Once that is done if you click on the Killfile link you will either get a popup from Greasemonkey saying that it’s a script and would you like to use it, or you will see a msg bar at the top of the browser content window that has a button saying pretty much the same thing, that this is a script and would you like to use it.

Once the script is installed head on over to Google Groups and you will see the added option to killfile a user.

S.P. | January 5, 2007 at 10:37 pm

Ok. Thanks. So does that mean I’ll have to install it on _every_ computer that I use to read Google Groups? Doesn’t that take away the whole point of using Google instead of proper usenet: the fact that I can access newsgroups from any computer without having to set up a newsreader with a usenet server account!

I do use Firefox at home, so I _could_ install it here, but I won’t be able to install it it at work, or in a cybercafe, etc.

Oh well, it sounded like a good idea anyway. At least it’s better than nothing I guess.

Mike Harvey | January 6, 2007 at 6:19 am

There’s something I don’t understand. Why does it say that you need to have Firefox With Google Toolbar in order to use Google Groups Killfile?

I am using Firefox 2.0.0.1 (without Google Toolbar), and I have the CustomizeGoogle extension, which, among other things, filters out Google ads.

As a result, when I went to this site to get Google Groups Killfile, i did not see the line above which says you need the special “Firefox With Google Toolbar” version of Firefox.

I saw:

You will need the following..

*
* GreaseMonkey 0.6.4
* Latest Google Groups KillFile Script

viewing the source, I see that that line about FF with Google Toolbar is part of a javascript

google_ad_client = “pub-2047186789174280″; google_ad_output = “textlink”; google_ad_format = “ref_text”; google_cpa_choice = “CAAQzcLH7QEaCD_4BVTjvVryKLGsuIEB”; //–>

I did not actually notice the blank line. I downloaded the script, and Greasemonkey happily accepted it. So Google Toolbar is not needed.

I posted on a Usent group that GG Killfile was a handy thing to have, and got heavily flamed by people saying i was trying to trick them into getting Google Toolbar! It was not until i viewed this site in Opera and IE6 that I realised what was happening.

Damian | January 6, 2007 at 11:11 am

You’re right Mike it doesn’t require the Google Toolbar at all, it’s just a GreaseMonkey script. That link is a Google referral link so I get $1 if anyone downloads Firefox from here. Never intended it to infer you needed the toolbar for it to work though as I did state it’s just a GreaseMonkey script.

Sorry for the confusion and hope this clarifies things (I’ll update the instructions to reflect that the toolbar is indeed entirely optional)

rekkidbraka | January 6, 2007 at 7:06 pm

Question for you: Is there a way to kill file messages on Invision Power Boards? If so, do you have the script so that we can make it happen? (Could you create it?) Just wondering. Thanks. These filters are so helpful in paring down the dross on certain boards.

Author comment by Damian | January 8, 2007 at 9:49 am

I took a peek at the Invision Boards and it looks like it can be done not sure how much time it would take though.

Mike Harvey | January 24, 2007 at 8:56 am

The new Google Groups redesign seems to have killed the version I was using.

moontaco | January 27, 2007 at 7:42 pm

Yeah, since Google Groups changed a few days ago, I’m unable to see ANY posts on it, not just the ones made by people I’ve killfiled.

Damian | January 29, 2007 at 7:11 am

The new version is verified as working. So give that a shot.

ironcladlou | March 27, 2007 at 7:15 pm

Holy shit, dude. From the bottom of my heart, thank you. This script is fucking awesome. Were I a woman, I would want to have your babies.

Martin X | June 27, 2007 at 1:30 pm

I just started using GGKiller and I gotta say it’s sweeet! You know how Usenet is – fulla trolls and dickheads – and up til now, cos I had to use Google Groups instead of a proper newsreader, I had to use a /mental/ killfile on the lusers – which ain’t foolproof I’m afraid (me being the fool in question!) But now I don’t see ‘em, they ain’t a prob to poor old sensitive me no more.

Of course, since I only just started using the script, issues may arise. But I gotta tell ya… good job!

Sebastian | July 4, 2007 at 5:58 am

Great job, thank you for this awesome script!

I’ve a tiny change request tough. In topic view
http://groups.google.com/group/Google_Webmaster_Help-chit-chat/topics?start=
when a troll did the last reply to a thread the whole thread is filtered out.

ucappa | August 27, 2007 at 2:01 am

Hi Damien,
I am using your sw and I have to thank you a lot.
I submit you a suggestion for some next release, that may be helpful in case of morphing (whem trolls adopt nicknames of ’safe’ newsgroup users).
If I well understand, GGkiller is based on nicknames: would it be possible to develop an updated version based on the email address?

Kind regards and thank you again for your valuable support.

Ucappa

Kilia | October 12, 2007 at 2:44 pm

Damian, is there a cutoff point as to how many one can put in the Killfile?

Author comment by Damian | October 12, 2007 at 6:19 pm

Not that I’m aware of Kilia, what’s happening?

Kilia | October 14, 2007 at 12:04 pm

I was just wondering if there was a limit on the killfile, Damien…that’s all. Thanks for replying with the good info. :)

Kilia | October 14, 2007 at 6:26 pm

Damian, nothing is going wrong with the program. lol
I was just wondering if there was a limit on the number of names one can put in their killfile, that’s all.

Many thanks for your wonderful program and replying and putting my mind at ease.

Archon | October 21, 2007 at 6:46 am

I’m using the newest version available and it’s killfiling all the messages.

Author comment by Damian | October 22, 2007 at 5:51 am

Most likely you have something in your killfile that is too broad in scope and is knocking out all the posts. Take a look at it, and remove entries one by one until the issue goes away. If this is a fresh install of the script with nobody in your killfile then I’m not sure what’s going on and will have to investigate further (mine still works fine)

Darren | October 26, 2007 at 1:37 am

Does this work with google reader too?

Author comment by Damian | October 26, 2007 at 6:08 am

It doesn’t no Darren, but I’ll take a look at implementing it.

Darren | October 27, 2007 at 1:08 am

Great, thanks Damian. It’d be even more useful if it did since I’ve started to use Google reader from both a google gadget and reader itself.
Cheers :)

Mitch | November 14, 2007 at 9:31 am

Damian,
Great idea, but I seem to be doing something wrong. I have greasemonkey installed into Mozilla firefox (v 1.5), and clicked on the link…confirmed the import of the script etc…but I still don’t see any Xs near author names in the google groups view…I’m clicking on the group name from my google homepage…do I need to do something different?
Thanks,
Mitch

Author comment by Damian | November 14, 2007 at 9:37 am

Mitch, in the topic list view the X is at the end of the authors name, and before the date. While in the topic summary view, there is a link Ignore User after the authors name.

Verify that in Greasemonkey the script is active. Right click on the monkey icon in Firefox’s status bar and you should see a check mark next to Google Groups Killfile.

Hope this helps. I just confirmed Google hadn’t changed anything and my copy of it is still working so hopefully this helps.

John | November 20, 2007 at 7:42 am

Damian,

Really like the killfile but I do have a question.

Would it be possible to modify (or add) a script to filter by the thread topic. I frequent a group where people just cannot resist the urge to reply to trolls. So, while the troll’s message is blocked, the topic still shows up since others have added their two cents worth. It would be nice to be able to kill an entire topic regardless of who contributed to it after it was started.

Thanks for all the hard work!

moontaco | November 24, 2007 at 9:57 am

Hi Damian. How does one uninstall the Killfile? I think that might be a good idea for me. Ever since I reinstalled (after Google Groups went beta), it’s been acting kind of wonky, and is increasingly blocking messages of people I never would have killfiled. So it seems to me that if I could uninstall it all, then reinstall it (starting over), that probably wouldn’t be happening, or at least, not at first.

Beth

Author comment by Damian | November 24, 2007 at 5:47 pm

To uninstall right click on the Greasemonkey icon, then manage scripts. You can uninstall from there. You might just want to click on the killfile menu item top right though to show the people on your list. If the names on there are too generic say ‘ab’ that would block anyone called *ab* i.e anyone with ab anywhere in the name because it wildcards the beginning and end of the entry. Delete folk until it starts working again.

moontaco | November 25, 2007 at 7:08 am

Hey Damian. I wanted to try uninstalling because of the wonkiness (hard to describe what I mean–just occasional oddities), so I did that, then reinstalled. Now, does this make sense? When I reinstalled it, it still had my old killfile list. I thought that would have all been wiped out.

Anyway, I am still having the same problem of it blocking people I don’t intend for it to block. The one name I could remember and check was Kevin Brady. I looked down my killfile list for anything that bore any resemblance to Kevin or Brady, but there was nothing on there.

Thanks,
Beth

Ipunty | November 26, 2007 at 1:01 am

Please email this poor man. He’s been trying to figure out what to download and where to install it, step by step. And then what happens . Does an icon show up when he enters Google? Does it filter threads and posters?
He’s using Google with Firefox

Or please write a step by step (above)
He’s a cancer patient who is trying to read and post to the newsgoup
And wants to block posters and threads.

I realize your product is free, but we need some help. If one person learns it, they can explain to the others. I don’t use Google and don’t use Firefox.
Thank you.

Author comment by Damian | November 26, 2007 at 8:07 am

IPunty, which part of the instructions above is he having an issue with?

AGT | November 27, 2007 at 12:27 am

Very useful however I seem to have found a bug. If the killfile targetee shows as a single character like “h”
and you add this poster to the ignore user list, nothing works properly anymore :

Merv Hrabi | November 27, 2007 at 3:36 am

It looks like a blank posting stopp the filtering of any remaining lines in the goolge groups. Okay on next page dispalyed.

Any chance of gettign a fix for this.

tiwag | December 18, 2007 at 5:29 am

is greasemoney verrsion 0.6.4 mandatory ?
i can’t find it for download

with the actual grasemonkey 0.7 (and firefox 2.0.0.11) i couldn’t install your latest script ( googleGroups.user.js )

any ideas ? thank you

Author comment by Damian | December 18, 2007 at 9:45 am

It’s working fine for me under 0.7 tiwag. What happens when you try and install it?

tiwag | December 18, 2007 at 10:15 am

Hi Damian !
thanks for the reply, now it’s working for me too.
i don’t know why but when i tried first to install your greasemonkey googleGroups.user.js script it didn’t work and no X’s were shown when browsing the google groups. so i thought it isn’t compatible with a newer grasemonkey version that posted in the requirements list.

happy that it’s working now with
Firefox 2.0.0.11
GreaseMonkey 0.7
and your latest Google Groups killfile script ( http://www.penney.org/googleGroups.user.js )

thanks !
brgds tiwag

tiwag | December 18, 2007 at 10:25 am

(removed typos from previous posting)

Hi Damian !
thanks for the reply, now it’s working for me too.
i don’t know why but when i tried first to install your greasemonkey googleGroups.user.js script it didn’t work and no X’s were shown when browsing the google groups. so i thought it isn’t compatible with a newer greasemonkey version than the one posted in the requirements list.

i’m happy that it’s working now with
Firefox 2.0.0.11
GreaseMonkey 0.7
and your latest Google Groups killfile script
( http://www.penney.org/googleGroups.user.js )

thanks !
brgds tiwag

darryl ramm’s blog » Computer Upgrade Time - Back to the Macintosh? | December 19, 2007 at 3:04 pm

[...] add-on, so runs on multiple platforms. I rely on this plug-in to run the KillFile script that gives kill files like behavior for Google [...]

Archon | December 31, 2007 at 10:24 pm

Would it be possible to make this script when it removes the posts by killfiled people grab enough posts from the next page to make it be the normal 30 posts per page? This would speed up browing the archives.

Adam | January 1, 2008 at 3:09 pm

I’ve found one user I can’t seem to killfile – see original poster at this URL :
http://groups.google.com/group/aus.tv/browse_frm/thread/b1e336ab72bfeba7/bda3ec8d28aebb3b#bda3ec8d28aebb3b
It’s another MI5 persecution post, so I’d like to kill it. However, when I add it to my killfile, the script stops displaying X’s and still displays both this user and several other users that are already in my kill file.

Any suggestions ?

Thanks,
Adam

SN | January 2, 2008 at 2:28 pm

thx for the plugin, its great !

req: can it do subject based kill, because theres always these MI5 spammers, and they use the MI5 in subject, or M’I5 or M-I`5 or you understand, its the letters M, I, 5, and sometimes with another letter or symbol between those.

?

Monty | January 2, 2008 at 8:27 pm

Any chance of adding a wildcard (*) feature in the subject line to kill such nuisances as the “MI5 Persecution” plague? Also, it would be great to have the ability to kill posts by boilerplate text, like signatures, in order to keep ahead of the rapid nym-shifters (like Rob Cypher).

bo | January 3, 2008 at 9:46 am

it would be great to hide all posts by crossposters cause he always hits lots of groups symul

so block all that have more than one newsgroup listed

Simon | January 4, 2008 at 5:59 pm

Damian: There is a problem adding names with apostrophes, punctuation, or spaces in the username. For example, “who’sthat” or “Hi, I’m Chucky”. Is there a method to add the name manually? What file are the names store in?

Author comment by Damian | January 4, 2008 at 6:10 pm

Sorry for the late replies guys…

Simon: The names aren’t stored in a file, they are a firefox property, type about:config and you’ll find them in there (filter for gg or kill i think). You are spot on in that apostrophes will hurt it, need a better way to escape them when I add them.

Monty: Subject based killing is definitely doable but I simply don’t have the time at the moment to implement it

Adam: Hmmm, I’ll have to look into that and get back to you

Archon: That isn’t possible I’m afraid, the script can only work with the data on the page served.

AGT: That is a problem yes, I wildcard the entire username so h becomes *h*.. I forget why :) I’ll look into fixing that.

Jeff | January 5, 2008 at 12:50 am

I’ve hacked up the topic list handling in the copy I’m using so that it kills by topic, rather than user, and does a regular expression match, rather than a check for equality, if you’d like to look at it.

The changes aren’t major; when handling the topic list, it uses a different XPath pattern and uses RegExp’s exec rather than equality when checking for a match; it prepends “User:” or “Topic:” to the killfile entry, depending on which it is; and it prompts the user in the killfile set routine to allow the user to edit the killfile entry before entering it.

Mark W | January 5, 2008 at 7:30 am

Damian, thanks for the note on about:config .

Using kill in the filter box works. Then I double-click on the greasemonkey entry that appears, and get a text-editable box with the killfile list.

Some questions:
1. So, we can just go ahead and edit the killfile list?
2. Can we do wildcard characters?
2a. And, is * the proper wildcard, or something is else?
3. What is the meaning of all the “…” appearing in the list entries?

Thanks Damian, great work on providing this service to us!

Mark

p.s. I find it easier to copy-and-paste the killfile list into a text editor like notepad, so that the entire string can be seen at once.

Author comment by Damian | January 5, 2008 at 9:58 am

Jeff thanks for updating the script; if you send me the changes you made and I’ll host them here, I was working on something similar last night but no point duplicating effort.

Mark, the … is how Google shows actual email addresses, they do it so spammers can’t just scrape addresses via Google Groups (not that they couldn’t just do it via another Usenet client). Wildcarding won’t work right now, lets see how Jeff implemented it and maybe that would work.

S | January 8, 2008 at 8:57 pm

Great little script you’ve built there! I was thrilled to find it, as I really didn’t want to install a dedicated newsreader, but was dealing with a real noisy troll problem. Thanks so much.

Just some quick feedback: Someone mentioned ~’s in usernames causing a problem. I’m also see this behaviour with other non-ascii characters, for instance

By JonnyQuest2®

doesn’t give you the “ignore user” option.

Thanks again.

Fred Goodwin | January 12, 2008 at 11:28 am

Damian:

Another satisfied customer here. I tried the BHO for MSIE over at holysmoke.org, but your script works better and is more intuitive — it was enough to make me switch from MSIE to Firefox (at least for reading Google Groups!).

Thanx,

Fred Goodwin

Fred Goodwin | January 17, 2008 at 8:08 am

Damian: thanx for the script — I’m having the same problem as Adam.

Somewhere along the way, the “X”s stopped displaying and I can’t seem to bring them back (although “Ignore User” is still showing on individual posts). I’ve tried un-killing various troll-names, to no avail.

Even restoring my entire killfile doesn’t bring back the Xs.

Author comment by Damian | January 17, 2008 at 8:34 am

Fred, Jeff Urs has done some work on the script and I’ll be posting that shortly. I’ll explain the new features and upload it later today. Hopefully it will take care of any issues you are having.

Fred Goodwin | January 17, 2008 at 1:02 pm

Damian:

Thanx — I know you’re not being paid to support us, but you do have our everlasting gratitude.

Fred Goodwin | January 17, 2008 at 1:39 pm

Another bit of info:

My KF is empty but the Xs still don’t appear in the NG I read most often. However, if I go to a NG I’ve never read before, I see the Xs.

Not sure if that helps you diagnose the problem, but I thought I’d post it.

Thanx again.

Fred Goodwin | January 17, 2008 at 1:51 pm

Sorry to keep coming back — someone posted this string as a way to filter all the MI5 spam:

{M[,'` \.\-]I[,'` \.\-]5.p.}

It assumes you can filter on subject, which I don’t think you’re current script does. But just in case any of the readers know how to do it, I thought I’d add this contribution.

Author comment by Damian | January 17, 2008 at 2:26 pm

I’ve just released the new version with Jeff’s updates (better author matching/topic blocking). Please post comments to the new 3.4 thread

<< Google Groups KillFile 1.4 Released

Find it!

Theme Design by devolux.org