4 ms·

Working on it as we speak! I'm currently running the tests and hope to have a 1.0.2 hotfix ready by lunch. EDIT: The 1.0.2 hotfix is now available with the tok

• dchest 11y ago
  Great! Make sure it's long enough: at least 16 bytes (32 hex characters) if you want to keep compatibility with current tokens, 32 bytes (64 hex characters) ideally.
• rbolte 11y ago
  I've opted for the 16 bits version right now as it fits better in the UI. There will be an additional issue to deal with improving the bitrate as well as making a suitable UI for it. EDIT: I'm using `crypto.randomBytes(16).toString('hex')` to be precise
  • dchest 11y ago
    I hope you meant 16 bytes :-) If so, it's fine. Edit: yep, 16 bytes.
    • rbolte 11y ago
      And it's done. The 1.0.2 hotfix is now available with the token generation fix as well as 2 other enhancements.
• yAnonymous 11y ago
  Don't worry, it's not critical or anything. JupiterMoon just seems to be a bit of an entitled *ss.
  • JupiterMoon 11y ago
    I thought that HN policy was that posts should keep a civil tone.
    • yAnonymous 11y ago
      My post was more civil than yours, so what's the problem? Basically forcing him to put up a patch for an unimportant issue on the same day with your entitled comment was a really crappy thing to do.
• JupiterMoon 11y ago
  Good stuff. Sorry if I came across as overly critical.