Implement Mr. Proxy

[GoogleCodeExporter]

We already (usually) connect to multiple servers per conversation. However, in 
order to help prevent perma bans, some users might want to connect to omegle 
through a proxy.

Step up, Mr. Proxy.

Original issue reported on code.google.com by darkimp...@gmail.com on 28 Feb 2012 at 8:27

[GoogleCodeExporter]

The connection to multiple Omegle servers doesn't actually help prevent the 
captcha, unfortunately - the people at Omegle seem to not be completely 
incompetent. How do you get perma ban from Omegle? (I know that they don't ban 
you for abuse.) xD I connect like 700 times a day for testing purposes, and 
while I get a shit load of captchas, I never get 'perma ban'.

Original comment by malaco...@gmail.com on 22 Mar 2012 at 6:01

[GoogleCodeExporter]

Yeah, you're right about the perma ban. That's what I initially thought was 
happening, but it turned out that my roommate was screwing around with the 
router while I was conducting some tests.

As to your point about the recaptchas, I haven't seen any evidence to suggest 
that the little trick with randomizing the server on a per stranger basis has 
any impact one way or another.

My hypothesis is that, due to the hokey load balancing mechanism employed by 
K-Brooks, the individual omegle servers are not clustered in any meaningful 
way. Therefore, it seems unlikely that they share session data. So by 
connecting to a different omegle server per stranger, I deprive K-Brooks of 
data to feed a possible heuristic to detect the application.

Speaking of heuristically detecting the application, according to a reddit feed 
I encountered, K-Brooks seems to be doing just that. In other words, the 
behavior of the application is different enough from the browser based client 
that he's able to use the application behavior as a factor in determining 
whether or not to begin a recaptcha flood.

Obviously, it's not a very dynamic heuristic since I'm able to avoid recaptchas 
in my snapshot build while only making minimal changes to the application's 
behavior.

Of course, with regards to application behavior, the browser interface (i.e. 
how the browser calls the omegle API) is going to be the gold standard. So the 
closer the application gets to approximating behaving like a web browser, the 
harder it will be for K-Brooks to definitively detect the use of the 
application. And the less likely it will be that omeglespy users will be 
subject to the recaptcha flood.

Original comment by darkimp...@gmail.com on 23 Mar 2012 at 12:44