Repository navigation
v2.0.0
LinkUnbound 2.0.0 — rewritten, for Windows and macOS
The first stable release of the 2.0 line. The whole program was written again: two small native binaries in Rust where 1.x was a Flutter application, one resident that draws the picker and the notice, one settings window opened on demand. The same idea as always — a link arrives, you say which browser opens it, and a rule remembers — with more of it done well.
-
Appears near the cursor, in two looks: a classic list or a mosaic of tiles that shows every profile at once.
-
Keys
1–9pick a row; Shift held, or the Private pill pinned, opens a private window with the switch each browser family expects;Ctrl+Ccopies the address;Escputs it away. Links clicked while it is open wait their turn. -
Says where the link comes from and which application sent it, after unwrapping Microsoft SafeLinks and the Edge-only scheme Teams and Outlook wrap links in.
-
Takes no focus when a rule decided: a small notice in the corner names the rule, with an Undo for six seconds.
-
Four reaches: this exact address, this host, the whole site, or everything a given application sends. The narrowest match wins, and a rule scoped to an app wins over any domain rule.
-
Written from the picker — reach first, then browser — or typed in from the Rules page, for a site not visited yet. A rule can ask for a private window.
-
Local documents open through the picker when you choose them for it:
.html,.pdfand the rest on Windows,.htmland.xhtmlon macOS. -
The resident lives in the menu bar as
LSUIElement, floats above every Space, and takes links, documents and launches as Apple Events. Default-browser registration goes through the system's own prompt; the browser that held the links before gets them back on unregistering. Login items throughSMAppService. -
Signed with a Developer ID and notarized, one disk image per chip:
aarch64for Apple Silicon,x86_64for Intel.brew install --cask linkunboundpicks by itself; a copy running under Rosetta updates into the native build. -
Registers under its own ProgId and re-points the registration when the install moves, without recreating what the person took away; Windows keeps the final choice through
UserChoice, as it should. -
A named pipe owned by the signed-in user hands every new link to the resident already running. The installer and the Microsoft Store package carry the same binaries, under the identity 1.x shipped with, so a Store copy is offered this one.
Six pages: Links (whether the system sends links here, what is wrong when it does not, and the repair), Rules, Browsers (detected, with Chromium profiles; hide, duplicate, or add a custom one), Application (theme, language, picker look, start at sign-in, global shortcut, background checks), Maintenance (diagnostic report, rescan, reset, unregister) and About. English and Spanish; light, dark or the system's.
Every six hours the resident asks the release feed without a window. A newer version shows as a strip atop the picker and under About; one press downloads the signed installer, checks it against the key built into the copy you are running, and runs it. Stable copies hear only about stable releases; the candidate switch under About opts into the next series. A Store copy updates through the Store.
2.0 is not compatible with the settings of the 1.x line and does not promise to carry them over. On Windows it reads the rules and browsers of a standalone 1.x install where they are and keeps the originals as rules.1x.json and browsers.1x.json before writing its own format; a Store copy of 1.x kept its files inside its package and they are not read. Remove 1.x before installing — the installer offers to; a Store copy has to be uninstalled by hand, or two residents run side by side with the same icon. On macOS 2.0 ships as dev.rgdevment.linkunbound; 1.x was com.rgdevment.linkunbound and nothing of it is read: quit it, remove it, and set LinkUnbound as the default once more.
Windows installer and macOS disk images from GitHub Releases, brew install --cask linkunbound, or the Microsoft Store when its review is through. Every finding is welcome as an issue.
What's Changed
- chore: replace the Flutter tree with the Rust skeleton by @rgdevment in #7
- fix: the answers the update circuit was giving that were not true by @rgdevment in #8
- Feat macos support by @rgdevment in #9
- fix: what the audit of the Mac port found, from the launch route by @rgdevment in #10
Full Changelog: v1.4.0...v2.0.0