[feature request]: ability to track references/metadata from hash | reverse reference #3417
Description
Is your feature request related to a problem? Please describe.
This is more like a suggestion to the backend team. What if we introduce downloading models by references, like a hash maybe.
Describe the solution you'd like
The thing is, if we are creating a workflow or some other solution, we often use what's in our system. Only few creators decides to take one more step and replace the model references to something global. And this lands us to something really intersting. If we have some exposed APIs to download metadata just from the hash, it will be better. We can talk to other communities to inforce this as well. From a local model, if it finds it in the huggingface, it will replace with the url or more readable reference. And this will definetly make hugging face a de facto standard for all workflows. We can talk to comfy ui to integrate this as well.
And this doesn't only solve problems for creators and users, it will resolve huggingface's storage issues quite well as well. It will store only unique data.
Describe alternatives you've considered
I can create a server with hash to reference server. Which will do this job. But it will be way more interesting if huggingface takes care of this.
Additional context
Add any other context or screenshots about the feature request here.
See, we can already pass down a huggingface URL in comfy ui workflow:
But if the model is present locally, we just pick the local model, and it's really not hard to do the reverse search, but quite boaring:
Take a look, these hash are already present, we just need to expose an API with rate limit:
I am willing to work on this one, and you know what if you want you can hire me in your team. You will get more awesome features like this. Good day!