note
vladb
You are right, coming up with spoilers for most obfuscations is a tough job. Unfortunately, even with ~ 500 XP left to my sainthood, I still am not able to de-obfuscate much of the code submitted to the [Obfuscated Code] section. I guess this requires special skill and much practice, not to mention countless hours of meditation.
<br><br>
I once read an excellent post by [japhy] titled [33780|Japhy's Obfuscation Review]. I wish we had more similar posts by serious obfuscation freaks (aka gurus ;)! Although, I learnt quite a few neat tricks from [japhy], I'm still far far away from being able to tackle or come up with my own obfuscations that would be hard to break. In fact, the furthest I came to writing an obfuscation is the code you see in my signature. And, of course, it still pales in comparison to some of the obfu's you've mentioned ;/. I also didn't get much ++ votes when I submitted this code to the [Obfuscated Code] section, titled [166530|System admin the obfuscated way]. (*hint* *hint* hope you drop a few extra ++ in the bucket ;-))
<br><br>
What I think would be useful, in addition to your idea, is to have more authors of original obfuscations to submit a link somewhere in their post to a spoiler page. Then, if anyone is interested in getting to the bottom of a complex obfu, he/she may simply hit the link and follow to the spoiler page.<br><br>
<b>UPDATE: </b> added last 'suggestion' paragraph ;)
<br><br>
_____________________
<code>
$"=q;grep;;$,=q"grep";for(`find . -name ".saves*~"`){s;$/;;;/(.*-(\d+)-.*)$/;
$_=["ps -e -o pid | "," $2 | "," -v "," "];`@$_`?{print"+ $1"}:{print"- $1"}&&`rm $1`;
print$\;}
</code>
169553
169553