Added Controls For The Copyright Year To user.json, A System to update users without pull requests, and a way to automatically update the server from the github repo.

Hi,

Sorry, I would have liked to make this 4 pull requests, but I don't know how.

First Pull Request:
I added the ability to set the years for the copyright in your user file, see the new README.md for more docs.

Also, I added some stuff to .htaccess and index.php to make it able to run on localhost.

---------

Second Pull Request:

Now Users Can Update their user.json without a pull request!
Simply:

*When You First Use curl -d'<user.json>' <mysubdomain>.mit-license.org, make sure you put a password property (this is now required).
*when you want to update your entry, run the same curl command, but with new data, remember to put in the same password.
*If you have the correct password, your user.json will be updated and pushed to github.
*your password is automatically hashed.

If you have already uploaded a user.json, just upload a user.json with one.

If for some reason someone needs to add a user via a pull request after merging this one, just hash their plain-text password with sha512.

---------

Third Pull Request:

You may or may not alredy have this, but I added a system so that when the reposotory is updated you can have it automatilcy update the server.

To set up:

* Upload this pull request to the server the old way
* Go to the mit-license repo
* Click "Settings" on the right hand side
* Click "Service Hooks" on the left
* Add a web url hook for `githubupdate.mit-license.org`
* Now when ever you push to github, the server will `cd /WWW/mit-license && /usr/bin/git pull origin master` then exit

---------------

Fourth Pull Request:

I replaced the 'Fork this project to get your own page that you can always link to.' with a link to web interface to that I built to add a user.json / cname with the web interface, no pull request or command line!

Thanks
Ari
For security reasons, this should be restricted to identifier-like values (possibly with dot-notation or number-index bracket access), but nothing more and special html characters or quoted values.

There's at least three separate security vulnerabilities I can think of right away:
1. MSIE ignoring content-type headers and parsing/executing responses as HTML if the first few bytes look like it.
2. Arbitrary script execution and possible disclosure of private or host variables (e.g. cookies).
3. Rosetta flash abuse (see: [miki.it/blog](http://miki.it/blog/2014/7/8/abusing-jsonp-with-rosetta-flash/), [Ars Technica](http://arstechnica.com/security/2014/07/weaponized-exploit-can-steal-user-cookies-on-ebay-tumblr-other-sites/)).
4.  ... 

Also, you may want to use use `isset()` as to not a PHP warning for undefined property "callback" on every other HTTP request. And consistently use single quotes.

Example:
```php
if ( isset($_GET['callback']) ) {
  $callback = preg_replace('/[^][.\\\'\\"_A-Za-z0-9]/', '', $_GET['callback']);
  if ($user) {
    $data = true;
  } else {
    $data = false;
  }
  header('Content-Type: text/javascript; charset=UTF-8', true);
  echo $callback . '(' . json_encode( $data ) .');'; 
  exit;
}
```

See also http://stackoverflow.com/a/8811412/319266