73 lines
5.1 KiB
HTML
73 lines
5.1 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en" data-theme="dark">
|
|
<head>
|
|
<meta charset="utf-8" />
|
|
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
|
<title>AI as a Community Manager — Krusty Planet Blog</title>
|
|
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
|
|
<link rel="stylesheet" href="/css/style.css" />
|
|
</head>
|
|
<body>
|
|
<nav class="navbar is-dark" role="navigation" aria-label="main navigation">
|
|
<div class="navbar-brand">
|
|
<a class="navbar-item" href="/"><strong>🌍 Krusty Planet</strong></a>
|
|
</div>
|
|
<div class="navbar-menu" id="nav-menu">
|
|
<div class="navbar-start">
|
|
<a class="navbar-item" href="/">Home</a>
|
|
<a class="navbar-item" href="/blog.html">Blog</a>
|
|
</div>
|
|
</div>
|
|
</nav>
|
|
<section class="section">
|
|
<div class="container is-max-desktop">
|
|
<a href="/blog.html" class="mb-4 is-block">← Back to Blog</a>
|
|
<h1 class="title">Using AI as a Community Manager Without Alienating Your Community</h1>
|
|
<p class="has-text-grey-light mb-5">April 2026 · Jezza Hehn</p>
|
|
<div class="content is-medium has-text-grey-light">
|
|
<p><em>[DRAFT — pending Jez's review and edits before publication]</em></p>
|
|
|
|
<p>I'm a community manager for Trust Café, a platform building a nice online space free from bigots and misinformation. I'm also a junior developer there. And I build AI tools. These roles sound contradictory to some people: "You work in community trust and you build AI? Aren't you part of the problem?"</p>
|
|
|
|
<p>It's a fair question. Here's how I think about it.</p>
|
|
|
|
<h2>What AI Is Good At in Community Work</h2>
|
|
|
|
<p><strong>Spam detection.</strong> My AI agent can scan incoming posts for patterns that match known spam behaviors: keyword stuffing, suspicious link domains, duplicate content across accounts, timing patterns (50 posts in 2 minutes). This doesn't replace human moderation, but it filters the obvious stuff so human moderators spend their time on nuanced cases.</p>
|
|
|
|
<p><strong>Research and fact-checking.</strong> When a user posts a questionable claim, my research agent can hunt down primary sources in seconds. Not "I think this is false" but "Here are three peer-reviewed studies and a WHO fact sheet that contradict this claim, with direct links." That's useful for moderators making decisions.</p>
|
|
|
|
<p><strong>Translation and i18n.</strong> Trust Café uses Weblate for translations. My agent helps identify untranslated strings, draft initial translations for human review, and spot inconsistencies across language files. Nobody wants to read machine-translated content, but machine-assisted translation workflows save enormous time.</p>
|
|
|
|
<p><strong>Content drafting (for research, not conversation).</strong> I use AI to draft technical documentation, API references, and internal process docs. I would never use it to write community-facing posts, responses to users, or anything that represents a human voice. The distinction matters.</p>
|
|
|
|
<h2>Where I Draw the Line</h2>
|
|
|
|
<p>I don't use AI to generate community-facing content. Full stop. Trust Café's users deserve human-written communication. When someone reports a problem and gets a response, that response came from a human who read their message and thought about it. If I need AI help composing something, I use it for structure and research, then rewrite in my own voice.</p>
|
|
|
|
<p>I don't use AI for automated user interactions. No auto-replies, no chatbots, no "I noticed you haven't posted in a while" messages generated by a model. Community is built on authenticity. Automating the human parts defeats the purpose.</p>
|
|
|
|
<p>I don't let AI make moderation decisions. It can flag things for review, but a human makes the call. Every time. No exceptions.</p>
|
|
|
|
<h2>The Technical Setup</h2>
|
|
|
|
<p>I run OpenClaw on a DigitalOcean VPS. My primary agent (CeeLo) connects to Venice AI for inference, uses Forgejo for code management, and has a dedicated email inbox via AgentMail. The whole stack costs under $30/month.</p>
|
|
|
|
<p>For Trust Café specifically, I've built Playwright tests for automated QA on the alpha environment, helped with i18n string management, and set up monitoring for the API. These are developer tasks where AI assistance is unambiguously appropriate.</p>
|
|
|
|
<h2>The Hard Part</h2>
|
|
|
|
<p>The hardest part isn't technical. It's explaining to people that "AI-assisted community management" doesn't mean "AI is managing the community." The tools help me do my job faster. They don't replace the judgment, empathy, and contextual understanding that make community management actually work.</p>
|
|
|
|
<p>Every community I've seen try to automate too much has suffered for it. Automated moderation without human appeal creates injustice. Automated engagement signals feel hollow. Automated responses to user concerns breed resentment. The AI is a tool in my toolkit, not a replacement for the human at the keyboard.</p>
|
|
</div>
|
|
</div>
|
|
</section>
|
|
<footer class="footer has-background-dark has-text-light">
|
|
<div class="content has-text-centered">
|
|
<p><strong>🌍 Krusty Planet</strong> — Privacy-focused AI consulting</p>
|
|
</div>
|
|
</footer>
|
|
<script src="/js/main.js"></script>
|
|
</body>
|
|
</html>
|