-
Notifications
You must be signed in to change notification settings - Fork 411
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.
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
[Content Request] Document IPNI / Indexers #1296
Comments
This comment was marked as resolved.
This comment was marked as resolved.
@TMoMoreau fyi |
Perhaps this is a separate issue but documenting reframe would be super useful. There's various resources you can find but querying reframe on the site doesn't yield any results. https://github.com/ipfs/kubo/releases/tag/v0.16.0 has configuration guidance.
|
"IPNI" (InterPlanetary Network Indexer) should be added to glossary: https://docs.ipfs.tech/concepts/glossary/ |
I'll get a draft PR made for this. Going to make a list here as well, to verify and keep track of what needs to be done.
@jacobheun I think it would be best to make a separate issue for the reframe documentation topic. |
Thanks. FYI Torfinn Olsen is gonna be the new indexer PM on this going forward. |
I think this is blocked until specs solidify and the implementation of the new API ships with Kubo 0.18. |
I guess this is unblocked because we've shipped Kubo 0.18 with default IPNI enabled (https://cid.contact/) by default. cc @willscott – mind dropping good specs/design docs for docs team to catch up with latest state of things? |
ipfs/specs#337 is probably the most useful definition for the API that's been shipped https://github.com/ipni/storetheindex-docs can be useful from the IPNI side |
@lidel can you help the docs team to determine if this is still relevant? https://docs.ipfs.tech/concepts/#peer-to-peer-sharing no longer exists, as it was removed when 2color and I redid the concepts section |
@TorfinnOlsen is probably a good point of contact here. The IPNI team would like to have docs here, and this remains a valid and effective way to do content routing. Since the use of delegated routing is on by default in current releases of kubo we probably should have documentation about it. |
Thanks @willscott |
I'm thinking we can add a new page in Concepts -> Subsystems and Components called IPNI that describes this subsystem |
@ElPaisano one thing to be aware of is a lot of the language around this specific topic is in a bit of flux right now. The document @willscott mentioned is the most important starting place however upon reviewing it I submitted a PR to include an important update that might be confusing to readers regarding Reframe which has since v0.19 Kubo release been deprecated. You should also be aware of the Delegated IPNS HTTP API which intends to delegate naming system functionality over HTTP APIs. I think from a broader descriptive perspective of the IPNI beyond what you'll find in storetheindex-docs you can use our teams overview blogposts as a valuable reference point on some of the more important points. How does the network indexer work There are a few more of these that dive deeper into topics involving more how to operate the network indexer and less how it routes content efficiently. If that type of documentation is beneficial for context sake let me know and I'll happily load your plate up with additional links. |
Cheers thanks @TorfinnOlsen Initial draft is here #1552. This would be good to quickly discuss in a sync call |
@TorfinnOlsen can you let me now if you will have a chance to review this week? I figure it might not happen with IPFS thing |
Redraft from @TorfinnOlsen is here https://github.com/TorfinnOlsen/IPNIdocumentation/blob/main/IPFSdocsIPNI.md. Will edit this and add to the PR |
We are working on Network indexer that index IPFS and Filecoin contents. We should add indexing doc / pointer on the ipfs page here under peer-to-peer-sharing https://docs.ipfs.tech/concepts/#peer-to-peer-sharing.
We can leverage the indexer gitbook to build the content page: docs.cid.contact
The text was updated successfully, but these errors were encountered: