Settings and activity
20 results found
-
18,372 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
·
-
18 votes
An error occurred while saving the comment RealityRipple
shared this idea
·
-
5 votesRealityRipple
supported this idea
·
-
2 votesRealityRipple
shared this idea
·
-
13 votesRealityRipple
supported this idea
·
-
34 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
·
-
5 votesRealityRipple
supported this idea
·
-
19 votesRealityRipple
supported this idea
·
-
69 votes
An error occurred while saving the comment RealityRipple
commented
Personally, I'd prefer some follower-related improvements to the IRC system, such as adding a 'follower=1'/'follower=0' tag to users' PRIVMSG, USERNOTICE.
RealityRipple
supported this idea
·
-
3 votesRealityRipple
shared this idea
·
-
154 votesRealityRipple
supported this idea
·
-
77 votesRealityRipple
supported this idea
·
-
498 votesRealityRipple
supported this idea
·
-
5 votesRealityRipple
shared this idea
·
-
169 votesRealityRipple
supported this idea
·
An error occurred while saving the comment RealityRipple
commented
This would be extremely useful for a myriad of purposes. Personally, I'd like to use it to parse tip/donation messages (payment memos) from authenticated users to be able to use them for emote-splosions (kappagens) on my home-made emote wall. As it is, I can support third-party emotes and emojis, as well as Twitch Global emotes, but the user's personal list is inaccessible without asking for "chat:read" permission and initiating a login to get the emote sets list from IRC.
Making this a public query would be ideal (allowing emote parsing of messages sent via third-party sources without requiring the user to give permission and trying to pass that permission through a third-party source [or via another token and temporary storage of the permission or the parse results]), but I understand if leaking who a user is subscribed to or how much they may have spent in a channel could be a privacy concern.
-
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
·
-
19 votesRealityRipple
supported this idea
·
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.