Skip to content

Driftstack 0.1.14

Latest

Choose a tag to compare

@driftstack-dev driftstack-dev released this 03 Sep 19:54

Driftstack 0.1.14

A batch of fixes and additions across the simulator and proxy tools, from a list of thirteen owner-reported items.

Simulator

  • Network pane — a DevTools-style panel showing each request's protocol (HTTP/3 in green), status, type, size and time, with a filter and Clear. It fills in as the device begins reporting requests.
  • URL bar shows a loading state on a slow proxy. When you tap a link and the page is slow to answer, the bar now shows a spinner and dims the old address instead of sitting silently on it, and tells you plainly when a page didn't load.
  • No more sideways shaking. A vertical scroll can no longer leak sideways movement into the page — drags lock to one axis, like a real phone.
  • Fits on small screens. On a laptop-sized display the simulator leaves room around itself instead of filling the screen; a size you set by hand is remembered.

Proxies

  • Latency is measured where it matters. The number shown is now measured from Driftstack's side, not from your own computer; the local reading is labelled "from this Mac" so the two can't be confused. Where a fleet machine is available, tests can run from the very Mac that runs your profiles, labelled as such.
  • A real QUIC verdict. The QUIC chip turns green only when a session has actually been observed carrying HTTP/3 through the proxy — never inferred, never guessed. Until then it reads as inferred.
  • Warnings before you rely on a proxy that can't work. Adding a proxy on your own machine or private network, or one with no username and password (IP-allowlist auth), now shows a clear warning explaining why profiles running on Driftstack's servers can't use it.

Getting started

  • The empty profiles view is one clear sentence and a button, in a lighter accent that matches the theme.
  • "Get set up" is for first-time users only. It no longer reappears after you've launched a session and later removed it.

Behind the scenes

  • Geolocation now uses the precise coordinates of your proxy's exit, so a page asking for your location gets one that matches your IP.