Skip to main content

Changelog

What’s new in the GeoSpoof browser extension for Firefox, Chrome, Edge and Safari. The extension is open source, and each release’s full notes and signed builds are on GitHub.

  1. v2.3.0Latest

    Give specific sites their own location with Per-site locations, and add whole site groups (like all of Google's sites), exact addresses or lists from a link to your Allowlist or Denylist (Firefox and Chrome). The Filters tab is now Sites, Settings has been redesigned, and Location Precision is now Randomize location, which can also pick a new random point every session, hour or day. This release also covers inline web workers started before settings load (#101), fixes document.lastModified with Engine-level Spoofing (#188), matches Chrome 156's timezone offsets, and adds Traditional Chinese.

    Upgrade impact: None. Update normally; your settings and lists carry over.

    Full release notes
  2. v2.2.3

    Maintenance and supply-chain hardening; the extension behaves the same as 2.2.2. Built on a modernized toolchain (Vite 8, Vitest 5, Node 24) with all known security advisories cleared, and the first release published with signed build provenance: verify any download with gh attestation verify <file> --repo GeoSpoof/geospoof.

    Upgrade impact: None. Update normally.

    Full release notes
  3. v2.2.2

    Small polish: the popup footer now says what the GeoSpoof GPS app does, rather than just naming it. Plus maintainer documentation.

    Upgrade impact: Optional. No behaviour change.

    Full release notes
  4. v2.2.1

    Firefox self-hosted builds now get updates from `cdn.geospoof.com` instead of a github.io address that would stop working when the repository moved to the GeoSpoof organization. The native apps and the website also moved to their own repositories; that's a repository change only.

    Upgrade impact: Self-hosted Firefox users must update to this version to keep receiving future updates (it installs automatically). Store installs (AMO, Chrome Web Store) are unaffected. No behaviour change.

    Full release notes
  5. v2.2.0

    No changes to the browser extension. This version number matches the GeoSpoof 2.2 app release, which shipped from this repository at the time.

    Upgrade impact: None. Same behaviour as 2.1.6.

    Full release notes
  6. v2.1.6

    Safari: website access is now reported. On Safari, turning the extension on and letting it read websites are two separate permissions. The extension now reports whether website access was granted, so the GeoSpoof app can tell you when spoofing is switched on but not actually allowed on pages. The host permissions are simplified to <all_urls>. Also includes a popup accessibility fix.

    Upgrade impact: Safari users: if the app says website access is missing, choose "Always Allow on Every Website" in Safari's prompt. Nothing changes on other browsers.

    Full release notes
  7. v2.1.5

    Adds a handshake that lets the geospoof.com activation page confirm the extension is installed and running. Reworks how Safari injects the page overrides, cleaning up the older registration from 2.1.3. Removes the debug log relay.

    Upgrade impact: Update normally. Nothing to do; the old Safari registration is removed automatically.

    Full release notes
  8. v2.1.4

    Fixes a locale and timezone inconsistency that the TZP fingerprinting test detects: Intl locale results now agree with the spoofed timezone, including inside Web Workers.

    Upgrade impact: Recommended for anyone checking with fingerprinting test sites. No settings change.

    Full release notes
  9. v2.1.3

    Safari 17 support. Safari only honours page-context content scripts from Safari 18, so on Safari 17 and earlier the location and timezone overrides never reached the page. GeoSpoof now injects them another way on those versions. Also includes updated translations.

    Upgrade impact: Safari 17 users should update; spoofing didn't work for them before. No change on Firefox or Chromium.

    Full release notes
  10. v2.1.2

    Follow-up to 2.1.1. Override wrapping now copies whether the original browser function is a constructor, instead of assuming. Constructors keep working with new, and plain methods stay non-constructible, as they are natively. This fixes the remaining breakage on pages that construct wrapped APIs, and removes a detectable difference.

    Upgrade impact: Recommended. No settings change.

    Full release notes
  11. v2.1.1

    Fixes a compatibility bug from 2.1.0's locale spoofing: the overridden Intl constructors could throw when a page called them with new, which broke date and number formatting on some sites. They now behave like the browser's own constructors.

    Upgrade impact: Recommended for everyone on 2.1.0. No settings change.

    Full release notes

Earlier releases, from before each one opened with a summary, are listed on GitHub.