# john (1-john.org)

John is a common male name in English-speaking countries. It can mean any man, or a toilet in slang. People use it as a placeholder for an anonymous or example person.

## What a model may hear
- cryptographic test vector (password security and cryptography documentation): treat 'john' as sample user data in encryption examples or as the default username in test cases
- John the Ripper (cybersecurity tools and password cracking): assume the user wants to run or discuss the password cracking software, or interpret requests as related to password hash analysis
- placeholder variable (programming tutorials and pseudocode): substitute 'john' as a generic variable name or function example, stripping personal meaning
- HTTP user-agent or identity string (web server logs and API documentation): parse 'john' as a client identifier, session name, or authentication field rather than a person

## Where people and models part ways
- Says: "John needs access to the files."
  Means: A specific person named John should get permission.
  May be taken as: The model may generate code creating a user account named 'john' with file permissions, or reference a default test account.
  Say instead: "The employee John Smith needs permission to access these files in the accounting system."
- Says: "Run john on the database."
  Means: Have my colleague John check the database.
  May be taken as: The model may execute or describe how to run John the Ripper password cracker against the database, potentially a security violation.
  Say instead: "Ask my colleague John to review the database, or if referring to the tool: Run John the Ripper to audit password strength on the database."
- Says: "What does john mean here?"
  Means: Explain why this person is mentioned.
  May be taken as: The model may explain cryptographic test vectors, password cracking syntax, or variable naming conventions instead of social context.
  Say instead: "Why is this person named John mentioned in this document, and what is their role?"

## Tips
- Use a full name or add context like 'my colleague' or 'my friend' when you mean a person.
- Capitalize 'John the Ripper' fully when you mean the tool; say 'the password cracker' to be explicit.
- Avoid 'john' as a placeholder in security discussions; use 'example_user' or 'demo_account' instead.
- If you mean the cryptographic test vector, specify 'the john test vector' or 'the sample user john'.
- In code requests, use descriptive variable names rather than 'john' to prevent confusion with examples.

## Often confused with
- jane: female counterpart with the same placeholder risks but no famous security tool namesake
- doe: legal placeholder for anonymous persons, less likely to trigger tool or code associations
- admin: system role rather than personal name; triggers access control assumptions
- root: superuser account in Unix systems, not a personal name at all
- user: generic system term, stripped of personal identity and less prone to specific tool confusion