8 results found

1. Keep topic type names below 64 bytes/characters

   Summary:
   While bandwidth across networks are usually a concern, internal bandwidth and memory footprints are also a concern. When using "channel.cheer" this is fine, but topics such as "channel.channel_points_custom_reward_redemption.update" approach an unnecessary level of verbosity and is roughly the largest topic name as of this moment. This can be left (though I'd prefer it to be shortened), but future events should be kept on a low byte footprint. Below 64 is my recommendation.

   Reasoning:
   Non-development basis: There is no real reason to provide a name of a topic that is over 64 characters, if this is the case, the name is likely in need a refactor.

   Developmental outlook: In many languages you can just merely look for a string and go on from there, but when dealing with low level api layers, multithreaded, and non-blittable types, this is not necessarily possible.

   Related Events:
   - All

   Some of note are the point redemption events which have a double encoding of "channel" which feels like a remnant of PubSub.

   Summary:
   While bandwidth across networks are usually a concern, internal bandwidth and memory footprints are also a concern. When using "channel.cheer" this is fine, but topics such as "channel.channel_points_custom_reward_redemption.update" approach an unnecessary level of verbosity and is roughly the largest topic name as of this moment. This can be left (though I'd prefer it to be shortened), but future events should be kept on a low byte footprint. Below 64 is my recommendation.

   Reasoning:
   Non-development basis: There is no real reason to provide a name of a topic that is over 64 characters, if this is the case, the name… more

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Closed  ·  2 comments  ·  EventSub  ·  Delete…  ·  Admin →

2. Provide a Redirect Event

   Summary:
   Filling in the holes of what chat provides and EventSub provides would be appreciated. In this case hosts, raids, and potentially front page promo attributions. There isn't much reason to have multiple unique events in this case as all of the aforementioned events are the same, a provider of a redirect (user), a recipient (broadcaster), and an attribution amount (viewers attributed to the event). The only specifier needed is a type or context. However, different events wouldn't be necessarily rejected in concept, it would just seem unnecessary. Since a condition is sent for the subscription to the event, one could use this to focus on which type they want to receive.

   New Topic(s):
   - channel.redirect

   Structure:
   event: {
   public string userid;
   public string username;
   public string userdisplayname;
   public string broadcasteruserid;
   public string broadcasterusername;
   public string broadcasterdisplayname;
   public string type; //auto host, host, raid, front page promo (twitch would be the user in this case)
   public int amount; //viewers attributed to the redirect
   }

   Summary:
   Filling in the holes of what chat provides and EventSub provides would be appreciated. In this case hosts, raids, and potentially front page promo attributions. There isn't much reason to have multiple unique events in this case as all of the aforementioned events are the same, a provider of a redirect (user), a recipient (broadcaster), and an attribution amount (viewers attributed to the event). The only specifier needed is a type or context. However, different events wouldn't be necessarily rejected in concept, it would just seem unnecessary. Since a condition is sent for the subscription to the event, one… more

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  EventSub  ·  Delete…  ·  Admin →
   Closed  ·  AdminMarc Szanto (Admin, Twitch) responded

   Autohost and host was removed. Raid is now provided in channel.chat.notification. Front page promo is not planned at this time.

3. Add Extension Broadcaster Ratings to EventSub topics

   Add an extension's broadcaster ratings to EventSub so we can get real time feedback on our extensions from broadcasters. This should be limited to app access token from the extension itself to subscribe.

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  EventSub  ·  Delete…  ·  Admin →
   Closed  ·  AdminMarc Szanto (Admin, Twitch) responded

   The Extension Broadcaster Ratings feature has since been deprecated

4. Enchance cheering eventsub(s) to include pin information

   With the changes coming to HypeChat and Cheering

   A cheer can/will be pinned in the pin bar

   Please enchance the relevant eventsub topics to include pinning information

   We'll also need a new EventSub topic for "cheer was unpinned" for when that cheer was autounpinned due to timeout or unpinned due to user/moderator action

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  EventSub  ·  Delete…  ·  Admin →
   Closed  ·  AdminMarc Szanto (Admin, Twitch) responded

   Hype Chat has since been removed as a feature

5. Add is_prime flag to EventSub Channel Subscription Message

   Is it possible to add a is_prime flag to EventSub's Channel Subscription Message ?
   https://dev.twitch.tv/docs/eventsub/eventsub-reference/#channel-subscription-message-event

   Currently I need to use EventSub Channel Chat Notification's to get the full information about subscriptions.
   https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#channelchatnotification

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  EventSub  ·  Delete…  ·  Admin →
   Closed  ·  AdminMarc Szanto (Admin, Twitch) responded

   This feature was added to the Channel Chat Notification event

6. Add a Soundtrack Topic to eventsub

   Similar to

   https://twitch.uservoice.com/forums/310213-developers/suggestions/41519041-provide-soundtrack-now-playing-information-for-a-s

   Please provide an eventsub topic for when a song changes/starts/stops on a channel

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  EventSub  ·  Delete…  ·  Admin →
   Closed  ·  AdminMarc Szanto (Admin, Twitch) responded

   Soundtrack has since been deprecated as a feature on Twitch

7. unsubscribing

   No information how to unsubscribe from getting events to webhook

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Closed  ·  2 comments  ·  EventSub  ·  Delete…  ·  Admin →

8. Successful failure.

   Step 2 is failing successfully with {"total":0,"data":[],"maxtotalcost":10000,"total_cost":0,"pagination":[]}. Why is this so ridiculously impossible to use? I've built API integrations with over 20 different web apps. This one is BY FAR the most difficult to use. All I'm trying to do is set up a webhook so that streamers can join my software and see when people subscribed.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Closed  ·  2 comments  ·  EventSub  ·  Delete…  ·  Admin →