Creating a youtube view bot. How do I avoid detection?

Status
Not open for further replies.

uchiha.jain

Regular Member
Joined
Sep 14, 2009
Messages
295
Reaction score
84
Hi, I'm creating a youtube view bot for a client.
The current plan is to use a headless browser like Phantomjs to open the video in a few tabs and close them once the playback is complete. For each tab:
- Use a random useragent string from a list
- Use a random proxy from a list
- Change the machine's mac address

Are there other things I should take into consideration to avoid any detection by Youtube?
 
I think your on to something. But I wonder whether an adjustable delay or a randomized delay would be another thing youtube looks at. If its always the same delay, every view, might raise a flag.

How are you building this?
 
Changing the machine's MAC address seems excessive. Websites simply can't capture it.

If you're worried about one of Google's client applications (ie. Chrome) capturing this data, relaying it to their servers and somehow associating it with you - just don't install their products on the machine.

Here's a few other things you missed:
  • Clearing the cookies each time before the video is loaded
  • Whether a lot of views from only non-registered accounts eventually flags the video
I would test each element in isolation on a new video - ie. user agent, IP address, cookies - to see whether keeping it static still increases the view counts. That will help you narrow down where to focus.
 
Hey guys, sorry I haven't been on BHW for a while. Been working on another project.

@meowking: I tried varying view length from 1 sec to 2 mins. It seems Youtube counts the view regardless of play time. But eventually the video gets flagged and view count stops increasing. I'm using nodejs and selenium for bot.

@cloaking: You are right about most things. I wish I'd read your reply sooner :(.
Changing MAC address is useless, yes. Among other factors IP address seems to directly affect the view counts the most. Other factors might have more effect in flagging. I'll do some more testing.
The tool currently does the following
- Create new firefox profile for each view. So cookies and LSOs are taken care of.
- Use a random useragent
- stormproxies.com for rotating proxies

Here's what I plan to do next:
- Flash cookies are stored somewhere in Appdata. Nuke them.
- Open a referring url first and click the link to youtube video. Exit by clicking link in description or another video.
- Use some logged in accounts to add some comments and like/dislikes.
- Implement distribution of useragents.

Hopefully that should do the trick.

Thanks for the advice so far. Will keep you guys updated.
 
Hey Sohom, Sorry I missed the email notification again.
In case you are not using stormproxies already: There shouldn't be a need for API. You only have to use their ip:port proxy and they take care of rotation at their end.

I'm also parallely working on a FB bot. Currently stuck at gmail + facebook registration (both asking for phone verification as soon as account is created). I'm currently testing whether it's an issue with the browser (squeaky clean window) or with the way the forms are filled. Should give a clue on how to proceed. Will update in a few hours.
 
Hey Sohom, Sorry I missed the email notification again.
In case you are not using stormproxies already: There shouldn't be a need for API. You only have to use their ip:port proxy and they take care of rotation at their end.

I'm also parallely working on a FB bot. Currently stuck at gmail + facebook registration (both asking for phone verification as soon as account is created). I'm currently testing whether it's an issue with the browser (squeaky clean window) or with the way the forms are filled. Should give a clue on how to proceed. Will update in a few hours.

I think even if you successfully avoid phone verification as soon as account is created, Facebook will roadblock it so you won't be able to log in to that account in the future until you make a phone verification.
 
I think even if you successfully avoid phone verification as soon as account is created, Facebook will roadblock it so you won't be able to log in to that account in the future until you make a phone verification.

I faced exactly this issue when I bought some accounts for testing. It was heavily mitigated by storing cookies so you don't have to login everytime.
My current problem is how to register so that facebook/gmail don't ask for phone verification. If that works, even regular attrition shouldn't be too much of an issue since you could replace the accounts at no cost.
 
Good luck dude, sounds like you could be onto something.
 
I faced exactly this issue when I bought some accounts for testing. It was heavily mitigated by storing cookies so you don't have to login everytime.
My current problem is how to register so that facebook/gmail don't ask for phone verification. If that works, even regular attrition shouldn't be too much of an issue since you could replace the accounts at no cost.
what about creating an account on FB by using Firefox mobile useragent so it looks like you are creating an account from you phone?
 
Create individual vms, each with unique footprint.

Have each vm connect through firefox and use a proxy/vpn/etc so that you get a new ip every time.
Clear cookies/cache, or better yet use private browsing
Utilize different user agents, screen resolutions, etc so that your profiles look different
Profit
 
Hi, I'm creating a youtube view bot for a client.
The current plan is to use a headless browser like Phantomjs to open the video in a few tabs and close them once the playback is complete. For each tab:
- Use a random useragent string from a list
- Use a random proxy from a list
- Change the machine's mac address

Are there other things I should take into consideration to avoid any detection by Youtube?[/QUOTE
Hi, I'm creating a youtube view bot for a client.
The current plan is to use a headless browser like Phantomjs to open the video in a few tabs and close them once the playback is complete. For each tab:
- Use a random useragent string from a list
- Use a random proxy from a list
- Change the machine's mac address

Are there other things I should take into consideration to avoid any detection by Youtube?

Will you be releasing your app here?? I kinda want it too but I just started programming...so I can't make one
 
Clearing cookies of course/using randomized view times etc.

Also most important have the bot search for the video through youtube rather than direct.
 
Hi, I'm creating a youtube view bot for a client.
The current plan is to use a headless browser like Phantomjs to open the video in a few tabs and close them once the playback is complete. For each tab:
- Use a random useragent string from a list
- Use a random proxy from a list
- Change the machine's mac address

Are there other things I should take into consideration to avoid any detection by Youtube?

I have an awesome case study for the YT bot and I am creating something exactly the same as you are.
Number of views from a single proxy should not exceed a certain amount per 24 hours. It is a fixed amount. Yes YT is dumb.
The parameters studied and which gotta be randomized: 1. User agent, 2. Browser, 3. View duration, 4. Time between views. All should be random IN ADDITION to number of views sent per day per IP to a video, number of overall videos seen by an IP per day, etc etc etc
Let me know if you wanna discuss further via PM ? :)
 
Hey i was also looking for such bot. Pm me so that we can discuss over that.
 
Hey guys, sorry I haven't been on BHW for a while. Been working on another project.

@meowking: I tried varying view length from 1 sec to 2 mins. It seems Youtube counts the view regardless of play time. But eventually the video gets flagged and view count stops increasing. I'm using nodejs and selenium for bot.

@cloaking: You are right about most things. I wish I'd read your reply sooner :(.
Changing MAC address is useless, yes. Among other factors IP address seems to directly affect the view counts the most. Other factors might have more effect in flagging. I'll do some more testing.
The tool currently does the following
- Create new firefox profile for each view. So cookies and LSOs are taken care of.
- Use a random useragent
- stormproxies.com for rotating proxies

Here's what I plan to do next:
- Flash cookies are stored somewhere in Appdata. Nuke them.
- Open a referring url first and click the link to youtube video. Exit by clicking link in description or another video.
- Use some logged in accounts to add some comments and like/dislikes.
- Implement distribution of useragents.

Hopefully that should do the trick.

Thanks for the advice so far. Will keep you guys updated.
Very useful information. Thank you. ;)
 
Google is pretty smart with detecting bots.
Basics should be to clean your cookies everytime, random useragents and proxies.
The harder part is making the views high retention, so Google doesn't know they are from bots. To achieve this, you also need to watch the video with youtube accounts, have different view times, different redirect headers and probably also rate the video a few times.
 
Hi, I'm creating a youtube view bot for a client.
The current plan is to use a headless browser like Phantomjs to open the video in a few tabs and close them once the playback is complete. For each tab:
- Use a random useragent string from a list
- Use a random proxy from a list
- Change the machine's mac address

Are there other things I should take into consideration to avoid any detection by Youtube?
hi buddy i having website views which i want to convert into views i having a particular country visit on my site want to convert that views into views if you able to provide me this kind of service than i will able to deal you
 
Status
Not open for further replies.
Back
Top