When you have a lot of streamers you want to farm (honestly not even that many, even 3 or 4) at the same time and they are all live around the same times the farming performance drops off pretty hard. Your high priority streams work fine, but stream number 3 or 4 wont get max farm. Its more effective to just open up all the channels in a browser with 7tv and kill the video (bandwidth lmao).
Proposed solution
Im not a super hard coder or anything, so take everything I am about to say with a large grain of salt, but maybe it would be more effective to instead of using the twitch API it just interacts with chrome (using chromedriver or something). The twitch API seems to have pretty strict rate limits, I tried to solve the bad performance by spitting the script into multiple instances but that didn't fix it (which is why I think it's just the API). Since I can open 5+ streams in browser to farm with no issues this might be more effective.
As for how to implement, like I said I'm not a big coder so I have no clue how chromedriver works or if there are better options for what I am suggesting.
Alternatives you've considered
I guess it could be possible to just optimize the API requests, but I dont know how the twitch API works either :/
Additional context
I know this is prolly a niche problem but I watch a few different streamers and would like to farm in all of them while all of them are live. Also this would make sure I farm everyone I want to while I am away at work.
rdavydov
commented
2 weeks ago
Is your feature request related to a problem?
When you have a lot of streamers you want to farm (honestly not even that many, even 3 or 4) at the same time and they are all live around the same times the farming performance drops off pretty hard. Your high priority streams work fine, but stream number 3 or 4 wont get max farm. Its more effective to just open up all the channels in a browser with 7tv and kill the video (bandwidth lmao).
Proposed solution
Im not a super hard coder or anything, so take everything I am about to say with a large grain of salt, but maybe it would be more effective to instead of using the twitch API it just interacts with chrome (using chromedriver or something). The twitch API seems to have pretty strict rate limits, I tried to solve the bad performance by spitting the script into multiple instances but that didn't fix it (which is why I think it's just the API). Since I can open 5+ streams in browser to farm with no issues this might be more effective.
As for how to implement, like I said I'm not a big coder so I have no clue how chromedriver works or if there are better options for what I am suggesting.
Alternatives you've considered
I guess it could be possible to just optimize the API requests, but I dont know how the twitch API works either :/
Additional context
I know this is prolly a niche problem but I watch a few different streamers and would like to farm in all of them while all of them are live. Also this would make sure I farm everyone I want to while I am away at work.