{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreic2qs5xfpfrsskggtzovmictc6bgpbroxubnvo4riysgivbahzkhe",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mliqhzdp5sa2"
  },
  "path": "/t/feature-request-blocking-accounts-models-etc/175888#post_11",
  "publishedAt": "2026-05-10T11:41:48.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "Yes! I completely agree with the negative search solution. To be honest, I kinda regret naming this thread “Blocking [things]” because it sounds too superficial and generic (I was too focused in the whole block thing even though the subject is broader than that, but at least I’m happy to know that I can block specific individuals if I want to, I didn’t know the report feature already allowed that!), but what I’m trying to convey is exactly what you described, a search system similar to google (but maybe a little closer to danbooru when taking into account the blacklist system I’m proposing, which could be temporary (like when searching for specific models, datasets, users.. at a time) or permanent (like when never wanting to see datasets of a particular topic, models of a particular architecture.. etc)).\n\nIf this really is resource-intensive, complex and HuggingFace truly needs a lot of effort to make something like this work (which I really don’t blame, I understand that its really difficult for developers to manage so many different features unfortunately), then any kind of API like you’re suggesting or maybe some kind of extension perfectly fits the bill! The core concept of this feature really is all about convenience and ease of use, I’d never wanna compromise the integrity of the app over a potentially code-breaking feature.",
  "title": "[Feature Request] Blocking accounts, models.. etc"
}