After not being able to access project maker for 4 days, it has finally opened. It took 15 minutes to do so but at least it’s a start. All the error logs say but one thing, cannot get
I have never in my life ever seen a piece of software phone home as much as Zennoposter does. Is it absolutely necessary to the functioning of the software, like it needing some sort of some critical on-the-fly computation that only the power of your super powered sever stack can provide or some mission critical information that somehow justifies such an all pervading ownership that it makes me want for the gentler ravages of some genuine botnet malware.
Does it really need to phone home so often?
I don’t know if over the last few days it’s been your sever with problems or my shitty proxies or if my vpn is getting tired of connecting to your site, but if this happens during the middle of a job:
2015-04-23 00:44:45.1522|WARN|ZennoLab.LogLibrary.InternalError|Error occured in module ""Message: "Lost connection with authorization server"
2015-04-23 00:44:56.1581|INFO|ZennoLab.LogLibrary.InternalError|Event in module ""Message: "Unable to reconnect to the authorization server"
why must it go and screw it all up just because it can’t talk to mommy? It’s not right. It’s not good being stuck on the end of it not good business practice –
The language of the criticalErrors log indicates that it was your servers:
2015-04-21 05:39:29.9855|ERROR|CurrentDomain UnhandledException
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 148.251.48.178:443
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
I know that it’s generic and I’ll probably never know and really, I don’t care because it’s not the point. Your customers should never be stopped from working with your software because of some misguided need to protect some code (what % of the is yours btw?).
Your software inspired me to learn about decompiling. Want to guess what my first project was? But seriously think about it, your software, which is not decompiling software, inspired one of your customers to learn how to decompile software. …just so that they could use it.
Don’t get me wrong, it’s some great software but for some reason you decided to go against the flow of modern software maker thinking by introducing bugs.
I have never in my life ever seen a piece of software phone home as much as Zennoposter does. Is it absolutely necessary to the functioning of the software, like it needing some sort of some critical on-the-fly computation that only the power of your super powered sever stack can provide or some mission critical information that somehow justifies such an all pervading ownership that it makes me want for the gentler ravages of some genuine botnet malware.
Does it really need to phone home so often?
I don’t know if over the last few days it’s been your sever with problems or my shitty proxies or if my vpn is getting tired of connecting to your site, but if this happens during the middle of a job:
2015-04-23 00:44:45.1522|WARN|ZennoLab.LogLibrary.InternalError|Error occured in module ""Message: "Lost connection with authorization server"
2015-04-23 00:44:56.1581|INFO|ZennoLab.LogLibrary.InternalError|Event in module ""Message: "Unable to reconnect to the authorization server"
why must it go and screw it all up just because it can’t talk to mommy? It’s not right. It’s not good being stuck on the end of it not good business practice –
The language of the criticalErrors log indicates that it was your servers:
2015-04-21 05:39:29.9855|ERROR|CurrentDomain UnhandledException
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 148.251.48.178:443
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
I know that it’s generic and I’ll probably never know and really, I don’t care because it’s not the point. Your customers should never be stopped from working with your software because of some misguided need to protect some code (what % of the is yours btw?).
Your software inspired me to learn about decompiling. Want to guess what my first project was? But seriously think about it, your software, which is not decompiling software, inspired one of your customers to learn how to decompile software. …just so that they could use it.
Don’t get me wrong, it’s some great software but for some reason you decided to go against the flow of modern software maker thinking by introducing bugs.