Google Groups KillFile 3.5.1 Released
There was a bug in the new script that messed things up when you drilled into a thread, Tim caught the bug and I’ve gone ahead and updated the script, so please update to Google Groups KillFile 3.5.1
Tags: Google Groups, killfile
[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
Yes. There’s a bug somewhere killing the posts when the posters name contains a dot.
There’s another bug attempting to kill a poster (and possibly a thread) where it contains a single quote.
I’ve seen both of them but I just haven’t had time to investigate. I suspect the first one is something to do with regular expression matching while the second is related to what the HTML actually looks like and the javascript call it inserts.