Allow the source of a user script to be accessed without incrementing the install count.
Repair display of fork history on script page.
Fix CIDR

Currently GH uses the [https://api.github.com/meta](https://api.github.com/meta)

``` json
{

    "verifiable_password_authentication": true,
    "hooks": [
        "192.30.252.0/22"
    ],
    "git": [
        "192.30.252.0/22"
    ]

}
```

We currently only allow 256 hosts when the `/22` means allow 1024 hosts/broadcasts ranging from 192.30.252.0 to 192.30.255.255 from them. While we may not need this many just yet there is no guarantee that the first 256 are not in use and we might get a WebHook notice or notice from the other 75% of the missed IPs.
Merge pull request #244 from Martii/fixRe4GitHubCIDR

Fix CIDR
Update CONTRIBUTING.md

Testing out online editing of this DOC file... typo... 1 word change.
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
Short term notice of not using email addresses for the unique Username on the login page

Applies to #233
Merge pull request #251 from Martii/Issue-233noticeOfNoEmail

Short term notice of not using email addresses for the unique Username o...
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"