oxedyne/daimond — www/guide/sync.html

8.0 KiB, 3 runs

created by r2519314175:1301, which is this file's identity for as long as the history lasts, whatever it is later renamed to

download · who wrote it · its history

1	<!DOCTYPE html>
2	<html lang="en" data-guide-locale="en" data-guide-locales="en de es fr ja ko pt-BR zh-Hans">
3	<head>
4	<meta charset="UTF-8">
5	<meta name="viewport" content="width=device-width, initial-scale=1.0, viewport-fit=cover">
6	<title>Cross-device sync — Daimond guide</title>
7	<link rel="icon" type="image/svg+xml" href="../assets/daimond_mark.svg">
8	<link rel="stylesheet" href="../css/variables.css">
9	<link rel="stylesheet" href="../css/guide.css">
10	<script src="frame.js"></script>
11	<script src="search-index.js"></script>
12	<script src="search.js"></script>
13	</head>
14	<body>
15
16	<header class="site-head">
17	<div class="site-head-inner">
18	<a class="brand" href="index.html" aria-label="Daimond guide, home">
19	<img class="wordmark wm-dark" src="../assets/daimond_word.svg" alt="Daimond" translate="no">
20	<img class="wordmark wm-light" src="../assets/daimond_word_dark.svg" alt="Daimond" translate="no">
21	<span class="brand-sub">Guide</span>
22	</a>
23	<nav class="site-nav" aria-label="Guide pages">
24	<a href="index.html">Getting started</a>
25	<a href="interface.html">The interface</a>
26	<a href="models.html">Models & credits</a>
27	<a href="chats-and-diamonds.html">Chats & Diamonds</a>
28	<a href="capps.html">Capps</a>
29	<a href="email-web-files.html">Email, Web & files</a>
30	<a href="accounts.html">Accounts</a>
31	<a href="sync.html" aria-current="page">Cross-device sync</a>
32	<a href="spending.html">Spending</a>
33	<a href="machine-operations.html">Machine Operations</a>
34	<a href="social.html">Social</a>
35	</nav>
36	</div>
37	</header>
38
39	<main>
40	<h1>Cross-device sync</h1>
41	<p class="lede">Daimond is local-first, so a second device starts empty. Cross-device sync carries your chats and workspace files between your own devices without the server ever reading them.</p>
42
43	<p>What travels through the gateway is one encrypted parcel only your devices hold the key to. The key comes from your passphrase and never leaves the browser, so the server stores the parcel and cannot open it. Nothing readable crosses between devices.</p>
44
45	<h2 id="s1">Linking a second device</h2>
46	<p>Each device makes its own identity, so typing your passphrase on a new one starts a <em>separate</em>, empty account instead of bringing your existing one across. To use the account you already have, <strong>link</strong> the new device to it. Three steps.</p>
47
48	<ol class="steps">
49	<li>
50	<h3 id="s2">On the device you already use, open the link dialog</h3>
51	<p>Click the <span class="ui">Link another device</span> button in the top bar. It shows a QR code and a one-time pairing code.</p>
52	<figure class="shot narrow" data-shot="pair-desktop">
53	<img src="img/pair-desktop.png" alt="The Link another device dialog, showing a QR code and a one-time pairing code that expires in about ten minutes.">
54	<figcaption>Your first device shows a QR and a code.</figcaption>
55	</figure>
56	</li>
57	<li>
58	<h3 id="s3">On the new device, scan the QR, or type the code</h3>
59	<p>Point the new phone's camera at the QR code: it opens Daimond and fills the code in for you, so you only tap <span class="ui">Link this device</span>. No camera? Open Daimond there, choose <span class="ui">Have a pairing code?</span>, and type the code. The code shown is only so you can check it matches the first device.</p>
60	<figure class="shot narrow" data-shot="pair-mobile">
61	<img src="img/pair-mobile.png" alt="The Link this device dialog on a phone after scanning, with the pairing code already filled in and a Link this device button.">
62	<figcaption>After scanning, just tap <span class="ui">Link this device</span>.</figcaption>
63	</figure>
64	</li>
65	<li>
66	<h3 id="s4">Unlock with the same passphrase</h3>
67	<p>The new device now holds your account. Unlock it with the <strong>same passphrase you use on your first device</strong> (not a new one) and your chats and files appear. A passkey can unlock it faster afterwards, once you add one there.</p>
68	</li>
69	</ol>
70
71	<div class="note"><strong>The passphrase is the same everywhere, but it cannot travel on its own.</strong> One account, one passphrase, on every device you link. The passphrase only decrypts a key the device already holds, so a browser that has never been linked has nothing for it to open. If a device asks you to <em>create</em> a passphrase rather than <em>enter</em> one, it is about to start a new account, and only linking it (or importing a backup of the old account into it) will bring the old one over.</div>
72
73	<h2 id="s5">What travels</h2>
74	<p>Your chats, your Diamonds and the graph you laid them out in, your mail, your workspace files, the devices on the account, and what you have paused. Any file travels, whatever kind it is: a photograph, a recording, a PDF or a spreadsheet reaches your other devices as text does, up to a gigabyte for one file. So does the Trash, so a deletion and a restore both reach every device.</p>
75	<p>What syncs is also what is kept in cloud storage, so a workspace can be larger than the device you are reading it on. A file that is not on this device still shows in the tree, marked with a cloud, and comes down when you ask for it. <a href="email-web-files.html">The Workspace</a> sets out the three states a file can be in, how space is freed as the browser fills, and what cloud storage costs.</p>
76
77	<h2 id="s6">Running a turn on another device</h2>
78	<p>When more than one of your devices is awake and linked, one can run a turn for another, and the answer syncs back to the device you started it on.</p>
79
80	<p>This is off until you turn it on, and set for one device at a time. One switch, <span class="ui">Hand off when you step away</span>, lets a turn running on this computer move to another awake device when you close it — the lid shuts, the tab closes, the connection drops. The turn finishes there and its answer syncs back, instead of sitting interrupted until you return.</p>
81
82	<p>The turn says where it went. It reads <span class="ui">Sent to your other devices</span>, then names the one that took it — <span class="ui">Laptop is doing this</span> — and the answer appears here when it is done. Two buttons sit beside it: <span class="ui">Take back</span> returns the turn to this device, and <span class="ui">Run here</span> runs it locally if no device picked it up or one could not finish. Naming your devices in the account settings is what makes these lines read as <span class="ui">Laptop</span> rather than <em>your other device</em>.</p>
83
84	<div class="note"><strong>You can nominate one device as the runner.</strong> Pick the one that is usually on — a desktop that stays awake — and hand-offs go to it rather than whichever device grabs the turn first. If it is offline when a turn is handed off, any awake device runs it instead.</div>
85
86	<p>An errand handed to another device, and the answer it sends back, are sealed to your account like everything else that crosses the gateway. The server routes an encrypted parcel it cannot open; only your own devices hold the key.</p>
87
88	<h2 id="s7">What it costs</h2>
89	<p>Cross-device sync is part of <strong>Pro</strong>, the one-time unlock, which stays bought once like the rest of Daimond. Without Pro a device works on its own; with it, your devices stay in step. Pro also turns on cloud storage and Email. The larger file bodies sync carries are kept in cloud storage, paid for from credits, with a free allowance before anything is metered.</p>
90
91	<div class="next">
92	<a href="accounts.html">← Accounts</a>
93	<a href="spending.html">Next: Spending →</a>
94	</div>
95	</main>
96
97	<footer class="site-foot">
98	<span>Daimond runs in your browser. Nothing here is sent to us.</span>
99	<nav aria-label="Guide pages">
100	<a href="index.html">Getting started</a>
101	<a href="interface.html">Interface</a>
102	<a href="models.html">Models</a>
103	<a href="chats-and-diamonds.html">Chats & Diamonds</a>
104	<a href="capps.html">Capps</a>
105	<a href="email-web-files.html">Email, Web & files</a>
106	<a href="accounts.html">Accounts</a>
107	<a href="sync.html">Cross-device sync</a>
108	<a href="spending.html">Spending</a>
109	<a href="machine-operations.html">Machine Operations</a>
110	<a href="social.html">Social</a>
111	</nav>
112	</footer>
113	</body>
114	</html>