Contribute to Open Source. Search issue labels to find the right project for you!

Non-self IPNS names need republishing

ipfs/go-ipfs

<!– Output From ipfs version --all) –>

Version information: 0.4.7

<!– Bug, Feature, Enhancement, Etc –>

Type:

<!– from P0 “Critical” to P5 “Relatively Unimportant”) –>

Priority: P2

Description:

It doesn’t look like names added by ipfs key gen ever get republished. I didn’t actually test it, but I’m fairly certain there’s no code for it.

It should:

  • at startup, call Republisher.AddName() for each key in the keystore.
  • same for every run of ipfs key gen, add the name to the republisher.

cc @edsilv I think this will affect you. You’ll have to run ipfs name publish --key=<name> <hash> every 12 hours, for now.

<!– This is for you! Please read, and then delete this text before posting it. The go-ipfs issues are only for bug reports and directly actionable features. Read https://github.com/ipfs/community/blob/master/contributing.md#reporting-issues if your issue doesn’t fit either of those categories. Read https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md if you are not sure how to fill in this issue. –>

Updated 26/03/2017 16:43 11 Comments

PeerID in IPNS key workflow

ipfs/go-ipfs

<!– Output From ipfs version --all) –>

Version information: 0.4.7

<!– Bug, Feature, Enhancement, Etc –>

Type: enhancement

<!– from P0 “Critical” to P5 “Relatively Unimportant”) –>

Priority: P3

Description:

  • ipfs name publish --key should accept a PeerID in addition to the key name.
  • ipfs key list should list the PeerID alongside the key name (-l arg should be default true).

<!– This is for you! Please read, and then delete this text before posting it. The go-ipfs issues are only for bug reports and directly actionable features. Read https://github.com/ipfs/community/blob/master/contributing.md#reporting-issues if your issue doesn’t fit either of those categories. Read https://github.com/ipfs/go-ipfs/blob/master/docs/github-issue-guide.md if you are not sure how to fill in this issue. –>

Updated 21/03/2017 04:12

ipfs files publish

ipfs/go-ipfs

The ipfs files publish command would take the current files root hash, and would publish it as an IPNS entry for the node. It’d effectively be a shortcut for ipfs name publish $(ipfs files stat --hash /).

This seems trivial but I think it might remove UX friction.

Updated 11/02/2017 05:00 2 Comments

Offline IPNS should resolve dnslinks

ipfs/go-ipfs

An offline node (ipfs daemon --offline) refuses to serve e.g. /ipns/ipfs.io because the resolver acts as completely offline.

In the optimal case, if we have already have all the required data, it should still serve that thing, since it doesn’t require any routing, IPNS lookups, or Bitswap trades.

Updated 09/01/2017 14:35 3 Comments

namesys: IPNS/DNS resolution is very slow

ipfs/go-ipfs

While checking performance I discovered that namesys introduces 400x to 5000x increased latency. See: IPFS path:

IPNS path:

I did hard refresh so e-tag and in browser caching shouldn’t matter.

Complete load requires almost 40x more time to complete under IPNS. I can repeat those results easily. You can also try for your self: fs:/ipns/ipfs.io and fs:/ipfs/QmTzQ1JRkWErjk39mryYw2WVaphAZNAREyMchXzYQ7c15n/

Updated 24/03/2017 19:36 5 Comments

IPNS mount fails offline

ipfs/go-ipfs

Tested in 0.4:

[root@test1 ipfs]# ~/go/bin/ipfs mount
12:51:25.225 ERROR  fuse/ipns: looking up /ipns/QmeRMMbeJvdGp5UALPqWDiwb4Wqn3WG7oK73n2wXJXAGC5: could not resolve name. ipns_unix.go:90
12:51:25.226 ERROR core/comma: error mounting: fusermount: exit status 1 could not resolve name. mount_unix.go:219
Updated 05/01/2017 10:05 6 Comments

Fork me on GitHub