Tone Tags Standard (0.1-alpha)
An attempt to standardize tone tags.
Tone tags are a good system, but even with the tone tag blog post the fundamental issue with abbreviated or hard-to-understand tone tags can be seen: you need that blog post to understand tone tags due the most common use of them to be just arbitrary letters.
Perfect examples:
/c = copypasta
/lu = a little upset
/nsb = not subtweeting (what does that even mean ???)
As such, only the /j (/joking) tone tag is allowed to be abbreviated like this due to its wide use.
The rest of tone tags can only use common abbreviations. I. e.
/ref (/reference)
Preferably, none at all
/sarcasm instead of /s or /sarc
Tone tags are allowed to go off-standard, but they must follow these criteria:
- Off-standard tone tag must directly describe how to interpret the text and not leave any room for doubt
- Understanding the tone tag must be no more complex than looking up a word in a dictionary (please don't use anything super complex, thanks)
It's important to note that tone tags, despite for their name, don't necessarily hint the tone of the message, but define hot the message needs to be interpreted.
[List of tone tags](#1232363747990044672 message)
Metatags
If you want to include additional information that not all people might understand, but understanding doesn't impact the interpretation of the message that much, you may use metatags, a something followed by status: /<something>:<status>.
Same shortening rules as of regular tone tags apply.
Examples:
/context:not-full (/ctx:not-full)
/irony-level:3 (/ir-lvl:3)
Metatags must always be safe to strip away.
[List of metatags](#1232363747990044672 message)