- Template bans fully introduced
- (16:15:19) ‹~moot› the extension is going to be changed soon but i want to force the new templated BRs
- (16:15:24) ‹~moot› sorry for the hassle, but this will make BRs actually work
- (16:15:35) ‹~moot› if you use templates, whereas as of now they basically never get filled because they are a huge pain in the ass
- (16:15:46) ‹~moot› so it's slightly more hassle but will actually result in them getting handled
- (16:16:21) ‹%kdel› whoa, new ban requests
- (16:16:39) ‹%kdel› awesome
- (16:17:16) ‹%kdel› oh, it's still not finished yet
- (16:18:15) ‹%dongfix› ya it is
- (16:18:20) ‹%dongfix› ALL IS WELL
- (16:23:43) ‹+Kyoubro› How are you going to fit BRs into templates?
- (16:23:53) ‹+Kyoubro› Tests on Azatsu?
- (16:24:29) ‹Azatsu› huehuehue
- (16:24:30) ‹+Kyoubro› And I fill out ban requests all the time. The main reason that I don't fill out ban requests is because they get cleared from the queue so slowly.
- (16:24:52) ‹+Kyoubro› I don't want to overwhelm the people who are working at it (primarily Katsurugi).
- (16:25:53) ‹+RapeApe9k› https://boards.4chan.org/tg/res/20555897#p20558038 wow
- (16:25:55) ‹+Kyoubro› Whenever I start filling out ban requests in earnest, the /a/ queue quickly reaches 100.
- (16:26:06) ‹+Kyoubro› And then I stop for a while to wait for Katsurugi to catch up.
- (16:26:16) ‹+Kazisho› I really only ban request if it's necessary.
- (16:26:28) ‹+RapeApe9k› dongfix, HotShot I_AM_ABIB kdel Zorpheus https://boards.4chan.org/b/res/422597032#p422617224 child nudity
- (16:26:35) ‹%kdel› http://postimage.org/image/lep9ibjzt/
- (16:26:46) ‹%kdel› that's pretty much how i treated ban requests until now
- (16:27:11) ‹%kdel› the old system was a big hassle and it was usually more productive to work on actual active reports
- (16:28:29) ‹+Kyoubro› https://www.4chan.org/reports/?mode=details&board=a&no=70997130 I'd like to fill out a ban request on this, but it's impossible to explain why without use of the "other" field. I think I'm only ever going to use "other" from now on...
- (16:29:04) ‹+Kyoubro› Hell, I actually see myself using ban requests LESS like this.
- (16:29:08) ‹%kdel› what're you talking about
- (16:29:15) ‹%kdel› just use the global rule for shitposting or trolling
- (16:29:20) ‹+Kyoubro› You can't see the image.
- (16:29:30) ‹+Kyoubro› The image is why it's banworthy.
- (16:29:32) ‹%kdel› yeah we can
- (16:29:38) ‹+Kyoubro› ...
- (16:29:41) ‹%dongfix› just use "Garbage outside of /b/" or quality of posts
- (16:29:44) ‹+Kyoubro› So now we're storing child pornography on the server.
- (16:29:47) ‹+Kyoubro› Great.
- (16:29:47) ‹+Kazisho› Eh, I thought you couldn't see the images?
- (16:29:50) ‹%dongfix› no
- (16:29:54) ‹%dongfix› cp is never stored
- (16:30:01) ‹+Kyoubro› Then why are you saving ban request images?
- (16:30:16) ‹+Kyoubro› Wasn't the reason those weren't saved because you didn't want to save CP on the servers?
- (16:30:18) ‹+Kazisho› Maybe it gets deleted if it's a CP request.
- (16:30:21) ‹Azatsu› so why not make it like this : ban requests with CP have the images deleted
- (16:30:24) ‹+Kazisho› ^
- (16:30:31) ‹Azatsu› the rest keeps the images
- (16:30:47) ‹+Kyoubro› If it's like that? Okay. If it's not? Then...
- (16:31:09) ‹%kdel› please don't ever use other
- (16:31:11) » Quit: Azatsu ‹~Fever@76173142.3BE2E7C3.A3870841.IP› ‹Read error: Connection reset by peer›
- (16:31:32) ‹+Kyoubro› Then I guess I'm done filing ban requests. So many of them are context-based that it's just not worth it otherwise.
- (16:31:34) » Join: Azatsu ‹~Fever@76173142.3BE2E7C3.A3870841.IP›
- (16:31:44) ‹%kdel› seriously?
- (16:31:47) ‹+Kyoubro› Eh, not like they did much of anything most of the time.
- (16:31:53) ‹+Kyoubro› Ban evasion and whatnot.
- (16:32:05) ‹%kdel› if they're that context heavy, then you might be requesting too trivial stuff
- (16:32:06) ‹Azatsu› still
- (16:32:20) ‹~moot› if it isn't templated, we shouldnt be banning for it
- (16:32:23) ‹%kdel› most banworthy posts should fit under one of the global rules
- (16:32:25) ‹~moot› because they arent actually breaking a rule.
- (16:32:31) ‹%kdel› yeah
- (16:32:33) ‹+Kyoubro› Trolling.
- (16:32:38) ‹~moot› against the fucking rules
- (16:32:39) ‹~moot› global 2
- (16:32:40) ‹+Kyoubro› It's impossible to explain why someone's trolling without context.
- (16:32:47) ‹~moot› i dont need to know why
- (16:32:48) ‹%kdel› you don't need to EXPLAIN
- (16:32:49) ‹~moot› you just need to put in
- (16:32:50) ‹~moot› "GLOBAL 2"
- (16:32:57) ‹~moot› we can see the image and comment
- (16:33:01) ‹%kdel› we mods will look at it and either approve or disapprove of the request
- (16:33:11) ‹~moot› we see the board, image, comment, and template
- (16:33:13) ‹%kdel› we can figure out for ourselves, and if we can't, we'll ask the janitor who requested it
- (16:33:17) ‹~moot› if it isnt obvious to us why you picked a template, youre an idiot
- (16:33:22) ‹+Kyoubro› And if you don't know that this has been posted in every thread for the past few weeks?
- (16:33:26) ‹~moot› and/or are trying to get us to ban for something that isnt against the rules
- (16:33:27) ‹+Kyoubro› Which does happen.
- (16:33:31) ‹~moot› then tell us here
- (16:33:34) ‹~moot› christ you're the mother of all axe grinders
- (16:33:38) ‹+AlBorland› WOAH
- (16:33:40) ‹+AlBorland› WOAH
- (16:33:43) ‹%kdel› or on /j/ on the board threads
- (16:33:47) ‹+AlBorland› LETS NOT JUST HAND AWAY THE TITLE I WORKED SO HARD ON
- (16:33:52) ‹+AlBorland› GTFO OF HERE MOOT
- (16:33:53) ‹+Kyoubro› Heh.
- (16:34:00) ‹+AlBorland› arent there clubs in ibiza you should be hitting?
- (16:34:37) ‹+Kyoubro› Well, I guess this is a tool I won't be using much. I hope it serves the other janitors well.
- (16:35:37) ‹+Kazisho› I like it, actually...
- (16:36:10) ‹~moot› every moderator is forced through templates now anyway
- (16:36:20) ‹~moot› and you can select "Other..." and enter your own reason
- (16:36:22) ‹~moot› and we can ban for it manually
- (16:36:51) ‹~moot› but the point of this is to a) be consistent about ban reasons and lengths, b) actually ban for things that are explicitly against the rules c) make ban requests faster to file and A MILLION TIMES FASTER TO FILL
- (16:36:58) ‹~moot› what used to take hours now takes minutes for moderators
- (16:37:07) ‹~moot› BRs were never effective for a number of reasons
- (16:39:03) ‹+AlBorland› is it the favelas they grew up in?
- (16:39:12) ‹+AlBorland› resulting in a lack of quality education?
- (16:40:55) ‹Azatsu› Anonymous 09/01/12(Sat)18:40 No.70998084 [Reply][Quick Reply]
- (16:40:55) ‹Azatsu› Starcraft 2 is better than Brood War
- (16:41:02) ‹+RapeApe9k› while i have no problems with this new system, perhaps an additional text field for janitor comments might address Kyoubro's issue. a template would still be required for any ban request, but the additional field could be used to give context. just a suggestion.
- (16:41:02) ‹Azatsu› what a coincidence
- (16:41:12) ‹~moot› you can click "other"
- (16:41:32) ‹~moot› let me see about adding a notes text field
- (16:41:50) ‹+Kyoubro› That would help significantly.
- (16:41:58) ‹Azatsu› so you just click a button with the specific rule that the guy is violating, unlike the old ban template that had a lot of options?
- (16:42:09) ‹Azatsu› some of them were quite redundant
- (16:42:16) ‹~moot› what?
- (16:42:25) ‹+RapeApe9k› he's comparing the old to the new
- (16:42:32) ‹Azatsu› like, why were there 5 options for permabanned tripfags and etc
- (16:42:42) ‹Azatsu› would be easier to just have "rule x - ban evasion, etc."
- (16:42:44) ‹+RapeApe9k› some of the old options were rarely used
- (16:42:44) ‹~moot› the old system requires a mod look at your reason, look at the post on a separate page, click a ban button, a ban panel popped up, and then populate the ban panel entirely
- (16:42:51) ‹~moot› azatsu: that's the way it works now?
- (16:42:55) ‹~moot› i dont even know the old system
- (16:42:56) ‹Azatsu› yeah
- (16:42:59) ‹Azatsu› that's why I think it's better
- (16:43:00) ‹~moot› i think you're referring to the chrome extension that i never used
- (16:43:01) ‹Azatsu› now
- (16:43:06) ‹Azatsu› yeah, that one
- (16:43:10) ‹~moot› i never used it
- (16:43:19) ‹~moot› i added ~125 ban templates to the system a few weeks ago
- (16:43:23) ‹~moot› i went through /rules by hand and added them all
- (16:43:34) ‹~moot› so there should be a template for anything in /rules
- (16:43:42) ‹~moot› and now mods just click an accept button or deny button
- (16:43:54) ‹~moot› accept puts in the ban automatically, no ban panel or anything
- (16:43:58) ‹~moot› deny just clears it
- (16:44:07) ‹~moot› what once took hours now takes minutes
- (16:44:15) ‹~moot› but it requires janitors actually use the templates, because manual entry is still a pain in the ass
- (16:44:22) ‹~moot› and again, not what i want because i want 99% of bans to be templated
- (16:44:37) ‹~moot› because it standardizes ban reasons and lengths, something we've always sucked at
- (16:45:23) ‹Azatsu› so for example, janitor files a ban request for "avatarfagging". mod clicks on accept and then the guy will be banned for avatarfagging without even having to bother with manually choosing the number of
- (16:45:27) ‹Azatsu› *the lenght of the ban
- (16:45:48) ‹%kdel› yeah, which is why it's so great
- (16:46:00) ‹Azatsu› that seems much more consistent and faster
- (16:49:35) ‹+RapeApe9k› i admit i'll miss the more visual nature of the chrome extension. having a thumnail and text preview helped in prioritization.
- (16:49:42) ‹+Kyoubro› Something worth considering would be a system similar how to the old ban request system worked on the janitor side, where you could click a button to populate an open text field with a reason of your choosing.
- (16:49:57) ‹Azatsu› takes too long to evaluate I guess
- (16:49:59) ‹+RapeApe9k› that's what he wants to avoid
- (16:50:05) ‹+Kyoubro› Any number of reasons could be strung together or edited as you chose.
- (16:50:07) ‹+RapeApe9k› as it would be inconsistent
- (16:50:19) ‹Azatsu› mootles wants something fast, consistent and practical
- (16:50:23) ‹+Kyoubro› Mm, I suppose.
- (16:50:32) ‹+RapeApe9k› just choose the most severe infraction
- (16:50:50) ‹Azatsu› and if you really want a custom reason, you click on other, as he said
- (16:50:50) ‹Azatsu› and input the context
- (16:51:04) ‹Azatsu› but I'd imagine that those should be avoided and only used in delicate cases
- (16:51:07) ‹+RapeApe9k› if a 'janitor comments' field is added, then context could go there
- (16:51:11) ‹+Kyoubro› Given that the only bans on /a/ I really care about are those for the more subtle trolling that isn't obvious in just one post? I can't say I like this system at all.
- (16:51:27) ‹+andonuts› http://i.imgur.com/oklxq.jpg
- (16:51:29) ‹+andonuts› I know this feel.
- (16:51:33) ‹Azatsu› well, you could always give the context to the mod by janiteam
- (16:51:42) ‹Azatsu› Hah
- (16:51:58) ‹+RapeApe9k› well, only if they're online
- (16:52:03) ‹+Kyoubro› ^
- (16:52:19) ‹+Kyoubro› I try to do that when I'm able, but sometimes there isn't anyone around.
- (16:52:25) ‹Azatsu› Hmm, but then as I've said before you would always have the other option
- (16:52:37) ‹%kdel› no offense to the janitors here but the whole point in this standardization is to get rid of personal comments
- (16:52:41) ‹+RapeApe9k› if we always use 'other', then we're defeating the purpose of the system
- (16:53:08) ‹%kdel› there are hundreds of new reports being made by, i don't know, the minute
- (16:53:19) ‹%kdel› and we're not going to look at a detailed comment for each one
- (16:53:20) ‹+Kyoubro› Reports or ban requests?
- (16:53:31) ‹%kdel› especially since we're just doing this on our own free time
- (16:53:47) ‹%kdel› all we want is a CONCISE system that allows for maximum speed nad efficiency
- (16:53:49) ‹~moot› the same reason we dont allow notes on user reports is because it's useless noise
- (16:54:11) ‹+Kazisho› RapeApe9k, https://www.4chan.org/reports/new.php . But don't use it for ban requests.
- (16:54:16) ‹Azatsu› there's always the ban appeal
- (16:54:24) ‹+Kyoubro› Then why don't we have more specific report reasons?
- (16:54:29) ‹%kdel› the global rules are already far reaching enough, they should all fit under there
- (16:54:30) ‹~moot› it should be obvious when looking at a post's image or comment why it was reported as a rule violation, spam, or illegal
- (16:54:32) ‹~moot› same goes for BRs
- (16:54:39) ‹Azatsu› because everything falls under 3 categories
- (16:54:42) ‹Azatsu› literally everything
- (16:54:43) ‹~moot› right
- (16:54:49) ‹~moot› it's either a RULE VIOLATION, ILLEGAL, or SAM
- (16:54:50) ‹~moot› SPAM*
- (16:54:56) ‹+Kyoubro› Well, you can say that for ban requests too.
- (16:55:34) ‹~moot› huh?
- (16:55:48) ‹+Kyoubro› Every ban request falls under rule violation, illegal, or spam.
- (16:55:59) ‹~moot› correct!
- (16:56:05) ‹~moot› because every fucking ban template deals with one of those three
- (16:56:13) ‹~moot› and there is a ban template for /EVERY BANNABLE THING LISTED IN THE RULES/
- (16:56:52) ‹+Kyoubro› Wouldn't it also help to extend the number of report reasons so that janitors can go through the report queue more quickly and efficiently?
- (16:57:03) ‹~moot› no
- (16:57:15) ‹~moot› why would splintering it further help?
- (16:57:41) ‹Azatsu› reports fall under the 3 categories. Those 3 categories for reports need to be broken up into the rules categories so there will be specific ban lenghts, and that will make going through the ban requests much easier
- (16:57:44) ‹Azatsu› that's how I see it
- (16:58:03) ‹~moot› the reason is just to help triage the importance of the report
- (16:58:07) ‹~moot› hence why illegal is at the top
- (16:58:13) ‹~moot› and posts with multiple reports show above others
- (16:59:20) ‹+Kyoubro› Because then it allows users to be clear on what they're reporting something for. "Illegal" is very clear most of the time (although a lot of users seem to think it just means "against global rules"), "spam" is also fairly obvious, but "rule" has a hell of a lot of subdivisions that aren't all obvious without looking at the context of the post.
- (16:59:48) ‹~moot› rule violation is binary
- (16:59:50) ‹~moot› it IS, or it ISNT
- (16:59:59) ‹~moot› if people are reporting for shades of grey, it probably shouldnt have been reported
- (17:00:10) ‹Azatsu› gray areas imo just need a deletion
- (17:00:15) ‹Azatsu› or even let for users to decide
- (17:00:21) ‹+VCR_Working› mm
- (17:00:23) ‹~moot› the three reasons triage how important the report is, i do not give two shits about why a user thinks it should be reported, that's for you to decide
- (17:00:26) ‹+Kyoubro› For example, there's a group of trolls on /a/ who target Horizon threads. Without context, it looks like the Horizon fans are reporting them because "stop hating what I like", but then when you go and look at the actual CONTEXT it turns out that there are a few trolls who have been doing this for months.
- (17:00:44) ‹~moot› great
- (17:00:47) ‹~moot› so take that into account!
- (17:00:58) ‹~moot› i dont know why you're applying your stupid /a/ drama shit across the board to every other use case for reports
- (17:01:03) ‹~moot› you're describing an edge case
- (17:01:06) ‹~moot› this works for 99% of cases
- (17:01:16) ‹~moot› making the system more complicated to deal with /a/ drama will make it shit
- (17:01:22) ‹+Kyoubro› Because these edge cases are what I spend most of my time on with /a/.
- (17:01:25) ‹%kdel› look, you guys as janitors are not stupid
- (17:01:31) ‹~moot› the point is to get reports sorted as quickly as possible, and ban requests filled as quickly as possible
- (17:01:36) ‹~moot› that's it
- (17:01:41) ‹%kdel› if YOU as a janitor believes the gray cases are black, then ban request under one of the global rules
- (17:01:56) ‹%kdel› then us MODS we'll take a look and if we agree, we'll approve
- (17:02:04) ‹%kdel› it's a simple system
- (17:02:23) ‹Azatsu› consider that mods that don't understand at all why did you submit that ban request will just go and ask you
- (17:02:33) ‹Azatsu› and you explain that horizon threads get specific treatment from a small group of trolls
- (17:02:38) ‹%kdel› yes, if we don't know, we will ask you on irc
- (17:02:47) ‹%kdel› it's not like this is some sort of automated system
- (17:02:50) ‹+Kyoubro› Never been asked in the past. But who knows, that may change.
- (17:02:56) ‹+VCR_Working› yeah
- (17:02:58) ‹Azatsu› that will probably change
- (17:03:03) ‹Azatsu› since now they will go through the BR's
- (17:03:04) ‹Azatsu› unlike before
- (17:03:08) ‹+andonuts› They can also check out threads pertaining to certain boards on /j/.
- (17:03:11) ‹Azatsu› that only 3 or 4 did
- (17:03:30) ‹~moot› mods didnt do ban requests because clearing the queue actually took /hours/
- (17:03:35) ‹~moot› i can go through 100 templated ban requests in minutes
- (17:03:43) ‹Azatsu› yeah they would complain about that
- (17:03:48) ‹+Kyoubro› Well, let's see, then. I hope I'm proven wrong.
- (17:03:49) ‹~moot› the old system had been ineffective for years
- (17:04:39) ‹+RapeApe9k› kdel https://boards.4chan.org/b/res/422617583#p422625086 child nudity
- (17:04:52) ‹Azatsu› it surely takes less time to click a yes or no than the old ban quest system, afaik
- (17:04:55) ‹+VCR_Working› https://boards.4chan.org/b/res/422617583#p422617583 here as well
- (17:04:56) ‹+RapeApe9k› next question is, should illegal shit be reported on channel first?
- (17:05:02) ‹+RapeApe9k› *still
- (17:05:06) ‹Azatsu› I think so
- (17:05:09) ‹Azatsu› since they are a big problem
- (17:05:24) ‹%kdel› banned
- (17:05:30) ‹~moot› no
- (17:05:32) ‹~moot› delete and BR it
- (17:05:35) ‹~moot› always remove it as quickly as possible
- (17:05:53) ‹~moot› and if there is someone evading, tell a mod to check the BR queue
- (17:06:01) ‹~moot› er spamming CP or spamming in general
SHARE
TWEET
Template bans fully introduced
a guest
Apr 13th, 2015
185
Never
RAW Paste Data
