You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand the difference between Streamlink and Streamlink Twitch GUI.
This is a feature request and I have read the contribution guidelines.
Description
One of my biggest uses of streamlink twitch gui is finding cool streams and just watching them in the background, usually speedruns for games I enjoy. I got in the habit as of recent of following each game I want to check out, and with the followed games tab, I used to be able to quickly check each of these for a speedrun.
I know it is now impossible to grab a list of followed games due to twitch's api, though, I'd assume its possible to build a local list of favorited games to check out and go back to, without needing to search for the game again or scroll through the large list of games.
This would not need to pull anything from twitch's API except for the already used information about the game: How many are streaming, how many viewers, icon, and all the streams of that game. Basically just a local list of favorites that has icons and all, fetching what it can from the servers.
This would end up making it much easier to browse through games/categories you want to see, without all the clutter of ones that aren't important.
Additional comments, screenshots, etc.
The text was updated successfully, but these errors were encountered:
This kind of feature does only work if the Twitch API supports individual game queries (by ID or name), so that the data of all locally stored fav games (game image, viewers data, etc) can be read.
The kraken v5 API unfortunately does not support this and only top games ordered by overall viewer count can be requested, which is useless in this case. The new helix API however does support this and offers an endpoint where up to 100 games can be queried in one request, by ID or by name. The new helix API namespace is not being used here yet though, as it has a lot of other restrictions and would first have to be implemented here.
I'm also usually against these kinds of feature requests, especially because storing data locally of a similar or even equal feature which Twitch provides on their website is confusing to the user who doesn't know that the data is not linked to their Twitch account. Also, querying individual records (games) instead of getting a list of records (games) from Twitch falls into the same category as local filtering, but since you can request up to 100 games in one API call, it's not that terribly inefficient. The same method is already being used for getting the list of live streams of a Twitch team.
But yeah, considering the current situation, an implementation of a local favorite game feature is quite reasonable. I will think about it, but don't expect me to start working on this any time soon.
Feature request
Description
One of my biggest uses of streamlink twitch gui is finding cool streams and just watching them in the background, usually speedruns for games I enjoy. I got in the habit as of recent of following each game I want to check out, and with the followed games tab, I used to be able to quickly check each of these for a speedrun.
I know it is now impossible to grab a list of followed games due to twitch's api, though, I'd assume its possible to build a local list of favorited games to check out and go back to, without needing to search for the game again or scroll through the large list of games.
This would not need to pull anything from twitch's API except for the already used information about the game: How many are streaming, how many viewers, icon, and all the streams of that game. Basically just a local list of favorites that has icons and all, fetching what it can from the servers.
This would end up making it much easier to browse through games/categories you want to see, without all the clutter of ones that aren't important.
Additional comments, screenshots, etc.
The text was updated successfully, but these errors were encountered: