No source, no privacy policy. Supporting new protocols/formats/stack requires one 'to talk about it' with them.
No source, no privacy policy. Supporting new protocols/formats/stack requires one 'to talk about it' with them.
But no, you don't have to keep tabs on it, because you don't have to use this tool. If you do choose to use this tool, you can play the probabilities and more than likely be fine.
Except they get fixed without someone threatening to disclose them.
> If you do just a bit of research you can find who I am, and where I live.
What do you expect me to do with that information? I'm being honest: I don't really get what that information would do for me if I found your code was doing something wrong, unless I thought it was worth my time to file a lawsuit.
> Code is not obfuscated.
We have very different definitions of this term.
> This is the best I can do.
Examples exist which show this statement to be wrong.
I think that the parent was more concerned with the lack of 64-bit (x64/AMD64/x86_64) support. The parent also takes issue with the usage of x32 to refer to 32-bit.