From: https://github.com/twitchdev/issues/issues/59

Brief description

Mod Change and Channel ban Change events don't note the required oAuth scope needed for the topic

https://dev.twitch.tv/docs/api/webhooks-reference#topic-moderator-change-events
https://dev.twitch.tv/docs/api/webhooks-reference#topic-channel-ban-change-events

Expected documentation

Add, (similar to Topic: User Changed)

Authentication
User Access Token must have the `moderation:read` for the user in question

Additional context or questions

https://discuss.dev.twitch.tv/t/webhook-topic-for-channel-ban-change-events-and-moderator-change-events-doesnt-require-oauth-scope/24105

All of your tutorials, links, and/or instructions are dated and unhelpful.

Try having someone follow any of this step-by-step, from scratch, and see if they can get something working, because I, nor my partners can make any usable sense of what is presented about extensions and creating/testing them.

This tutorial looks very unprofessional.

The example GitHub repository is not available from an official Twitch source, but lives in someone's personal
account at:
https://github.com/sonia145

These GitHub organizations would be better alternatives:
https://github.com/twitchtv
https://github.com/twitchdev

Extensions Manager Overview -> Capabilities -> Request Identity Link

Description refers to viewer as a male ('his'). This is likely to offend some people?

It would be nice to have a "next" or "continue" button. It is confusing to navigate after reading "what are we going to build", I wasn't sure where this building was going to happen.

This guy does not resemble reality. Part 4: Enabling Drops; Click Your Console ( Where is it, I clicked Your Dashboard); Click Drops ( Where is it? How am I suppose to find it?).
Not approvable