-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Prioritize announcement of pin roots #10365
Labels
effort/days
Estimated to take multiple days, but less than a week
exp/intermediate
Prior experience is likely helpful
kind/enhancement
A net-new feature or improvement to an existing feature
P1
High: Likely tackled by core team if no one steps up
topic/routing
Topic routing
Comments
lidel
added
kind/enhancement
A net-new feature or improvement to an existing feature
topic/routing
Topic routing
P1
High: Likely tackled by core team if no one steps up
exp/intermediate
Prior experience is likely helpful
effort/days
Estimated to take multiple days, but less than a week
labels
Mar 7, 2024
Seems reasonable. The main tradeoff here is that we might over-read data from disk which may/may not be that important. The reprovider strategies are here Lines 130 to 139 in e22f47a
Probably the easiest way to do this is:
|
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
effort/days
Estimated to take multiple days, but less than a week
exp/intermediate
Prior experience is likely helpful
kind/enhancement
A net-new feature or improvement to an existing feature
P1
High: Likely tackled by core team if no one steps up
topic/routing
Topic routing
Hopefully inexpensive optimization that would help Collab cluster, and content routing based on Amino DHT in general:
This ensures most important CIDs are out of the door (in the spirit of ipfs/specs#462), and we can slowly announce everything else.
The text was updated successfully, but these errors were encountered: