Seth Turin

Thanks, I really appreciate that. I built pretty much this entire version with my own two hands. After deconstructing what worked and didn’t work in 5, I went through and created 5.5, and it’s been great improving it up to 5.8.5. It's been a labor of love. And hate. And yelling at the computer at 3am, but mostly love.

Sorry guys, programmers are notoriously bad at estimating release dates, and UBot Stealth is no exception. The UBot Browser is crucial to UBot Studio, and is understandably difficult to replace. We have a term for this in the biz - we call it unit testing, or integration testing in this case. I even wrote a couple blogs on it, here and here. We do have a test suite here to make sure the commands work. Maintaining a test suite to log into specific websites would be harder to maintain, only because websites are prone to change, and the scripts would have to constantly be kept up to date.

For what it's worth, the stealth browser (still incomplete) is considerably faster than the old ubot browser. It also gives you the option of running headless, which makes it very similar to a socket-based bot in performance, only with all the ease of use of a browser bot. But kreatus is correct. 5.8.5 is an in between version that we released to solve a few issues while we continue perfecting UBot Stealth.

juicehunter is incorrect in his assertion. The cake is not a lie.

I posted about this in another thread: http://www.ubotstudio.com/forum/index.php?/topic/18162-well-they-have-definitely-been-working-on-the-browser-crash-issue/?p=112827 If you're seeing specific issues, the quickest way to get them fixed is by adding them to our tracker and letting support know. As for custom error pages, that sounds like a great feature request!

I want to state at the outset, to anyone not familiar with this particular issue, that browser crashes in UBot Studio affect mostly fringe cases of high-stress bots. To date, in the 4 or 5 years that we've been hearing about them, we have yet to have a single browser crash bug reported in our bug tracker that we could actually reproduce locally. But it's true, browsers do crash. To shed some light on what all this means, consider the following links: https://code.google.com/p/chromium/issues/list?can=2&q=crash&colspec=ID+Pri+M+Stars+ReleaseBlock+Cr+Status+Owner+Summary+OS+Modifie

wise words. feature creep kills.

Well, I'm pretty excited

Welcome to the community Steve! Let me clear up a bit about the Bot Bank. We first made it as a means for people to quickly share simple website scripts, a means of crowdsourcing. We had some early success with it, but it wasn't getting the amount of activity that we needed, so we sectioned off the website scripts and we essentially repurposed the Bot Bank to house some of UBot Studio's more advanced functionality, the UBot Extended Library. The Website section is still there and should be functional, but it's likely that many of the scripts are out of date, due to how frequently websites c

Yes, this should work as you expect.

You guys are awesome. Great answers.

I've yet to see a single problem in tumblr that can't be fixed by switching the user agent. Be careful listening to folks who focus more on problems than solutions. UBot Studio is designed to let you attack problems from 1000s of different angles. If one doesn't work, another surely will! I'm glad that the user agent fix is working for you, GreyHat!

Can you tell us which site this is?

Just out of curiosity, why sell it instead of keeping it?

Great tips! Anyone else have stuff to add? Here's mine: Get yourself set up with an affiliate program and start talking to affiliates. The right person selling your stuff can easily net you 4 or 5 figures in a single campaign.

great post. the software should do this on its own. I'm going to add an issue to the tracker for this.

This is something I'd like to add, but I can't make any statement on when. In the mean time, my favorite concept for desktop automation comes from the MIT labs, in a project called sikuli. Also, it's free! Check it out: http://www.sikuli.org/

Yes, it has become clear that this issue will need a more permanent solution. We are looking into it.

I would fill a list with all the possible choices and then use $random list item

Yeah, there's no need to argue the counting issue. In either case, thread safe is an issue and we need a better parallel processing system. So getting back to the spirit of this thread, here are my two: 1. Simplified threading system, to make thread safety a non-issue and to make thread complexity easier to manage 2. Object oriented design capabilities, to help organize large bots, but without overcomplicating the basic scripting system for beginners.

Ok, I spent a little time playing with this. This one is different than any of the examples I had seen so far. When I run the script, it does actually crash. When I drilled down into it, I can confirm that this is genuinely a thread safety issue. Now, I still want to draw a distinction between this and counting issues. Kev was correct when he said: The counting issues are just an artifact of multithreading being genuinely difficult to do correctly. The crashing issue is because lists are not thread safe. And actually, neither are variables. This is actually kind of a sticky problem to

Ah, Thank you! Quickly though, I'd like to try and explain what I think you guys are seeing with threading. Imagine a fruit bowl filled with fruit, and a bunch of hungry gorillas. In normal program flow, the gorillas stand in line, each awaiting his turn to take a piece of fruit from the bowl. If you have a zookeeper keeping count of how much fruit there is, he will have no problem doing so. Now imagine the same scenario, but instead of lining up, the gorillas may take fruit whenever they please in a free-for-all. Two gorillas might take fruit at the same time, or several seconds might pass

Server-side compiling actually serves two major functions: Makes UBot harder to crack and keeps you from having to download and install a lot more software, some of which may involve paid licenses. But anyway, we get around 1000 compiles per day, and we definitely have better things to do than mine them for secrets. Where is this grapevine and why was I not invited?! Seriously, our post-Edward dev strategy is still being formulated, and details have not been discussed outside the team. lolwut Awesomium does have some annoying issues here and there. It's built on top of the chromium pr

Honest answer: We designed the plugin api to abstract away most of the complexity of the UBot Core. We purposefully designed it so that beginning programmers could be highly productive. The UBot Core is a whole different monster. It would be like asking a masseuse (even a talented, productive masseuse) to perform open-heart surgery.

Hey guys I'm working on a nice blog post to update everyone on what's going on here at UBot HQ. But just so you're not in suspense, I'll give you the TL;DR version here. Yes, it's true, Eddie is no longer with the company. There are mixed feelings about it, but ultimately it's the right thing for us, for you, and for him. My team is working hard to find a replacement. As our community has grown over the years, so too have the technology requirements and quality standards increased since we hired Eddie 3 years ago. We are taking our time to make sure we have the right fit. In the interim,