Skip to content
This repository was archived by the owner on Jun 20, 2023. It is now read-only.

Consider renaming to go-ipns-record #1

Closed
Stebalien opened this issue Jun 15, 2018 · 2 comments
Closed

Consider renaming to go-ipns-record #1

Stebalien opened this issue Jun 15, 2018 · 2 comments

Comments

@Stebalien
Copy link
Member

This package doesn't contain resolution logic. We'll probably want a package containing a value store based resolver/publisher and go-ipns may be the right place for that.

Mr0grog added a commit to Mr0grog/go-ipns that referenced this issue Jun 18, 2018
This is based on a note in ipfs#1, which seems like an important and useful clarification :)

License: MIT
Signed-off-by: Rob Brackett <rob@robbrackett.com>
Stebalien pushed a commit that referenced this issue Jun 19, 2018
add upstream patches
@vasco-santos
Copy link
Member

As discussed in the js-ipfs PR feat: IPNS, I totally agree with this rename.

@hacdias
Copy link
Member

hacdias commented Jun 6, 2023

This repository is no longer maintained and has been copied over to Boxo. We are now in the process of reviewing issues and PRs and moving the ones that are still relevant.

@hacdias hacdias closed this as not planned Won't fix, can't repro, duplicate, stale Jun 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
No open projects
Archived in project
Development

No branches or pull requests

3 participants