AI summary by TwinMind
Seeing Other People's Steam Accounts: The Christmas Caching Catastrophe
Tom Scott
6m 58s
Introduction & Context
- Christmas Day incident at Steam requiring explanation despite creator's planned break
- Reference to childhood "chinny reckon" skepticism concept for later use
Web Caching Background
- Early web: simple server-to-disk page loading without caching needs
- Modern web complexity: Steam homepage requires 50+ file requests, 5-6MB data
- Backend processing: database queries for 10,000+ games, pricing, personalization
- Database-intensive operations require significant processing power
Steam's Caching Infrastructure
- Multiple caching layers: CDNs, browser caching, server-side caching
- Problem occurred in server-side caching layer
- Scale: 10,000+ requests/second for homepage alone
- Cache duration: seconds to 30 minutes depending on content
- Distributed architecture: hundreds of servers with individual caches
- Load balancing: requests routed to available servers
- Cache variations: 30+ versions per server (languages, regions, devices)
- Performance benefit: orders of magnitude faster than database queries
Traditional Caching Logic for User Authentication
- Anonymous users: receive cached versions (majority of traffic)
- Logged-in users: traditionally bypass cache for personalization
- News sites example: millions reading, few editors with login access
- Cache avoidance for personalized content to prevent data mixing
Steam's Modified Caching Strategy
- Higher proportion of logged-in users than typical sites
- Sale periods: users frequently reload pages while logged in
- Decision to cache some pages for logged-in users
- Two critical requirements:
- Clear cache when data changes
- Never serve one user's cached page to another user
The Christmas Day Incident
- Quick caching system change made on Christmas Day
- Goal: improve site performance
- Critical error: cache servers configured to ignore user identification
- Cache servers stopped differentiating between users and their settings
Technical Failure Sequence
- User A requests personal account page
- Server caches User A's page with private data
- User B requests their account page fraction of a second later
- Server serves User A's cached page to User B
- Process repeated across multiple servers
- Cache expiration: 1+ minutes, then cached next unlucky user's data
- Cycle continued with different users' data being cross-served
Historical Precedent
- Norwegian government 2012: identical caching error
- 15-minute incident exposing tax returns
- All users saw Kenneth Belcovski's personal details from Oslo
- Personal apology made to Kenneth
Security Limitations & Misinformation
- POST requests (purchases, password changes) bypass cache
- Login cookies validated for account modifications
- Claims of unauthorized purchases during incident likely false
- "Chinny reckon" skepticism applied to purchase claims
- Error handling would prevent cross-account transactions
Collaboration Request
- Seeking YouTube gamer/Twitch streamer for 2016 collaboration
- Specific requirements mentioned but not detailed
