tinybot.
The Discord bot running the submission pipeline, moderation queue, and uptime alerts — combining active VPS tooling with planned API expansion.
Active Core · tinybot.py & Field Logging
Right now, tinybot.py operates as a focused discord.py worker running under systemd at /opt/tinyfiles/worker/tinybot.py. It responds to both legacy prefix commands and direct mentions, writing append-only operational field notes straight to disk at tinybot_events.log.
tinybot_events.log on disk.Systemd Service Model
The worker runs inside the /root/bot-env virtual environment on our IONOS VPS. Managed directly by systemd, it restarts automatically within 5 seconds on failure and pipes journal output straight to the system log:
Soon Planned · Two-File Pipeline Expansion
As the PHP and MySQL API endpoints come fully online, tinybot.py will scale its architecture into a dedicated two-file pipeline helper to automate creator submissions and moderator review flows:
pipeline_worker.py
Monitors incoming creator submissions from #submissions and the /submit modal, enforces size limits (5 MB max for HTML, 16 KB max for Python scripts), strips third-party trackers, and stages clean items into review.
mod_bridge.py
Links Discord moderator actions (✅ approve / ❌ reject reactions in #mod-queue) directly to the backend API — instantly pushing approved works live, broadcasting #releases updates, and pinging #status on health changes.
Planned Slash Commands & Background Loops
HEAD request to /healthz to verify live site availability./api/works?sort=new.Manage Messages permission) to inspect pending submissions and review reaction rules.Background Loops
- Uptime (every 5 min): Pings
/healthzand posts state changes to#statusonly on actual transitions (up/down) to avoid spam. - Community boards (every 2 min): Polls
/api/community/postsand pushes new thread alerts to#community. - Releases (every 10 min): Polls
/api/works?sort=new&limit=20and announces unseen slugs to#releases.
Guardrails & What It Won't Do
- No auto-publishing: Every submission requires human verification or moderator sign-off before reaching the public index.
- No DM scraping: The bot operates strictly within designated server channels and public slash commands.
- Zero third-party telemetry: No external trackers, webhooks, or cross-platform relays outside local API calls.
See Also
Check Captain's Log for live build updates, Language Models for automated screening notes, or Submit for current manual review guidelines.