Repository navigation
Releases
Mooring 0.3.0-preview.45
Mooring 0.3.0 preview 45 — Linux desktops, and pairing with a PIN
Preview 44 was never published, so this preview is the first to include its PIN pairing: Show Pairing PIN… on one Mac, Pair a Mac… and six characters on the other, with no long code and no need to share the screen first. The preview 44 notes describe it in full. Both Macs need this preview to pair with a PIN; the long code still works for older previews.
Linux desktops. Choose Add Linux Desktop and enter how you reach the computer with SSH: an ~/.ssh/config alias or user@host. Mooring connects through your own /usr/bin/ssh, keys and agent, never asks for an SSH password, and listens on 127.0.0.1 only. Its own viewer then signs in to a VNC server such as wayvnc with RSA-AES inside the tunnel. You type that computer's password for each sign-in; it is sent once and never saved or logged. After two rejected sign-ins within ten minutes Mooring waits before allowing another try. Before you sign in, a read-only check over SSH says whether the desktop is locked. If it is, unlock it in the viewer: Mooring never types a password into a lock screen.
The viewer works like Mac-to-Mac viewing: full screen, with this Mac's menu bar and Dock hidden so the desktop's own top bar is reachable, the same footer below the picture (⌃⌘D) with Exit Full Screen, and ⌘ as the desktop's Super key. With Mooring allowed in Accessibility, ⌘-Tab and ⌘-Space reach the desktop too. With Match this screen on, a Hyprland desktop shows on a virtual screen sized to the picture area, including the row beside the camera housing, so it fills the screen with no bars. While it is up, Hyprland's own pointer is hidden and this Mac's pointer is the only one. The computer's own screen, pointer and workspaces come back when you disconnect, and on their own within about 20 seconds if Mooring quits or the connection drops. Tested with wayvnc 0.10.2 on Hyprland 0.57 (Omarchy).
Apple Screen Sharing is gone. Mooring no longer opens Screen Sharing for any Mac. A Mac address saved for it by an earlier preview is listed as Needs pairing, with Pair a Mac… or Remove….
Known limits: on a large virtual screen the picture updates only a few times a second while much of it changes. The pointer over a Linux desktop is always this Mac's arrow, not the desktop's I-beam or resize shapes. Only one viewer at a time gets the virtual screen; another one connecting meanwhile sees the computer's own screen.
Local validation covers Rust, including the VNC client against a fake server, the SSH tunnel and desktop check with fake ssh, the virtual screen script under sh and dash, and PIN pairing; the native input, media and session suites; the Linux viewer's layout and input; encrypted loopback streaming; the packaged CLI; and the app build. Signing in to wayvnc through a real tunnel and the virtual screen were checked against a real Linux laptop. PIN pairing between real Macs, and viewing a Linux desktop from a second Mac, remain separate acceptance checks.
Use Check for Updates… on each Mac, or download the ZIP. Updates install while idle. Apple silicon and macOS 14 or later; Developer ID signed, notarized and stapled. All tests, builds, signing and packaging run on the local Mac. GitHub Actions remains disabled.
Mooring 0.3.0-preview.43
Mooring 0.3.0 preview 43 — More than one Mac
Until now, a viewing Mac could in practice reach only the sharing Mac it was showing. While a session was open, Pair a Mac… brought that session's window forward instead of opening the pairing form, and choosing another saved Mac in the menu bar or in Connections did the same, though the menu offered to connect to it. Pairing a second Mac meant ending the first session.
The pairing form now opens at any time. While another Mac is on screen, it says that Mac disconnects once the new one connects. That session stays up while the code is tried, so a wrong, used or expired code leaves it running. Once the new Mac connects, the first session ends as if its window were closed, and the new Mac opens. Choosing any saved Mac switches to it the same way, and choosing the Mac on screen returns to it. A choice made while Mooring is reconnecting to a dropped Mac now takes over instead of doing nothing.
Mooring still shows one Mac at a time, and a sharing Mac still takes one viewer at a time: while another Mac is viewing it, a new pairing with it can't finish until that session ends. Switching needs this preview only on the viewing Mac; the protocol is unchanged.
In preview 42, the clear space beside the viewing Mac's camera notch still left a wide empty space on the sharing Mac: it logged 142 points to spare. A probe on that Mac showed every position from 700 to 10,000 landing in the same slot. Some of its icons evidently share one stored position, as icons that were never rearranged can. macOS keeps such icons together as a block that no app can place an item inside, so Mooring moves the whole block left of the notch. To fix it, on the sharing Mac hold ⌘ and drag each icon in that block once; dropping it back in place is enough. Each drag gives the icon its own position, and the next full-screen session fits the gap to the notch. The sharing Mac's log now suggests this when more than 64 points are to spare, and Settings → Viewing → Use the space beside the camera has the same tip. The README explains it, and scripts/probe-menu-bar-order.swift maps where a Mac can place a new menu bar item. The log hint comes from the sharing Mac, so it needs this preview too.
Local validation covers Rust, the native input, media and session suites, encrypted loopback streaming, the packaged CLI and the app build. Pairing a second sharing Mac and switching between them with real Macs remains a separate acceptance check, as does a full-screen session after ⌘-dragging the sharing Mac's icons.
Use Check for Updates… on each Mac, or download the ZIP. Updates install while idle. Apple silicon and macOS 14 or later; Developer ID signed, notarized and stapled. All tests, builds, signing and packaging run on the local Mac. GitHub Actions remains disabled.
Mooring 0.3.0-preview.42
Mooring 0.3.0 preview 42 — Searching wider
In preview 41, the clear space beside the viewing Mac's camera notch still reached well past it on the right: the sharing Mac logged 138 points to spare. The search for the spacer's slot tried positions only up to the gap's own distance from the right edge of the menu bar. That assumed an icon's stored position never exceeds its distance, which held on the Mac where the fix was tested but not on the sharing Mac. Its icons carry larger stored positions, perhaps from being arranged on a fuller or wider menu bar, so the search stopped about four icons short of the notch.
Trials now start at the gap's distance and double while they land right of the gap, up to the position where macOS puts an item leftmost. Then they narrow down to a single point. A placement typically takes 10 to 13 trials of about half a second each, while the sharing Mac's status icons shuffle. The sharing Mac's log names the result, for example "menu bar gap placed beside the viewer's camera, 9 points to spare on its right (position 230 after 10 trials)". Both Macs need this preview, as for preview 39.
Local validation covers Rust, the native input, media and session suites, encrypted loopback streaming, the packaged CLI and the app build. On a real menu bar, a gap asked for at 1400–1460 points among the status icons was placed at exactly 1400–1469, 9 points to spare, after 10 trials. A gap left of all the status icons, at 1200–1250, widened to the leftmost slot with 1 point to spare after 6 trials. A real two-Mac session with this preview on both Macs remains a separate acceptance check.
Use Check for Updates… on each Mac, or download the ZIP. Updates install while idle. Apple silicon and macOS 14 or later; Developer ID signed, notarized and stapled. All tests, builds, signing and packaging run on the local Mac. GitHub Actions remains disabled.
Mooring 0.3.0-preview.41
Mooring 0.3.0 preview 41 — A closer fit
In preview 40, the sharing Mac's status icons moved out from behind the viewing Mac's camera notch, but the clear space reached about 80 points past the notch on the right. There were two causes. The search for the spacer's slot stopped about 12 points short of exact, and some slots can be reached only through a narrow range of positions, so it could skip the nearest one. Also, a status item is 16 points wider than its length, which pushed the spacer's left edge past the gap's.
The search now narrows down to a single point, in at most ten trials. Each trial is read only once the item stops sliding into place. While the gap is placed, the sharing Mac's status icons shuffle for about four seconds. The spacer's length now allows for the padding, so its left edge meets the gap's. Its right edge may fall up to 4 points short of the gap's, which includes a margin beyond the notch. The sharing Mac's log says how much room is left over: "menu bar gap placed beside the viewer's camera, N points to spare on its right". The gap is placed again if icons push into it for five seconds, or leave more than 24 points of extra room for ten seconds, at most every 30 seconds. Both Macs need this preview, as for preview 39.
Local validation covers Rust, the native input, media and session suites, encrypted loopback streaming, the packaged CLI and the app build. On a real menu bar, a gap asked for at 1400–1460 points among the status icons was placed at exactly 1400–1477, 17 points to spare, and the nearest slots were at 1443 and 1477. A real two-Mac session with this preview on both Macs remains a separate acceptance check.
Use Check for Updates… on each Mac, or download the ZIP. Updates install while idle. Apple silicon and macOS 14 or later; Developer ID signed, notarized and stapled. All tests, builds, signing and packaging run on the local Mac. GitHub Actions remains disabled.
Mooring 0.3.0-preview.40
Mooring 0.3.0 preview 40 — Clear of the camera
In preview 39, the sharing Mac kept the span behind the viewing Mac's camera notch clear with an empty status item, but created it as the leftmost status item. It kept icons added later out of the gap, but couldn't move icons already there. On a crowded menu bar, four of the sharing Mac's status icons still sat behind the notch. The empty item now goes just right of the gap and reaches left to the gap's left edge, so the icons in between move left of the notch.
macOS places a new status item by the order of the items' stored positions rather than at an exact distance, so the sharing Mac finds the slot with a short search: one trial item at a time, at most six steps. While it searches, the sharing Mac's status icons shuffle for about three seconds. If icons to the right of the gap later grow into it for five seconds, as a network meter can, the gap is placed again, at most every 30 seconds. When status items already reach past the gap, it starts left of them as before. App menus still take precedence: when they reach the gap, macOS hides status items. Both Macs need this preview, as for preview 39.
Local validation covers Rust, the native input, media and session suites, encrypted loopback streaming, the packaged CLI and the app build. On a real menu bar, a gap asked for at 1400–1460 points among the status icons was placed at 1384–1477 and removed afterwards. A real two-Mac session with this preview on both Macs, with status icons that sat behind the notch in preview 39, remains a separate acceptance check.
Use Check for Updates… on each Mac, or download the ZIP. Updates install while idle. Apple silicon and macOS 14 or later; Developer ID signed, notarized and stapled. All tests, builds, signing and packaging run on the local Mac. GitHub Actions remains disabled.
Mooring 0.3.0-preview.39
Mooring 0.3.0 preview 39 — Edge to edge
On a viewing Mac with a camera notch, full screen while controlling now uses the row beside the camera. The sharing Mac's menu bar moves up into that row, its bottom level with the notch's, and nothing below it is hidden. The sharing Mac keeps the span behind the notch clear, so its app menus and status items flow around it and menus on both sides open on the sharing Mac. Settings → Viewing → Use the space beside the camera turns this off; it is on by default and applies while Match Shared Screen to This Mac is on. The viewer asks for the gap through a new session capability, so both Macs need this preview. With an older sharing Mac, full screen stays below the notch as before.
The remote pointer now reaches every edge. The viewer divided pointer positions by the picture's width, while the sharing Mac maps the last position to its last point, so the pointer stopped about a point short of the right and bottom edges and a Dock hidden on the right never appeared. The first and last points now map exactly to the remote screen's edges. In full screen, moving past the picture holds the remote pointer at that edge, however fast the move. In a window, moving across the black bars does the same. Clicks in the bars are still ignored.
⌘-Tab and other system shortcuts reach the sharing Mac only when Mooring is allowed in Accessibility on the viewing Mac. When it isn't, control now starts with a notice over the picture, once per window and with Open Accessibility Settings…, including when the footer is hidden. The session log says whether shortcuts are captured.
Local validation covers Rust, including the new menu bar messages in each direction and with and without the capability; native input checks for edge mapping, full-screen edge holding and the notch arithmetic; native media and session suites; encrypted loopback streaming; the packaged CLI; and the app build. On a notched MacBook Pro, a harness drove the real viewer into full screen with a synthetic remote screen, and a capture of the top row matched pixel for pixel. The menu bar gap was set and removed on a real menu bar. A real two-Mac session with this preview on both Macs, long app menus, and status items that already reach the notch remain separate acceptance checks.
Use Check for Updates… on each Mac, or download the ZIP. Updates install while idle. Apple silicon and macOS 14 or later; Developer ID signed, notarized and stapled. All tests, builds, signing and packaging run on the local Mac. GitHub Actions remains disabled.
Mooring 0.3.0-preview.38
Mooring 0.3.0 preview 38 — No route like home
Record a demo without showing your Macs' names or network addresses. Turn on Settings → General → Hide computer information for demos to use anonymous Mac names, mac-1.no-route-home.invalid, “NXDOMAIN sweet NXDOMAIN,” and reserved example addresses, including 2001:db8::dead:beef. The preference persists and updates Mooring windows, menus and tooltips immediately. Connections still use their saved endpoints. Remote desktop content and Apple's Screen Sharing windows are outside this view preference.
With demo privacy off, Connections and Settings → Viewing list every saved address for a paired Mac, with readable address scopes and the last connected address first. General settings show this Mac's Bonjour hostname and assigned IPv4 and IPv6 addresses by interface, including tunnels, loopback, link-local and inactive interfaces. Remote address lists contain the addresses learned when pairing, rather than a live discovery scan.
Either Mac can remove a pairing. Connected Macs running this preview exchange an authenticated revocation notice, end the session and require a fresh pairing code. Revocation survives restart and leaves other approved connections intact. Offline removal erases the local credential immediately; it cannot update an unreachable Mac's Allowed Macs list. New pairings use a separate device key for each sharing Mac; existing pairings retain their keys until paired again.
Removing an older pairing could fail with Keychain ownership error -25244 and incorrectly suggest unlocking the Mac. Mooring now erases the complete credential and its key without changing the item's ownership when deletion is refused. If erasure also fails, it reports the error and keeps the saved row for retry. Existing-item updates change only the credential data.
Local validation covers Rust, mocked Keychain deletion/erasure failures, revocation and fresh pairing over encrypted loopback, preservation of other approved keys, native media and input, the packaged CLI, and the app build. The native UI was checked with synthetic Macs and isolated preferences. Real two-Mac sessions and the affected Mac's Keychain ACL remain separate acceptance checks; update both Macs to test revocation notices.
Use Check for Updates… on each Mac, or download the ZIP. Updates install while idle. Apple silicon and macOS 14 or later; Developer ID signed, notarized and stapled. All tests, builds, signing and packaging run on the local Mac. GitHub Actions remains disabled.
Mooring 0.3.0-preview.37
Mooring 0.3.0 preview 37 — One home
Mooring's source, releases, and signed update feed now share one public GitHub repository. The Mooring website introduces the app and links to the latest preview and source.
This preview switches installed apps to the consolidated update channel. Existing release URLs redirect to the same repository, allowing older installations to reach this update. The Developer ID, Sparkle signing key, bundle identifier, preferences, saved Macs, and pairing identities remain compatible.
The static website is prepared and reviewed locally, then served by GitHub Pages with Actions disabled. Builds, tests, signing, and packaging continue to run on the local Apple silicon Mac.
Local validation covers Rust, native media and input, encrypted loopback streaming, the packaged CLI, and app build. The isolated updater test checks the previous app, redirect migration, installation and relaunch, and refusal of tampered archives and altered feeds. Downloaded-app behavior, permissions, and real two-Mac checks remain separate acceptance tests. Native sessions remain experimental.
Mooring 0.3.0-preview.9
Mooring 0.3.0 preview 9 — Sharper text
Installed copies of preview 6 or later update to this version by themselves when no session is connected.
Full colour detail for text
The picture used H.264 with 4:2:0 colour, which stores colour at a quarter of the resolution. That blurs coloured and small text: terminals, syntax highlighting, thin UI lines.
Apple silicon can encode and decode HEVC with full 4:4:4 colour in hardware. When both Macs support it, Mooring now streams HEVC 4:4:4 at the same resolution and frame rate.
At launch, each Mac encodes and decodes one small HEVC 4:4:4 frame in hardware and reads back the colour format it actually produced. Only a Mac that passes announces the capability. The sharing Mac streams HEVC 4:4:4 only to a viewer that announced it, and otherwise uses H.264 as before.
The session log says which codec is in use:
- Sharing Mac: "streaming HEVC 4:4:4 at 1920×1080, 4:4:4 chroma confirmed".
- Both Macs: whether the launch self-test passed.
Mixed versions keep connecting
The connection protocol now negotiates a version. At the start of a session, each Mac announces what it supports, and new features switch on only when both sides support them. A Mac on preview 9 still connects to one on previews 4–8, which falls back to H.264. Later features can be added the same way without breaking connections between Macs that update at different times.
Menu
Check for Updates… now sits at the bottom of the menu, just above Quit Mooring, with the installed version on the line above it.
Validation
Local validation passed with Rust session tests covering:
- version negotiation, including falling back to a host that accepts only version 4;
- the capability Hello (once only, version 5 only, unknown bits kept);
- HEVC packets and each malformed variant;
- reading 4:4:4 from an SPS;
- HEVC refused to a viewer that didn't announce it.
On this Mac (M1 Ultra), the hardware HEVC 4:4:4 path handled 120 paced 1080p frames at 60 fps:
- Encode: 10.4 ms mean, 11.5 ms at the 95th percentile. H.264 averages about 10.6 ms.
- Decode: 3.4 ms mean.
- Independent check: ffprobe reads the stream as HEVC Rext
yuv444pwith no B-frames.
Over the encrypted loopback, both sides negotiated version 5, exchanged capabilities, and the viewer decoded HEVC 4:4:4 frames from the host.
The viewing MacBook Pro's hardware support for HEVC 4:4:4 decoding hasn't been confirmed yet. Its launch self-test decides automatically, and its log reports the result.
Apple silicon and macOS 14 or later. Developer ID signed, notarized and stapled. Published to the public update feed. All CI and builds run on the local host; GitHub Actions is disabled on both repositories.
Mooring 0.3.0-preview.8
Mooring 0.3.0 preview 8 — Smoother picture on the viewing Mac
Installed copies of preview 6 or 7 update to this version by themselves: when no session is connected, within about four hours. It is the first update meant to arrive with no action at all.
Every decoded frame gets its own screen refresh
Telemetry from a preview 7 session showed the viewing Mac decoding 55–59 frames per second during motion but drawing only 30–50. The network, capture and decoding were keeping up; frames were lost in the last step.
The viewer used to draw each frame as soon as it arrived. It allowed only one frame on the graphics card at a time, and a frame arriving while another was being drawn replaced the waiting one. Frames arriving close together, as Wi-Fi delivers them after a pause, lost all but the newest.
Now:
- Paced by the display: the viewer draws once per screen refresh, up to 120 Hz on ProMotion displays.
- Nothing lost to bunching: up to two decoded frames wait their turn, so frames that arrive together are each shown. A third replaces the oldest, which limits the extra delay to one refresh.
- Two frames on the GPU: up to two frames can be rendering at once.
- Correct colour on wide-gamut displays: the picture is tagged sRGB, so macOS colour-matches it correctly. Colours may look slightly less saturated than before, and now match the sharing Mac.
Diagnostics
Every 10 seconds of a session, the viewing Mac logs where its frames went: decoded, drawn, waiting for the GPU, or replaced, plus drawing time on the processor and the GPU. This stays on that Mac and is never sent to the other one, so the connection protocol is unchanged. Read it on the viewing Mac with:
/usr/bin/log show --last 1h --style compact --predicate 'subsystem == "dev.mooring" AND eventMessage CONTAINS "viewer drawing"'Validation
Local validation passed with 153 Rust tests and every native Swift suite. scripts/measure-native-present.swift feeds decoder-style 1920×1080 frames at 60 fps through the viewer's drawing code, in a window on screen:
- Even arrival: all frames drawn at 60 fps, both in a 1600×900 window and at a 3456×2234 Retina drawable size.
- Frames arriving in pairs: 60 of 60 in the window, and 57 of 60 at the Retina size, where the rest were replaced by design.
- Cost on this Mac (M1 Ultra): about 0.2 ms on the processor and 0.1–0.3 ms on the GPU per frame.
The viewing Mac's own numbers will come from its log.
Apple silicon and macOS 14 or later. Developer ID signed, notarized and stapled. Published to the public update feed. All CI and builds run on the local host; GitHub Actions is disabled on both repositories.