[Case Study] Ubot Studio !

looking forward to this as well.. would save me the time of programming some of these sites
 
Cool, seems like I might have to take a few days off from coding this bot while I look for a new place.

Regards.
 
wanted to check out how this is going. . i was interested in coding my own ubot for some of the web 2.0's . . what version you using? I have a love/hate relationship with it, but it has made its money back a number of times, so i can't hate it that much.
 
Hehe... This is actually a very simple bot to make and by making it even simpler than you currently are, it becomes extremely light weight and more dynamic.

I was creating something like this for a while until I came to the conclusion that UBot is unable to load data to a drop down at any other point aside from startup. I had it running, working and all.. But there was just one point that I could not get past the lack of a dropdown.

1. Scrape the page for all form fields... Add their "name" attribute to a list.
2. Setup predefined content types (name, email, etc.) and allow the user to assign those types to each form field.

3. Save these associations to a text file in a unique format that you can use UBot/RegEx to separate the data.

4. Have a part of the program that READS these associations and takes action accordingly.

For example... Say we go to the Google homepage. We have 3 form fields (we have more, but let's pretend).. The search term, the search button and the lucky button. Say we want to search for "cheese". Then we would assign "cheese" to one of our content types and assign that content type to the text box.

I ended up with a syntax like this:

www.google.com#!#type(name="search",cheese)#!#click,(name="btnk")#!#

So all the user did was told the tool "my name is cheese.. type my name to the search box and click the button." Which translated that info to the tools syntax, then the tool has a "posting" ability, which reads the syntax....

read list item... add list to list.. (everything between #!#)
ends up with a list like this:
type(name="search",cheese)
click(name="btnK")

Then just use your flow... "if type, then TYPE to name="search", cheese.

It works for ALL commands, so you can basically create a tool that can DO ANYTHING on ANY page and is completely trainable by your end user!!

You can use navigate, click, type, captcha, etc, etc, etc.

I was also very fascinated with a tool like this from UBot......... Then I found Magic Submitter. :P
 
Hehe... This is actually a very simple bot to make and by making it even simpler than you currently are, it becomes extremely light weight and more dynamic.

I was creating something like this for a while until I came to the conclusion that UBot is unable to load data to a drop down at any other point aside from startup. I had it running, working and all.. But there was just one point that I could not get past the lack of a dropdown.

1. Scrape the page for all form fields... Add their "name" attribute to a list.
2. Setup predefined content types (name, email, etc.) and allow the user to assign those types to each form field.

3. Save these associations to a text file in a unique format that you can use UBot/RegEx to separate the data.

4. Have a part of the program that READS these associations and takes action accordingly.

For example... Say we go to the Google homepage. We have 3 form fields (we have more, but let's pretend).. The search term, the search button and the lucky button. Say we want to search for "cheese". Then we would assign "cheese" to one of our content types and assign that content type to the text box.

I ended up with a syntax like this:

www.google.com#!#type(name="search",cheese)#!#click,(name="btnk")#!#

So all the user did was told the tool "my name is cheese.. type my name to the search box and click the button." Which translated that info to the tools syntax, then the tool has a "posting" ability, which reads the syntax....

read list item... add list to list.. (everything between #!#)
ends up with a list like this:
type(name="search",cheese)
click(name="btnK")

Then just use your flow... "if type, then TYPE to name="search", cheese.

It works for ALL commands, so you can basically create a tool that can DO ANYTHING on ANY page and is completely trainable by your end user!!

You can use navigate, click, type, captcha, etc, etc, etc.

I was also very fascinated with a tool like this from UBot......... Then I found Magic Submitter. :P

That logic is actually a lot more complicated than it should be. The common form fields pretty much remain the same for every site , even the captcha types.

The easier implementation is to create one master subroutine and call it for each site than make the minor changes as needed to it for the different fields.

In the end you end up with a lot less code and an easier to maintain bot.

Magic submitter is built with the Watin core which I could use just as easy as I could magic submitter if I chose to - but then I'd still be making an actual project out of it which is what I am trying to avoid.
 
That logic is actually a lot more complicated than it should be. The common form fields pretty much remain the same for every site , even the captcha types.

The easier implementation is to create one master subroutine and call it for each site than make the minor changes as needed to it for the different fields.

In the end you end up with a lot less code and an easier to maintain bot.

Magic submitter is built with the Watin core which I could use just as easy as I could magic submitter if I chose to - but then I'd still be making an actual project out of it which is what I am trying to avoid.

Ubot actually has some selectors that do this all automatically.
Like <username field> and <password field>, it will automatically find those fields for you. There is about 25 or so of these auto fields.

I haven't played with Watin, but my guess Ubot is much easier to work with. It's amazingly fast for throwing together automation, it is just the bugs (which have been better lately) and the lack of certain key features. It also has a lot of overhead if you do anything really big. Those types of projects I would recommend C# or Delphi for anyway.
 
For what it is at it's price I think ubot is pretty great. But I've certainly had some issues with it too. Made a couple bots that I was pretty proud of though they ended not working very well for my niche.
 
Ubot actually has some selectors that do this all automatically.
Like <username field> and <password field>, it will automatically find those fields for you. There is about 25 or so of these auto fields.

I haven't played with Watin, but my guess Ubot is much easier to work with. It's amazingly fast for throwing together automation, it is just the bugs (which have been better lately) and the lack of certain key features. It also has a lot of overhead if you do anything really big. Those types of projects I would recommend C# or Delphi for anyway.

That's true, I am most likely going to try to avoid using any of those commands for now though. For some reason I can just see it causing me headaches down the road.

I agree on skipping Ubot for larger projects. You can't do much large stuff in Ubot anyhow due to it's lack of libraries right now not to mention no database support.

It looks to me like this project should work just fine though.
 
Any updates Gary? :)

Sorry for not updating this thread. My place got burglarized and I am in the process of moving right now.

Should be all settled in my new place by Monday ( fingers crossed ) , then I can get back to work on this bot.
 
Lets go opensource. You can post the ubot source here... we will learn from your source and work on more sites and post it here too. What say?
 
Last edited:
Lets go opensource. You can post the ubot source here... we will learn from your source and work on more sites and post it here too. What say?

Hi, thats a great idea - But I have to admit that I always got an N under "works well with others" in school.

End of the day I'd just rather be soley responsible for the app working correctly or not.

Sorry.
 
Hi, thats a great idea - But I have to admit that I always got an N under "works well with others" in school.

End of the day I'd just rather be soley responsible for the app working correctly or not.

Sorry.
What happened with the app?
 
Back
Top