>>47528874Thanks, the biggest problem is getting the data itself though.
Pulling from TwitchTracker only allows 25 ids in a row before it starts to cut access.
If you move too fast, it'll restrict your ip and even if you don't, there's a lot of corrupted data.
From the 37,049 streams i pulled for instance, around 7k were corrupted and needed a 2nd, 3rd pull, and manual fixing after that, especially where it just couldn't get peaks that weren't "d" or empty.
