Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Why? #41

Closed
timthelion opened this issue Feb 25, 2017 · 2 comments
Closed

Why? #41

timthelion opened this issue Feb 25, 2017 · 2 comments

Comments

@timthelion
Copy link

You write of the URL standard:

This isn't optimal. Instead, addresses should be formatted so:

but you don't write WHY it isn't optiomal and WHY your new standard is better...
@ghost
Copy link

ghost commented Feb 26, 2017

Agreed, this aspect is very under-documented. ipfs/in-web-browsers#4 has a rough version of this, and I'm currently working on making this a proper nice document.

@ghost ghost self-assigned this Nov 9, 2017
@ghost
Copy link

ghost commented Mar 15, 2019

The readme addresses this better now

@ghost ghost closed this as completed Mar 15, 2019
Jorropo pushed a commit to Jorropo/multiaddr that referenced this issue Dec 4, 2021
@Stebalien
Merge pull request multiformats#41 from multiformats/fix/hexupper-prefix
f0792f7 
fix hexupper prefix
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@timthelion