Filter list of potential providers using an exclude list#91
Merged
Conversation
d70-t
approved these changes
Feb 12, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
A list of potential providers is shown at the bottom of each dataset landing page.
However, the term "provider" is somewhat ambiguous. IPFS (and Helia) view it as a purely technical term referring to "nodes that can deliver the data", whereas we view it as "nodes that store/pin the data". The most obvious difference between these two definitions are the local and public gateways. Often, both are able to deliver data without pinning it.
This PR defines an exclusion list to prevent those on it from being shown in the list of data providers on the landing page.