Choice Best fit Trust boundary Operational cost
Server-side search Public or mixed-trust rooms Server returns only visible participants Index, rate limits, and observability
Client-side filtering Small, closed rooms Client already receives the full roster Minimal, until the roster grows
Peer-to-peer lookup Rare, identity-safe sessions Every peer can learn the shared directory Signaling and membership complexity
Decision rule: use server-side participant search for a multiplayer quiz game when players don't already need the full roster. Keep the search token scoped to one room and one action. Client-side filtering is the simpler runner-up for a small, trusted session in which revealing every display name is already acceptable.
This is mostly a trust decision, not a fuzzy-search decision. A Node.js service can lowercase names and rank prefixes in a few lines; the hard part is preventing a participant from turning a search box into a directory export.…