Skip to content

Releases: manu-tech-code/drift-releases

v1.1.14

Choose a tag to compare

@manu-tech-code manu-tech-code released this 17 Oct 19:24

Web apps, new in this release

Any site can be installed as an app of its own, the way Safari's Add to Dock does it.

  • File → Install This Site as an App… reads the page's web app manifest and shows what it found: the name, where it opens, the window it asks for and where it will live. You can rename it before installing.
  • A real app in your Applications folder. Drift writes it with the site's own icon (converted to a .icns), its name and its theme colour, so it appears in the Applications folder, Launchpad and Spotlight like any other app. A site without a manifest still installs, using the page's title and favicon.
  • A window of its own. No tabs, no sidebar, no address bar: the app's icon and name, back, forward, reload, and a title bar tinted with the site's colour. Menu commands act on it, and its size and position are remembered.
  • Links that leave the site open in Drift. An address outside the app's scope — another host, another port, a different folder — is handed to the browser as a tab instead of quietly replacing the app's page, so an app never gets lost down a link. Sign-in redirects and form posts stay in the app, because otherwise you could not sign in at all.
  • File → Manage Web Apps… lists what you installed, opens it, shows it in the Finder, or removes it — moved to the Trash, so it can be put back.

What this is not: Safari's web apps run their own process with their own identity. These are small launchers that open the site in Drift's own window, so Drift has to be installed, the Dock shows Drift while the app runs, and quitting Drift closes it. That is said plainly in the README.

Fixes

  • Touch ID enrolment failing with -25299. The 1.1.13 build and a second copy of Drift — a debug build, say — could not see each other's Keychain item, so enrolling a fingerprint failed with "The key could not be read from the Keychain (error -25299)". Each build now keeps its key under its own account name and replaces its own item instead of colliding with a sibling's.
  • Two servers on one Mac. Caught before it shipped, while web apps were being tested: the scope of an app compared hosts but not ports, so 127.0.0.1:8898 counted as 127.0.0.1:8899. The port is part of the site now, with a test pinning it.

287 tests in 18 files, no warnings in either configuration. Everything else is as it was in 1.1.13.

v1.1.13

Choose a tag to compare

@manu-tech-code manu-tech-code released this 17 Oct 15:00

Passwords, new in this release

Drift can keep your logins now.

  • An encrypted vault. Logins are sealed with AES-GCM under a key derived from your master password by PBKDF2-HMAC-SHA256 at 600,000 rounds. The master password itself is never stored, so the file on disk holds only a version, the iteration count, the salt and the ciphertext — and a wrong master password is refused by the authentication tag rather than being allowed to produce nonsense.
  • Save when you sign in. Submit a login form and Drift offers to save it, naming the user name it caught. It offers only over https (or loopback), never in a private space, never on a site the lookalike guard has flagged, and only while the vault is unlocked.
  • Fill with ⇧⌘F, or from the command bar. Several accounts for one site get a picker. Logins match on the registrable domain, so a saved example.com never answers for notexample.com.
  • Unlock with Touch ID. The vault asks for your fingerprint when its window opens and falls back to the master password on a failed or cancelled read. The fingerprint check is Drift's own: a system-gated keychain item needs a provisioning profile this build doesn't carry, and the setting says exactly that.
  • Drift → Passwords… (⌘⌥P). Search, add, edit, delete, reveal, copy (cleared from the clipboard after 45 seconds), generate a password, and lock. Closing the window locks it; it also locks itself after a configurable idle period, and locking throws the key away and empties the entries from memory.

Fixes

  • IP addresses in the vault. The registrable-domain helper turned 127.0.0.1 into 0.1, so the save prompt offered to file a login for "0.1", and two unrelated addresses ending .0.1 would have shared one entry. IP literals are recognised and kept whole now.
  • Unlabelled fields. The add-login sheet drew its fields with no labels and no placeholders at all. Every vault field now has a visible name and an example, the way the rest of the app's settings do.

Everything else is as it was in 1.1.12: extensions, fingerprint protection, site permissions and the page rendering are untouched.

v1.1.12

Choose a tag to compare

@manu-tech-code manu-tech-code released this 17 Oct 09:20

What's Changed

Features

  • Make the browser harder to single out, and stop asking for the keychain at launch

Fixes

  • Clear every Swift 6 concurrency warning, and stop the pipeline hiding failures

Other changes

  • Give permissions a prompt that remembers, and a screen that lists them

v1.1.11

Choose a tag to compare

@manu-tech-code manu-tech-code released this 17 Oct 00:46

What's Changed

Fixes

  • Make the AI answer readable instead of a wall of Markdown

Chores

  • Bump the version to 1.1.11

v1.1.10

Choose a tag to compare

@manu-tech-code manu-tech-code released this 17 Oct 00:08

What's Changed

Features

  • Let any AI service be used, not just Anthropic

Chores

  • Bump the version to 1.1.10

v1.1.9

Choose a tag to compare

@manu-tech-code manu-tech-code released this 16 Oct 23:44

What's Changed

Features

  • Add a unit test suite, wire it into CI, and remove three landmines
  • Name the source files after what they hold, not the order they were built
  • Move the store's feature methods out of the class file
  • Move four more store sections out of the class file
  • Let the user add their own search engine
  • Show a site's TLS certificate, and fix two bugs that hid behind it
  • Translate pages on this Mac instead of handing every address to Google

Fixes

  • Run CI for stacked pull requests, and correct two README claims

Chores

  • Bump the version to 1.1.9

v1.1.8

Choose a tag to compare

@manu-tech-code manu-tech-code released this 09 Oct 19:38

What's Changed

Other changes

  • Make pull to refresh deliberate and reliable: a steady pull always refreshes, a flick or slight scroll never does
  • Bump the version to 1.1.8
  • Version 1.1.8 (build 11)

v1.1.7

Choose a tag to compare

@manu-tech-code manu-tech-code released this 09 Oct 18:03

What's Changed

Other changes

  • Don't let the default-browser question block links sent from other apps
  • Bump the version to 1.1.7
  • Version 1.1.7 (build 10)

v1.1.6

Choose a tag to compare

@manu-tech-code manu-tech-code released this 09 Oct 16:13

What's Changed

Other changes

  • Add a first-run tour with a spotlight on the real window, and a protection shield in the focus bar
  • Bump the version to 1.1.6
  • Version 1.1.6 (build 9)

v1.1.5

Choose a tag to compare

@manu-tech-code manu-tech-code released this 09 Oct 13:37

What's Changed

Other changes

  • Show a pull indicator while swiping down to refresh, and refresh when you let go
  • Bump the version to 1.1.5
  • Version 1.1.5 (build 8)