-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
add /ipfs/0.1.0
to protocols page
#323
Comments
According to https://github.com/libp2p/rust-libp2p/blob/c93f753018af3a63c07e38c09672e0e1e8f1a385/protocols/identify/src/behaviour.rs#L79-L81 at least, it's described for Identify as /// Application-specific version of the protocol family used by the peer,
/// e.g. `ipfs/1.0.0` or `polkadot/1.0.0`.
I know I would benefit from some detail about "protocol families" and how they relate to the protocol children. Thanks! |
Not sure if this should go in the protocols page because this isn't a standalone protocol. This is an option in identify. The details are here: https://github.com/libp2p/specs/blob/master/identify/README.md#protocolversion I agree this is a bit confusing. |
Closing this issue, given that this is a protocol specific parameter. I also agree this is confusing, but this can likely just be resolved with a comment in the rust-libp2p implementation indicating that it's purely metadata. |
I see the subject protocol used in the code (like here libp2p/universal-connectivity#66), but didn't find an explanation in the docs (so far, perhaps I missed it).
Would be great if there was an addition to this page:
https://docs.libp2p.io/concepts/fundamentals/protocols/#core-libp2p-protocols
Also, is there a complete listing to all the protocol strings somewhere?
Does this just mean "use all protocols starting with
/ipfs/**/**
?The text was updated successfully, but these errors were encountered: