Doxxing attempt in megathread
Reported personal addresses and phone numbers in response to a heated debate.
Ready to claimKYUUBI turns the modqueue into claimable cases. Small Reddit teams see which case matters, whether somebody is already working on it, and what the next safe action is — without dashboard clutter or duplicate work.
Doxxing attempt in megathread
Reported personal addresses and phone numbers in response to a heated debate.
Ready to claimGraphic violence in meme post
Multiple users reported disturbing content disguised as a humorous image.
You claimedOff‑topic spam campaign
Repeated suspicious links across multiple comments.
Stale soonSurface urgency and report relevance before the team wastes attention.
Show claim state, owner and stale risk directly in the work object.
Expose only safe actions for the current claim and session state.
KYUUBI is not a broad suite. It is a precise coordination layer for small volunteer teams handling queue pressure.
Every modqueue item becomes a case with a clear state: unclaimed, claimed, stale or resolved.
Destructive actions activate only when the actor holds the valid claim.
Claim, release, heartbeat, override and resolve updates reach connected sessions without manual refresh.
Every claim, override and moderation action becomes an immutable audit event.
A moderator scans state, claims atomically, acts only when safe, and the team sees the result.
The architecture stays server-side where it matters: the UI runs in a Devvit Custom Post, while Reddit API calls stay in Devvit.
One-handed, state-led interface embedded as a Devvit Custom Post.
Flat JSON bridge and one server-side message dispatcher.
Watched multi-step transactions protect case and user claim pointers.
No Reddit OAuth token reaches the client. Lead override stays blocked until server-side role checks are implemented — safer blocked than weakly trusted.
Moderation actions are bound to valid ownership, not just visible buttons.
FLUBBER softness clarifies change: claim feedback, lease pressure and queue settling.
The release candidate proves the core coordination loop and keeps weak trust paths out of the demo.
Flutter and Devvit communicate over a flat JSON bridge.
Claim exclusivity is enforced in Redis with watched transactions.
Lead override remains disabled until server-side role checks exist.
A precise moderation workflow app, not a bloated admin dashboard.
The handoff stays practical: Devvit checks, Flutter checks and a local mock preview path.
cd devvit npm install npm run typecheck npm test npm run build
cd flutter flutter pub get dart run build_runner build --delete-conflicting-outputs flutter analyze flutter test flutter build web --release
cd flutter flutter build web --release -t lib/main_dev.dart -o build/web_dev python3 -m http.server 8080 --bind 0.0.0.0 -d build/web_dev cd devvit npx devvit login npx devvit upload npx devvit install r/YOUR_TEST_SUBREDDIT
For contest questions, feedback, collaboration ideas or moderator workflow notes, send a short message.
hello@inkandironglow.comKYUUBI gives small teams a shared live object: one case, one owner, one safe next action. It keeps character around the work and clarity inside the work.