Repository navigation
Releases
uConnect 0.2.0 beta 3
uConnect 0.2.0 beta 3 brings the folder sync feature set to the desktop and changes how a device gets to take part in sync. Protocol: sync 1.2 and 1.3 (local policy and message semantics; no message changed shape, beta 2 peers still connect).
Folder sync
- Synced Folders window: every file with its state (synced, waiting to send or receive, transferring with progress, in conflict, ignored, skipped, held back or blocked), a tree and a flat view, search and filters, and per file Open, Show in folder, History, Ignore everywhere and Skip on this device.
- Rules editor for
.syncignore(every device) and.syncskip(this device only) with gitignore syntax, a live preview of which rule decides each path, a probe field, and a warning before saving that says how many synced files would stop syncing. - Devices view: online or last seen, what is left to send and receive with an ETA, the file in flight, when it was last fully in sync, how many paths it holds back, and pause per device.
- Transfers in the left pane with speed; folder summary (size, file count, free space); Kept files with restore from
.synctrash; a large-delete guard that holds back a round of deletes that would remove much of the folder at once; conflict preview per device (size and date); tray notifications for conflicts, held names and waiting deletes; Settings › Services › Synced Folders. - Sync permissions. A device takes part once it is granted Offer sync (it is sent your folder offers and the folders it is a member of) or Receive sync (its offers are shown so you can join them), like any other permission: special rules, a network rule or the defaults. Members that had special rules get both permissions once, on first start, so nothing stops syncing on update. The per-folder Send/Accept grants are unchanged. (#2, #4)
- Engine: a change counts as sent once the peer's own index shows it; planning is paced by how long a round takes; the local-block index is built once per change; the state file is written less often while fetching. (#4)
- Protocol sync 1.2: a folder that leaves a peer's offers is forgotten by the receiver, and a grant change greets the peer again.
Packages
| File | Platform |
|---|---|
uConnect-0.2.0-beta.3-windows-x64.zip |
Windows 10/11, x64. Unzip and run uConnect.exe. Includes the rendezvous server, the extended-display driver and the uConnect Camera component. |
uConnect-0.2.0-beta.3-macos-arm64.zip |
macOS, Apple silicon. Ad-hoc signed: right-click › Open the first time. |
uConnect-0.2.0-beta.3-linux-x86_64.AppImage |
Linux, x86_64. chmod +x and run. |
uConnect-0.2.0-beta.3-linux-x86_64.tar.gz |
Linux, x86_64, the same build unpacked. |
SHA256SUMS.txt lists every file. The mobile app for Android is released separately as uConnect Mobile 0.2.0 beta 3.
Known issues
- The conflict view compares size and date per device; it does not show contents side by side.
- The virtual camera is Windows-only; macOS has no camera extension yet.
uConnect 0.2.0 beta 2
The second beta of uConnect 0.2: your computers and phones, connected through a rendezvous server and end-to-end encrypted, sharing files, folders, screens, cameras and even displays.
Beta. Expect rough edges, and keep backups of anything you sync. These builds are not publisher-signed or notarized: on Windows, SmartScreen may ask for confirmation.
macOS: no macOS build in this release yet (the build Mac was not reachable). The 0.1.0 beta 3 macOS package remains available; a macOS build of this release will follow.
What's new
Updated build, 2026-10-24 (Windows package replaced; built from d30f62d). The Linux packages below are still the original beta 2 build (9c2175a) and do not include the streaming changes; refreshed Linux and first macOS packages will follow.
📡 Streaming rewritten (screen/camera 2.0, updated build)
Screen and camera streams now travel the way real-time services send video: numbered packets with repair packets sized to what the path loses, lost pieces asked for again within a round trip, a bandwidth estimate from the viewer's feedback every 50 ms that the encoder follows, a quality ladder that steps the picture down on a thin path and back up when it recovers, encoders without a keyframe schedule, and a playout clock on the viewer that absorbs the network's jitter instead of freezing or skipping. One lag budget of a second applies on both ends. Media goes over UDP only (direct or through the relay); the TCP fallback for video is gone.
Measured on a phone over mobile data (the case that prompted this): from under 10 fps with 1–3 s of lag and a freeze every second or two, to 30 fps/480p with ~70 ms of lag on a ~1 Mbit/s uplink with 10% loss, and 60+ fps watching a desktop. On a LAN, 1080p at 60–70 fps with 30–60 ms of lag.
Also: the playback buffer setting gains Automatic (the new default); the statistics overlay shows the buffer in use, recovered and repeated packets, and the host's round trip, loss, repair and estimator state; a hardware encoder that stops producing (seen with VideoToolbox) gives way to OpenH264 mid-stream. Protocol: screen/camera 2.0 in docs/protocol.md — the media header changed shape, so desktops and phones update together.
🛡️ Special rules and network rules replace "trust"
For each device, the first of these applies:
- its special rules: permissions of its own, added after comparing fingerprints;
- this topic's network rules: ordered address patterns such as
m.m.m.x(your own subnet),100.x.x.xorx.x.x.x, matched against the address its direct connection really comes from (not one it reports); - your defaults, which may now include any permission (with a warning for camera, screen or control).
Rules are per topic, and a device can ask another for its rules on this topic for quick setup on a trusted network (you review them before importing).
📁 Folder sync with phones
Folders now sync with uConnect Mobile too. Only devices with special rules take part; removing a device's special rules takes it out of sync.
🎥 Camera sharing
- Share any camera (or a chosen set), view a phone's camera; a "without asking" permission, rotation, and a camera picker on the viewer.
- Camera and screen viewers share one header bar with icon controls and per-view quality.
📱 Phones
- Invite QR code (Topic › Show Invite QR Code, and on the connect page): a phone scans it and uConnect Mobile opens on the topic.
- Watch and control an Android phone's screen.
✨ Interface
- Color schemes: Follow system, Dark, Darker, Light, Colorful.
- Settings: a General page, an icon per page and guides tying sub-pages to their section.
- Device tab: Connected from (the device's address), one "What It Lets You Do" section with what each service allows and a button to open it, copy buttons, a shield for special rules.
- Devices list: special rules and relayed connections as icons; a shorter context menu with icons.
- Sharing shows in the tray instead of a floating banner; device-type glyphs in avatars; crisp vector icons throughout.
- Relay mode: auto, always or direct.
🧩 Protocol
rules 1.0 (rules.get / rules.list / rules.err), sync 1.1 membership (special rules), and an implementation-neutral identity-proof context string. See docs/protocol.md. Devices on 0.1.0 do not verify identities with 0.2.0 devices: update them together.
Downloads
| File | |
|---|---|
uConnect-0.2.0-beta.2-windows-x64.zip |
Windows 10/11 x64, with the rendezvous server and the extended-display driver |
uConnect-0.2.0-beta.2-linux-x86_64.AppImage |
Linux x86_64 (glibc 2.39+, e.g. Ubuntu 24.04) |
uConnect-0.2.0-beta.2-linux-x86_64.tar.gz |
The same, as a plain archive |
SHA256SUMS.txt |
Checksums |
The phone app: uConnect Mobile 0.2.0 beta 2.
Windows build from d30f62d (2026-10-24); Linux builds from 9c2175a.
uConnect 0.2.0 beta 1
The third beta of uConnect Desktop: your computers, connected through a rendezvous server and end-to-end encrypted, sharing files, folders, screens and even displays.
Beta. Expect rough edges, and keep backups of anything you sync. These builds are not publisher-signed or notarized (see below).
Highlights
🖥️ Extended display
Use another computer's screen as an extra monitor. A Windows or macOS host gains a real monitor, which the OS treats like any other, shown full screen on the other device (any desktop can be the display).
- Pick the resolution and refresh rate, or match the other screen; the pointer is drawn on the remote screen.
- The receiving device asks for consent and lets you choose which of its screens to use; hold Esc there to stop.
- Tuned for Wi-Fi: it rides out short loss bursts and recovers from them in about 2 seconds.
- The showing device stays awake and doesn't dim (Windows, macOS and Linux).
- Windows installs the bundled display driver once, with administrator approval; macOS needs nothing extra.
🔗 Devices you trust
Devices meet in a topic shared by an invite link, verify each other's fingerprints, and each decides exactly what the others may do.
📁 Files and folders
- Storage: browse, download and upload files and whole folders in the folders a device shares.
- Folder sync: keep a folder the same across several devices.
🎥 Screen sharing and remote control
Each behind a consent prompt on the sharing device, with a sharing bar and a hotkey to stop.
Camera sharing is in progress and not finished in this version.
🛰️ Your own server, included
Every package now carries uconnect-rendezvous, the rendezvous server your devices meet through: run it on any machine they can all reach and point uConnect at it (Settings → Connection). It introduces devices and relays them only when their networks won't connect directly; it holds no keys and can't read their traffic. SERVER.txt in the package says how to run it; the Linux build is a single static binary, with a systemd unit, at the top of the .tar.gz.
🧭 Lives in your tray
Closing the window keeps uConnect running in the system tray (the menu bar on macOS), from where it opens, connects, copies the invite link, stops sharing or exits. It can start when you sign in, hidden in the tray.
New since beta 2
- The rendezvous server ships in every package (see above).
New in beta 2
- macOS hosts: the pointer now shows on the extended display (it was sent too large for viewers to accept); the screen capture keeps running when the network forces quality changes, instead of restarting (which flashed the recording indicator and cost frame rate); uConnect asks for Screen Recording itself and says how to allow it.
- A screen share is no longer ended when another monitor goes away (such as an extended display ending).
- The pointer follows the virtual monitor if it is placed or moved after the session starts.
- Linux keeps a screen showing an extended display awake.
- A refreshed icon, with more room around the mark.
Downloads
| Platform | File |
|---|---|
| Windows 10/11 x64 | uConnect-0.1.0-beta.3-windows-x64.zip: extract all, run uConnect.exe |
| macOS (Apple silicon) | uConnect-0.1.0-beta.3-macos-arm64.zip: extract, open uConnect.app |
| Linux x86_64 (Ubuntu 24.04 or newer) | uConnect-0.1.0-beta.3-linux-x86_64.AppImage (chmod +x, then run), or the .tar.gz (extract, run AppRun) |
SHA256SUMS.txt lists every file's checksum. Each package includes its Qt runtime and FFmpeg (LGPL); nothing else needs installing.
Known limitations
- No signing yet. Windows SmartScreen may warn on first run ("More info" → "Run anyway"). macOS blocks the first launch: choose Open Anyway under System Settings → Privacy & Security, or run
xattr -dr com.apple.quarantine uConnect.app. - macOS: after allowing Screen Recording, reopen uConnect. Builds are for Apple silicon only.
- Windows extended display driver: test-signed, so Windows also asks whether to trust its publisher.
- Linux: needs glibc 2.39 (Ubuntu 24.04 or as new); on Wayland, screen sharing is view-only, and Linux cannot yet gain an extended display (it can be one).
- An extended display needs both devices on the same network; its quality follows the Wi-Fi link (a wired link or 5 GHz helps).
- The rendezvous server must be reachable by every device: on one network its local address will do; across the internet it needs a public address or a forwarded port. Open its port for both TCP and UDP. The macOS build of the server is not notarized either (
xattr -d com.apple.quarantine uconnect-rendezvous).
uConnect 0.1.0 beta 2
The second beta of uConnect Desktop: your computers, connected through a rendezvous server and end-to-end encrypted, sharing files, folders, screens and even displays.
Beta. Expect rough edges, and keep backups of anything you sync. These builds are not publisher-signed or notarized (see below).
Highlights
🖥️ Extended display
Use another computer's screen as an extra monitor. A Windows or macOS host gains a real monitor, which the OS treats like any other, shown full screen on the other device (any desktop can be the display).
- Pick the resolution and refresh rate, or match the other screen; the pointer is drawn on the remote screen.
- The receiving device asks for consent and lets you choose which of its screens to use; hold Esc there to stop.
- Tuned for Wi-Fi: it rides out short loss bursts and recovers from them in about 2 seconds.
- The showing device stays awake and doesn't dim (Windows, macOS and Linux).
- Windows installs the bundled display driver once, with administrator approval; macOS needs nothing extra.
🔗 Devices you trust
Devices meet in a topic shared by an invite link, verify each other's fingerprints, and each decides exactly what the others may do.
📁 Files and folders
- Storage: browse, download and upload files and whole folders in the folders a device shares.
- Folder sync: keep a folder the same across several devices.
🎥 Screen sharing and remote control
Each behind a consent prompt on the sharing device, with a sharing bar and a hotkey to stop.
Camera sharing is in progress and not finished in this version.
🧭 Lives in your tray
Closing the window keeps uConnect running in the system tray (the menu bar on macOS), from where it opens, connects, copies the invite link, stops sharing or exits. It can start when you sign in, hidden in the tray.
New since beta 1
- macOS hosts: the pointer now shows on the extended display (it was sent too large for viewers to accept); the screen capture keeps running when the network forces quality changes, instead of restarting (which flashed the recording indicator and cost frame rate); uConnect asks for Screen Recording itself and says how to allow it.
- A screen share is no longer ended when another monitor goes away (such as an extended display ending).
- The pointer follows the virtual monitor if it is placed or moved after the session starts.
- Linux keeps a screen showing an extended display awake.
- A refreshed icon, with more room around the mark.
Downloads
| Platform | File |
|---|---|
| Windows 10/11 x64 | uConnect-0.1.0-beta.2-windows-x64.zip: extract all, run uConnect.exe |
| macOS (Apple silicon) | uConnect-0.1.0-beta.2-macos-arm64.zip: extract, open uConnect.app |
| Linux x86_64 (Ubuntu 24.04 or newer) | uConnect-0.1.0-beta.2-linux-x86_64.AppImage (chmod +x, then run), or the .tar.gz (extract, run AppRun) |
SHA256SUMS.txt lists every file's checksum. Each package includes its Qt runtime and FFmpeg (LGPL); nothing else needs installing.
Known limitations
- No signing yet. Windows SmartScreen may warn on first run ("More info" → "Run anyway"). macOS blocks the first launch: choose Open Anyway under System Settings → Privacy & Security, or run
xattr -dr com.apple.quarantine uConnect.app. - macOS: after allowing Screen Recording, reopen uConnect. Builds are for Apple silicon only.
- Windows extended display driver: test-signed, so Windows also asks whether to trust its publisher.
- Linux: needs glibc 2.39 (Ubuntu 24.04 or as new); on Wayland, screen sharing is view-only, and Linux cannot yet gain an extended display (it can be one).
- An extended display needs both devices on the same network; its quality follows the Wi-Fi link (a wired link or 5 GHz helps).
- You need a reachable rendezvous server; none is bundled.
uConnect 0.1.0 beta 1
The first public beta of uConnect Desktop: connect your computers through a rendezvous server, end-to-end encrypted, and share files, folders, screens and displays between them.
Beta. Expect rough edges, and keep backups of anything you sync. These builds are not publisher-signed or notarized (see below).
Downloads
| Platform | File |
|---|---|
| Windows 10/11 x64 | uConnect-0.1.0-beta.1-windows-x64.zip — extract all, run uConnect.exe |
| macOS (Apple silicon) | uConnect-0.1.0-beta.1-macos-arm64.zip — extract, open uConnect.app |
| Linux x86_64 (Ubuntu 24.04 or newer) | uConnect-0.1.0-beta.1-linux-x86_64.AppImage (chmod +x, then run), or the .tar.gz (extract, run AppRun) |
SHA256SUMS.txt lists every file's checksum. Each package includes its Qt runtime and FFmpeg (LGPL); nothing else needs installing.
What's in it
- Topics and trust: devices meet in a topic shared by an invite link, verify each other's fingerprints, and each decides what the others may do.
- Storage: browse, download and upload files and folders in the folders a device shares.
- Folder sync: keep a folder the same across several devices.
- Screen sharing and remote control, each behind a consent prompt on the sharing device. Camera sharing is in progress and not finished in this version.
- Extended display: a Windows or macOS computer can use another device's screen as an extra monitor (any desktop can be the display). Best on the same local network.
- System tray: closing the window keeps uConnect running in the tray (the menu bar on macOS), from where it opens, connects, stops sharing or exits. It can start when you sign in, hidden in the tray.
Known limitations
- No signing yet. Windows SmartScreen may warn on first run ("More info" → "Run anyway"). macOS blocks the first launch: choose Open Anyway under System Settings → Privacy & Security, or run
xattr -dr com.apple.quarantine uConnect.app. - Windows extended display driver: installed by the app on first use, with administrator approval. It is test-signed, so Windows also asks whether to trust its publisher.
- macOS builds are for Apple silicon only; screen sharing and control need Screen Recording and Accessibility permissions.
- Linux: needs glibc 2.39 (Ubuntu 24.04 or as new); on Wayland, screen sharing is view-only, and Linux cannot yet gain an extended display (it can be one).
- You need a reachable rendezvous server; none is bundled.