oxedyne/daimond/www/guide/email-web-files.html
15.1 KiB, 1 run
created by r2519314175:1177, 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>Email, Web & files — 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" aria-current="page">Email, Web & files</a> |
| 30 | <a href="accounts.html">Accounts</a> |
| 31 | <a href="sync.html">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>Email, Web & files</h1> |
| 41 | <p class="lede">The sources a daimon works from: mail you can read and answer, web pages it can show or drive, files it can read and write, and the tools it does the work with.</p> |
| 42 | |
| 43 | <h2 id="s1">Email</h2> |
| 44 | <p>The Email panel lives in the dock and holds your mailboxes and what is in them. A browser cannot open a mail connection on its own, so Daimond connects through a gateway, which hands back the raw message and forgets your credential. Your mail is written into the Workspace as ordinary files, so the agent's file tools already read it.</p> |
| 45 | |
| 46 | <figure class="shot" data-shot="email"> |
| 47 | <img alt="The Email panel: the mailboxes at the top and a list of messages below, with buttons to write, add a mailbox and sync." src="shots/email.png" loading="lazy"> |
| 48 | <figcaption>The Email panel. Its header buttons write a message, add a mailbox, and sync.</figcaption> |
| 49 | </figure> |
| 50 | |
| 51 | <h3 id="s2">Adding a mailbox</h3> |
| 52 | <p>Choose <span class="ui">+</span> (add a mailbox) in the Email panel header. Type your address and Daimond guesses the server settings for common providers; every field stays editable, because a guess is not a fact. Most providers want an <strong>app password</strong> (a single-purpose password you generate in your mail account's security settings) and not your account password. The panel says where to find it for your provider.</p> |
| 53 | <div class="note">Your mail credential is stored on this device, wrapped under your passphrase. It is handed to the gateway only for a single sync, held for one conversation with your mail server, and then forgotten. Daimond stores no mail on any server and never sees your account password.</div> |
| 54 | |
| 55 | <h3 id="s3">Reading and syncing</h3> |
| 56 | <p>Choose <span class="ui">⟳</span> (sync now) to fetch what has arrived. A sync asks only for messages newer than the last one held, so it stays quick. Click a message to open it onto the stage, beside the chat, so you can ask the daimon about it while you read.</p> |
| 57 | |
| 58 | <h3 id="s4">Writing a message</h3> |
| 59 | <p>Choose <span class="ui">✎</span> (write a message) to open the Compose panel on the stage. Fill in <strong>From</strong>, <strong>To</strong>, an optional <strong>Cc</strong>, a <strong>Subject</strong> and the body; attach files with <span class="ui">Attach…</span>; keep a draft with <span class="ui">Save draft</span>. Nothing sends by itself.</p> |
| 60 | <div class="note"><strong>Only you can send mail.</strong> The <span class="ui">Send</span> button is the one thing in Daimond that puts mail on the wire, and only a person can press it. The daimon can draft a message beside you, but it cannot send it.</div> |
| 61 | |
| 62 | <h2 id="s5">The Web panel</h2> |
| 63 | <p>Ask Daimond to open a web page (<em>“show me the Rust ownership chapter”</em>) or paste a link into the chat. Three ways it can put a page on the stage, and which works depends on the site.</p> |
| 64 | |
| 65 | <figure class="shot" data-shot="web-panel"> |
| 66 | <img alt="The Web panel showing a page on the stage, with back, reload and open-in-a-tab controls in its header." src="shots/web-panel.png" loading="lazy"> |
| 67 | <figcaption>The Web panel. A page shown here sits beside the chat, so the daimon can be asked about it.</figcaption> |
| 68 | </figure> |
| 69 | |
| 70 | <div class="cards"> |
| 71 | <div class="card"> |
| 72 | <h3 id="s6">Show it</h3> |
| 73 | <p>The page appears in the panel. Most sites refuse to be embedded (the web's clickjacking defence, the same in every browser), so this works only for the minority that allow it.</p> |
| 74 | </div> |
| 75 | <div class="card"> |
| 76 | <h3 id="s7">Read it</h3> |
| 77 | <p>Daimond fetches the page and reads its text, so it works when showing does not. It reads the words, not pictures or anything drawn by JavaScript, and you do not see the page. Daimond does.</p> |
| 78 | </div> |
| 79 | <div class="card"> |
| 80 | <h3 id="s8">Drive it</h3> |
| 81 | <p>With <strong translate="no">Daimond Hands</strong>, a browser add-on, Daimond opens a real page in a real tab, signed in as you, and works it while you watch. This is the only way to work a live, logged-in site.</p> |
| 82 | </div> |
| 83 | </div> |
| 84 | |
| 85 | <div class="note"><strong>Signing in stays yours.</strong> When you sign in on a driven page, Daimond stops watching entirely (no text, no picture, no keystrokes) and never sees your password. You hand the wheel back with <strong>Resume Daimond</strong>, and that button is in the browser tab, not in Daimond, so a page can never take the wheel from you.</div> |
| 86 | |
| 87 | <h2 id="s9">The Workspace</h2> |
| 88 | <p>The Workspace panel, in the dock, is your files as an ordinary tree of folders. This is where the agent reads and writes: uploads, mail, documents and anything it produces all live here.</p> |
| 89 | |
| 90 | <p>With a Diamond open, the panel shows either everything here or only the files that Diamond holds. The <strong>📎</strong> on every row attaches one to whatever is in focus; <a href="chats-and-diamonds.html">Chats & Diamonds</a> sets out what attaching does, what a daimon may then open, and what that protects you from.</p> |
| 91 | |
| 92 | <h3 id="s10">Three ways to get a file in</h3> |
| 93 | <p>Getting a file into the workspace and attaching it to a Diamond are separate acts. There are three ways in, and each is for a different case:</p> |
| 94 | <ul> |
| 95 | <li><strong>Upload files</strong>: the arrow-into-tray button in the panel header. For one file or a handful. An ordinary file picker, in every browser.</li> |
| 96 | <li><strong>Import a folder…</strong>: for a whole folder that should live in the browser workspace and sync. Chromium-based browsers only.</li> |
| 97 | <li><strong>Open a real folder</strong>: the <span class="ui">Machine</span> chip. Your own disk <em>is</em> the workspace: nothing is copied and nothing syncs. Chromium-based browsers only.</li> |
| 98 | </ul> |
| 99 | <p>An agent can also write a file where it is allowed to, and mail arrives here as ordinary files.</p> |
| 100 | |
| 101 | <figure class="shot" data-shot="workspace"> |
| 102 | <img alt="The Workspace panel: three chips reading Browser, Machine and Cloud, buttons to import a folder or save a copy, and a file tree in which one file is marked as being in cloud storage and another is pinned." src="shots/workspace.png" loading="lazy"> |
| 103 | <figcaption>The Workspace. The chips name where the workspace lives; below them, <em translate="no">interviews.txt</em> is in cloud storage rather than on this device, and <em translate="no">report-draft.txt</em> is pinned so it is always kept here.</figcaption> |
| 104 | </figure> |
| 105 | |
| 106 | <h3 id="s11">Working with files</h3> |
| 107 | <p>The Workspace header carries buttons: <span class="ui">New file</span>, <span class="ui">New folder</span>, <span class="ui">Upload files</span>, <span class="ui">Parent folder</span>, <span class="ui">Refresh</span>. Under them a <strong>breadcrumb</strong> names every folder above the one you are in, each clickable, so a folder three deep is never a dead end. A filter box narrows a long list, and searches from where you are downward rather than stopping at the current folder.</p> |
| 108 | <p>Below the tree, <strong>System</strong> opens Daimond's own files: the store the Diamonds themselves live in. They are kept in the browser rather than in the folder you have open, and they travel between your devices. The tree above deliberately leaves them out, since a delete cross beside <code translate="no">diamonds/</code> would take every Diamond you have.</p> |
| 109 | |
| 110 | <h3 id="s12">Where a workspace lives</h3> |
| 111 | <p>Three chips at the top of the panel name the places a workspace involves. Clicking one opens that place's controls.</p> |
| 112 | |
| 113 | <div class="cards"> |
| 114 | <div class="card"> |
| 115 | <h3 id="s13">Browser</h3> |
| 116 | <p>This browser's own private storage, on your device and reachable by nothing outside Daimond. It is where a workspace lives unless you say otherwise. Its size is whatever the browser grants, which on an iPhone is not much, and a browser may clear it without warning.</p> |
| 117 | </div> |
| 118 | <div class="card"> |
| 119 | <h3 id="s14">Machine</h3> |
| 120 | <p>A real folder on this computer's disk. The agent works in it directly, so the same files are in your own file manager, and it is roomier than what a browser grants. But it stays on that one computer, never travelling to your other devices, and only a Chromium-based browser can open one.</p> |
| 121 | <p><strong>The folder is the whole of what the agent can see.</strong> Nothing above it and nothing outside it is visible to Daimond. Clicking the chip while the agent is working there says so, and offers <span class="ui">Forget this folder</span> to stop Daimond holding a record of it.</p> |
| 122 | </div> |
| 123 | <div class="card"> |
| 124 | <h3 id="s15">Cloud</h3> |
| 125 | <p>Not a third place to work but where the workspace is kept, which is what lets it be far larger than any one device holds. Its chip opens a view of what is stored, what is not on this device, a <span class="ui">Free up space</span> button and a <span class="ui">Credits</span> button.</p> |
| 126 | </div> |
| 127 | </div> |
| 128 | |
| 129 | <p>The first two are alternatives, the agent working in one or the other. The third is not an alternative but where the bytes are kept. The admin panel's storage rows show how much space each is using.</p> |
| 130 | |
| 131 | <div class="note">What is kept in cloud storage is <strong>encrypted before it leaves</strong>, as a sync parcel is, so we hold bytes we cannot read.</div> |
| 132 | |
| 133 | <h3 id="s16">Held, in cloud storage, or pinned</h3> |
| 134 | <p>A file is in one of three states, and the tree shows which:</p> |
| 135 | <ul> |
| 136 | <li><strong>Held on this device</strong>: it opens at once.</li> |
| 137 | <li><strong>In cloud storage only</strong>: marked with a cloud. Still your file, still listed, still safe, simply not here at the moment. Clicking it brings it down, and so does the fetch control on its row.</li> |
| 138 | <li><strong>Pinned</strong>: kept on this device always and never freed automatically. The pin sits on the row, beside a control that frees a held file's space.</li> |
| 139 | </ul> |
| 140 | <p>As the browser's storage fills, the files longest unused are freed back to cloud storage on their own; a pinned file never is.</p> |
| 141 | |
| 142 | <div class="note"><strong>Freeing a file is not deleting it.</strong> It stays in cloud storage, the tree still lists it, and it comes back when it is asked for. Only a deliberate delete removes a file.</div> |
| 143 | |
| 144 | <h3 id="s17">Any kind of file</h3> |
| 145 | <p>Any file is stored and travels between your devices, up to a gigabyte each. Opening one that is not text shows its size and a download button instead of trying to display it.</p> |
| 146 | |
| 147 | <h3 id="s18">Moving files in and out</h3> |
| 148 | <p>Two buttons sit beside the chips. <span class="ui">Import a folder…</span> copies a folder from this computer in, after which it syncs and is stored like everything else. <span class="ui">Save a copy…</span> writes the workspace out to a folder on this computer, and says how many cloud-only files it left behind rather than fetching them. Neither changes where the agent is working, and both need a Chromium-based browser.</p> |
| 149 | |
| 150 | <p>While the agent is working in a real folder a third button appears, <span class="ui">Change folder…</span>, and it is the only control that opens a folder picker. Moving between <span class="ui">Browser</span> and <span class="ui">Machine</span> does not: Daimond remembers the folder you last used, so going back is one click on the chip.</p> |
| 151 | |
| 152 | <h3 id="s19">What the agent may fetch</h3> |
| 153 | <p>When the agent needs a file that is in cloud storage, it is told so plainly and has to fetch it deliberately. Nothing is downloaded quietly behind a read: a download can be large and, once storage is priced, costs you money. A cap limits how much the agent may bring down on its own initiative, after which it comes back and asks.</p> |
| 154 | |
| 155 | <h3 id="s20">What cloud storage costs</h3> |
| 156 | <p>Not a subscription. Like everything else leaving the browser it is paid for from <a href="models.html">credits</a>, and the one-time Pro unlock stays one-time. At present it is free and unmetered, until it can be sold properly.</p> |
| 157 | <div class="note">If a storage charge ever cannot be covered, <strong>nothing is deleted straight away</strong>. Reading and downloading stay free for six months, so everything can be retrieved, and only then is the paid overflow removed. The free working set never is.</div> |
| 158 | |
| 159 | <h2 id="s21">Tools</h2> |
| 160 | <p>Open the <span class="ui">Tools · N of M</span> row in the admin panel to see what Daimond can do. It is called Tools, not Upgrades, because most of what it lists is free and already yours.</p> |
| 161 | |
| 162 | <figure class="shot" data-shot="tools-panel"> |
| 163 | <img alt="The Tools panel listing the built-in tools the agent can use and the unlockable tools with their prices." src="shots/tools-panel.png" loading="lazy"> |
| 164 | <figcaption>The Tools panel: the built-ins you already have, and the unlockable tools with their prices.</figcaption> |
| 165 | </figure> |
| 166 | |
| 167 | <p>Two kinds of tool appear:</p> |
| 168 | <ul> |
| 169 | <li><strong>Built-in tools</strong>: what the agent is already handed, free. The panel lists exactly what it holds, so it cannot promise a tool that is not there.</li> |
| 170 | <li><strong>Unlockable tools</strong>: extras with a price, shown with whether this account already holds the unlock.</li> |
| 171 | </ul> |
| 172 | <p>To add one, choose it and confirm; the cost is drawn from your credits, and once unlocked it stays available.</p> |
| 173 | |
| 174 | <div class="next"> |
| 175 | <a href="capps.html">← Capps</a> |
| 176 | <a href="accounts.html">Next: Accounts →</a> |
| 177 | </div> |
| 178 | </main> |
| 179 | |
| 180 | <footer class="site-foot"> |
| 181 | <span>Daimond runs in your browser. Nothing here is sent to us.</span> |
| 182 | <nav aria-label="Guide pages"> |
| 183 | <a href="index.html">Getting started</a> |
| 184 | <a href="interface.html">Interface</a> |
| 185 | <a href="models.html">Models</a> |
| 186 | <a href="chats-and-diamonds.html">Chats & Diamonds</a> |
| 187 | <a href="capps.html">Capps</a> |
| 188 | <a href="email-web-files.html">Email, Web & files</a> |
| 189 | <a href="accounts.html">Accounts</a> |
| 190 | <a href="sync.html">Cross-device sync</a> |
| 191 | <a href="spending.html">Spending</a> |
| 192 | <a href="machine-operations.html">Machine Operations</a> |
| 193 | <a href="social.html">Social</a> |
| 194 | </nav> |
| 195 | </footer> |
| 196 | </body> |
| 197 | </html> |