Furrin_Gok said:
Old news.

I'm well aware. The solution could also be implemented client-side, with a little Javascript tossed into the blacklist functions to the extent of "hey, I'm still working on this, don't display it until I'm done".

Of course, this could result in a small increase in load-times on searches that aren't heavily effected by the blacklist. A faster method for blacklisting (i.e. storing the list as a cookie rather than making a get request every time) could help with that. It's generally bad for accessibility when a page's contents rapidly change as it's loading, and accidentally showing people gore when they specifically told you not to is REALLY bad for accessibility.