Indexing Reference Guide
This page provides examples of both acceptable and unacceptable @handle name registration
Simple Registration
Scenario | Inscription | Valid | Rule |
---|---|---|---|
Default | @handle | Yes | Standard |
Capitalization | @Handle | Yes | All caps will be indexed lowercase |
Space in front | @handle | No | First character must be an @ |
Space in back | @handle | Yes | Everything after a space is ignored |
Newline in front | @handle | No | First character must be an @ |
Newline in back | @handle | Yes | Everything after a space is ignored |
Space in name | @han dle | No | Everything after a space is ignored |
Accepted symbols | @hand-le_ | Yes | Letters, numbers, underscores (_), and hyphen (-) only |
Unaccepted symbols | @handle! | No | Letters, numbers, underscores (_), and hyphen (-) only |
Emoji | @handle🙂 | No | Letters, numbers, underscores (_), and hyphen (-) only |
Advanced Registration
All simple registration rules apply with some JSON-specific adjustments:
Scenario | inscription | Valid? | Rule |
---|---|---|---|
Default | { "p": "@handles", "op": "data", "name": "@handle" } | Yes | Valid JSON5 |
Trailing commas | { "p": "@handles", "op": "data", "name": "@handle", } | Yes | Valid JSON5 |
Newline OUTSIDE of keys or values | { "p": "@handles", "op": "data", "name": "@handle" } | Yes | Valid JSON5 |
Newline INSIDE of keys or values | { "p": "@handles", "op": "data", "name": "@handle " } | No | Invalid JSON5 |
Last updated