{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibknnmnulxlpypoqsyobcoy2gy7rofwmn7lu767mj74vjbhfeabn4",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mi4rlfz4cbf2"
  },
  "path": "/t/spaces-build-issue-has-been-solved/170269#post_7",
  "publishedAt": "2026-03-28T10:30:41.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "violate HF policies",
    "Automatically bans users",
    "Infrastructure issues (maybe related, maybe not related)"
  ],
  "textContent": "John6666:\n\n> The key point is that rather than the restrictions having become permanently stricter (at the moment), we are currently in the midst of a “mishap.”\n>\n>   1. Intentional (maybe) new restriction system\n>\n\n>   * Automatically pauses Spaces that violate HF policies\n>   * Automatically bans users who create a large number of policy-violating Spaces?\n>\n\n>   2. Errors (bugs?) in the restriction system\n>\n\n>   * The above measures were applied beyond HF’s intended scope\n>   * The resulting fallout\n>\n\n>   3. Infrastructure issues (maybe related, maybe not related)\n>\n\n>   * Issues with Spaces Start, Restart, and Build\n>   * Strange 400 errors\n>   * Issues where Spaces logs are not displayed\n>   * and more…?\n>\n\n\nI think that is a bug, not due to policies. Maybe have some problem in HF’s base and they’re still fixing it then we should wait at least few days. It’ll be better soon.",
  "title": "Spaces Build issue has been Solved"
}