130 results found
-
graph syntax not built on deploy
The graphs on this page don't look right. The graph syntax is displaying, not the graph itself.
%% Extensions Overview Diagram graph LR Twitch --> | - postMessage - | Extension Extension --> | - postMessage - | Twitch Extension --> | - HTTP - | APIs Extension --> | - HTTP - | EBS[Extension Backend] Identity --> Twitch Chat --> Twitch Memes --> Twitch
3 votes -
The documentation doesn't express how to properly authenticate a chatbot without human intervention
This page suggests "OAuth Authorization code flow" but i don't believe this is correct because for a chatbot to be effective you would need the access token to never expire or the process to handle expiry and refresh to be event driven. Having a robot/non-existing user login seems misleading or wrong.
3 votes -
Update References to v5 API
There are reference to V5 API here to get user and channel ID.
Combined with the GitHub Sample at https://github.com/twitchdev/pubsub-javascript-sample that is still using it this is very confusing to get to work.
Suggest to update the sample and this article to reference the helix APIs instead.3 votes -
IRC Landing page/guide -> twitchapps.com
https://dev.twitch.tv/docs/irc
As a getting started/IRC docs landing page is confusing new developers
As it references
The token to authenticate your chatbot with Twitch's servers. Generate this with https://twitchapps.com/tmi/ (a Twitch community-driven wrapper around the Twitch API), while logged in to your chatbot account. The token will be an alphanumeric string.
And doesn't reference anything about the "right way" to auth/scopes needed
Until the end of the guide.
Authentication using not a third party site should be more prevalent in the guide.
3 votes -
Get Custom Reward Redemptions "missing redemption status"
Declares that only broadcasterid and rewardid are required.
A call to
results in
{
"error": "Bad Request",
"status": 400,
"message": "missing redemption status"
}The documentation lists status as not required
3 votes -
anonsubgift, anonsubmysterygift, anongiftpaidupgrade are documented but never occur
https://dev.twitch.tv/docs/irc/tags#usernotice-twitch-tags documents anonsubgift and anongiftpaidupgrade. I found this announcement post https://discuss.dev.twitch.tv/t/anonymous-sub-gifting-to-launch-11-15-launch-details/18683 saying that apparently it was temporarily disabled as a workaround. As far as I can tell to this day the workaround is used. The documentation should be updated to remove the originally planned but never put into service types, and instead document that anonymous gifts come from AnAnonymousGifter.
3 votes -
Remove jQuery from the GA Example
The examples for Google Analytics suggest using jQuery. Which is extra bloat if an extension hasn't use jQuery to start with and can lead to confusion
3 votes -
Chat and Pubsub - channel:moderate
As per this other uservoice
The moderation actions PubSub at time of writing requires a key from the channel you wish to listen to with the scope
channel:moderate
However the scopes page
https://dev.twitch.tv/docs/authentication/#scopes
is mis leading as it only talks about how the scope works for chat leading to confusion with pubsub operation
"Perform moderation actions in a channel. The user requesting the scope must be a moderator in the channel."
The wording needs to be changed and/or the pubsub topic adjusted to support being able to read moderator events as a moderator
3 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?
3 votes -
The Validate requests endpoint omits the expiry from the example response
URL
https://dev.twitch.tv/docs/authentication#validating-requests
{
"clientid": "<your client ID>",
"login": "<authorized user login>",
"scopes": [
"<requested scopes>"
],
"userid": "<authorized user ID>"
}should be
{
"clientid": "<your client ID>",
"login": "<authorized user login>",
"scopes": [
"<requested scopes>"
],
"userid": "<authorized user ID>",
"expires_in": timeInSeconds
}3 votes -
Extension popout "by default"
From: https://github.com/twitchdev/issues/issues/72
Brief description
By default, pop-out control is enabled for panel Extensions and for extension “live configuration views” (see the Live Config Path setting on the Asset Hosting tab in the Extensions manager).
https://dev.twitch.tv/docs/extensions/required-technical-background
The documentation suggests that extension developers can disable pop-outs. Which is not the case
3 votes -
User/Channel ID needs to be a string
From: https://github.com/twitchdev/issues/issues/70
Brief description
The documentation for creating signing JWT's don't explicitly state that
user_id
/channel_id
in JWT's need to be an explicit string literalhttps://dev.twitch.tv/docs/extensions/building/#signing-the-jwt
https://dev.twitch.tv/docs/extensions/reference#send-extension-pubsub-messageExpected documentation
Where: exp is the Unix epoch timestamp when the payload will expire. Be sure to provide a buffer, to allow potential positive time drift. user_id is the Twitch user ID that owns the extension, where the user ID is cast as a string literal. role is set to external.
3 votes -
HTTP Response codes unclear
From: https://github.com/twitchdev/issues/issues/69
Brief descriptionSome endpoints return a 204 code no content.
But this is only highlighted in the example responses and not in the "main documentation"For example
https://dev.twitch.tv/docs/extensions/reference#send-extension-pubsub-message
https://dev.twitch.tv/docs/extensions/reference#send-extension-chat-messageEach endpoint documented could be extended to include usual HTTP response codes.
Expected documentation
The expected response code for success when theres no body response
Common non 2xx codes for the endpoints3 votes -
Information about config service unclear
From: https://github.com/twitchdev/issues/issues/55
Brief description
https://dev.twitch.tv/docs/extensions/building#using-the-configuration-service
Doesn't mention the key bit of information regarding the size limit of 5kb
Additional context or questions
It's important to note here as people will start designing an extension and then discover the sizing limit late into construction of an extension. For clarity the limit should be noted here also
3 votes -
Webhooks (Un)Subscribe Parameters
From: https://github.com/twitchdev/issues/issues/14
Brief description
https://dev.twitch.tv/docs/api/webhooks-reference
the
hub.topic
section is out of date, in the JSON Body ParametersExpected documentation
Just changed it to something like "refer to later in this docs for the available topics"
3 votes -
Followed list to indicate subscription
In your list of followed streamers, you can see which ones you have a gift subscription to. It would be great to see which channels you subscribe to in this list as well.
2 votes -
Wrong description in Create Prediction
Description of 'outcomes' in 'Create Prediction' says that array size must be 2. Isn't the current limit between 2 and 10?
2 votesWe are updating the API to support more than 2 outcomes.
-
Apply for appeal Yandere Simulator
Yandere Simulator has done a lot changes to since 5 years ago since its been banned including censoring blood pools, nudity and panty shots to make video streams more friendly. I recommend taking second look at game for all improvements its great game and deserves second chance. I wasn't sure to place category I apologize for that. All I'm asking is for second look at game in its current state for reconsidered banned that is all and thank you for your time.
2 votes -
Add additional examples.
Add examples of popular 3rd party libraries.
The current example is very specific and only targets one language. Many community driven libraries are continuously developing and mainting IRC capablities in languages such as; Python, JS/TS, C# and more.
It would be nice in general to see more support for these libraries and even giving some sort of verfication to popular libraries that are maintained and meet quality standards.
2 votes -
Sample code in the Status section is mac only.
Sample code for windows users would be awesome!
2 votes
- Don't see your idea?