`ipfs name publish` to same hash from separate computers

From @doesntgolf on Fri Jan 01 2016 15:34:07 GMT+0000 (UTC)

I’m wondering if publishing to the same IPNS hash from separate computers is 1) doable now, 2) not yet doable but planned, or 3) not possible or not planned.

Copied from original issue: https://github.com/ipfs/faq/issues/88

From @fazo96 on Fri Jan 01 2016 21:51:09 GMT+0000 (UTC)

It would be number two as far as I know :+1: It’s planned but not doable yet

From @whyrusleeping on Tue Jan 05 2016 10:31:47 GMT+0000 (UTC)

this is planned, and should be implemented fairly soon (many other things will depend on this capability) https://github.com/ipfs/specs/tree/master/keystore

From @RichardLitt on Mon May 02 2016 19:37:40 GMT+0000 (UTC)

@whyrusleeping What is the status on this? Curious.

From @wigy-opensource-developer on Wed Nov 09 2016 15:13:07 GMT+0000 (UTC)

We need this feature for an open source project we are working on atm. Since there seems to be little progression on this, we would like to help implementing parts of it on our fork.

Our use-case is that the private key used for signing the IPNS record is not shared with the IPFS node that republishes the record. For that we need to

  • Allow the IPNS record author ID to be different from the peer ID of the IPFS node (requires some refactoring of the existing code that would be needed for the keystore feature anyway)
  • Add an API command to publish an IPNS record that was already signed by the caller
    • the IPFS node maintains a list of allowed author IDs and rejects to republish records written by other authors
    • if the IPFS node finds a record with greater sequence number, it reports an error including the highest sequence number found on the network

@whyrusleeping Would these changes be something that you would be happy to merge back?

From @Kubuxu on Thu Nov 10 2016 15:28:18 GMT+0000 (UTC)

@wigy-opensource-developer there is separate program that can be used for that: https://github.com/whyrusleeping/ipns-pub
and you can use ipns-key program to generate key-pair. This can be the workaround for now.

From @wigy-opensource-developer on Fri Nov 11 2016 05:26:08 GMT+0000 (UTC)

Thanks, I have already seen those tools. Our use case cannot assume that the author has internet access every 12 hours to republish the IPNS record. Also, we cannot give the private key to the node that has continuous internet access. Correspondingly, we need to separate the responsibilities of signing and publishing the record.

From @lgierth on Sat Nov 12 2016 03:06:10 GMT+0000 (UTC)

@wigy-opensource-developer we have IPRS (record system) in the works on and off, which will allow you to pin other nodes’ IPNS records and should benefit your use case. It’s likely not gonna happen in the few weeks left this year :frowning:

But we’re on it and it would be great to have your feedback: https://github.com/ipfs/specs/search?q=iprs&type=Issues&utf8=✓