Any use case in which the delay of said methods undermines real-time designs around real-time chat.
Quoting my earlier post: “This method introduces unnecessary delay to the process of identifying Followers which […] can obstruct the function of more specialized bots and Extensions with features designed to effectuate Broadcaster-Viewer interactions in a “low-latency” way.”
My use case is Text-to-Speech read from chat in real-time while filtering Followers. API delay on top of stream delay is intolerable and working around a limit of 120 requests per minute on channels with millions of Followers is time-consuming. The API being necessary imposes a burden on Developer resources to store returned information that is not otherwise needed. Furthermore, the relevance of stored information is diminished when it cannot be updated in real-time to fulfill its singular real-time purpose for being requested (filtering Followers).
The elephant in the room is that Followers lack a fundamental chat tag communicating that status in real-time, which every other user group possesses. Developers with real-time designs around filtering Followers are forced to work around a method limited to 120 requests per minute.
Followers represent the Broadcaster’s core audience and can be the largest group for filtering purposes. Developers designing real-time features around chat will face hurdles filtering around this important group without a chat tag.
Should the creative potential of all Developers to design real-time user interactions around real-time user data in chat be limited to the few use cases we can cite or conceive in this thread?