So looks like Greasemonkey changed the way I was supposed to save things within Firefox which prevented the KillFile from being updated. Quick fix and it looks like we are back in business :)
Here is the link to the updated script.
If you need to clear your old kill list completely just type about:config into the address bar and then seach for killfile – right click and reset that to clear your list.
Tags: Google Groups, killfile
Is there a way to format the script so as to examine the message headers of a Usenet post, and remove cross-posted messages? This would be greatly appreciated, as it would allow us to killfile those huge trolling cross-posted threads that go across many different newsgroups.
Where can I check the version number on my copy? Displaying it at the bottom of the menu for editing the killfile seems like a convenient place.
Now if there was just an upgrade to catch all those decorated spam ads.
hahaha — I had to look at the Greasemonkey manual to remember how easy installing was … putting it on a new machine taxed my grey cells.
-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
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
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.
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.
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
Great script! I am having problems killing names with special characters. One nick is (^^/). Nicks that have ‘ also do not work. Again, great job.
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.
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.
Is the script working currently? I’m not seeing the x’s. Haven’t rebooted yet though.
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.
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