Skip to content

Instantly share code, notes, and snippets.

@markthomas93
Forked from velzie/manifest-v2-chrome.md
Created November 24, 2024 08:08
Show Gist options
  • Save markthomas93/67e7f49043d38700de1c2212cb1996b6 to your computer and use it in GitHub Desktop.
Save markthomas93/67e7f49043d38700de1c2212cb1996b6 to your computer and use it in GitHub Desktop.

Revisions

  1. @velzie velzie revised this gist Aug 9, 2024. 1 changed file with 2 additions and 1 deletion.
    3 changes: 2 additions & 1 deletion manifest-v2-chrome.md
    Original file line number Diff line number Diff line change
    @@ -25,6 +25,7 @@ Open regedit, and create `Software\Policies\Google\Chrome\ExtensionManifestV2Ava

    ## MacOS
    In a terminal, run:
    `defaults write com.google.Chrome ExtensionManifestV2Availability 2`
    `defaults write com.google.Chrome ExtensionManifestV2Availability -int 2`
    `defaults write com.google.Chromium ExtensionManifestV2Availability -int 2`

    (note that i haven't tested this for mac. please let me know if it doesn't work)
  2. @velzie velzie revised this gist Jun 10, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion manifest-v2-chrome.md
    Original file line number Diff line number Diff line change
    @@ -21,7 +21,7 @@ echo '{ "ExtensionManifestV2Availability": 2 }' | sudo tee /etc/opt/chrome/polic
    - run the commands from the linux section

    ## Windows
    Open regedit, and create `Software\Policies\Google\Chrome\ExtensionManifestV2Availability` as a dword set to `0x00000002`
    Open regedit, and create `Software\Policies\Google\Chrome\ExtensionManifestV2Availability` in HKEY_LOCAL_MACHINE as a dword set to `0x00000002`

    ## MacOS
    In a terminal, run:
  3. @velzie velzie revised this gist Jun 6, 2024. 1 changed file with 2 additions and 3 deletions.
    5 changes: 2 additions & 3 deletions manifest-v2-chrome.md
    Original file line number Diff line number Diff line change
    @@ -8,9 +8,8 @@ You can use this as a regular user, which will let you keep your mv2 extensions
    ## Linux
    In a terminal, run:
    ```bash
    sudo mkdir -p /etc/opt/chrome/policies/managed
    echo '{ "ExtensionManifestV2Availability": 2 }' | sudo tee /etc/opt/chrome/policies/managed/policy.json
    echo '{ "ExtensionManifestV2Availability": 2 }' | sudo tee /etc/opt/chromium/policies/managed/policy.json
    sudo mkdir -p /etc/opt/chrome/policies/managed /etc/opt/chromium/policies/managed
    echo '{ "ExtensionManifestV2Availability": 2 }' | sudo tee /etc/opt/chrome/policies/managed/policy.json /etc/opt/chromium/policies/managed/policy.json
    ```

    ## ChromeOS
  4. @velzie velzie revised this gist Jun 6, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion manifest-v2-chrome.md
    Original file line number Diff line number Diff line change
    @@ -1,7 +1,7 @@
    # How to keep using adblockers on chrome and chromium
    1. google's manifest v3 has no analouge to the `webRequestBlocking` API, which is neccesary for (effective) adblockers to work
    2. starting in chrome version 127, the transition to mv3 will start cutting off the use of mv2 extensions alltogether
    3. this will inevitably piss of enterprises when their extensions don't work, so the `ExtensionManifestV2Availability` key was added and will presumably stay forever
    3. this will inevitably piss of enterprises when their extensions don't work, so the `ExtensionManifestV2Availability` key was added and will presumably stay forever after enterprises complain enough

    You can use this as a regular user, which will let you keep your mv2 extensions even after they're supposed to stop working

  5. @velzie velzie revised this gist Jun 6, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion manifest-v2-chrome.md
    Original file line number Diff line number Diff line change
    @@ -1,5 +1,5 @@
    # How to keep using adblockers on chrome and chromium
    1. google's manifest v3 has no analouge to the `webRequestBlocking` API, which is neccesary for (good) adblockers to work
    1. google's manifest v3 has no analouge to the `webRequestBlocking` API, which is neccesary for (effective) adblockers to work
    2. starting in chrome version 127, the transition to mv3 will start cutting off the use of mv2 extensions alltogether
    3. this will inevitably piss of enterprises when their extensions don't work, so the `ExtensionManifestV2Availability` key was added and will presumably stay forever

  6. @velzie velzie revised this gist Jun 6, 2024. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion manifest-v2-chrome.md
    Original file line number Diff line number Diff line change
    @@ -28,4 +28,4 @@ Open regedit, and create `Software\Policies\Google\Chrome\ExtensionManifestV2Ava
    In a terminal, run:
    `defaults write com.google.Chrome ExtensionManifestV2Availability 2`

    (note that i haven't tested this. please let me know if it doesn't work)
    (note that i haven't tested this for mac. please let me know if it doesn't work)
  7. @velzie velzie revised this gist Jun 6, 2024. 1 changed file with 5 additions and 1 deletion.
    6 changes: 5 additions & 1 deletion manifest-v2-chrome.md
    Original file line number Diff line number Diff line change
    @@ -6,6 +6,7 @@
    You can use this as a regular user, which will let you keep your mv2 extensions even after they're supposed to stop working

    ## Linux
    In a terminal, run:
    ```bash
    sudo mkdir -p /etc/opt/chrome/policies/managed
    echo '{ "ExtensionManifestV2Availability": 2 }' | sudo tee /etc/opt/chrome/policies/managed/policy.json
    @@ -24,4 +25,7 @@ echo '{ "ExtensionManifestV2Availability": 2 }' | sudo tee /etc/opt/chromium/pol
    Open regedit, and create `Software\Policies\Google\Chrome\ExtensionManifestV2Availability` as a dword set to `0x00000002`

    ## MacOS
    `defaults write com.google.Chrome ExtensionManifestV2Availability 2`
    In a terminal, run:
    `defaults write com.google.Chrome ExtensionManifestV2Availability 2`

    (note that i haven't tested this. please let me know if it doesn't work)
  8. @velzie velzie revised this gist Jun 6, 2024. 1 changed file with 8 additions and 0 deletions.
    8 changes: 8 additions & 0 deletions manifest-v2-chrome.md
    Original file line number Diff line number Diff line change
    @@ -12,6 +12,14 @@ echo '{ "ExtensionManifestV2Availability": 2 }' | sudo tee /etc/opt/chrome/polic
    echo '{ "ExtensionManifestV2Availability": 2 }' | sudo tee /etc/opt/chromium/policies/managed/policy.json
    ```

    ## ChromeOS
    - enable developer mode
    - upon rebooting, go into vt2 (shift+ctrl+right arrow function key)
    - log in as root
    - type in `/usr/libexec/debugd/helpers/dev_features_rootfs_verification && reboot`
    - upon rebooting, go into vt2 again and log in as root
    - run the commands from the linux section

    ## Windows
    Open regedit, and create `Software\Policies\Google\Chrome\ExtensionManifestV2Availability` as a dword set to `0x00000002`

  9. @velzie velzie created this gist Jun 6, 2024.
    19 changes: 19 additions & 0 deletions manifest-v2-chrome.md
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,19 @@
    # How to keep using adblockers on chrome and chromium
    1. google's manifest v3 has no analouge to the `webRequestBlocking` API, which is neccesary for (good) adblockers to work
    2. starting in chrome version 127, the transition to mv3 will start cutting off the use of mv2 extensions alltogether
    3. this will inevitably piss of enterprises when their extensions don't work, so the `ExtensionManifestV2Availability` key was added and will presumably stay forever

    You can use this as a regular user, which will let you keep your mv2 extensions even after they're supposed to stop working

    ## Linux
    ```bash
    sudo mkdir -p /etc/opt/chrome/policies/managed
    echo '{ "ExtensionManifestV2Availability": 2 }' | sudo tee /etc/opt/chrome/policies/managed/policy.json
    echo '{ "ExtensionManifestV2Availability": 2 }' | sudo tee /etc/opt/chromium/policies/managed/policy.json
    ```

    ## Windows
    Open regedit, and create `Software\Policies\Google\Chrome\ExtensionManifestV2Availability` as a dword set to `0x00000002`

    ## MacOS
    `defaults write com.google.Chrome ExtensionManifestV2Availability 2`