Built from nothing to a full chat, voice, and community platform in under three weeks.
This page replaces the old project-status dump with a curated view of what's actually live, how fast this has moved, and — the part that matters most going forward — what's next, in priority order, with realistic timelines.
How we got here
A sample of the pace — not every change, just the shape of it
What's actually live
Grouped, not itemized — see NEXT_STEPS.md for full technical detail
💬Core chat & voice
Real-time text and voice channels, self-hosted LiveKit SFU with screen share and webcams, DM voice/video calls, group direct messages, DM polls and events, Unicode and private custom server emotes with reduced-motion static variants, reactions, replies, mentions, pins, search, polls, versioned rich-message formatting, per-server/per-channel notification overrides, and clickable links with automatic preview cards.
🛡️Accounts & safety
Required verified email, optional 2FA and recovery codes, Argon2id password hashing, encrypted media-safety quarantine, an 18+ policy with fail-closed consent, privacy-conscious active-session inventory, a protected first-party moderation bot with scoped AutoMod, warnings, reversible mutes, case history, and Control Center operations — hardened by two independent full-codebase security audits with every Critical/High finding fixed.
🎲Game Hub
Campaign Desk, Game Lobby, and Community Atlas as owner-toggled channels — with join policies (open / invite / request), session details, host notes, temp voice channels, and IGDB search.
🔌Integrations
Spotify OAuth listening status with in-app Premium playback, Twitch watch parties with live chat and emotes, IGDB-powered game search with cover art, and KLIPY-powered GIF, sticker, and clip search.
◇Developer platform
A live Developers portal for registering applications and bots, declaring scoped permissions, managing redirect URIs, and issuing one-time hash-only credentials. Bots have a real in-app identity: a server owner can review and approve an install link with a chosen permission subset — found either directly or through an opt-in, searchable public directory — an installed bot can send messages (optionally with clickable action buttons) through its own token, and can receive signed webhook events for channel activity and button clicks. Third-party sites can also let users sign in with their Krit identity via OAuth, with a Connected Apps pane to review and revoke access at any time.
◆Roles & permissions
Managed @everyone and custom roles, fixed theme-safe colors, owner self-assignment, optional role sections in the right member panel, role-colored names in server chat, hierarchy-safe assignment, 37 granular permissions, role/member channel overrides, member removal and bans, and server-side enforcement across chat, media, voice, video, settings, invites, and webhooks.
🖥️Desktop & mobile
Windows (Authenticode-signed via Azure Trusted Signing), Linux (AppImage/DEB/RPM plus a checksum-verified universal install command), and Android native apps, with a public source-free numerically ordered GitHub history containing all 33 retained releases and 64 installer packages, in-app auto-update, hybrid local game-activity detection across Steam/Epic/GOG/Xbox/Battle.net (2.0.32), and taskbar/dock unread badges. The release hub no longer advertises or links back to this direct-access progress page.
⚙️Infrastructure
PostgreSQL 17 + Redis 7.4 in production, two load-balanced application nodes (OVH1 + OVH2) sharing one database over a private WireGuard link with nginx weighting tuned to each node's actual fixed overhead, plus durable maintenance and audited feature kill switches in the staff Control Center.
Priorities & timeline
What's next, ranked by what actually matters, with realistic estimates
This week
Backlog cleared — remaining items are blockedIdentity, server-owner install consent, a public opt-in directory, bot messaging with action buttons, signed event delivery, click-time authorization, and OAuth login are all live. Everything else on this roadmap needs physical hardware, a business decision (signing keys, developer accounts), or a deliberate production-topology change — nothing left that's a straightforward next build.
1–2 weeks
Platform reach and polishWindows and Linux confirmed on real machines: title bar, taskbar unread badge, fast clean startup, tray reliability, and the game detector correctly identifying real installed titles while a full package audit closed out several false-positive reports. Android device pass still outstanding.
Build target exists but isn't signed, notarized, or published. Needs a macOS runner and Apple Developer signing.
Still on the debug keystore convention — needs a protected release key before any Play Store submission.
A dead-end fullscreen bug and a bandwidth-pause bug fixed and shipped on desktop. Remaining: camera/screen-recording permission handling on macOS, once real macOS hardware is available to verify against.
Bigger bets
Larger scope, no immediate deadlineA real production-topology change (Redis-backed realtime routing and voice membership, multiple app containers behind the live load balancer), not a routine feature — needs deliberate planning and explicit go-ahead before touching it. Once multi-worker is live, stage the 400 / 750 / 1,400 concurrent-user soak tests outlined in the scaling plan.