Conversation
|
yeah, this might not be a terrible idea, at least so we have a prompt to consider carefully if we ever want to add a @mxinden @marten-seemann any objections or input? |
No objections from my end. Maybe @lidel has thoughts on this. |
|
I think multiformats/multiformats#63 is also relevant here in some way. |
|
No objections, but I don't feel confident enough to give an approval. |
|
What can I do to make it confident enough for an approval? |
rvagg
left a comment
There was a problem hiding this comment.
no harm in reserving it, it'll save potential future pain if we accidentally allocate a multibase with / that's not related to multiaddr, and if we decide somehow to add one then we can undo the reservation but it'd be an intentional thing
The code
/is used by multiaddr, so it seems reasonable to me to reserve this character.For example, if there could be a data structure like this:
{ "address": "<value>" }The
<value>could be:QmYyQSo1c1Ym7orWxLYvCrM2EmxFTANf8wXmmE7DWjhx5N12D3KooWD3eckifWpRn9wQpMG9R9hX3sD158z7EqHWmweQAJU5SAbafzaajaiaejcal72gwuz2or47oyxxn6b3rkwdmmkrxgkjxzy3rqt5kczyn7lcm3lBut this could maybe also the value:
/ipfs/QmYyQSo1c1Ym7orWxLYvCrM2EmxFTANf8wXmmE7DWjhx5N