Skip to content
Translate Ideas and Comments
Choose language:
There was an error during translation

Developers

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

115 results found

  1. Currently, almost all of the endpoints that are involved in EventSub as well as twitch.tv have TLS 1.3 support except for id.twitch.tv . For applications with restrictions on older TLS, this becomes a blocker. My application is currently utilizing a library with tls 1.3 only which seems to be failing on id.twitch.tv (i believe twitch sends a hello packet and terminates the connection to downgrade it).

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. The DELETE EventSub Subscription https://dev.twitch.tv/docs/api/reference#delete-eventsub-subscription takes a single ID, and nothing else (aside from auth etc). I propose allowing multiple IDs to be passed in for a single call, for example id=<id1>&id=<id2>&id=<id3> - potentially up to 100 like other APIs.

    This would then unsubscribe from all of the IDs, assuming they pass all the normal auth checks etc.

    Currently it takes us 15 calls to unsubscribe from all the subscriptions that we are 'done with', adding up to around 3.5 seconds of time spent round tripping the calls. It seems like there would be a lot of value in making…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Most bot functionality is behind trigger characters, with "!" being the most popular. For such bots, receiving a webhook message for every message in chat is an unnecessary number of requests. I suggest a simple prefix comparison or regular-expression based "message_filter" condition to allow limiting channel.chat.message subscriptions, reducing network overhead and load at the cost of a single comparison.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Add Timestamp when message was sent to channel.chat.message

    Why?
    Including the original timestamp of when a message was sent would be extremely valuable for multiple reasons:

    Improved Debugging – When a server processes a message with delay, having access to the actual sent time makes it much easier to identify and troubleshoot latency issues in the message flow.

    Support for Time-Sensitive Chat Games – Some chat-based games rely on the exact send time of a message to determine whether to process it. In the event of lag, having the original timestamp allows developers to rely on Twitch’s data rather than…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. IRC's CLEARCHAT has ban-duration accessible at all scopes, but EventSub's channel.ban requires channel:moderate scope, i.e must be a mod. This information is normally available to all chatters; 3rd party chat programs cannot migrate from IRC and retain feature parity

    Either the information should be provided via channel.chat.clear_user_messages, or, better, the scope for channel.ban should be expanded. Information can be restricted if the scope does not have channel:moderate.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. When a chat message is

    PARTYHAT Happy Partner Anniversary

    That chat message needs an identifier for "was prefilled from prompt"

    As it is translated to the users local langage (not the channels language), so if a chat moderation bot is enforcing English (or whatever language) the mod bot can ignore/respond accordingly.

    Notably if a bot is looking for "non latin" characters chinese is an easy wack in error for example

    And doing "any message that starts with PartyHat" is a loophole, since theres also not API for "when is a channels 'versary"

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Reason for this is because when creating new redemption awards they always add the beginning of the list, what if I wanted to do specific orderings. I would like to remove the "new" indicator or have it say new but in the correct sorted order.

    As an aside, I would also love to see bulk redemption pushing, havent seen a way to do this one either.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Please provide a topic that emits when an extension is activated/deacted/changed in a slot on a channel.

    I would not expect it to require a scope as https://dev.twitch.tv/docs/api/reference#get-user-active-extensions doesn't require a scope.

    It would be useful to monitor/confirm into third party tooling that extensions have been updated, especially when the dashboard is used to update, or it's auto updated due to an extension/game automatic switch.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Allow filtering the event sub subscriptions list by specific transport destinations

    Some people may use a clientID to feed more than one application.
    So being able to ask the API to filter by destination would be useful.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Please add user details to the 'automod.message.hold' subscription type like:
    1. Badges
    2. Or/and moderator, VIP and subscriber status

    https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#automodmessagehold

    That way we can determine the severity of the held message based on the user.

    It currently works like this in the first-party AutoMod queue and in Twitch chat, where a user's chat badges are shown.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Polls are visible to anyone in the stream chat, why is a special scope required to view the poll via the API?

    The channel.poll.progess etc. events should require the same scope as channel.chat.message.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. The channel.chat.message subscription changes its message type to gigantified/message effect when these power ups are used, but - in contrary to when bits are cheered directly - does not tell, how many bits were used to use the power up. For loyality tools and rewards, tracking bits cheered with power ups would be amazing.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Scope formatting inconsistency. The channel.chat.usermessagehold and channel.chat.usermessageupdate sections have the word "scope" inside the code tag instead of outside like the other sections.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. I think it would be useful to add the possibility to select in which shard in a conduit a subscription will be created. This would made the developer to have more control over subscriptions created in a conduit. I think this feature would fit in as an optional parameter in the request body at creating a subscription within a conduit.

    I know the conduits are made to balance the traffic over shards and connections but giving the developer more controll over which subscriptions goes in which shards is something that will make developing over conduits better.

    In my opinion this…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Previously PubSub had a field called "bitstotalused" in a cheers payload that represented all-time user bits which is not currently available in EventSub events. This is an important data that I was using to cache data for custom leaderboards widget that requires any data prior to its existence. Unfortunately, to obtain this data you have to make a Leaderboard API call by user_id, which is really inconvenient.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Please add the total amount of cheered bits and subs that occurred during the hype train to the channel.hype_train.end event. These numbers are already visible above chat and in the activity feed after the train finished.

    It currently only contains top contributors, but not overall numbers from all contributors. The top contributors could be improved as well, as it only contains a total integer. When that total is 5000, it could be either 10 tier 1 subs, 2 tier 3 subs or a mix.

    The overall total integer is even worse as it has bits mixed in there as well.

    …

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. title basically :-D

    We get the bits used in a cheer event but we don't get the new total for that user

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Today there is a ban event on the EventSub. It allows us to know who has been banned, by whom, and above all, if it is permanent or not, which allows us to make the difference in a ban and a timeout. This is not the case during the event of unban, we do not know if the origin, it was a permanent ban ...

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Everything is in the title. Today we do not know who created the prediction or the vote. It is necessary to make an API call, which is really sad ...

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Updated

    https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types#channelchannel_points_custom_reward_redemptionupdate

    To declare which moderator/broadcaster/user did the update, and if it was API omit.

    This may be more appropritate to add to the proposed moderator actions topic instead https://twitch.uservoice.com/forums/310213-developers/suggestions/42991875-please-provide-a-topic-s-for-all-kinds-of-moderat

    This is useful to track which moderator handle the Reward Redeem (whatever it was). And/or track bad actors/mistakes.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?