Timeline for HTML5 game obfuscation
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 17, 2012 at 22:21 | comment | added | Matt Kemp | I would call it its 'base mechanic': it's really easy to steal on the web. This is why we have the speed and complexity of innovation we do. Newton, Picasso, Eliot and I'm sure more have all coined maxims around direct theft, even if nobly justified by the shoulders of giants. Shakespeare was excellent at theft. | |
| Jul 17, 2012 at 22:13 | comment | added | CobaltHex | well i wouldnt call it a really nice thing; more of a "blessing and a curse" situation | |
| Jul 17, 2012 at 12:41 | comment | added | Ricardo Souza | Just a quote from anywhere: "What a man do any other man can undo." and I add to it: "With the right intent and will, nothing is really protected." | |
| Jul 16, 2012 at 21:59 | comment | added | daemonfire300 | @Esailija the average effort it takes is not the same, except you are a trained reverse engineer/security expert/hacker/waht so ever. | |
| Jul 16, 2012 at 20:07 | comment | added | Esailija | flash and java can be decompiled, binaries can be disassembled, javascript can be deobfuscated. Your source is not protected just because you didn't write it in javascript. | |
| Jul 16, 2012 at 19:52 | history | edited | Matt Kemp | CC BY-SA 3.0 |
added 611 characters in body
|
| Jul 16, 2012 at 19:36 | history | answered | Matt Kemp | CC BY-SA 3.0 |