Killfile launched as extension for chrome, firefox

[dtm]

In my previous post, I said I was working on a version of my old killfile script as a chrome extension.

Well, that's now happened! And I have it as both a firefox and a chrome extension. (Same source, mostly.) I still need to go through and clean out the list of supported sites, but note that in addition to the sites it supports directly, it also supports any site that uses disqus through an iframe. (Like rawstory.com, wired.com, and many, many others; sadly, Shakesville uses disqus in a different manner that I can't handle yet)

1. Killfile for chrome


2. Killfile for firefox

The chrome extension can also be found by going to the chrome webstore and searching for it; the firefox addon can't be found by going to the main page and searching because firefox has a review process for addons that's really slow. It might be reviewed by Christmas.

On chrome, your killfile list is shared across all your devices if you sign into chrome and do the chrome sync thing. On firefox, it's strictly local.

The full source is on github.

Comments

[(Anonymous)]

First off, Thenk you!
Seems to work fine so far with one exception:
In a long nested sub-thread within a comment thread, it seems to stop after 15 comments, leaving all comments after that immune, including the poster you "hushed".

[dtm]

Do you have an example page where this happens? A URL?

[shiftercat.livejournal.com]

(Trying again, since the first attempt did something funny with the link):

I may have an example here (http://www.patheos.com/blogs/slacktivist/2014/02/25/can-you-obsessively-patrol-tribal-boundaries-without-appearing-to-be-a-ridiculous-self-parody-who-long-ago-lost-every-last-vestige-of-faith-hope-and-love/). For the first few comments it's fine; continue in the sub-thread, and up pops the troll again. Especially if you had to hit "Load more comments".

page on which the killfile stops working

[(Anonymous)]

You asked for an example of the killfile ceasing to block in a long or deeply nested thread. I was using it on the following:

http://www.patheos.com/blogs/slacktivist/2014/08/14/the-beautiful-people-all-send-their-excuses/#disqus_thread

I blocked a specific user, and for the first three pages I was seeing "hush" after each post, and "post from X was blocked" on the user's posts I was blocking. But after that, the "hush" options vanished and the blocked user reappeared. This happens consistently in lengthy, deeply nested comment threads on two separate machines. I have reinstalled the killfile but it doesn't help.

killfile stops working

[(Anonymous)]

If I post a URL my message is rejected as spam, but try it on the lengthier (300+ comments) threads on Patheos blog "slactivist". After a few pages it simply stops working; the blocked poster's posts appear normally, and no posts have "hush" after them anymore. I do not know if this is a length problem or a nesting problem.

Re: killfile stops working

[dtm]

Okay, yeah, I see this now. I don't know what's happening so it's going to take some time to fix.

Re: killfile stops working

[(Anonymous)]

Thanks so much for looking into this. When it does work it's great.

Re: killfile stops working

[shiftercat.livejournal.com]

The problem appears to be fixed now. Thanks very much!

[ashi.livejournal.com]

Thanks, works great!

[(Anonymous)]

Thank you so very much for this. It's really a sanity saver. I've been sharing it with other Troll Haters.

~Random Internet Person

Possibly of interest

[livejournal.livejournal.com]

User rahirah referenced to your post from Possibly of interest (http://rahirah.livejournal.com/643953.html) saying: [...] ts you would rather not see. If you're using Chrome or Firefox, there is a nifty extension here [...]

Thank you!

[(Anonymous)]

I really like killfile. My only request would be that I not even have to see the blocked messages. Is there any way to completely remove the existence of a poster you don't want to see?

Spammers are still quite annoying because I have to wade through hundreds of blocked messages to get to real content.

Requirements?

[(Anonymous)]

Does Killfile for Firefox require cookies be enabled or that you retain some history or a cache? I've disabled pretty much everything in Firefox (cookies, history, cache set to 0, etc)to reduce virus/malware issues and Killfile has never worked. I also run Ad Block Plus but I don't think that would matter.

Re: Requirements?

[dtm]

I don't believe that any of those things would prevent killfile from working, but I will have to test it. I hope to have some time to test that scenario this weekend.