Add option to get consistent ids for identical timestamps.

By passing :jitter => false, we do not randomize the top 3 bytes.
Default to empty hash in #initialize.
Change option :jitter to :randomize.
Merge pull request #7 from finn-no/consistent-time-uuids

Add option to get consistent ids for identical timestamps.
fix release
Revert "fix release"

This reverts commit f67dc9555b9acbe02efda5c9e2a39c05ff23cb52.
update manifest
 update gemspec
 update CHANGELOG
update gemspec;
Added the licenses in the gemspec
Merge pull request #8 from amanelis/gemspec-license

Added the licenses in the gemspec
When bytes are directly passed to the constructor and the ruby version supports encoding, ensure they are forced to ASCII-8BIT(binary) encoding so ==/to_s doesn't return strings that are encoded differently
Merge pull request #9 from brightbits/master

Ensure ==/to_s work correctly when raw bytes are passed in different encodings
Enable user provided non-randomized salt for clock and node fields

It is recommended that the passed salt is genereated by a quality
hash function like SHA1 or MD5
This implementation is not RFC4122 compliant
Merge pull request #10 from tsenart/usersalt

Enable user provided non-randomized salt for clock and node fields instead of jitter
fixed gemspec homepage url to point to github repo
Merge pull request #11 from kbrock/master

change homepage url
Fix comparison of UUIDs with the same time.

There was an inconsistency where two different UUIDs created from
the same time would correctly report == as false, but confusingly
report <=> as 0. Now <=> is implemented per RFC 4122's "Rules for
Lexical Equivalence", and == is no longer a special case.
Merge pull request #13 from nearbuy/fix_comparison

Fix comparison of UUIDs with the same time.