How to moderate kids’ small online community groups: what I learned testing post approval and new flairs
9:30 PM, last Tuesday, I’m folding a pile of my 10-year-old Jax’s soccer practice hoodies that’ve been sitting on the couch for three days, and my phone won’t stop buzzing. The Discord I moderate for our local elementary’s after-school Minecraft club has 82 unread notifications, and I already know half of them are spam reports. Two weeks before that, we’d scrapped our old no-approval system, turned on structured post approval for new users, and added new flairs to sort everything. I wasn’t sure it would work, but I was sure the old system couldn’t keep going.
We launched the club last fall, with 70 kids between 9 and 11, all playing on a private server after homework. At first, we kept it simple: one rule (no mean comments, no spam), two mods (me and another dad), automated filters and kid-led reporting to keep things clean. It worked for the first two months. Then in January, the cracks showed. Someone joined pretending to be a 5th grader, posted links to a fake Roblox gift card scam in three channels before we caught it. Then a group of kids got into a fight over a server raid, and one posted a screenshot of another kid’s base with the caption “lmao this is garbage.” By the time I got home from work and saw it, 20 kids had commented, half of them piling on. Three parents emailed me that night saying they were pulling their kids out because the space felt too toxic.
We held a Zoom meeting with the club’s teacher sponsor and a handful of parent volunteers to hash out a fix. Mrs. Lopez, the 5th grade tech teacher, suggested we test post approval and add new flairs to organize everything. A lot of parents pushed back at first: said we were hovering too much, that kids need to learn how to handle conflict online on their own. I get that. I’d rather my kid learn how to respond to a mean comment now than when he’s 16 on Instagram. But I also watched Jax come home quiet that week, because his own survival base got roasted, and he said he didn’t want to play Minecraft anymore. So we agreed to try it for a month.
What we rolled out was simple: post approval for all new users’ first 10 posts, so we could check for spam or harmful content before it went live. Then we added two sets of new flairs: user flairs for grade level and role, so I can see immediately if someone posting in the 4th grade channel is actually a 4th grade parent volunteer, not a random scammer. Then post flairs: four options total: Just Sharing, Need Feedback, Off-Topic, Need Help. That’s it, no more.
The first three days were chaos. I was approving posts at red lights, during dinner, while I waited for Jax’s piano lesson to end. Wait time for a post was sometimes 40 minutes, and kids were complaining in general chat that their content never showed up. Jax even called me out at dinner: “I built a whole castle with a working waterfall and I had to wait 30 minutes for you to approve it. By then everyone was done with homework and no one even saw it.” He wasn’t wrong. So we adjusted fast: we gave one to two parent volunteers from each grade limited mod access for their grade’s channel, so a 4th grade parent can approve 4th grade posts right away, instead of waiting on me or the other main mod. That cut average wait time down to under five minutes, and cut our main mod workload by 70%.
The biggest surprise was what the flairs did, beyond just organization. After two weeks, I noticed that posts tagged with Need Feedback got almost exclusively constructive comments. Before flairs, when a kid posted their base and asked what people thought, half the comments were “cool” and a quarter were just bluntly negative. Now, if it’s tagged Need Feedback, kids will say things like “I love your roof, maybe you could add some windows to the front to let light in?” The flair doesn’t just sort content, it sets an expectation before anyone even starts typing. It reminds people what the post is for, without me having to type a reminder comment on every post.
Post approval didn’t turn out to be the censorship a lot of parents worried it would be, either. Most of the time, when a new kid writes a mean comment, it’s not even intentional. Last week, a new 4th grader commented “this is bad” on a build, and it sat in my approval queue. Two minutes later he DMed me: “Wait that came out wrong. I meant it’s harder than anything I can build, can I change it to ‘wow this is so good I could never build this’?” The 30-second delay of approval just gave him time to think before his comment went live. It’s a pause, not a ban.
We’ve kept the system lightweight to avoid burning everyone out: we only require approval for a new user’s first 10 posts. After that, posts go live automatically, and we just rely on the report button that pings mods immediately. We keep the number of flairs small, because any more than five options and kids just pick a random one and don’t bother with the right label. We don’t delete every offhand mean comment, either: we talk to the kid who posted it, check in with the kid who was on the receiving end, and only suspend access if it’s repeated.
It’s not perfect. Two weeks ago, a 5th grader who’d been posting for three months got a mean comment that slipped through the cracks, and he left the server for three days. We got it sorted, invited him back, talked through what happened, but it was still a mess. Some weeks we have more spam than usual, some nights I’m still approving posts at 10 PM when I should be asleep. But more kids are staying in the club now, Jax plays every Wednesday again, and last week he posted his new castle, tagged it Need Feedback, got 12 comments with helpful tips, and talked about it the whole drive home from school. We’re tweaking it still, testing comment approval for the off-topic meme channel next month to cut down on weird spam links. It’s not a perfect fix, but it’s better than what we had before.
Please indicate: Thinking In Educating » How to moderate kids’ small online community groups: what I learned testing post approval and new flairs