So, beneath some genuine sounding apologies, we find another attempt to find out our real identities. Despite the polite tone of the message, its contents can be translated to: "We asked you nicely before and you refused, so if you want us to retract our FUD post about your miner, you must reveal your identity to me." Well, we don't react well to threats, even polite ones
I don't blame you for wanting to keep your identity a secret, and good job standing your ground. I wouldn't have reacted to Nicehash's message any differently.
However, there were a few days this past week where your clients were scrambling trying to find your software, and since this thread is constant attack by malware shilling sockpuppets, this episode put your clients in a high-risk situation. Many didn't know whether the software they found was the right version, and there was also suspicion that your Mega and Bitcointalk.org accounts were hacked, or (god forbid,) you went rogue yourself.
Checksums are great, but they don't guarantee that your accounts haven't been hacked, or the software and checksums weren't replaced by the hacker. To help the members of this forum (and the folks at Github will appreciate it also) I suggest you create
and stake a PGP key that you use to sign the binaries and/or the checksums. That gives the community a second factor for authentication. If this kind of thing happens in the future we can use the PGP to authenticate your checksums or the binaries and avoid this kind of drama.