Settings and activity
-
6 votes
zneix supported this idea ·
-
203 votes
An error occurred while saving the comment zneix supported this idea ·
-
11 votes
zneix supported this idea ·
-
8 votes
zneix supported this idea ·
-
11 votes
zneix supported this idea ·
-
11 votes
zneix supported this idea ·
-
280 votes
We wanted to provide further context regarding this request as it is the most upvoted suggestion. There are several great use cases for providing the offset of Clips (including those above), but there are also ways in which it can be used negatively. For that reason, our initial decision was to no longer provide this information. With your feedback provided here, we are actively evaluating how to balance enabling good use of this information for creators while negating its potential for abuse. The status will be updated when we can share more information.
zneix supported this idea ·
-
8 votes
zneix shared this idea ·
-
153 votes
zneix supported this idea ·
-
13 votes
zneix shared this idea ·
-
143 votes
An error occurred while saving the comment zneix commented
@ScottRC While emote-sets tag from `USERSTATE` (and `GLOBALUSERSTATE`) are useful and give us all the information to look up emote sets by IDs I wanted to address the existing issue with that solution here as well - so far, these are the IDs of emotesets I've encountered so far that have the same issue as described by @Rosuav on the Twitchdev forums[1]: `472873131` `477339272` `488737509` `537206155` `564265402` `592920959` `610186276`. Trying to lookup those in Helix returns empty arrays as I believe that whether a user has emotes from those sets or not is tied to user's account.
The only alternative would be to use Kraken's Get (Authenticated) User's Emotes, but given today's announcement about Kraken decomission we'd need a way to query those in Helix. Many third-party chat clients (including the one I currently maintain) use this functionality and it's very important to us.[1] https://discuss.dev.twitch.tv/t/announcing-api-endpoints-for-twitch-emotes/32073/16
zneix supported this idea ·
-
6 votes
zneix supported this idea ·
-
3 votes
zneix supported this idea ·
-
27 votes
zneix supported this idea ·
-
8 votes
zneix supported this idea ·
-
52 votes
zneix supported this idea ·
-
210 votes
zneix supported this idea ·
-
121 votes
zneix supported this idea ·
-
62 votes
zneix supported this idea ·
-
103 votes
zneix supported this idea ·
With a change that was made some time ago to the response of /vips command it's now not always possible to get a full list of all the VIP users in a chat - the response returns display names instead of login names, which, in case of users with non-ascii display names or custom "fancy names with spaces" (e.g. 'sournothardcore') it's impossible to use that non-ascii display names against helix's Get Users endpoint and get their user ID that way. Many third-party tools relied on and still use responses of /mods and/or /vips to effectively get a list of users with these roles in the chat.
While response on /mods didn't change and is off-topic here, /vips one did and like I said, makes it impossible to know who is a user if they have a display name that doesn't match their login name; adding an API to get VIP users would fill in this gap and fix the issue that the change I've mentioned has introduced.