Project Overview
This bot was built to help server operators understand identity changes over time and to keep communities safer by surfacing username changes, highlighting metrics around them, and providing simple moderation tools accessible from a web portal.
It collects gateway events, persists historical username snapshots, and exposes search and notification controls to admins so they can audit and act quickly.
Tools, Technologies, and Frameworks
Technical Deep Dive
High event throughput and Discord gateway rate limits required careful handling to avoid lost events or bans. Storing full history efficiently and enabling fast search also posed design tradeoffs.
Implemented sharded bots with an event queue and worker pool to smooth spikes. Debounced frequent username changes, used Redis for idempotency and rate token buckets, and designed a compact append-only history schema optimized for reads.
What This Shows About My Proficiency
- Integrating with third-party real-time APIs while respecting rate limits
- Designing event-driven pipelines and scalable workers
- Data modeling for time-series / change-history use cases
- Delivering a small web admin UX integrated with OAuth