Thank you for your explanation. 1 minute is usually not enough to determine if a streamer is really offline or has just technical difficulties (restarting OBS takes longer than 1 minute, rebooting even more). As I said, it took me a long time to make automatic hosting really relieable. As soon as the streamer goes offline, my bot checks at least 3 times (once per minute/configurable) if the Twitch API confirms the streamer to be offline. My goal is not to max out the number of hosting. My goal is to make sure that the best targets I have are hosted.
There is also another downside. Let’s say something is not working properly in a stream (e. g. music not playing) then the caster will now think about restarting the stream because he may loose all his hosts. So he rather reduces the quality of his stream than loosing most of his viewers and that may lead to worse streams.
I’m totally fine when the chat tells me that the streamer is offline, but the host should not be removed unless I want that. As I said before hosting is a user choice … so basically automatic unhosting is like removing panels from the profile as soon as a link in it is not available for some time.