-
Channel Badges Please provide an official API to get
- Subscriber Badges
- Bits badges
- Other kinds of badges that are channel specific/modifiers there of
For a channel.
8 votes -
Bans topic sends for timeouts and bans but doesn't differentiate The bans topic will send an event for someone getting banned or timed'out from the channel.
The bans topic doesn't tell you if it was a ban or a timeout.
- Timeout's either need to be a seperate topic (not preferred)
- The payload extended to include a time parameter, so timeouts can be differetiance (preferred)
(Webhooks have the same problem ironically)
6 votes -
Fix or improve your API Documentation. Step 2 is unclear or wrong.
I'm unable to make it work only by changing the Client-ID, nor removing the Authentication headers.
You should precise that both need to be changed. Or maybe the OAuth token should work, but it doesn't.Fix your documentation it's important for developers that everything written here is clear and easily understandable by anyone (or at least devs).
I recommend you to make a full review of the entire documentation... (Get some newbie devs to test it, if they do not understand, it's not written correctly)
Also I really encourage you to make some sample…
5 votes -
Endpoints to approve/deny messages held for review by AutoMod Messages held by AutoMod for review can be received through the documented
chat_moderator_actionsPubSub topic, however the New Twitch API does not appear to offer a way for moderators to approve/deny these messages, which would be useful for bots or moderators that use third-party tools to further customize their moderation experience.4 votes -
Webhooks topic(s) don't note required oAuth 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-eventsExpected documentation
Add, (similar to
Topic: User Changed)Authentication
User Access Token must have the `moderation:read` for the user in questionAdditional context or questions
4 votes -
Accurate documentation 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.
3 votes -
Host example code in an official Twitch organization on GitHub 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/sonia145These GitHub organizations would be better alternatives:
https://github.com/twitchtv
https://github.com/twitchdev2 votes -
don't assume gender of viewers in documentation Extensions Manager Overview -> Capabilities -> Request Identity Link
Description refers to viewer as a male ('his'). This is likely to offend some people?
2 votes -
UX improvement 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.
1 vote -
Enabling Drops 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 approvable1 vote
- Don't see your idea?