feat(config): single-purpose deleagted routing endpoints #10806
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this is poc of optional configuration that would allow for IPNS-only and Peer-only endpoints. unsure how useful this would be in real world, my assumption is that single config is better and also encourages people to decentralize/federate routing systems with tools like https://github.com/ipfs-shipyard/someguy which exposes providers+peers+ipns
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Caution
Do not merge, this is PoC/exploration.
this is poc of optional configuration that would allow for IPNS-only and Peer-only endpoints.
unsure how useful this would be in real world, my assumption is that single config is better and also encourages people to decentralize/federate routing systems with tools like https://github.com/ipfs-shipyard/someguy
which exposes providers+peers+ipns
👉 parking this as a draft for now – let's see how single config from Kubo 0.35 works, and if anyone raises a need for this at all
my personal preference would be to keep things simple for now and not split – feedback welcome
Open questions
cid.contact, which is providers-only, and we explicitly disabled querying its endpoint for peers and ipns? how to ensure users are able to override default, or set own routers?