Comments on: Google Groups KillFile 3.5.3 Released http://www.penney.org/google-groups-killfile-3-5-3-released.html a little knowledge is a dangerous thing Fri, 09 Sep 2011 15:29:05 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: B. Weaver http://www.penney.org/google-groups-killfile-3-5-3-released.html/comment-page-1#comment-48880 B. Weaver Wed, 11 May 2011 18:34:13 +0000 http://www.penney.org/google-groups-killfile-3-5-3-released.html#comment-48880 I tried posting this yesterday, but it did not show up on the website...so apologies if it does eventually appear twice. The killfile script has been working very well for me for quite a while. However, I just started having a very strange problem with it: I.e., it now works ONLY when I'm not logged in to my Google account. When I log in, all evidence of the script vanishes--e.g., no options to ignore users or topics, and topics/users that are abolished to the killfile when I'm not logged in suddenly reappear. Has anyone else experienced this? I'd be grateful for any thoughts on how to fix it. Cheers, Bruce I tried posting this yesterday, but it did not show up on the website…so apologies if it does eventually appear twice.

The killfile script has been working very well for me for quite a while. However, I just started having a very strange problem with it: I.e., it now works ONLY when I’m not logged in to my Google account. When I log in, all evidence of the script vanishes–e.g., no options to ignore users or topics, and topics/users that are abolished to the killfile when I’m not logged in suddenly reappear.

Has anyone else experienced this? I’d be grateful for any thoughts on how to fix it.

Cheers,
Bruce

]]> By: B. Weaver http://www.penney.org/google-groups-killfile-3-5-3-released.html/comment-page-1#comment-48867 B. Weaver Wed, 11 May 2011 01:04:01 +0000 http://www.penney.org/google-groups-killfile-3-5-3-released.html#comment-48867 Just wondering if anyone else has encountered this problem: The killfile script works just fine, but only when I'm not logged in to my Google account. As soon as I do log in, all evidence of the script vanishes, and messages/threads I've killed reappear. Any thoughts on why this is happening? Thanks. Just wondering if anyone else has encountered this problem: The killfile script works just fine, but only when I’m not logged in to my Google account. As soon as I do log in, all evidence of the script vanishes, and messages/threads I’ve killed reappear. Any thoughts on why this is happening? Thanks.

]]> By: Jim D in TN http://www.penney.org/google-groups-killfile-3-5-3-released.html/comment-page-1#comment-48734 Jim D in TN Thu, 05 May 2011 11:42:22 +0000 http://www.penney.org/google-groups-killfile-3-5-3-released.html#comment-48734 Is the script working currently? I'm not seeing the x's. Haven't rebooted yet though. Is the script working currently? I’m not seeing the x’s. Haven’t rebooted yet though.

]]> By: Mike http://www.penney.org/google-groups-killfile-3-5-3-released.html/comment-page-1#comment-48134 Mike Sun, 10 Apr 2011 04:12:45 +0000 http://www.penney.org/google-groups-killfile-3-5-3-released.html#comment-48134 The latest version of Greasemonkey (9.X) breaks the fabulous killfile script, so I reverted to the last 8.X version. I'm using Firefox 3.6, and the older version of Googlegroups. The latest version of Greasemonkey (9.X) breaks the fabulous killfile script, so I reverted to the last 8.X version. I’m using Firefox 3.6, and the older version of Googlegroups.

]]> By: just john http://www.penney.org/google-groups-killfile-3-5-3-released.html/comment-page-1#comment-43305 just john Tue, 07 Dec 2010 21:23:45 +0000 http://www.penney.org/google-groups-killfile-3-5-3-released.html#comment-43305 You'll note Google is rolling out a new way of doing Groups. If you release an updated version of your script, you'll continue to be My Hero. Thanks for all you've done so far. You’ll note Google is rolling out a new way of doing Groups.

If you release an updated version of your script, you’ll continue to be My Hero.

Thanks for all you’ve done so far.

]]> By: Anonymous http://www.penney.org/google-groups-killfile-3-5-3-released.html/comment-page-1#comment-43263 Anonymous Sun, 05 Dec 2010 23:48:11 +0000 http://www.penney.org/google-groups-killfile-3-5-3-released.html#comment-43263 Great script! I am having problems killing names with special characters. One nick is (^^/). Nicks that have ' also do not work. Again, great job. Great script! I am having problems killing names with special characters. One nick is (^^/). Nicks that have ‘ also do not work. Again, great job.

]]> By: Bruce http://www.penney.org/google-groups-killfile-3-5-3-released.html/comment-page-1#comment-41071 Bruce Wed, 19 May 2010 17:35:27 +0000 http://www.penney.org/google-groups-killfile-3-5-3-released.html#comment-41071 I have an entry in my killfile that hides the poster in the treelist, but the postings still show. What am I doing wrong? -d I have an entry in my killfile that hides the poster in the treelist, but the postings still show. What am I doing wrong?

-d

]]> By: David http://www.penney.org/google-groups-killfile-3-5-3-released.html/comment-page-1#comment-41025 David Sat, 15 May 2010 18:31:41 +0000 http://www.penney.org/google-groups-killfile-3-5-3-released.html#comment-41025 Richard -- the slash is actually be a backslash, which in regular expression argot usually means that the next character is to be used "as is" instead as a special regular expression thingy. In the names my killfile has problems with, there is a '.' as seen in the google news view, and "backslash dot" in the killfile. Even the shorter ones fail to kill properly, so it isn't just the length of the name that is the issue. Editing the killfile entry with Z, I've replaced "\." with ".*" (more regular expression argot), but the posts aren't successfully killed this way, either. For some examples, in sci.space.shuttle there some posters who include an initial and a period in their display names. The killfile presently does not kill them. Richard — the slash is actually be a backslash, which in regular expression argot usually means that the next character is to be used “as is” instead as a special regular expression thingy.

In the names my killfile has problems with, there is a ‘.’ as seen in the google news view, and “backslash dot” in the killfile. Even the shorter ones fail to kill properly, so it isn’t just the length of the name that is the issue. Editing the killfile entry with Z, I’ve replaced “\.” with “.*” (more regular expression argot), but the posts aren’t successfully killed this way, either.

For some examples, in sci.space.shuttle there some posters who include an initial and a period in their display names. The killfile presently does not kill them.

]]> By: Richard http://www.penney.org/google-groups-killfile-3-5-3-released.html/comment-page-1#comment-40029 Richard Thu, 18 Mar 2010 18:10:46 +0000 http://www.penney.org/google-groups-killfile-3-5-3-released.html#comment-40029 Further to my last post, when I check the list of banned posters, the window is of insufficient length to show the entire alias, and it also shows incorrect transcription - what above is a sequence of periods turns into a sequence of periods and slashes. Also, I could not remove the incorrect alias from the killfile - there was no room to do it. Further to my last post, when I check the list of banned posters, the window is of insufficient length to show the entire alias, and it also shows incorrect transcription – what above is a sequence of periods turns into a sequence of periods and slashes. Also, I could not remove the incorrect alias from the killfile – there was no room to do it.

]]> By: Richard http://www.penney.org/google-groups-killfile-3-5-3-released.html/comment-page-1#comment-40028 Richard Thu, 18 Mar 2010 18:02:53 +0000 http://www.penney.org/google-groups-killfile-3-5-3-released.html#comment-40028 Wow, thanks for updating your wonderful script. Is there any way to get it to work on jerks who use very long aliases. I tried it on //SHOES THROWER\....................................................................................................................................................}|{@........................................................................\> and although the x appears, it does not block him. Thanks for your work. Richard Wow, thanks for updating your wonderful script. Is there any way to get it to work on jerks who use very long aliases. I tried it on
//SHOES THROWER\………………………………………………………………………………………………………………………………….}|{@………………………………………………………………\>

and although the x appears, it does not block him. Thanks for your work.

Richard

]]>