Skip to content
This repository has been archived by the owner. It is now read-only.

Are there restrictions for the name of IPFS links? #201

Closed
JustinDrake opened this issue Nov 23, 2016 · 2 comments
Closed

Are there restrictions for the name of IPFS links? #201

JustinDrake opened this issue Nov 23, 2016 · 2 comments

Comments

@JustinDrake
Copy link

JustinDrake commented Nov 23, 2016

In the whitepaper, an IPFSLink is defined as

type IPFSLink struct {
  Name string
  Hash Multihash
  Size int
}

The paper then allows for content addressing using the name. It is noted that paths work like in traditional UNIX filesystems and the Web.

screen shot 2016-11-23 at 14 11 38

Can Name be an arbitrary string, with characters such as whitespace or /, or any character disallowed in web URIs? Does the protocol require that Name be sanitised so that OSes/filesystems/applications can safely parse name paths?

@ghost
Copy link

ghost commented Nov 23, 2016

I'm not sure there are any restrictions right now. If a link name contains a forward-slash, you just won't be able to address it through the standard ipfs tools (cli, gateway, fuse). There's a lengthy interesting discussion in ipfs/kubo#1710.

@flyingzumwalt
Copy link
Contributor

flyingzumwalt commented May 23, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants