Hello, USERINPUT
\n \n \n```\n\n:warning: **CAUTION**: this is not the correct encoding for embedding the contents of\na `\n```\n\n:warning: **CAUTION**: you need to always put quotes around the embedded value; don't\nassume that it's a bare int/float/boolean constant!\n\n:warning: **CAUTION**: this is not the correct encoding for the entire contents of a\n`\n```\n\nThis function escapes certain characters within a JSON string. Any character\nnot matched by `/[\",\\-\\.0-9:A-Z\\[\\\\\\]_a-z{}]/` is escaped consistent with the\n[`js(value)`](#jsvalue) escaping above. Additionally, the sub-string `]]>` is\nencoded as `\\x5D\\x5D\\x3E` to prevent breaking out of CDATA context.\n\nBecause `<` and `>` are not matched characters, they get encoded as `\\x3C` and\n`\\x3E`, respectively. This prevents breaking out of a surrounding HTML\n`\n```\n\n### jsObj(value)\n\nSanitizes output for a JavaScript literal in an HTML script context.\n\n```html\n \n```\n\nThis function encodes the object with `JSON.stringify()`, then\nescapes using `json()` detailed above.\n\nFor example, with a literal object like `{username:'Albert\n\n```\n\n#### JSON is not a subset of JavaScript\n\nArticle: [JSON isn't a JavaScript\nSubset](http://timelessrepo.com/json-isnt-a-javascript-subset).\n\nJSON is _almost_ a subset of JavaScript, but for two characters: [`LINE\nSEPARATOR` U+2028](http://www.fileformat.info/info/unicode/char/2028/index.htm)\nand [`PARAGRAPH SEPARATOR`\nU+2029](http://www.fileformat.info/info/unicode/char/2029/index.htm). These\ntwo characters can't legally appear in JavaScript strings and must be escaped.\nDue to the ambiguity of these and other Unicode whitespace characters,\n`secure-filters` will backslash encode U+2028 as `\\u2028`, U+2029 as `\\u2029`,\netc.\n\n### jsAttr(value)\n\nSanitizes output for embedded HTML scripting attributes using a special\ncombination of backslash- and entity-encoding.\n\n```html\n click to activate\n \n```\n\nThe string `