Settings and activity
29 results found
-
15 votes
nerixyz supported this idea ·
-
15 votes
nerixyz supported this idea ·
-
64 votes
nerixyz supported this idea ·
-
13 votes
nerixyz supported this idea ·
-
14 votes
We are looking into this. Thanks for the request!
nerixyz supported this idea ·
-
14 votes
nerixyz supported this idea ·
-
17 votes
We are investigating adding an EventSub subscription type for sub upgrade events.
nerixyz supported this idea ·
-
17 votes
nerixyz supported this idea ·
-
36 votes
nerixyz supported this idea ·
-
39 votes
We plan to support pinned messages in the Twitch API and EventSub.
nerixyz supported this idea ·
-
61 votes
nerixyz supported this idea ·
-
102 votes
nerixyz supported this idea ·
-
153 votes
nerixyz supported this idea ·
-
281 votes
nerixyz supported this idea ·
-
91 votes
nerixyz supported this idea ·
-
6 votes
nerixyz supported this idea ·
-
13 votes
nerixyz supported this idea ·
-
4 votes
An error occurred while saving the comment nerixyz supported this idea ·
-
3 votes
nerixyz supported this idea ·
-
19 votes
nerixyz supported this idea ·
I want to add that it's impossible to only timeout users that aren't timed out already solely through the API with a moderator token.
Right now I have to track the timeouts with PubSub and put them in redis. It would me much easier if I could check the user's status first and then issue a timeout.
I suppose in my specific case it would be sufficient if the "Ban User" endpoint included a parameter that would specify the behaviour if the user is already timed out or banned (like `no_modify` to not modify any existing timeout).