My experience building a YT viewer bot

Despite being told I was wasting my time I gave it a try anyway. After a lot of trail and error I ended up with a pretty decent bot that by all means operated how I wanted it to.

The result is a multi threaded bot that changes proxies, spins user agents, spins reffers, clears all cookies including flash, has random viewing times all upon each view.

It works perfectly besides the fact that it doesn't actually generate views. I tested it many times with 100's of private proxies and it simply doesn't work.

After looking into it a little deeper the bot would need to be able to spoof just about everything in order to work Mac address, screen resolutions, OS and so much more. After all that you still have to find a work around for the wireless location tracking big G uses.

I've settled on this bot being well beyond my capabilites. All that being said, its pretty obvious why there aren't any YT viewer bots around that actually work.

Good info. Im sure you gained some good knowledge on your trial.

are you just trying to run it via webbrowser control?

phatzilla said:

are you just trying to run it via webbrowser control?

Click to expand...

Yes...

Hey, i found the following on youlikehits

YouTube caches all views. This means that views from YouLikeHits can take up to 72 hours to show up on your video. YouTube also has a tricky algorithm that will sometimes block chunks of views which may make the numbers on YLH different than on YouTube.

Click to expand...

Did you check, whether your views increased after 72 hours of running the bot.

Actually I don't believe I checked that far out. I was pretty much waiting 48hours. I may give it another kick and see..

man you can find a way soon.. just don't do what a bot maker usually does.. since yt and google knows what these normal people do.. I'm not a programmer so i don't know what you do.. but google hire tons of programmer to patch these holes..

if you look on fiverr there are some gigs that sell thousands of views in a short span of time and they even delivers dozens of orders each day. And this can only be done by using a bot..

as what everyone says.. always think outside the box.. and never give up.. success will come after solving a lot of problems..

Good luck..

did u wait to run the video some seconds before pass to other proxy?

You should wait approx. 3 days.. I've coded one in the past (3 or 4 weeks ago) and didn't even change user agents or referer. And I didn't even have any private proxies (they were public). And it really worked. Of course many proxies were blacklisted, but I could see the views growing (had less than 20 views at the beginning, after botting over 120).

Don't give up dude. It's no magic

/edit
forget to say: my bot is using sockets, no browser bullshit.

Since I really like the spirit and motivation of OP in this thread, that the infamous .net webcontrol is NOT the thing ever created in the history of computing to simulate a web browser.. Chances are that all you hear around is not exactly true about what does or does not work.. G' luck!

In all fairness mate, that sort of bot will struggle to generate views... You need to be doing http requests to YouTube's video stat server (You also need to generate a few things in the URL or scrape them for each view). So basically you need to sniff the requests being sent when watching a video and emulate them as closely as you can.

Did you test your bot with unlisted/listed, aged/new videos and also with videos that have over/under 300 and 1000 views?
You should test your bot with atleast 20 or more different videos. Even if testing sucks because you have to wait to see the results.

I'm sure when you spend enough time and have emulated the requests closely as you can then you probably have done 80% of the work, the other 20% are just fine tuning.

It's probably easier as you might think and dumber persons have successful build a yt view bot before you, the only difference is that they haven't quit until it worked

I wish you good luck

Using a webbrowser sucks. You need to get into sockets and http requests.