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.

I once read an excellent post by japhy titled 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 System admin the obfuscated way. (*hint* *hint* hope you drop a few extra ++ in the bucket ;-))

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.

UPDATE: added last 'suggestion' paragraph ;)

_____________________

$"=q;grep;;$,=q"grep";for(`find . -name ".saves*~"`){s;$/;;;/(.*-(\d+)
+-.*)$/;
$_=["ps -e -o pid | "," $2 | "," -v "," "];`@$_`?{print"+ $1"}:{print"
+- $1"}&&`rm $1`;
print$\;}
[download]

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.