How It Works
Diagrams of the systems actually running on this site — what happens when you sign in, what the background job does while you are not looking, and how a public page serves everyone without paying for it twice. Pick one.
-
D01 / 03
ViewTitle
Signing in
OAuth 2.0 with PKCE — why the request that starts the login and the request that finishes it have to prove they are the same request.
Same verifier, or no token
See the diagram -
D02 / 03
ViewTitle
The update cycle
What the background job does every cycle, and why the whole design is shaped by a read costing 1 quota unit and a write costing 50.
Reads are cheap — writes cost 50
See the diagram -
D03 / 03
Channel Stats
The cache
How a public page serves every visitor from one API call, so the quota bill stays flat no matter how much traffic it gets.
One read serves every visitor
See the diagram