[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/j/ - Janitor & Moderator Discussion

Name
Options
Comment
File
  • Please read the Rules and FAQ before posting.



File: 1350442119123.jpg (352 KB, 1280x800)
352 KB
352 KB JPG
I've been using a grease monkey addon that lets me search for strings throughout a board, so I use it to search for "blox" and it's helped me a lot to get rid of those shitty posts.

But I got to thinking of a way to proactively fight it. Rather than straight up banning someone if their posts contain "blox" which would just result in more captcha writing to bypass the robot or just gibberish in general, why not simply not bump the thread if their posts contains some form of /blox/i ?
>>
The way I've been dealing with 'blox' posts is on a case by case basis. It seems like almost half of 'blox' posts are original content and they decided to tag it with a blox for shits and giggles.

I think that another effective tool to raise post quality in /r9k/, beyond disabling thread bumping from blox-posts, would be adding forced anonymous.
>>
Hmm, what if, a post that is delete and contains blox gets a mute of a certain period?



Delete Post: [File Only]
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.