Sample frontend performance stats to 1%.
Set GA sample rate through config

reddit uses Google Analytics[0] as a tool to track events on the reddit.com
website, which allows for gathering page load and user event data while
keeping users anonymized. However, with the high volume[1] of traffic
that reddit recieves, the data collection limit[2]-- even with a premium
account-- is often surpassed by a large volume.

Wikpedia states[3] "... sampling is concerned with the selection of a
subset of individuals from within a statistical population to estimate
characteristics of the whole population." We can, using this principle,
send a small portion of user events to Google Analytics collection
endpoints rather than sending the entire data set and achieve a
reasonable approximation of global user behavior without exceeding
reasonable data usage limits as defined by Google Analaytics.

In order to achieve this, the Google Analytics javascript library
provides a method to set a sampling rate[4], a percentage from 1-100.
By calling:

```
_gaq.push(['_setSampleRate', '80']);
```

One can set the sample rate to 80% of users. In reddit's case, I suggest
a default sampling rate of 50%. Here, I have added the `_setSampleRate`
properties to the `_gaq` object created within `utils.html`. It gets its
value from the config, which allows for easy value changes and avoids
using a 'magic value' set multiple places in the code.

[0] - https://www.reddit.com/help/privacypolicy#p_22
[1] - https://www.reddit.com/r/AskReddit/about/traffic
[2] - https://support.google.com/analytics/answer/1070983?hl=en
[3] - http://en.wikipedia.org/wiki/Sampling_(statistics)
[4] -
https://developers.google.com/analytics/devguides/collection/gajs/methods/gaJSApiBasicConfiguration#_gat.GA_Tracker_._setSampleRate
Send all RUM timings to hivemind instead of /web/timings

Use the new hivemind stats server to collect data rather than
/web/timings, so all the data collection goes to once place.
Move stats collection sample rate to config

This way, we can update the rate in one place.
Sidebar: always link to moderator info

[A user suggestion][0] from /u/Motha_Effin_Kitty_Yo.

Aside from the url hacking, the only previous way to get to this page was to
click the more link for subreddits with "too many" mods.  Since this
information is public, we might as well make it easily available no matter how
many mods there are.

[0]: https://www.reddit.com/r/ideasfortheadmins/comments/2mqmj2/provide_a_view_about_link_in_moderator_box_even/
Improve moderator info page title

Since this page is accessible to non-mods, it doesn't make much sense to title
it "edit moderators" - people who can't edit anything can see it.

Also, while I was messing around in here, I noticed the titles we put on these
pages are awfully generic.  I didn't want to touch too many things, so we're
only adding a subreddit suffix to this page.
graphite: Don't send counters for timers to tallier.

This extra data does tell us how many timer samples were averaged out
before being reported to tallier, but in general it causes us confusion
and takes up space in packets and we've never really needed it.
Swap contact tel for email.
Determine if a comment is gildable from can_save

Previously this was being done with can_reply, but that can make
archived comments, comments in subreddits the user is banned from, etc.
ungildable. Now that comment-saving is available to all users (and not
just ones with gold like it was at the time), can_save is a better
indicator to use.
Fix autofocus

Only 1 `autofocus` attribute is allowed per the spec.  Having two
was causing it to randomly choose between the two username fields.
Since we handle this manually in the modal I've removed it there.
On /login we only want it on the login field.
Fix https domain for beta
Allow modal to be closed with esc
Add subscribe link to verify when coming from /promoted
Increase minimum password length to 6
vote: Track valid_thing and valid_user rates in Graphite.

This will get us a baseline for each of these so that when I refactor
this code I can feel more confident I haven't changed things.
stylesheets: Remove dynamic stylesheet serving.

Since the introduction of the media providers and the default
installation of the filesystem media provider, it's no longer necessary
for local / non-AWS installs to use dynamically served stylesheets.

This patch removes that option to reduce complexity in the stylesheet
flows.
media: Take advantage of HTTP & HTTPS media being on the same domain.

Since we have an HTTPS-capable CDN in front of our S3 static domains
now, it's far faster for clients to use the CDN on HTTPS as well rather
than going straight to (high-latency) S3.

This patch makes it so that we continue to store URLs with explicit HTTP
schemes but instead of conditionally converting to HTTPS, we render
protocol-relative URLs. This should be safe for systems using the
filesystem media provider as we've installed an SSL cert there all
along.
stylesheets: Add protocol-relative stylesheets.

Now that we have protocol-relative media objects, there's no need to
maintain HTTP and HTTPS variants of subreddit stylesheets. Instead,
we'll start writing all new stylesheets with protocol-relative image
URLs. Old subreddits will continue to use their protocol-specific
stylesheets for now until new stylesheets are uploaded or existing ones
migrated.
Don't treat gettext's output as HTML: JS edition

We don't trust gettext's output, so we can't treat its output as raw HTML.
HTTPSify emailed links containing secret tokens

Thanks to @edent for the report!