Hey all – thank you so much for all of your feedback around this change. We understand that this was a feature that many of you used in various situations, including the ability for Moderators to highlight or distinguish messages in Chat, and we agree that is important. We are listening to your ideas and feedback in this area – stay tuned for updates!
To provide context as to why we’ve made the decision to remove the original functionality of the /me command, we wanted to address the way this feature was being used to perpetrate abuse against members of our community. While we recognize this change is frustrating for some, the safety of our community remains our top priority.
An error occurred while saving the commentDinip commented
I was using this route to check the host list of active channels to give "tickets/entries" based on the amount of time that a user has their host in that specific channel... Now that this route is gone, I can only give those on the host event received in chat which is also a pain to access since I need to launch a chat instance for each user because the event is only emitted to the streamer...
The endpoint could be moved to helix, even with token "protection" like the subs route...