Very interesting concerns about URLs! I've looked into better ways of addressing recently too, but coming from different problem spaces: 1. how to decouple con

Very interesting concerns about URLs! I've looked into better ways of addressing recently too, but coming from different problem spaces: 1. how to decouple content from location, i.e. location-addressing vs. content-addressing 2. how to accept more network connection constructions than what URLs permit (proxying, domain fronting, tunnels, etc.) > We could also imagine a new URL syntax, with fewer and less ambiguous syntactic meta-characters. That's part of what we're attempting for network addressing with the multiaddr format: https://github.com/multiformats/multiaddr https://github.com/multiformats/multiaddr - If the author of the article is reading here, I'd love to hear your thoughts! We're going with encapsulation and a posix filesystem compatible plan9-ish syntax and approach there. multiaddr describes the semantics of networking namespaces, and then various content systems bring their own namespaces. IPFS brings the /ipfs and /ipns namespaces for its content.