Idiot code
This redirect may meet Wikipedia's criteria for speedy deletion as a page that is patent nonsense, consisting purely of incoherent text or gibberish with no meaningful content or history. This does not include poor writing, coherent vandalism and hoaxes (G3), coherent material not written in English, badly translated material, etc. This criterion also does not apply to pages in the user namespace. See CSD G1.
If this redirect does not meet the criteria for speedy deletion, or you intend to fix it, please remove this notice, but do not remove this notice from pages that you have created yourself. If you created this page and you disagree with the given reason for deletion, you can click the button below and leave a message explaining why you believe it should not be deleted. You can also visit the talk page to check if you have received a response to your message. Note that this redirect may be deleted at any time if it unquestionably meets the speedy deletion criteria, or if an explanation posted to the talk page is found to be insufficient.
Note to administrators: this redirect has content on its talk page which should be checked before deletion. Administrators: check links, talk, history (last), and logs before deletion. Consider checking Google.This page was last edited by Dicklyon (contribs | logs) at 07:28, 24 January 2008 (UTC) (17 years ago) |
 |
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.