No it doesn't. Just any unofficial build which included my honeypot branch (which is what caused your shutdowns too by the way).
However, the honeypot was setup to show how stupid and unsecure unofficial builds are.
And instead of learning from past experiences, my branches are being pulled again with no word about the actual cause of the shutdowns from last time.
Shutdowns were purely intentional (and a documented feature of those builds - apparently unaware to the person creating those builds).
I read this thread with great amusement (like many others by the way; but also a little bit shocked) because instead of looking into the problems you people were just shouting at each other about some overclocking / overheating bullshit. This could easily have emptied your bank account in the background.. It was malicious code running on your or your parents machine - and you ran it.
Now the sane thing would have been to review all code in question and put procedures in place to prevent this.
But instead builds keep getting pushed, no reflection of what happened.
If I (or really anybody whose branches are being included in these builds..) wanted to do something bad (hint: I don't; others might), I could easily do it (I won't; others might).
Thank your providers of unofficial builds for running malicious code on your machines
It could have been something / someone far worse - like a malicious user formatting your drive, stealing your passwords / credit card information or whatever.
Note that this is entirely unrelated to my Citra contributions or official Citra.
Heck, all of the malicious code was submitted as "John Doe" who didn't even have a valid e-mail address. Nobody should have trusted this crap.
