User Agent Switcher

Recent Commits

• ray-lothian(22 Oct 26)

  Merge pull request #295 from M26Pershing90mm/add-current-windows-browser-profiles Add current Windows browser profiles while retaining historical entries

• Sakai(22 Oct 26)

  Remove temporary build verification workflow after passing all checks

• Sakai(22 Oct 26)

  Correct test alignment with sorted source asset order

• Sakai(22 Oct 26)

  Diagnose browser parser classification during temporary verification

• Sakai(22 Oct 26)

  Temporarily run build validation for PR #295 (remove after test)

• Sakai(22 Oct 26)

  Move Windows browser profiles to source assets and revert generated JSON changes

• ray-lothian(22 Oct 26)

  Merge pull request #288 from bvobart/fix/youtube-captions-260 Keep real headers on YouTube's integrity-token request (fixes #260)

• ray-lothian(22 Oct 26)

  Merge pull request #294 from M26Pershing90mm/fix-korean-option-descriptions Clarify Korean option descriptions in v2 and v3

• Sakai(21 Oct 26)

  Keep existing node assets and retain only v3 browser profile updates

• Sakai(21 Oct 26)

  Limit current Windows browser profile updates to v3

• Sakai(21 Oct 26)

  Add current Windows browser profiles while retaining historical entries

• Sakai(21 Oct 26)

  Clarify Korean option descriptions in v2 and v3

• ray-lothian(21 Oct 26)

  Merge pull request #291 from YiGeon/add-korean-translation Add Korean (ko) translation

• YiGeon(20 Oct 26)

  Add Korean (ko) translation

• Bart van Oort(15 Oct 26)

  keeps real headers on YouTube's integrity-token request (#260)

• ray-lothian(03 Oct 26)

  Merge pull request #285 from M26Pershing90mm/patch-1 Update print statement to reflect farewell message

• Sakai(03 Oct 26)

  Append modern Samsung Internet profiles without removing existing entries

• Ray Lothian(30 Sept 26)

  version 0.7.2

• Ray Lothian(30 Sept 26)

  fixes Server-Timing marker is page-visible

• Ray Lothian(30 Sept 26)

  prototype-level hardening

• Ray Lothian(30 Sept 26)

  Improving JavaScript spoofing in override.js part 1

• Ray Lothian(30 Sept 26)

  keeps the JS marker alive on SW-relayed navigations

• Ray Lothian(30 Sept 26)

  improves sandboxed-iframe bypass

• Ray Lothian(30 Sept 26)

  make protected a consistent bypass and remove challenges.cloudflare.com from the default protected list

• Ray Lothian(22 Sept 26)

  Extension security report validation based on https://github.com/ray-lothian/UserAgent-Switcher/issues/257#issuecomment-5729663511

• Sakai(20 Sept 26)

  Update print statement to reflect farewell message This PR modernizes the Samsung Internet Android user-agent dataset by replacing the legacy-heavy device list with a smaller set of current Galaxy S and Galaxy A device profiles. The existing samsung internet-android.json contains many historical Samsung Internet user agents representing old Android releases, discontinued Galaxy devices, and very old Samsung Browser / Chromium versions. Examples include: Galaxy S5 / SM-G900F Android 5.0 SamsungBrowser/2.1 Chrome/34.0.1847.76 Galaxy S8-era devices Android 7, 8, and 9 profiles other discontinued Samsung devices and browser versions These entries are historically valid, but they no longer represent the Samsung Internet environments that most users are likely to emulate today. Why remove the old profiles? The primary reason is website and browser compatibility, not simply security. Changing the User-Agent does not install an old browser engine, so an old UA string should not itself be treated as a browser security vulnerability. However, many websites still inspect User-Agent strings when deciding how to handle a client. Using an old Samsung Internet profile can therefore cause a modern browser session to be identified as an obsolete Android/Samsung Browser environment. This may result in: unsupported-browser warnings; legacy mobile layouts; unnecessary compatibility fallbacks; disabled web features; incorrect browser capability detection; incorrect device detection; older authentication or payment compatibility paths; inaccurate analytics or browser-detection results. For example, a profile such as: Mozilla/5.0 (Linux; Android 5.0; SAMSUNG SM-G900F Build/LRX21T) SamsungBrowser/2.1 Chrome/34.0.1847.76 ... represents a real historical Galaxy S5 environment, but selecting it today can cause websites to treat the session as an Android 5 / Chromium 34 browser. Historical profiles can still be useful for dedicated compatibility testing, but keeping hundreds of them in the primary Samsung Internet Android list makes the modern profiles difficult to locate and makes the list less representative of current Samsung devices. Proposed modern device profiles The replacement list focuses on current and recently supported international Galaxy models. Galaxy S series Galaxy S26 Ultra:SM-S948B->Android 17 Galaxy S25 Ultra:SM-S938B->Android 16 Galaxy S24 Ultra:SM-S928B->Android 16 Galaxy S23 Ultra:SM-S918B->Android 16 Galaxy S22 Ultra:SM-S908B->Android 16 Galaxy A series Galaxy A57 5G:SM-A576B->Android 16 Galaxy A37 5G:SM-A376B->Android 16 Galaxy A27 5G:SM-A276BAndroid 16 Galaxy A17 5G:SM-A176BAndroid 16 Galaxy A07 5G:SM-A076B->Android 16 The proposed profiles use: Samsung Internet 30.0 Chromium 143 current Galaxy model identifiers current Android versions Samsung Internet UA Reduction Samsung Internet 24.0 and later normally uses User-Agent Reduction. A real modern Samsung Internet UA may therefore contain: Android 10; K instead of exposing the physical Android version and Galaxy model directly. For example: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/30.0 Chrome/143.0.0.0 Mobile Safari/537.36 The new profiles in this proposal intentionally use explicit device information such as: Android 17; SM-S948B or Android 16; SM-S938B because these profiles are intended for device-specific spoofing/emulation. They should not be interpreted as claiming that Samsung Internet 30 normally exposes these values in its reduced User-Agent. If this project intends to include only naturally observed UA strings, the reduced Android 10; K format should remain and device-specific identification should instead be implemented through profile metadata and User-Agent Client Hints. File replacement For direct/local use, replace: v3/data/popup/browsers/samsung internet-android.json with the new modern Samsung Internet Android dataset. The resulting file contains only the current Galaxy S/A device profiles and removes historical entries such as: SM-G900F Build/LRX21T SM-G955U SamsungBrowser/2.1 SamsungBrowser/10.2 obsolete Android 5–9 Samsung profiles Important repository build behavior The files in: v3/data/popup/browsers/ are generated files. The repository's node/build.js reads UA strings from: node/assets/*.json and regenerates the browser-specific JSON files. Therefore, replacing only: v3/data/popup/browsers/samsung internet-android.json is sufficient for direct/local testing, but it is not sufficient for a permanent upstream change. A future build would recreate the file from the existing source UA dataset and could restore the legacy entries. For a permanent upstream implementation, the appropriate process is: remove the obsolete Samsung Internet Android UA entries from the relevant node/assets/*.json source files; add the new current Galaxy S/A device profiles; regenerate the browser data using the existing build process; verify the resulting samsung internet-android.json; confirm that obsolete Samsung Internet Android profiles are no longer regenerat

• Ray Lothian(01 Sept 26)

  version 0.7.1

• Ray Lothian(01 Sept 26)

  improves managed storage to set preferences by keys not by json

• Ray Lothian(01 Sept 26)

  prevents Firefox from looping when remote-address is set by managed storage

• Ray Lothian(31 Aug 26)

  concurrency-safe wrapper for network configuration