Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
First is giving each livestream its own one-time unique stream ID instead of simply using a is_live true/false flag. This would help recognize a new stream if there was downtime for a notification bot and it missed a streamer's offline time before they went live again.
The second is providing the streamer's user data as part of the channel data. Currently, to grab all relevant data, two API calls need to be made: one to get the channel data and one to get the profile picture and display name. The user data could be coupled into the channel data so only one API call needs to be made to get all the needed information about a channel and the streamer behind it.
Describe alternatives you've considered
I haven't thought of any other alternatives.
Additional context
None.
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
First is giving each livestream its own one-time unique stream ID instead of simply using a is_live true/false flag. This would help recognize a new stream if there was downtime for a notification bot and it missed a streamer's offline time before they went live again.
The second is providing the streamer's user data as part of the channel data. Currently, to grab all relevant data, two API calls need to be made: one to get the channel data and one to get the profile picture and display name. The user data could be coupled into the channel data so only one API call needs to be made to get all the needed information about a channel and the streamer behind it.
Describe alternatives you've considered
I haven't thought of any other alternatives.
Additional context
None.