Anyone following along probably has questions about just how the heck we're using a single YAML fence in a Markdown file as shared storage for multiple users?
Well we're not.
The <oculus-fence> Web Component assigns as session id the first time one is called. The rest of them share the same id while until the session expires. The `write_path` method intercepts calls containing X-Wanderland-Client-Id and cuts them their own slice of the universe - an overlay driver tracking an append-only list of updates made by that session.
Replay on read. Multi-player ready. Collision proof updating.
Game on Wayne. Game on Goose









