Skip to content

V1.0.5

Choose a tag to compare

@drachescript drachescript released this 30 Oct 10:40
· 26 commits to main since this release
b05932e

v1.0.5 — Quality-of-life + follows & mod-view fixes (30/10/2025)

Highlights

  • Fetch My Follows now ignores the left sidebar and scrapes only the Following → Channels grid, with reliable auto-scroll to load your entire list.
  • Moderator View aware: if /moderator/<login> (or an equivalent channel page) is open, the extension won’t open a second / <login> tab.
  • Autoplay/unmute resilience: unmute helper handles Chrome’s autoplay policy with UI fallbacks, visibility-based retries, and gentle jitter.

Added

  • Options → Follows: two fetch modes
    • Open active tab (auto-scroll): opens the official page and auto-scrolls to harvest all usernames.
    • Use my current Twitch tab: scrapes the page you already opened and scrolled.
  • Options → Help: inline Helix setup with one-click PowerShell / cURL token snippets and “insert into config” buttons.
  • Config auto-migration: new keys are added without wiping your existing values.
  • Popup: Open Settings button and lightweight status line (enabled + next check countdown).

Changed

  • More human tab opening: wait for load, inject content_unmute.js, temporarily disable auto-discard to avoid “blank/muted” tabs on bursts.
  • Dedupe & max-tabs trimming tightened (LRU).
  • README/Store text updates and dark-mode polish in Options/Popup.

Fixed

  • Follows fetcher no longer picks up Live Channels/recommended rows from the sidebar.
  • More consistent clean-up of tabs for channels that go offline (short grace period).
  • Popup event binding race that could throw “addEventListener of null”.

v1.0.5 — Quality-of-life + follows & mod-view fixes (30/10/2025)

Highlights

  • Fetch My Follows now ignores the left sidebar and scrapes only the Following → Channels grid, with reliable auto-scroll to load your entire list.
  • Moderator View aware: if /moderator/<login> (or an equivalent channel page) is open, the extension won’t open a second / <login> tab.
  • Autoplay/unmute resilience: unmute helper handles Chrome’s autoplay policy with UI fallbacks, visibility-based retries, and gentle jitter.

Added

  • Options → Follows: two fetch modes
    • Open active tab (auto-scroll): opens the official page and auto-scrolls to harvest all usernames.
    • Use my current Twitch tab: scrapes the page you already opened and scrolled.
  • Options → Help: inline Helix setup with one-click PowerShell / cURL token snippets and “insert into config” buttons.
  • Config auto-migration: new keys are added without wiping your existing values.
  • Popup: Open Settings button and lightweight status line (enabled + next check countdown).

Changed

  • More human tab opening: wait for load, inject content_unmute.js, temporarily disable auto-discard to avoid “blank/muted” tabs on bursts.
  • Dedupe & max-tabs trimming tightened (LRU).
  • README/Store text updates and dark-mode polish in Options/Popup.

Fixed

  • Follows fetcher no longer picks up Live Channels/recommended rows from the sidebar.
  • More consistent clean-up of tabs for channels that go offline (short grace period).
  • Popup event binding race that could throw “addEventListener of null”.

Installation / Update

Option A — Chrome Web Store (recommended):
Install or update from: https://chromewebstore.google.com/detail/twitch-tab-manager/dagoljomgoainmmfldhnikegghjhbdaf

Option B — Manual (dev):

  1. Download the ZIP from this release (or load your local folder) and import via chrome://extensions → Developer mode → Load unpacked.
  2. In the popup, toggle On, then open Options to configure config.json and use Fetch My Follows.

Notes

  • Helix vs HTML: set "live_source": "auto" (default) to use Helix when credentials are present and fall back to the HTML method otherwise.
  • Tokens expire; if checks start

Notes

  • Helix vs HTML: set "live_source": "auto" (default) to use Helix when credentials are present and fall back to the HTML method otherwise.
  • Tokens expire; if checks start returning 401, regenerate your App Access Token and update config.json.

Links

  • Changelog: see the repository’s README (#changelog section).
  • Issues / feature requests: open an issue on the repo.