Two-person test
Test Nodex with a friend, step by step.
This checks two things on a real network: that nobody is ever shown data older than 6 seconds, and whether two browsers on different connections can actually exchange data. It does not measure cost savings.
Preflight (both people)
The steps
- Both people: use a desktop Chrome or Edge window
Open the same https address on both computers. Keep the Nodex tab visible and the laptop awake for the whole run (about 6 minutes). A hidden or sleeping tab pauses the test.Phones and Safari are fine for a second run, not the first. - Both people: run the preflight below
Press "Run checks". Browser support and server reachability must be green. Press "Check my connection" to see what kind of network path you have.The connection check contacts a public STUN server (Google), which sees your public IP address. Nothing else is sent. - Owner: sign in with the admin invitation
Open the sign-in page, paste the admin token, and leave "Remember me" off unless this is your own computer. - Friend: sign in with the tester invitation
The owner sends this token privately (not in a group chat). It works for one person; do not forward it. - Owner: start a shared room
In Admin, open Runs, fill in a title, set the node count to 2, and press "Start simulated test". Join it as coordinator and keep that page open. - Friend: confirm the profile and pick the room
Setup, then Profile, then Room. Choose "Coordinator + tester", select the shared room the owner created, and press the join button. - Both: wait for two ready nodes, then run
Both names show as ready in the room. Press Run and follow the on-screen steps without closing the tab.Do the first run with both of you on home networks. Repeat it once with the friend on a phone hotspot: that is the harder case. - Both: send evidence and note the result
Evidence, then Send. Receipt shows what was recorded. A pass needs: no read older than 6 seconds, no version going backwards, and a peer connection that actually carried data. - Owner: revoke the friend's token afterwards
Admin, then Tokens, then revoke. Evidence files hold no addresses or tokens, but the invitation should not outlive the test.
What each side can see
Each of you can see the other's public IP address while connected, and so can the signaling and STUN servers. Result files contain no addresses, tokens or response bodies. If that is not acceptable, do not run the test.