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.
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?
The text was updated successfully, but these errors were encountered:
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.
JustinDrake commentedNov 23, 2016
•
edited
In the whitepaper, an
IPFSLinkis defined asThe paper then allows for content addressing using the name. It is noted that paths work like in traditional UNIX filesystems and the Web.
Can
Namebe an arbitrary string, with characters such as whitespace or/, or any character disallowed in web URIs? Does the protocol require thatNamebe sanitised so that OSes/filesystems/applications can safely parse name paths?The text was updated successfully, but these errors were encountered: