Repository navigation
Conversation
…efusal path, inbound budget, frame-ancestors self - wireProto.js: WIRE_PROTO (1), protoOf (absent = 1, unreadable = refused), caps, refuse message, the People rows; a debugStores-only test hook (debugWireProto / __stores.wireProto.setProto) - peerHandler: proto + caps on every dial and in the modules message; inbound dials checked before any whitelist/card/wiring; a refusal dial (joinresult denied + refuse) or a refuse message; a protocol gate at the receive pipeline head (latched per link, holds while unknown on a newer build); no reconnect window or mesh-fill redial for a refused peer - wireBudget.js: per-peer messages/s + bytes/s budget and an object size cap at the pipeline head, counted drops + one throttled toast (wireErrors.noteWireDrop), never a disconnect - frame-ancestors defaults to 'self'; /play and /discord keep * without a play origin - People: '<name> needs to reload (older version)' Co-Authored-By: Claude Opus 5.5 <[email protected]>
…ws, OPEN-CORE.md + CLAUDE.md notes Chain 1 results in ~/.code/lanes-30/101/proto/logs: wire-proto 38/1, wire-flood 16/2 (flood sender timer-throttled in headless), dial-metadata 42/2 (to A/B on v1.65.0), join-result, wire-hardening and the peak runs green. LIMITS still the provisional values; the measured peaks are far below them. Co-Authored-By: Claude Opus 5.5 <[email protected]>
…rs-older line The trigger click was silent-caught and could land under a toast; peer-moderation opens it the same way. Co-Authored-By: Claude Opus 5.5 <[email protected]>
…ous bursts LIMITS: 10,000 msgs/s (~19x the 534 peak), 64 MB/s (~60x measured, above one data channel on a fast LAN), 64 MB object cap (~240x the largest scenes-repo/template object, above a textured model at the 25 MB import cap). Unit test asserts >= 4x each peak and bytes/s >= object cap. wire-flood 3: B sends 3 x 3000 synchronously (a headless setTimeout loop never crossed the cap), B's rendering paused for both frame windows, rAF deltas start at the first frame, and the toast count is asserted after the object cap (1) and again after the flood (still 1, the per-minute rule). Co-Authored-By: Claude Opus 5.5 <[email protected]>
1.66.0 Co-Authored-By: Claude Opus 5.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Roadmap 101 F1 + F4 (lane 101-proto). Do not merge — 101-int merges after the 17 Nov launch. Base v1.65.0 with v1.66.0 merged in.
What it does
F1 — session protocol in the handshake. Every dial's PeerJS metadata and the
modulesmessage now carryproto(WIRE_PROTO = 1,src/lib/wireProto.js) andcaps(wb,dev,fc). A peer that sends noprotospeaks 1. When two peers speak different protocols they do not connect, and no scene data is applied on either side:The check runs before the whitelist, the approval card and any wiring. A link with no dial metadata passes on a protocol-1 build; on a newer build its messages are held until its
modulesarrives. A refused peer is not redialled by the reconnect window or mesh fill, and a typed Connect clears that. Production stays on protocol 1, so two peers on the same build behave exactly as before. Additive extensions (for example 80a) become acapsflag, asOPEN-CORE.md"The session protocol" describes.F4 — per-peer inbound limits. Each peer has a budget at the head of the receive pipeline (
src/lib/wireBudget.js):objectsize cap of 64 MB.Each limit is at least 4x the peak measured on the heaviest suites and on every scenes-repo/template object. A message over budget is dropped and counted (
budget:*in Diagnostics). The person sees one notice per peer per minute, and the link stays up.Framing.
build/_headerssendsframe-ancestors 'self'when no play origin is configured;/playand/discordkeep*. With a play origin set (production) nothing changes.Measured peaks (receiving page, per peer, per 1 s)
Proof
battery.json):wire-proto39/0: both directions, reconnect after refusal, mesh fill, the gate on a link with no metadata.wire-flood20/0: heavy legit loads drop 0. A flood has 8,701 of 9,000 messages dropped, one notice, the link stays open, and the receiver's median frame time is unchanged.join-result41/0;wire-hardening,move-wire-shape,late-joiner-floor,session-volume-limits,topo-channel,dialback-sync,multiselect-v2,peer-moderation45/0,peers-popover21/0,fast-channel-loss32/0,fast-channel-fallback5/0,version8/0.dial-metadata43/1 — the failing check ("a later plain dial to the same peer carries no cloud data") fails the same way on v1.65.0 without this branch.npm run buildgreen.🤖 Generated with Claude Code