Page MenuHomeMiraheze

Make CreateWiki-Blacklist private
Closed, DeclinedPublic

Description

If the abuser(s) can see what regex is disallowed, they will just go around it. We need to either make it private somehow, or move it to another wiki (staffwiki or cvtwiki).

Event Timeline

All blacklists are public. Hiding is bad practise, increases likelihood of false positives, less scrutiny and unless it contains private data, the wrong approach.

@John If you have an active spammer/troll all it takes is for them to check the recent changes and they can easily go around the filter (not that this would be impossible without it, but it being private makes it less likely).

Maybe a better approach would be/have been to integrate AbuseFilter into it, so then what's private and what's public can be easily controlled.

Or as I've advocated in the past, getting rid of this section is way better. It's literally useless as good requests use like 50 bytes. Bad ones used thousands. Limit it to 100, spam is severely reduced which is what a blacklist does anyway.

CnocBride mentioned this in Unknown Object (Diffusion Commit).Aug 10 2017, 20:13
John claimed this task.

I'm going to decline this specific thing based on my argument "if you need this, you're doing something really bad" particularly for a blacklist.