Tested with node.js 4.2.2

The .npmignore file is there because of npm ignoring the 'config' module;
This happens because it looks into the .gitignore file while installing.

See merge request !1

Those tables were used prior to the introduction of `removeToken`.

* Create package.json for easy installation with npm
* Move AUTHORS file in package.json
* Move all the code in server/ in the root
* Rename and update INSTALL.md

* Update database schema
* Update usage on the server-side
* Allow multiple statements on the MySql interface

* Implement B -> A SMP public key authentication
* Update schema to reflect the new and moved message/storage parts
* Add option to mark the received SMP question unsafe and counter-authenticate
* Make support function available only in the current file
* Share key2 and key3 in both SMP directions as per specs
* Make SMP both directions optional

Conflicts:
	server/socket.js

Conflicts:
	client/js/crypto/common.js
	client/js/crypto/fhmqv.js
	client/js/model/collection.js
	client/js/model/group.js
	client/js/model/message.js
	client/js/model/modelbase.js
	client/js/model/post.js
	client/js/model/sessionuser.js
	client/js/network.js
	client/js/router.js

A merge like this must never happen again :P

Add the salt column to `Raven`.`User`
Add *.`removeToken`
s/publicKey/signingPublicKey/ in `Ranve`.`Group{,History}`