652: Talking to Bots, Building Browser Games, and Political LLMs

What It Covers

Chris Coyier and Dave Rupert discuss browser game development challenges, CMS content protection strategies, AI chatbot interactions, database syncing solutions like PouchDB, and the complexities of maintaining clean content in publication systems.

Key Questions Answered

• •Defensive CMS Design: Remove HTML editing from content boxes entirely, use separate fields for images, excerpts, and galleries instead of one "danger box" where authors write raw HTML that breaks when themes change or widths adjust over time.
• •Game Accessibility Planning: Browser games built with Canvas lack inherent accessibility unless developers add HTML-based UI elements, keyboard controls like WASD or arrow keys, and Gamepad API support for adaptive controllers used by players with limited mobility.
• •Content Publishing Workflow: Implement role separation where authors cannot hit publish directly but must submit to editors who verify tags exist, images are optimized to WebP with proper source sets, and no empty paragraphs or formatting errors appear.
• •AI Bot Detection Patterns: Chatbots often exhibit rigid argumentation patterns, fishing for counterpoints rather than genuine discussion, with hidden prompts instructing politeness that users occasionally glimpse in tools like Cursor when generating code responses.
• •Local-First Database Strategy: PouchDB enables offline-capable applications by storing data in IndexedDB locally and automatically syncing with CouchDB backends when connectivity returns, eliminating the need to build custom synchronization logic for notes or data-heavy apps.