MOTM: July votings [CLOSED]

[LilUziVert]

Well, you are touchy about critique as no one else, but I will add smth for my own defence since I'm not a dissing hater. For almost a year I was promoting your tool here
https://www.nulled.t...machine-azatej/

Actually, I edited topic like a 3-4 days ago (would half year ago, but I forgot totally). Obviously, you will respond with no fucks given, well I wrote it not for boosting your sales but for readers so you'll get your point. Your problem is that you can't spot the difference between opinion and trash talk, but its old topic already, picked your person because you are obviously known. I said once from my point of view you ruined great tool which obviously you took as hating. And I might be wrong, but I used SNIPR once in last 6 months and obviously, it was a specific experience. No, I'm not saying its a miner, I'm not retarded, might be even my h/w fault, but surely you would insult anyone posting smth like that, as you insulted me back in a day. I'm just touchy also.  

No offence, but I cannot read that garbage, no idea what your saying.

Also, yes, you got some nice cores there, but cores != threads, Threading does NOT take cores into account, cores != threads cores != threadpools.

While yes, that CPU is higher than normal, you should instead of throwing that screenshot out making SNIPR look bad, and tell me what you did to cause it, and I can take a look.

 

Email-Checker already has a known bug where after time, it will start constantly doing an infinite while loop as the stream from the TCP Connection to the IMAP server would respond an unexpected byte, resulting in SNIPR trying to retry, while this normally works, like 99% time. Sometimes it will continue returning unexpected bytes, and not an end-stream byte (-1 byte as int32) resulting in it constantly looping on an open stream, that constantly just returns garbage and never closes the connection.

Most likely, that bug is what you hit. The reason I believe so is because of your memory, thats the usual mem that would be used by the Email-Checker.

 

lmk if im wrong

[Skyline]

No offence, but I cannot read that garbage, no idea what your saying.

Also, yes, you got some nice cores there, but cores != threads, Threading does NOT take cores into account, cores != threads cores != threadpools.

While yes, that CPU is higher than normal, you should instead of throwing that screenshot out making SNIPR look bad, and tell me what you did to cause it, and I can take a look.

 

Email-Checker already has a known bug where after time, it will start constantly doing an infinite while loop as the stream from the TCP Connection to the IMAP server would respond an unexpected byte, resulting in SNIPR trying to retry, while this normally works, like 99% time. Sometimes it will continue returning unexpected bytes, and not an end-stream byte (-1 byte as int32) resulting in it constantly looping on an open stream, that constantly just returns garbage and never closes the connection.

Most likely, that bug is what you hit. The reason I believe so is because of your memory, thats the usual mem that would be used by the Email-Checker.

 

lmk if im wrong

you're * 

[AZATEJ]

No offence, but I cannot read that garbage, no idea what your saying.

Thanks for confirming my overall point where I mentioned you first time in that thread. 

Mate its not about a fucking picture, its a meme, its about how you react like some rollercaster- from insults to explanation. My English might be a fucking garbage, but usually specific kind of people comment it, usually they lack manners that much to use it as an argument, grow the fuck up. If you cannot read it then don't read it.

 

It is really simple and it is how H1Z1 and other games went downhill - Updates that were better if they were not there. 

Its same scenario with child which got too much care of their parents, metaphoric as fuck.

[Psych0path]

Good luck, I am new so I do not know who to pick

vote for @AZATEJ ty

[Hyunv]

Actually I'm a bot from Azatej so I'll vote for him thanks.

[bleach]

Please congratulate @AZATEJ !