Settings and activity
39 results found
-
2 votes
RealityRipple
shared this idea
·
-
13 votesRealityRipple
supported this idea
·
An error occurred while saving the comment -
12 votes
An error occurred while saving the comment RealityRipple
commented
People online love to tie polls intentionally. A blind voting option would be a great way to prevent that from happening when a poll needs a more accurate response.
RealityRipple
supported this idea
·
-
28,183 votes
Thank you for raising this issue and sharing your feedback. We are in the process of rolling out a Beta version of Ukrainian localization across Twitch. Users who have their mobile devices set to Ukrainian should automatically see Twitch in Ukrainian once our roll out is 100% complete, and web users with their system language set to Ukrainian will also be able to experience our Beta version. We want to make the Twitch service accessible to as many people as possible, and localization is a part of that.
Once the rollout is finished, we will mark this issue as "Completed." Thank you.
RealityRipple
supported this idea
·
-
2 votesRealityRipple
shared this idea
·
-
1 voteRealityRipple
shared this idea
·
-
22 votes
An error occurred while saving the comment RealityRipple
commented
Providing info only if the user is @tagged would require any commands such as "!so" to require an "@" instead of it being optional, but it would have the added bonus of not requiring an API call to look up the right name. I can see potential use cases for both methods.
RealityRipple
shared this idea
·
-
7 votesRealityRipple
supported this idea
·
-
16 votesRealityRipple
supported this idea
·
-
42 votes
An error occurred while saving the comment RealityRipple
commented
Additional suggestions:
Make the "follower" tag appear only for users authorized with the "moderator:read:followers" scope for the message's channel.
Include the "follower" tag on relevant USERNOTICE and USERSTATE events as well, not just PRIVMSG.
Include the follow date as a Unix timestamp or other duration of time as a non-zero value for the "follower" tag, to allow for rules like "must be following for 20 minutes" or "must have been a follower for 3 days".RealityRipple
supported this idea
·
-
7 votesRealityRipple
shared this idea
·
-
7 votesRealityRipple
supported this idea
·
-
21 votesRealityRipple
supported this idea
·
-
3 votesRealityRipple
shared this idea
·
-
179 votesRealityRipple
supported this idea
·
-
715 votesRealityRipple
supported this idea
·
-
6 votesRealityRipple
shared this idea
·
-
10 votes
An error occurred while saving the comment RealityRipple
commented
Adding "following=0/1" or something similar to the tags of user-triggered events (such as PRIVMSG, USERNOTICE, and USERSTATE) and a USERNOTICE on the actual follow event of a user would be an easy way to accomplish this and provide a little extra detail. It would be especially useful for bots that have "follower-only" commands. Otherwise, a time-consuming API request has to be made between the command and the response.
RealityRipple
supported this idea
·
-
23 votesRealityRipple
supported this idea
·
This also applies to the VIP status, which doubles everything regarding this issue.
I also suggest allowing these queries without the respective scopes, if and only if the user_id parameter exists and is set to the authenticated user. It would also be helpful to implement the same removal of scope for the /helix/channels/vips query and /helix/moderation/moderators API queries, for the same reason.
Without these changes, any clients that care what their own channel status is will need to be over-scoped, requiring moderation:read and channel:read:vips even if it doesn't care about those scopes. This also can lower user trust, in cases where the functionality of the project is otherwise unrelated to moderating or VIPs.
Making these changes will also bring EventSub closer in line with IRC, which can provide all this data immediately via its USERSTATE message.