Make the docs closer to OAuth specs. The docs say to send parameters to /token (and /revoke) in the query string, but this is non-standard. Twitch supports the parameters in either the query string or request body.

The documentation should prefer the standard approach of sending parameters in the request body.

This documentation isn't clear enough, it implies that the ID attribute should be set to the channel name, but for whatever reason it has to be set to 'chat_embed' and then the channel name goes in the SRC URL, replacing the 'hebo' text. There's no description of how the 'src' attribute should be presented so this isn't immediately clear.

The new mod view is great and all.

But it would be useful if extensions can add items to the Automod queue for moderators to moderate user submitted content (as per the new #7 guidelines for extension content moderation).

And said item have webhook/EBS powered accept/reject buttons or similar

https://dev.twitch.tv/docs/embed

is missing the docs search function top left/first item in the nav

https://i.gyazo.com/76d10ed7c987ed262276501e25231ac6.png

"WWW-Authenticate header" vs "WWW-Authenticate header"

https://dev.twitch.tv/docs/irc#overview

Row:
client.connect();

Should be replaced with:
client.connect().catch((err) => {console.log('Connection error!', err)});
or smth like that.

Let's show users how to write good code, and show them, that all Promises should be handled. Unhandled promise rejections is bad!

Tmi.js Library also have connect example which contain promise handling

Token is not really required for listening topics like public points reward redeems.

The scopes page on Authentication(https://dev.twitch.tv/docs/authentication/#scopes)

is missing the documented scope from the Helix Get Moderators

Returns all moderators in a channel.

Authorization
Requires OAuth Scope: moderation:read

https://dev.twitch.tv/docs/extensions/reference#helper-viewer


The Twitch.ext.viewer object is a collection of info about the twitch viewer that is watching the channel page where your extension is activated. It will only be populated if the viewer is logged in, and only after the `onAuthorized` callback has been called. Accessing its properties will otherwise return `null`.


Should be


The Twitch.ext.viewer object is a collection of info about the twitch user that is watching the extension view.


Or something, as the viewer helper object exists on all views!

https://dev.twitch.tv/docs/extensions/reference/#send-extension-pubsub-message

The docs say Valid values: "broadcast", "global".

But, the target 'whisper-opaqueId' to send "per user" pusub message is missing.

The Get Broadcast Subscriptions docs https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptions was updated to include gifterid and giftername fields, but neither of these were added to the example.

Also, the example is erroneous because it shows the same user id for both broadcaster and subscriber, but they represent different usernames, which is impossible.

https://dev.twitch.tv/docs/authentication

"Code samples are available here."

This line needs to be updated to point to different examples as the repo has been updated, for example for nodejs example its now at:

https://github.com/twitchdev/authentication-node-sample

not sure why someone decided it made sense to separate examples rather than place them in one repo

https://dev.twitch.tv/docs/authentication/getting-tokens-oauth#oauth-client-credentials-flow

There's no information about error response and it doesn't seem to be fully compatible with RFC 6749 which means I can't find info about possible errors easily.

https://dev.twitch.tv/docs/api/reference/#get-extension-transactions

Unlike other documentation, https://api.twitch.tv/ is omitted from the URL and the example call

Add parameter to enable dark mode for chat please.

https://discuss.dev.twitch.tv/t/new-extension-policy-updates-including-a-moderation-section/24410/3

As noted for the new policy, we should prevent people banned/timed out from the channel, from submitting content.

Theres no way to do that without an extensions developer creating an external oAuth loop to request the relevant scopes from a broadcaster.

Duplicate the subscription scope capability to a the channel moderation scope to facilitate this policy being enforceable and negate the need for two sets of keys for each extension.

Td

In the dev docs, can you add an "Updated" field with the date of when the page was last updated, or what versions the doc works with? Trying as a newbie now, there's some stale info in here.