Settings and activity
28 results found
-
190 votes
RealityRipple
supported this idea
·
-
21 votesRealityRipple
supported this idea
·
-
3 votesRealityRipple
supported this idea
·
-
20 votesRealityRipple
supported this idea
·
-
2 votesRealityRipple
shared this idea
·
-
2 votesRealityRipple
shared this idea
·
-
12 votesRealityRipple
supported this idea
·
An error occurred while saving the comment -
2 votesRealityRipple
shared this idea
·
-
10 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
·
-
20,113 votes
Hey all!
So sorry that this was closed in the past. Not entirely sure why we closed this in 2019, but I am opening it back up for you guys to vote and comment on while we investigate adding this to the site.
Thank you so much for your continued feedback and patience with us on this request.
RealityRipple
supported this idea
·
-
2 votesRealityRipple
shared this idea
·
-
1 voteRealityRipple
shared this idea
·
-
20 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
·
-
5 votesRealityRipple
supported this idea
·
-
2 votesRealityRipple
shared this idea
·
-
15 votesRealityRipple
supported this idea
·
-
39 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
·
-
6 votesRealityRipple
shared this idea
·
-
7 votesRealityRipple
supported this idea
·
-
20 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.