Okay, first of all, I have no idea if this bot is even possible to make, I know nothing about coding. I would love to pay a coder to make this bot for me, but I have zero dollars to invest in this, so I may as well throw it out there for the forum's sake. That being said, let me get started on explaining the idea. I have read through many of the newer posts on the frozen views subject, and this is what I've come up with. So for this bot, the idea would be exactly the same as Tube Increaser, just more complicated, ie. simulating real traffic so YouTube is none the wiser. All right, one feature at a time. 1. Proxies, this would probably be the most complicated part of it. To whoever decides to make this bot, you would need to provide proxies to the people who buy the product as Tube Increaser does, except you would have the consumers give you an e-mail address (either their main e-mail or a throw-away, their choice) to send unique proxies to daily. I mean a lot of them, since in this idea each proxy will only be used a few times each, because it appears that YouTube is freezing the views when one IP address views the same video many times in a short period of time. You would need to make it possible to set the number of times one proxy could view the video, a variable of two numbers, between 1 and 8 let's say. For example, they open the program, load in their proxies, and then they get to enter 2 numbers in 2 blank fields, the first is the minimum number of views one proxy could give a video, an the second being maximum. So if they decide to set it to "1-8", I imagine that would work with the new system. Also, it would need to pick a random proxy out of the list for each individual view, not the same one over and over again, and then the next. The bot would just need to randomly pick one proxy in the list, pick a number between the variable numbers for that proxy, give the video a view, and record all of this information, then move to another proxy. Now obviously you don't want the proxies to just go through the list and come back to the first and just keep going in the same order, so you'd need it to be able to pick the same proxy again at random, even if it has been used and others in the list haven't. Once a proxy has reached it's view threshold, it would be removed from the list by the bot. 2. Another thing you would need to set as a variable number is the time it spends watching the video, and also how many proxies would be in use at one time on that video. So another example, two blank fields, the first is the minimum percentage of the video the proxy would need to watch, the second is maximum, which you should always set for 100%. So in that case you could even make the second number invariable, and keep it at 100%. And then with the number of proxies in use at one time you would have two more variable boxes, the first being the minimum number of proxies watching the video, the second being the maximum. You could set these two as low or as high as you want, depending on your connection. That really about wraps up my theory, if anyone has ideas on improving it, reply to this, let's get this going. Also, if you make this program based on the ideas I've presented here and it does end up working, don't be a dick, let me have a copy for free. One last note I think is important to add, I noticed that if you click on a video from someone's channel or the related videos section on the right, it adds to the end of the url "&feature=channel_page" or "&feature=related" respectively, so if you do use a bot, make sure you remove everything after the video ID in the url. If you don't understand why, it's because it would look bad if all of the views were coming from related videos or your channel, as this is extremely unlikely to happen authentically.