Roadmap 0.11, SuperCad Studio
SCF.8 Blob sync: sc_blob and project files by sha256 into the account's encrypted cloud folder, on demand
Rows sync as rows; large bytes (drawings, textures, point clouds) need their own writer, a list of what a device does not hold yet, and one writer per project for drawing data.
super-file-11 2026-11-20: Sending is built: super-blobsync.js (a client of /api/v1/vault/<folder>/f/supercad/blobs/<2>/<sha256>: create=1, hashed on the way in and out, quota and access answers carried back; CloudAccess::explainFolder and Storage::checkFolder with the folder owner decide on the server) and super-blobsync-wire.js (after a Save, on a computer that opted in with cc-super-blob-sync and is signed in). bin/test-super-blobsync.mjs 42/0 with fixture accounts: owner, view-only teammate, stranger, lapsed folder, signed out, offline, over quota. The real route is bin/test-vault-cloud.php.
scf-built-11 2026-11-21: BUILT, in the lab. Real page and REAL cloud folder: tools/super-test/blob-sync-live.mjs 9/0 (a fixture with one seat, cc-super-blob-sync on: a Save sends every file of the project by sha256 into the account's folder, each read back and hashed equal, a second Save sends nothing twice; every blob deleted through the API afterwards, bucket version included).
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.