When trying to sign up for patchwork for the first time about patchwork HOT 12 CLOSED

Console.logging message out of ssb-feed i get:

*****WWWEEEEE*****
{ previous: null,
  author: 'lzMHSo63Do77Fg4qdDrcIk6yJ+HWQs6YH+fD217S6+s=.ed25519',
  sequence: 1,
  timestamp: 1444535285679,
  hash: 'sha256',
  content: 
   { type: 'about',
     about: 'lzMHSo63Do77Fg4qdDrcIk6yJ+HWQs6YH+fD217S6+s=.ed25519',
     name: 'bret' },
  signature: 'xzdtZHR7cTQn1iVj2PFmupgHS+PSUQajmHjdokR/KP4n8ec5G4mwrSF+1tC/3OckRNX4iIJctlDFtXTFwSbRBQ==.sig.ed25519' }

@dominictarr said it was strange that the hash is missing @ ¯\_(ツ)_/¯

from patchwork.

Yeah, that's pretty odd. I'll poke around for spots where that could be happening...

from patchwork.

Note, the *****WWWEEEEE***** was a logging marker I thew in. I started digging into node_modules with console.log in hand in order to understand whats going on.

from patchwork.

We found the issue, @dominictarr has a fix coming

from patchwork.

Ok, run npm update so that ssb-keys is version 4.0.5 and your issue should be resolved.

from patchwork.

\o/ Will a little after work! Out of curiosity, was this the fix? ssbc/ssb-keys@76a13d6

Will close out this evening after I test.

from patchwork.

No, the fix was
dominictarr/ssb-keys@ace73b3#diff-168726dbe96b3ce427e7fedce31bb0bcR125

Basically the situation is, you had a slightly old keyfile format from an
earlier version, that didnt have the @ sigil in the ID. That caused
everything to freak out. So, we just add the @ if it's missing.

On Wed, Oct 14, 2015 at 8:27 PM, Bret Comnes [email protected]
wrote:

\o/ Will a little after work! Out of curiosity, was this the fix?
ssbc/ssb-keys@76a13d6
ssbc/ssb-keys@76a13d6

Will close out this evening after I test.

—
Reply to this email directly or view it on GitHub
#34 (comment).

from patchwork.

@bcomnes did this work for you?

from patchwork.

Swamped by work. Haven't had a chance to check yet 😦 I'll post back if it doesn't

from patchwork.

okay, I'm gonna reopen this till you confirm

from patchwork.

Basically the situation is, you had a slightly old keyfile format from an earlier version, that didnt have the @ sigil in the ID.

Totally possible. I tried this a while back.

from patchwork.

Ok I got on! 😀

@lzMHSo63Do77Fg4qdDrcIk6yJ+HWQs6YH+fD217S6+s=.ed25519

from patchwork.