penney dot org

FYI: I was having a problem getting the new script to update that had been going on since approximately version 4.0. Firefox would show that the new script was loaded (newest version), but the changes wouldn’t take effect. Despite updating, the behavior of the program didn’t change, and new features didn’t show up. Uninstalling/reinstalling didn’t work.

I finally decided to delete the killfile variable from prefs.js (with Firefox closed), and voila…the new script started working, with the new features such as topic suppression, etc.

I don’t know if this was a bug, or what. My killfile was quite long–well over 100 entries–and it had stopped working for some time, nothing was being killed. There might be a limit to the length of the variable?

Works like a charm now! Thanks.

I installed Google Groups KillFile (FireFox) and it worked great. I exited Google Groups and when I reentered Google Groups, my KillFile content was reset to empty. How can I save my killfile so that I don’t have to reenter the content to kill each time I enter Groups Google?

Thank you,
Michael

[apologies is this posts twice...not sure it went throught first time]

Hi Damien,

Thanks so much for the script–it is so nice to have this.

I wanted to point out something I discovered that was keeping it from working correctly in my browser/Greasemonkey configuration (I believe…I’m not a programmer).

I was having that symptom where the “X”s wouldn’t display to the right of topic or author. I tried disabling a bunch of my add-ons to no avail (NoScript, AdBlock, FlashGot, TrackMeNot, Customize Google), then finally it dawned on me to try disabling other Greasemonkey scripts.

Turned out, another Geasemonkey script I’m using, “Pagerization”, seems seems to interfere with Killfile. So I’ll have to abandon it or perhaps I can turn them on and off as needed.

You (or anyone reading), please let me know if you have thoughts or solutions on this issue. I should get an email notifiication if more comments are made here.

Cheers,
Cal

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

I still can’t seem to get any sort of regex based wildcarding to work. For example .*@163.com doesn’t eliminate all posters from 163.com.. (I really wish it would).

– HappyHax0r

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

@HappyHax0r:

Sorry, but I haven’t used this script in ages. But are you definitely adding a regular expression?

IIRC, you need to go into the “killfile” and do “Edit regular expression”. By default it escapes all the RE chars (so as to preserve the old behaviour) so you need to manually remove them again in that dialog to actually use a regular expression.

@Doc Martian

All I can suggest is using a regular expression and try killfiling on something like phin$ or phin[^e]. I’ve no idea which (if either) of these might work.

Tim.

My Firefox browser recently updated Greasemonkey automatically, and since then, the clickable link at the top of the page that allows one to access the list of blocked authors and titles is no longer visible. The killfile still works as before, and I can still add authors and topics to the killfile by clicking on the Xs, but I cannot delete authors and/or topics or edit them to include regular expressions. Can anyone tell me how to access the list again? Thanks

Dilip Sarwate

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.

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

Dear Damien. [Running Firefox 3.5.5 under Mac OSX 10.5.8]
I’m seeing the same phenomenon as reported by Tater
Gumfries (October 19th, 2009) that no killfile button is
visible. I can find no way to see nor edit the killfile.

While I have not done extensive experiments, I’ve
verified that no other greasemonkey script is triggering
on the google-groups page, and I’ve disabled most
add-ons, and returned FF to its default theme; alas no
joy. Is it possible that Google Groups has changed its
format? (By the way, in FF on MacOSX, in what file is
the killfile stored?)
Thanks again Damien for your fine script.
Sincerely, -gentsquash

@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);