Previously, we generated and prepended a long salt before generating
password hashes. This resulted in the hash verification cutting off long
before it should do. This form of salting is also not necessary with
bcrypt as it's provided by the password hashing and verification
functions themselves, so totally rip it out.

This commit also adds the functionality for the server to automagically
upgrade users to use the new hashing system, which means better
security and more assurance that people can't bruteforce passwords.

No need to apply a database upgrade to do this, whoo! \o/

README.md: self-signed, not unsigned

refactor irc.Socket

implement fakelag (#189)

partial fix for #217

try to fix travis by pinning a goreleaser release

The sync.atomic documentation says:

"On both ARM and x86-32, it is the caller's responsibility to arrange
for 64-bit alignment of 64-bit words accessed atomically."

See discussion on issue; this might not be a complete fix but it's
definitely better than the current behavior.

fix #214

nickserv: implement GHOST, GROUP, DROP, and INFO

Sequence of events:

1. client.nickTimer.Stop()
2. client.server.accounts.Logout(client)
3. accounts sees that client is no longer logged in, does client.nickTimer.Touch()
4. 30 seconds later, RandomlyRename resurrects the zombie client

add an option to expose a pprof http endpoint

fix #204

Empty channels were only cleaned up on PART, not QUIT.

two nickname reservation fixes