There's a user, Rayne-Chan, who has been spamming the craziest, most wtf artwork recently. You can check it out here:
http://www.e621.net/post?tags=user%3ARayne-Chan

Frankly, I don't think it has any redeeming value on the site, and I'm tired of seeing it fill up my front page.

So I want to block it, then I won't see it or have to deal with it anymore. Problem is, I know how to block keywords, but I don't know how to block based on everything a single user uploads.

Please help?

Try using a regular tag blacklist instead. Some of that's pretty okay.

Not a lot, but some.

Or, better: try growing a pair and sucking it up. I sift through the shit manually, no blacklist required.

blacklist user:rayne-chan

I'm not ENTIRELY sure I fixed the bug with blacklisting users with capital letters in their name yet though.

tony311 said:
I'm not ENTIRELY sure I fixed the bug with blacklisting users with capital letters in their name yet though.

Alright I'm real curious. Why does a letter being capitalized change things system wise?

Rainbow_Slash said:
Alright I'm real curious. Why does a letter being capitalized change things system wise?

Because I made the blacklist convert to lowercase when you submit it so that blacklisting, for example, Female, will actually blacklist females. But then it broke blacklisting users, because your blacklist entry of 'rayne-chan' (which was converted to lowercase along with the rest of the blacklist) does not match the user 'Rayne-Chan'.

tony311 said:
> a post about how I use exact-case matching for strings

This is why equalsIgnoreCase was created.

perhaps you could impose something that converts all usernames to lowercase in the system (like underscores becoming spaces) or have it blacklist both uppercase and lower. I really have no idea what I'm talking about but maybe it helps some.

Rainbow_Slash said:
perhaps you could impose something that converts all usernames to lowercase in the system (like underscores becoming spaces) or have it blacklist both uppercase and lower. I really have no idea what I'm talking about but maybe it helps some.

Hi, my name is toLowercase, it's nice to meet you.

Hrm... well, I wonder. Javascript isn't exactly my forte, but what if you guys made the following change in the blacklist code:

register: function (post) {
        post.tags = post.tags.match(/\S+/g)
        post.match_tags = post.tags.clone()
        post.match_tags.push("rating:" + post.rating.charAt(0))
        post.match_tags.push("status:" + post.status)
        post.match_tags.push("user:" + post.author.toLowerCase())
        post.match_tags.push("id:" + post.id)
        // insert the following line:
        post.match_tags.each(function (tag) { tag = tag.toLowerCase(); });
        this.posts.set(post.id, post)
    },

Then, in init_blacklisted:

tags.each(function (tag) {
                if (tag.charAt(0) == "-") {
                    b.exclude.push(tag.slice(1).toLowerCase());
                } else {
                    b.require.push(tag.toLowerCase());
                }
            });

I think that will put the image tags and blacklisted tags both in lowercase for when you call require.all() and exclude.any() in apply_blacklists(), but I'm not sure if that would break the sidebar, though.

I don't know offhand how to override the javascript the server is giving me to test it on my machine, and it's near enough to my bedtime that I'm just half-heartedly spit-balling anyways. I might have some spare energy to look at it more closely at some later date. Or I might decide to play Diablo 3. Something.

Yes, that is (essentially) the fix in question. I just don't know if the fix actually went through.