ver 1.2.0
A rename, and the groundwork for a Chrome Web Store listing. No behaviour changes — if v1.1.0 works for you, this one works the same way.
Renamed to TailExt
The extension used to ship as "Tailscale Extension", carrying Tailscale's wordmark and icon. That was never appropriate for anything published: the BSD-3 licence this code is under says the copyright holder's name may not be used to promote derived products without permission, and it invites people to mistake this for an official client.
It is now TailExt, with its own artwork. Tailscale is still named as the service this works with, and the popup keeps its attribution link to the upstream project. This remains unofficial and unaffiliated.
Firefox users: the add-on id changed from browser-ext@tailscale.com to tailext@iazat.github.io, so Firefox treats this as a new add-on rather than an update. Remove the old one first.
Changes
- New icon, with a full set of sizes. The toolbar icon was previously a single 128px image the browser squashed down to 16, which turned it to mush; each connection state now ships artwork drawn for the size it is displayed at.
- The manifest declares an icon set at all, which it never did.
- The README says plainly what is tested and what is not, and documents how releases are built.
- Notes for a store submission live in
docs/chrome-web-store.md, and there is now aPRIVACY.md.
Install
Download the zip for your browser — ts-browser-ext-chrome-v1.2.0.zip or ts-browser-ext-firefox-v1.2.0.zip — and unzip it. Each contains only what the browser needs; the source archives below carry the whole repository and are not what you want here.
Then load it unpacked (chrome://extensions → Developer mode → Load unpacked, or about:debugging → Load Temporary Add-on in Firefox), open the popup, and run the command it prints. It builds and registers the companion backend, which the extension does nothing without.
Requires Go, and macOS or Linux.
Upgrading from v1.1.0? Remove the old extension first rather than loading both — on Firefox the changed add-on id makes it a separate add-on, and on Chrome two copies will each try to register their own backend.
Known limitations
Unchanged from v1.1.0:
- Firefox has not been run live. Its test suite passes and its code is diffed against the working Chrome copy, but no build has been loaded through
about:debugging. - Windows cannot register the native host. The binary builds, but there is no registry install path yet.