KILLFILE 2.0

first draft. blanks divs rather than deleting them, board numbers are strings. will tidy up when i have time.

http://www.koogy.clara.co.uk/ilx/boardblacklist.user.js

ok, unwanted DIVs now set to not display.

also, choice of a blacklist or a whitelist, set WANT or DO_NOT_WANT as appropriate. see examples in code.

divvies

Oh my god how could I have been posting here for six fucking years and never have ever clicked on "site new answers"? I AM SO DUM

It was just added in Keith's last upgrade, you're ok!

koogs you are awesome and heroic ty

shralp a dik ilm never i look at u again

curiously it seems that the killfile doesn't work on poll threads (i see blocked user posts on them)

probably because the dom tree has another level of crap in it for those.

it's currently looking for "//div/p/*[@class='name']" - divs at any level containing a paragraph containg something that has class=name attribute. i guess it needs to be vaguer. will look into it. am currently trying to find the sizes of 44000 jpegs though for our massive launch tomorrow. so it probably won't be today.

hey no problem just thought i would mention it, just surprised i hadn't noticed it before!

nope, looks ok on mine (disney thread)

the opening question is still shown though, as it's a big form.

there should be a poll about who is the most killfiled user and then they should be banned. that would be fun.

And then the next round the next day, and the next the next, and so on until only Estela is left.

now you're just being silly

D@ano, sorry to not be able to catch up in London last weekend - I spent most of it spewing.

we have that effect on visitors

:}

yeh sorry it is working on poll threads but on one i'm seeing some posts blocked and others by same user on same thread are not. odd. no matter.

can you email me the details sieve. ta.

have done

ok, slight update uploaded - "if (poster != null)"...

was breaking on polls due to the auto bump post from the system being in slightly different format to normal posts.

the site new answers killfile is sometimes working, sometimes not.
is anybody else noticing this?

url has no properties on line 43.

saw something similar with the other code - works ok until you hit a page with poll results in it - poll results are missing one of the things the code looks for so it falls over.

is the NOT WORKSAFE entry - it's in an extra <span>. will fix it this weekend.

thanks dude! you rule.

now handles NOT WORK SAFE warnings on site new answers page (7am sunday morning). haven't been able to test it against live site because there are currently no warnings on site new answers but it works against the copy i took so...

http://www.koogy.clara.co.uk/ilx/boardblacklist.user.js

I stuck one in for you to test... Top of HTML playground if you have to bump it by the time you see this.

cheers. was a little bug in it - my debugging limit of 20 messages was still in there (oops) but other than that it's ok. updated now.

baseball and noizeboard values only in there as an example of usage 8)

Is there a reason why threads from ModReqFor are showing up even if my specified WANT list does not include it?

is that bang up to date Lee (i just fixed something similar when there was a NOT WORK SAFE thing in the page)

this morning the problem i'm having is not being able to find SiteNewAnswers. has something changed?

wasn't logged in. schoolboy error.

I installed the one linked in this post, which I reinstalled and re-edited. Still get ModReqFor. Not an urgent deal, though.

the "LOCKED" causes problems.

it does "var thisLink = answers.snapshotItem(i).firstChild;" to get the a href for the board id, gets confused when it doesn't get a url. should be a bit more robust.

A weird thing I just noticed: the killfile works fine on normal threads but not on poll threads?

oic blueski reported same upthread a bit.

Hmmm, this doesn't seem to be working for me. (I'm assuming that the killfile erases everything the killfiled user has posted and not just what he or she posts after you've installed the killfile.)

Subtle!

it doesn't work on JW's username because of the chinese tomato at the end
(it's my fault really)

Sorry, I'm not trying to create drama here, I'm really trying to minimize it.

you can block posts by entering only part of a username tho (koogs version at least)

i have wrong version at home because i get this:
invalid flag after regular expression
[Break on this error] undefined
kilxor.user.js (line 18)

but it works fine on my work pc

So no one knows what I'm doing wrong? I followed all of Jaq's steps, and the only thing I did to the script was change [/fule1/,/fule2/] to [/user's name/].

try the version where you can block partial usernames?

make sure the monkey is brown and not gray

Yep, that was the problem, Tom. Thanks!

>> make sure the monkey is brown and not gray
> Yep, that was the problem, Tom. Thanks!

lol

you can block even odd characters (someone has a name featuring only two chinese characters, another has a crescent and star), you just need to know how to specify them in the javascript. involves hexadecimal to decimal conversions, or vice versa. oh, is in examples in script, use unicode - \uABCD (but view source shows characters as decimal entities - 〹 hence the conversion)

a pox on the bbcode convertor. &#12345;

Bless this. :D

I always wonder if (some) people have killfiled me. :-(

i never would, even if i was a killfiler, which i'm not.