Allow the source of a user script to be accessed without incrementing the install count.
Loosen up the death grip on #19 with `switch`

* `switch` is designed to handle multiple logic cases since ES3 and forward.
* There is no requirement for the prior restrictions in any of the styleguides currently mentioned
* Noted that curly braces can be used for code folding, otherwise they are mostly useless imho and as far as I know
* Added `expressionNth` to the sample with a simple fall through.
* GMs requirement of adding a comment for fallthroughs seems rather tautological since this is how the statement has been in the C family of languages and all of its derivatives for many decades.
Go with GM styled comment requirement of `// fallthrough` syntax instead of curly braces.

* Apply some more of the styleguide to the STYLEGUIDE.md
* Clarify in notation that sometimes a `switch` may not always be the best option for readabilty in some cases.
* Leaving the choice of curly braces up to each contributor for the time being. Code folding is nice but ususally `switch` isn't that complex enough to need that.

Applies to #245 and #19
More symmetry with the styleguide of indent with 2 spaces in the STYLEGUIDE.md examples

* Applies to #19 and pushed in #245
Missed symmetry on 2 indention spaced example.

* Applies to #19 and pushed in #245
Add recommendation for `setTimeout` from #208

* Almost verbatim copied from sizzle

Applies to #245 and #19 and recomendend at https://github.com/OpenUserJs/OpenUserJS.org/issues/208#issuecomment-47728667
Clarify server side usage of node.js specific API

Applies to #208 and implemented in #245
Add additional functionality for `parseMeta`

* Some adherance to STYLEGUIDE.md
* Some routine optimization
* Additional parameter for `parseMeta` to not clobber a parsed metadata block e.g. not normalized
* Default to normalized meta with existing stored Object on S3
* Add normalized flag to all existing `parseMeta` calls

Applies to #232 and eventually #243 and #53
Add other upmixes for keys that have way too many synonyms

* Alphabetize final target
* Alphabetize uniques
* Add `@icon` to uniques... this should prevent multiple icon values from being downloaded to save user bandwidth

Applies to #232
Show notice about preferred support if `@supportURL` exists

* Use a "Well done" notice so we don't scare people off.
* Make this dismissable... some chatter on USO had ppl complaining about those not being dismissable

Applies to #239
Copy and rereferenced all downloadable fonts to pro/dev

* Leaving fontawesome CSS uncompressed for the time being... this is better to find and fix any bugs on a specific line rather than all one one single line.
* Dereferenced googleusercontent font and added to bootstrap.css

Applies to #227
Slight message change to cancel some possible confusion

Applies to #239
Fix url to full percent encoding when replying.

* Don't know why this isn't done by default with `encodeURI` or `encodeURIComponent` but needs to be done otherwise we end up with `Re#comment-146b1dd0263):` when a script name and/or discussion has parens in it.
#241 "Search user's script" -> "Search jerome's scripts"
Implement general Fx Open Search for the site

* Upcoming Fx 33 has this on about:newtab... so best to get us in there early... does work with earlier versions too.
Drop off the .org portion to simplify the text a bit on what is shown

* Easily undone if needed but we, and just about everyone I've seen usually refer to ourselves as OUJS not OUJSO.

Applies to #254
Fix undeclared variable in strict mode

Applies to #232
Throw in strict mode into every part in OUJS

* Moved some code around to accomodate this
* Fix undefined variables including one from #246 if this gets merged in first
Make a note of always using strict in our code

Applies to #255
Change generic node.js support to exact and above for strict mode

* https://www.npmjs.org/doc/json.html#engines
* http://stackoverflow.com/questions/9031888/any-way-to-force-strict-mode-in-node

Applies to #255