Google Groups KillFile 3.4.2 Released

Well after poking around a bit I found all kinds of broken bits and pieces in the script and this release should work as you expect it to.

As always update your script by clicking on this link which will update your script to the latest and greatest.

Apologies with the bumpy release, hopefully it will be smooth sailing here on out.

Tags: ,

27 Responses to “Google Groups KillFile 3.4.2 Released”

  1. Nathan says:

    Damian,
    Everything appears to be working perfectly for me now!

    Thanks a ton,
    Nathan

  2. Damian says:

    Finally :) Glad it’s working out for you.

  3. Fred Goodwin says:

    Can someone post a topic:xxx I can use to kill all the MI5 spam?

  4. Mark W says:

    Hello Damien,

    I’m having a problem with adding topics & wildcards to the killfile list.

    For example, I click the X next to a post with this topic:
    M,I.5 P ersecution my res ponse to th e haras sment

    When the “edit window” pops up, I edit the topic name by adding the .* wildcard, changing the entry to:
    Topic:M,I.5.*

    However, the post still appears when I refresh the screen. And the killfile list does not have the string I entered, rather the entry has mysteriously morphed into this (extra “\” characters have been inserted):
    Topic:M,I\.5\.\*

    To “fix the problem” I can edit the entry in about:config, deleting the extra \ characters (which appear as %5C in the about:config entry)

    Another problem (related?). After having edited the entry in about:config, I cannot remove the entry by clicking on “Killfile” and clicking the X next to the entry there. I must go to about:config to remove it.

    Mark

    p.s. This problem happens with two versions of Greasemonkey, 0.7.20070607.0 and 0.7.20080121.0,
    and the recent Google Groups Killfile version 3.4.2 (I updated it on 1/26/08)

  5. Mark W says:

    Fred,

    The following seems to kill much, but not all, of the MI5 spam. Just copy-and-paste the following to the end of your kill list:

    %FFTopic%3AM%60I%205.*%FFTopic%3AM%27I-5.*%FFTopic%3AM%2CI.5.*%FFTopic%3AM-I%205.*%FFTopic%3AM.I%2C5.*%FFTopic%3AM%20I.5.*%FFTopic%3AM.I%275.*

    This will kill topics that begin with the following:
    M`I 5
    M’I-5
    M,I.5
    M-I 5
    M.I,5
    M I.5
    M.I’5

    Oddly, when I add %FFTopic%3AM%27I.5.* (to kill topics starting with M’I.5 ), ALL of the topics reappear, but without the “X” next to them.

    BUT … if I remove the previous entries, and have the same %FFTopic%3AM%27I.5.* ( M’I.5 ) so that it is the sole topic-killed item in the kill list, then topics with M’I.5 do disappear. Not only that, but topics with M’I-5 (which is not in the kill list) ALSO disappear.

    Weird.

    Regards,

    Mark

  6. Mark W says:

    FYI to Damian: one can test the string in my previous message by going to the group sci.engr.lighting, and view posts from Dec. 31 and Jan. 1 (2008). As of Jan. 26, this link will take you there:

    http://groups.google.com/group/sci.engr.lighting/topics?hl=en&start=710&sa=N

    — Mark

  7. Fred Goodwin says:

    Mark:

    Thanx!

    Fred

  8. Jim says:

    When a subject has been changed to a previously killfiled topic, the topic reappears and it appears that clicking on the X next to the new title has no effect.

    E.g,
    1. Title 1
    2. Renamed Title (Killfiled as expected)
    3. Re: Title 1
    4. 2nd Renamed Title (Clicking on X has no effect)

  9. SilentOtto says:

    First, I want to sing your praises for taking the time to write this script. I’ve been waiting for a long time for a Google Groups kill filter.

    It’s been working flawlessly for me with one exception.

    I’ve been trying to killfile a certain poster with no success.

    I read through the forum before I decided to bother you and, as another poster has already noted, that there seems to be a problem with adding kill file entries that contain an apostrophe (‘).

    The one that’s vexing me is a holocaust denier/spammer who signs his USENET posts “B’iny’amin C’r’amer”.

    As you can see, there are several apostrophes.

    Here’s a link to one of his posts, in case you need it:

    http://groups.google.com/group/soc.history.what-if/browse_frm/thread/0a6c8b69be662396#

    When I click the “X” next to his name, nothing happens.

    I can successfully killfile the thread, but not the poster.

    I’ve tried adding him manually, as recommended in other forum entries, with no success.

    The manual entry shows up in the killfile list, but there is no apparent effect on his posts. They continue to appear.

    These are the permutations that I tried.

    FFB’iny’amin C’r’amer

    FFB’iny’amin%20C’r’amer

    FFB%iny%amin C%r%amer

    FFB%iny%amin%20C%r%amer

    FFB%’%iny%’%amin%20C%’%r%’%amer

    Another interesting thing is that I cannot remove the entry I manually created from the killfile list by clicking on the “X” next to the entry.

    Again, when I do so, nothing happens.

    However, I can manually delete it and that gets rid of it.

    Is there something I’m missing?

    I really did try and figure this out on my own without bothering you, but I’m stumped.

    Thanks, and keep up the good work.

    Slackers like me depend on guys like you.

  10. SilentOtto says:

    First, I’d like to thank you for taking the time to write this script. There has long been need for a kill filter for Google Groups.

    It’s been working flawless for me with one exception.

    There seems to be a problem killfiling users that contain an apostrophe (‘) in their user name.

    I was unable to killfile a user who calls himself “B’iny’amin C’r’amer”.

    As you can see, there are several apostrophes.

    Here is a link to one of his posts in case you need it:

    http://groups.google.com/group/soc.history.what-if/browse_frm/thread/c694610fe0ab52f1#

    When I click on either the “X” next to his user name on the topic list page, or the “ignore user” tab on the message page, nothing happens.

    I can, however, killfile the entire thread that he’s posting to and that works as it’s supposed to.

    I read the forums, another poster mentioned this bug also.

    I followed the suggestion that I add the offending user name manually.

    When I did so, the name showed up in the killfile, but no action was taken in removing his posts.

    Following the advice of another forum post, I tried a number of variations on the name when I manually added the offender to the killfile.

    I tried:

    B’iny’amin C’r’amer

    B’iny’amin%20C’r’amer

    B%iny%amin%20C%r%amer

    B%’%iny%’%amin%20C%’%r%’%amer.

    None met with success.

    Again, the entries show up in the killfile, but no action is taken.

    Also, I was unable to remove the entries from the killfile by pressing the “X” next to them, and had to delete them manually after I discovered that they wouldn’t work.

    Am I missing something?

    Any suggestions would be appreciated.

    Again, thanks for taking the time to write this script. Aside from this little problem it works great.

  11. Richard says:

    Hi Damian,

    First of all, I want to thank you for this script. It has really provided a more enjoyable google groups experience for me. I have found what appears to be a bug in the latest version as well as some previous versions. When an author’s “name” is very long, like over 100 characters, which is permitted by google, clicking on the X next to the name in Topic List or on Ignore User in Topic Summary does nothing – it just sits there. There is one moron who is ruining the group I am in by constantly posting from a day in the future from his chinese server, thus always appearing on top, and he chooses very long names. If you could fix this, I would be much obliged. Thanks, Richard

  12. Jeff Smith says:

    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?

  13. Damian says:

    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.

  14. Eternal thanks says:

    I concur with Jeff Smith. There is a bug when adding names that have an email address and no user name. Google represents the address with an ellipsis.

    chinawholesal…@hotmail.com becomes:

    %FFchinawholesal\.\.\.@hotmail\.com

  15. George says:

    The topic filter doesn’t work at all for me. There is no “X” to kill the topic, unless I am doing something wrong. Also, it seems to be having trouble both with truncated addresses, and with names with spaces/special characters. The reg-ex expressions don’t appear to work (MI5* filters previously posted don’t work). Thanks.

  16. Tim says:

    I think there might be a problem where both the subject and author of the same post are killfilled. It’s not hiding the posts but is hiding the Xs to killfile for any killfiled posts.

  17. Michael McNeil says:

    Thank you for the script.

    I keep losing topics that are replied to by the posters I have killfiled. This thread problem only seems to occur when the ignored is the latest person to post a reply.

    I think it reappears when someone else puts their monica below it.

    Where can I find this script or programme on Windows XP? Is it part of Firefox or should it appear in the Programmes list in the Start menu?

  18. Damian says:

    You are all right, the regexp thing hosed the app… I’ll get it fixed in short order. Sorry about that.

  19. Michael McNeil says:

    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

  20. Damian says:

    It is yes. I plan to get this fixed early this week. Bear with me.

  21. Damian says:

    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.

  22. Tim says:

    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.

  23. Tim says:

    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.

  24. Damian says:

    Ahh, good idea Tim, I’ll incorporate this change in the next release.

  25. Simon says:

    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.

  26. Damian says:

    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.

  27. Marius Andersen says:

    Thank you so much for making this. Where is the link for editing the list?

Leave a Reply

You must be logged in to post a comment.