Comments on: Google Groups KillFile 3.4.2 Released http://www.penney.org/google-groups-killfile-342-released.html a little knowledge is a dangerous thing Sat, 15 May 2010 18:31:41 -0700 hourly 1 http://wordpress.org/?v=3.0 By: Damian http://www.penney.org/google-groups-killfile-342-released.html/comment-page-1#comment-30928 Damian Thu, 11 Jun 2009 13:37:46 +0000 http://www.penney.org/google-groups-killfile-342-released.html#comment-30928 Until Chrome supports plugins this isn't something I'm going to actively work on. I think there is a way you can install GM scripts in Chrome, so it might work as-is but it's not something I've tried. Until Chrome supports plugins this isn’t something I’m going to actively work on. I think there is a way you can install GM scripts in Chrome, so it might work as-is but it’s not something I’ve tried.

]]> By: Simon http://www.penney.org/google-groups-killfile-342-released.html/comment-page-1#comment-30901 Simon Thu, 11 Jun 2009 06:08:09 +0000 http://www.penney.org/google-groups-killfile-342-released.html#comment-30901 Do you have a version of this for Google Chrome yet? Or do you plan on setting one up in the near future? Thanking you in advance. Do you have a version of this for Google Chrome yet? Or do you plan on setting one up in the near future? Thanking you in advance.

]]> By: Damian http://www.penney.org/google-groups-killfile-342-released.html/comment-page-1#comment-16517 Damian Wed, 19 Mar 2008 12:52:47 +0000 http://www.penney.org/google-groups-killfile-342-released.html#comment-16517 Ahh, good idea Tim, I'll incorporate this change in the next release. Ahh, good idea Tim, I’ll incorporate this change in the next release.

]]> By: Tim http://www.penney.org/google-groups-killfile-342-released.html/comment-page-1#comment-16516 Tim Wed, 19 Mar 2008 12:47:51 +0000 http://www.penney.org/google-groups-killfile-342-released.html#comment-16516 Hmm, Seem to be having problems posting a comment. Second try. I've made the following changes to my version that fixes the problem where multiple patterns attempt to kill the same topic: --- googlegroupskillfile.user.js.orig 2008-03-19 12:45:16.791559000 +0000 +++ googlegroupskillfile.user.js 2008-03-19 12:45:16.081662000 +0000 @@ -179,8 +179,7 @@ var user = cand.textContent; var blocked = false; - for (var j=0; j<list.length; j++) { - blocked = false; + for (var j=0; !blocked && j<list.length; j++) { topicRE.compile("^" + list[j]); if (topicRE.test(topic) || topicRE.test(user)) { @@ -275,9 +274,9 @@ for (var i=0; i<candidates.snapshotLength; i++) { var cand = candidates.snapshotItem(i); var user = cand.textContent; + blocked=false; - for (var j=0; j<list.length; j++) { - blocked = false; + for (var j=0; !blocked && j= 0) { wrappingTable = document.evaluate("ancestor::table[2]", cand, null, XPathResult.ORDERED_NODE_SNAPSHOT_TYPE, null); Tim. Hmm, Seem to be having problems posting a comment. Second try.

I’ve made the following changes to my version that fixes the problem where multiple patterns attempt to kill the same topic:

— googlegroupskillfile.user.js.orig 2008-03-19 12:45:16.791559000 +0000
+++ googlegroupskillfile.user.js 2008-03-19 12:45:16.081662000 +0000
@@ -179,8 +179,7 @@
var user = cand.textContent;
var blocked = false;

- for (var j=0; j<list.length; j++) {
- blocked = false;
+ for (var j=0; !blocked && j<list.length; j++) {

topicRE.compile(“^” + list[j]);
if (topicRE.test(topic) || topicRE.test(user)) {
@@ -275,9 +274,9 @@
for (var i=0; i<candidates.snapshotLength; i++) {
var cand = candidates.snapshotItem(i);
var user = cand.textContent;
+ blocked=false;

- for (var j=0; j<list.length; j++) {
- blocked = false;
+ for (var j=0; !blocked && j= 0) {
wrappingTable = document.evaluate(“ancestor::table[2]“, cand, null, XPathResult.ORDERED_NODE_SNAPSHOT_TYPE, null);

Tim.

]]> By: Damian http://www.penney.org/google-groups-killfile-342-released.html/comment-page-1#comment-16396 Damian Tue, 11 Mar 2008 18:24:55 +0000 http://www.penney.org/google-groups-killfile-342-released.html#comment-16396 I've just uploaded an updated script 3.4.3 that I think has addressed the problems. Please let me know of any cases where it doesn't work (include a URL and the username) and I'll update things as necessary. Happy Blocking. I’ve just uploaded an updated script 3.4.3 that I think has addressed the problems. Please let me know of any cases where it doesn’t work (include a URL and the username) and I’ll update things as necessary.

Happy Blocking.

]]> By: Damian http://www.penney.org/google-groups-killfile-342-released.html/comment-page-1#comment-16374 Damian Mon, 10 Mar 2008 04:48:38 +0000 http://www.penney.org/google-groups-killfile-342-released.html#comment-16374 It is yes. I plan to get this fixed early this week. Bear with me. It is yes. I plan to get this fixed early this week. Bear with me.

]]> By: Michael McNeil http://www.penney.org/google-groups-killfile-342-released.html/comment-page-1#comment-16369 Michael McNeil Sun, 09 Mar 2008 23:54:59 +0000 http://www.penney.org/google-groups-killfile-342-released.html#comment-16369 Seems to find this type of address difficult to block: el...@no.spam probably: ellis@no.spam Is it something to do with munged addresses? This is the origial: Path: g2news1.google.com!news4.google.com!proxad.net!feeder1-2.proxad.net!usenet-fr.net!club-internet.fr!feedme-small.clubint.net!news-out1.kabelfoon.nl!newsfeed.kabelfoon.nl!bandi.nntp.kabelfoon.nl!sn-xt-ams-06!sn-xt-ams-05!sn-post-ams-02!sn-post-sjc-01!supernews.com!news.supernews.com!not-for-mail From: el...@no.spam () Newsgroups: sci.geo.earthquakes,alt.talk.weather Subject: Re: 17:14 Date: Sun, 09 Mar 2008 18:16:11 -0000 Organization: S.P.C.A.A. Message-ID: X-No-Archive: Yes References: X-Newsreader: trn 4.0-test76 (Apr 2, 2001) Originator: el...@no.spam () Cache-Post-Path: no.spam!unkn...@no.spam X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/) X-Complaints-To: abuse@supernews.com Lines: 9 Seems to find this type of address difficult to block:
el…@no.spam
probably: ellis@no.spam

Is it something to do with munged addresses?
This is the origial:

Path: g2news1.google.com!news4.google.com!proxad.net!feeder1-2.proxad.net!usenet-fr.net!club-internet.fr!feedme-small.clubint.net!news-out1.kabelfoon.nl!newsfeed.kabelfoon.nl!bandi.nntp.kabelfoon.nl!sn-xt-ams-06!sn-xt-ams-05!sn-post-ams-02!sn-post-sjc-01!supernews.com!news.supernews.com!not-for-mail
From: el…@no.spam ()
Newsgroups: sci.geo.earthquakes,alt.talk.weather
Subject: Re: 17:14
Date: Sun, 09 Mar 2008 18:16:11 -0000
Organization: S.P.C.A.A.
Message-ID:
X-No-Archive: Yes
References:
X-Newsreader: trn 4.0-test76 (Apr 2, 2001)
Originator: el…@no.spam ()
Cache-Post-Path: no.spam!unkn…@no.spam
X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/)
X-Complaints-To: abuse@supernews.com
Lines: 9

]]> By: Damian http://www.penney.org/google-groups-killfile-342-released.html/comment-page-1#comment-16327 Damian Thu, 06 Mar 2008 21:27:32 +0000 http://www.penney.org/google-groups-killfile-342-released.html#comment-16327 You are all right, the regexp thing hosed the app... I'll get it fixed in short order. Sorry about that. You are all right, the regexp thing hosed the app… I’ll get it fixed in short order. Sorry about that.

]]> By: Damian http://www.penney.org/google-groups-killfile-342-released.html/comment-page-1#comment-16025 Damian Wed, 13 Feb 2008 17:25:05 +0000 http://www.penney.org/google-groups-killfile-342-released.html#comment-16025 It used to work, but I haven't tested it since we moved to using regular expressions to do the matching (and . is a special regexp character) I'll do some testing and see if something broke. It used to work, but I haven’t tested it since we moved to using regular expressions to do the matching (and . is a special regexp character)

I’ll do some testing and see if something broke.

]]> By: Jeff Smith http://www.penney.org/google-groups-killfile-342-released.html/comment-page-1#comment-16024 Jeff Smith Wed, 13 Feb 2008 16:39:33 +0000 http://www.penney.org/google-groups-killfile-342-released.html#comment-16024 Is there a known issue with Ignoring 'truncated' user names. When new users sign up and don't give a nickname but give a long email address (ie. >35 characters), google truncates the username and inserts ellipsis just before the "@" sign in the User field of the post. At least in some cases, this seems to break the 'Ignore User' function. I've came across a particular case where a single poster is using two different User IDs: one with a nickname - which I can Ignore - and one with only the long email address - which I can't. To control harvesting of email address from Usenet, google now protects the expansion of those truncated User names with a character recognition task. Perhaps that's somehow blocking the 'matching' process between the entry in the Killfile, and the Used ID at the top of each post? Is there a known issue with Ignoring ‘truncated’ user names. When new users sign up and don’t give a nickname but give a long email address (ie. >35 characters), google truncates the username and inserts ellipsis just before the “@” sign in the User field of the post. At least in some cases, this seems to break the ‘Ignore User’ function. I’ve came across a particular case where a single poster is using two different User IDs: one with a nickname – which I can Ignore – and one with only the long email address – which I can’t.
To control harvesting of email address from Usenet, google now protects the expansion of those truncated User names with a character recognition task. Perhaps that’s somehow blocking the ‘matching’ process between the entry in the Killfile, and the Used ID at the top of each post?

]]>