Content Warning
Welcome to Nasty Nomenclature —a site dedicated to exploring coding naming conventions with adult-oriented humor and imagery.
This site contains:
- 🔞 Adult-oriented content and imagery
- 😏 Sexual humor and innuendo
- 💪 Images of partially nude male figures
- 🔥 Mature themes and suggestive language
This site is intended for adults only. If you are offended by mature content or adult humor, we recommend you leave now.
The Exchange Protocol
When two systems want to... interface... they need to agree on how to touch each other. Here are the standards for a safe and pleasurable data exchange.
JSON Bodies
The payload. The meat. When sending a JSON body, most modern APIs prefer the gentle curves of camelCase .
*Unless you're talking to Python or Ruby backends, then they might want the long snake.
URL Parameters
The address. How you find the spot. URLs are case-insensitive, so keep it lowercase. Use kebab-case or snake_case .
*Never use camelCase here. Some servers convert everything to lowercase, and your hump will get flattened.
HTTP Headers
The foreplay. Setting the mood before the request. The standard here is Train-Case (or Kebab-Pascal).
X-Auth-Token: 12345
*Capitalize the first letter of each word. It shows respect.