![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
dtmIn 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)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.
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)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.
no subject
Date: 2013-12-27 09:57 pm (UTC)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".
no subject
Date: 2014-01-01 01:19 am (UTC)no subject
Date: 2014-03-09 03:57 am (UTC)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
Date: 2014-08-14 10:28 pm (UTC)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
Date: 2014-08-14 10:30 pm (UTC)Re: killfile stops working
Date: 2014-08-14 10:39 pm (UTC)Re: killfile stops working
Date: 2014-08-15 01:43 am (UTC)Re: killfile stops working
Date: 2014-10-25 09:06 pm (UTC)