Return to Question

edit: I'm still waiting on an answer or resolution to this. I would like to file my résumé on Stack Overflow Careers, but the reverse engineering clause is currently preventing me from doing so (the other issues are not stopping me, but they do make me feel a bit uncomfortable). It's especially troubling because, as pointed out in the comments, that clause is forbidding the exact same thing that Stack Overflow itself did in order to enhance the WMD editor that it uses.

edit: I'm still waiting on an answer or resolution to this. I would like to file my résumé on Stack Overflow Careers, but the reverse engineering clause is currently preventing me from doing so (the other issues are not stopping me, but they do make me feel a bit uncomfortable). It's especially troubling because, as pointed out in the comments, that clause is forbidding the exact same thing that Stack Overflow itself did in order to enhance the WMD editor that it uses.

This seems rather excessive, especially for a programmer-oriented site like Stack Overflow. When answer questions on Stack Overflow, I sometimes de-minify Stack Overflow's own JavaScript or CSS in order to explain how something works with reference to Stack Overflow itself. According to this, I am not allowed to de-minify any of Stack Overflow Career's code in order to inspect how it works.

(I'm not sure how to tag this question; it's not exactly a request for a feature, nor is it exactly a bug, so I've marked it as discussion, but I would like to see this actually fixed)

This seems rather excessive, especially for a programmer-oriented site like Stack Overflow. When I answer questions on Stack Overflow, I sometimes de-minify Stack Overflow's own JavaScript or CSS in order to explain how something works with reference to Stack Overflow itself. According to this, I am not allowed to de-minify any of Stack Overflow Career's code in order to inspect how it works.

(I'm not sure how to tag this question; it's not exactly a request for a feature, nor is it exactly a bug, so I've marked it as discussion, but I would like to see this actually fixed.)