Lovely :[]

I am very excited for offline mode.  This needs to be top priority. Once people realize that taking down the site no longer takes down the bots, the attacks will die out.

 

Also, when the bot is running and trying to connect to the host, there is massive CPU usage. Perhaps it's a bug?

Edited August 7, 201312 yr by dreamliner

Sounds great, keep it up guys.

Now let's hope OsBot won't suffer the same fate that ruined wBot!

thanks cant wait for offline mode

Just wondering how you are going to deal with non-vip user opens multiple clients?

 

Waiting for offline mode! It will big step forward for osbot client!

 

 

(Are you going get even near making client lighter? It seems to be currently pretty heave for cpu)

cant wait for the new host thanks for updating us

This is great

gkGoodjob keep up the gooxworkkk

can a admin help me out i changeded pass and more likely fuckedup now i dont get a email to recover

 

 

Good work looking forward to the revisions 

I am very excited for offline mode.  This needs to be top priority. Once people realize that taking down the site no longer takes down the bots, the attacks will die out.

 

Also, when the bot is running and trying to connect to the host, there is massive CPU usage. Perhaps it's a bug?

It's not a bug it's the client which is trying to connect to the server every 5 seconds.

I am very excited for offline mode.  This needs to be top priority. Once people realize that taking down the site no longer takes down the bots, the attacks will die out.

 

Also, when the bot is running and trying to connect to the host, there is massive CPU usage. Perhaps it's a bug?

It's not a bug it's the client which is trying to connect to the server every 5 seconds.

I can refresh my chrome browser to 0.0.0.0 every 5 seconds and it won't destroy my CPU.

 

 

I am very excited for offline mode.  This needs to be top priority. Once people realize that taking down the site no longer takes down the bots, the attacks will die out.

 

Also, when the bot is running and trying to connect to the host, there is massive CPU usage. Perhaps it's a bug?

It's not a bug it's the client which is trying to connect to the server every 5 seconds.

 

I can refresh my chrome browser to 0.0.0.0 every 5 seconds and it won't destroy my CPU.

 

 

You'll never understand what I mean. 

You'll never understand what I mean.

And what he could have understood wrong? Client reconnects every 5 seconds, but problem is (=bug) that how much processing client does for it...

Edited August 8, 201312 yr by Smg24

sweeet