Multiple separators

[CMCDragonkai]

Hey we're studying this library for a full libp2p implementation.

I have to ask however, is that why did you make it so that it can parse many separators.

The parser accepts /ip4/////////127.0.0.1/////////. I wasn't aware this is a legal multiaddress.

[basile-henry]

Hey!

The reference js implementation seems to accept multiple separators as can be seen in the source code. In general I think it is a good behaviour for this kind of library to be a bit looser on the definition when parsing and very strict when generating the address.

I believe http addresses have the same behaviour, try to navigate to https://github.com/basile-henry////hs-multiaddr////////////////issues////////////////3

[CMCDragonkai]

Thanks for the answer. That's a good idea for human to machine interfaces, but for machine to machine interfaces then I'd prefer strictness and simplicity. But since it's in the go impl, then we'll just go with it. Hopefully this can be defined in the spec.

[basile-henry]

Isn't the point of the string representation of a multiaddr to be for human to machine interfaces? The binary encoding is a lot more strict!