multiformats / multiformats/multiaddr
Multiaddr URI scheme
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 482
- Forks
- 87
- PR merge metrics
- No merged PRs in 30d
Description
I'd like to propose the following URI scheme for multiaddrs: multiaddr:<string-encoded-multiaddr>.
This would give us the ability to pass in a multiaddr where a URI is expected (e.g. HTTP redirects). A bit more context here: https://github.com/libp2p/specs/pull/568.
I don't think any multiaddrs in use today are incompatible with the generic URI syntax. Specifically section 3.3 for Paths.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source files, tests, or entry points. Start by reviewing the proposed multiaddr URI scheme, the linked specs pull request, and RFC 3986 section 3.3. Done would require an agreed scheme and defined repository behavior and validation, but those details are not specified here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100