Skip to content

Update README login instructions for 3.0.3 (device code flow)#708

Merged
MrSprigster merged 1 commit into
anxdpanic:masterfrom
einanderson:docs/readme-device-login
Jul 11, 2026
Merged

Update README login instructions for 3.0.3 (device code flow)#708
MrSprigster merged 1 commit into
anxdpanic:masterfrom
einanderson:docs/readme-device-login

Conversation

@einanderson

Copy link
Copy Markdown
Contributor

The README's LOGIN section still describes the browser-based "Get OAuth token" flow, which was removed in 3.0.3 (#704 / #707) — the setting no longer exists, so the instructions can't be followed anymore.

This updates the README to match 3.0.3:

  • LOGIN now documents the device code flow (Settings - Login - Login (device code) → twitch.tv/activate)
  • Adds a note that automatic token refresh requires a public Client ID (same as the in-add-on hint), with the steps to register one and where to enter it (Settings - Developer - OAuth Client ID)
  • Adds a short section for the new ad-free/Turbo device login (Settings - Subscriber and Turbo Benefits)

Docs only, no code changes. Menu paths are quoted from resources/language/resource.language.en_gb/strings.po.

🤖 Generated with Claude Code

The LOGIN section still described the browser-based 'Get OAuth token'
flow, which was removed in 3.0.3 - the setting no longer exists.
Document the device code login, the public Client ID requirement for
automatic token refresh, and the new ad-free/Turbo device login.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@MrSprigster
MrSprigster merged commit 82f4a7b into anxdpanic:master Jul 11, 2026
2 checks passed
@einanderson
einanderson deleted the docs/readme-device-login branch July 11, 2026 19:11
@einanderson

Copy link
Copy Markdown
Contributor Author

@MrSprigster Hi, what a project :) at least everything is fine. me and claude had a couple of very long sessions... hopefully some people will have fun with this reworked plugin and of course big benefits to anxdpanic for making it possible <3 without his base there would be no way for a rework.

@MrSprigster

Copy link
Copy Markdown
Collaborator

@einanderson Thanks for the efforts you put in and welcome to the long list of contributors to this project over the years. I was just a small part of keeping it going a very long time ago now. Hoping we collectively keep it going for many more years. And yep, huge respect to @anxdpanic for the extensive work he put in to keep the project alive. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants