Comments on: Google Groups KillFile 3.5.1 Released

By: Damian

Damian — Mon, 30 Nov 2009 16:20:59 +0000

Thanks for the fix. I've incorporated the change into version 3.5.2 which can be found here I've also closed comments for this version, please post any new comments to the 3.5.2 release post

By: Anonymous

Anonymous — Mon, 30 Nov 2009 16:01:59 +0000

@Tater
Fixed it… I just changed some xpath stuff:

// Add the Killfile Menu Option to the top nav
candidates = document.evaluate(“//DIV[@class='gtopbar']//nobr//a”, document, null, XPathResult.ORDERED_NODE_SNAPSHOT_TYPE, null);

becomes

// Add the Killfile Menu Option to the top nav
candidates = document.evaluate(“//DIV[@id='guser']//nobr//a”, document, null, XPathResult.ORDERED_NODE_SNAPSHOT_TYPE, null);

By: damian

damian — Mon, 19 Oct 2009 18:56:53 +0000

I’ll see if I can take a look and figure out what’s happened. Bear with me.

By: Tater Gumfries

Tater Gumfries — Mon, 19 Oct 2009 18:55:01 +0000

The killfile button no longer appears on my upper right set of choices, and it is the same on all my computers. I have tried reinstalling both the Google Groups Killfile script, as well as Greasemonkey, and there is no effect. I cannot access the killfile contents to set old offenders free.

By: Tater

Tater — Sun, 18 Oct 2009 18:20:41 +0000

Tater is unable to see the kill bin anymore. They’s folks in the bin that Tater wants to let out, but there ain’t no way of doin it no more. Tater tried uninstallin and reinstallin, both the greasemonkey and the Google Groups killfile, but that didn’t help.

By: Tater

Tater — Sun, 18 Oct 2009 18:10:17 +0000

“There’s also a bug where the script wildcards too easily. eg: There’s a poster ‘Phin’ and whenever I killfile him, the posts for ‘Dr. Phineas J. Martian’ killfile as well.”

That’s not a bug — that’s a feature. Next version will killfile you automatically as the default.

By: Doc Martian

Doc Martian — Mon, 04 May 2009 23:51:27 +0000

There’s also a bug where the script wildcards too easily. eg: There’s a poster ‘Phin’ and whenever I killfile him, the posts for ‘Dr. Phineas J. Martian’ killfile as well.

By: HappyHax0r

HappyHax0r — Fri, 03 Apr 2009 16:18:39 +0000

Tim, since you appear to be a developer on this:

I cannot seem to get wildcard blocking to work… I’ve tried .*@163.com, and [A-Za-z0-9]+@163.com (both valid regular expressions that work for this address in perl), and neither of them block all posts from 163.com.

Any suggestions?

– HappyHax0r

By: Tim

Tim — Thu, 11 Sep 2008 12:12:12 +0000

Yes. There’s a bug somewhere killing the posts when the posters name contains a dot.

There’s another bug attempting to kill a poster (and possibly a thread) where it contains a single quote.

I’ve seen both of them but I just haven’t had time to investigate. I suspect the first one is something to do with regular expression matching while the second is related to what the HTML actually looks like and the javascript call it inserts.

By: Richard

Richard — Mon, 08 Sep 2008 14:43:31 +0000

Hi Damien,

As ever, thanks for this great script. Let me describe what I am experiencing. When I click on the X on the poster B.H.Cramer, his posts vanish from the group header list. When viewing a thread, his name disappears from the tree, although should he change the subject, the new subject does appear in the tree. His messages do still appear in the message list to the right of the tree. If standard view is chosen, his messages appear. In the killfile, his name appears as
B\.H\.Cramer . If I try to edit, the name appears in the edit window without backslashes.

Thanks,
Richard