Roadmap 0.11, SuperCad Studio
SCL.1 SuperCad Studio licence tokens: sign in once, the app renews itself
Anyone may download SuperCad Studio; it runs only with a signed licence token tied to the account (Ed25519: the site signs with its secret key, the app checks with the public key compiled in). Sign-in issues the token; default lifetime 10 days (.env SUPERCAD_LICENCE_TTL_DAYS). At start-up: no token, expired, or 36 hours or less left → call home for a new one (failing that, the sign-in screen); while running it checks hourly. People ask for a longer lifetime on /account/supercad (11–365 days, with a reason); staff approve, decline or end it on /admin/supercad#licence, and can sign computers out. Spec docs/SUPERCAD-LICENCE-SPEC.md; site test bin/test-supercad-licence.php (102). Built 2026-11-03; waiting on the lab Windows build test (0.9.0 lab build, staff and lab testers only).
super-lic-09 2026-11-05: Checked against the spec: site 102/0 (as www-data), node test/licence.test.mjs 18/0, a site-signed token verifies with the app's public key (same key as .env), 10 days / renew 36 h. The app side (sign-in, renew, offline wording, sign-in over the work with Save first) is in desktop-shell licence.rs; its cargo tests were not run here (no builds on the VPS). Gap closed: Settings had no "Signed in" row (SuperCad Studio a Discord member settings.inc). Not built or run on Windows: the 0.9.0 lab build predates that row.
SEEN 2026-11-20 (studio-checks-11): the SuperCad Studio test build 0.10.90 (new shell + licence check, 0.10.1 pages) run on real Windows, signed out, shows Sign in to SuperCad Studio (licence.html), no app. Signing in needs a real account. (studio-checks-11)
Community comments
No comments yet
Add detail as we go: how you would use it, files or steps that show the problem, what other programs do. The team reads every comment.
Sign in or create a free account to add a comment.