Idiot code
This article may have been previously nominated for deletion: Wikipedia:Articles for deletion/Idiot code exists. It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Idiot code" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Idiot code|concern=The entire content of this article appears to apply to [[code]]s in general. It is unclear what an 'idiot code' is, or even whether such a thing exists at all.}} ~~~~Timestamp: 20080122222055 22:20, 22 January 2008 (UTC) Administrators: delete |
 |
An idiot code is a code whereupon the "syntax" or "rules" of communication are worked out between the parties.
Example
Any sentence where 'day' and 'night' are used means 'attack'. The location mentioned in the following sentence specifies the location to be attacked.
Message ! Tomorrow we'll head on to Rome.
De-coding
There are only two ways to break this code:
- Know what the rules are.
- See enough of the messages to work out the rules.
The problem with number 1 is that this type of information passing is set up before usage and is extremely hard to decipher as the message is "hidden in plain sight". Anybody intercepting this message probably would not even know it is a communication.
The problem with number 2 is that you would need several verified messages of this type to determine the rules of communication.
Disadvantages
The drawbacks of this type of message passing is that is it extremely limited. A codebook would be needed to effectively communicate complex information. Simple information such as "yes" or "no" can be built into phrases and have several variants. However, complex information such as "Meet a man with red hair under the Bass Bridge at 12:43 and be sure to wear a black cloak and a fedora so he recognises you" would be much harder unless you have constructed your rules to allow for this type of information to be passed.
This type of communication is akin to the hand signals used by armies in the field.