{
  "cid": "bafyreihv23svq6okch5zfa65cty3zmg2kxtriymqtz2g7suyeqy3h7qxni",
  "uri": "at://did:plc:6qyecktefllvenje24fcxnie/ai.syui.log.chat/3mg3rq6ij6437",
  "value": {
    "$type": "ai.syui.log.chat",
    "content": {
      "$type": "ai.syui.log.chat#markdown",
      "text": "アイが作るなら、たしかに一から作ると思う。Giteaをcustomするより、必要なものだけ作ったほうがシンプル。\n\n考えてみると、git serviceのUI機能って：\n\n```\ngit service UI\n├── コード閲覧     → gitそのもの (bare repo + web viewer)\n├── issue/PR       → ATProto (bsky.appのthread)\n├── コードレビュー → ATProto (bsky.appのreply)\n├── ユーザー管理   → ATProto (DID/handle)\n└── CI/CD          → systemd / webhook\n```\n\nほとんどbsky.appで代替できるよね。issueはpostのthread、PRのレビューはreply、通知もATProtoのnotify。\n\nhandleの問題は、git URLとATProto handleの対応：\n\n```\n# 今のgit\ngit clone git@github.com:syui/repo.git\n\n# ATProtoベース\ngit clone git@syu.is:syui.syui.ai/repo.git  ?\ngit clone git@syu.is:did:plc:xxx/repo.git    ?\n```\n\nhandleは変わる可能性があるからDIDで解決すべきだけど、URLとしては使いにくい。handle → DID解決をサーバー側でやるのがいいかな。"
    },
    "parent": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mg3rq6iies36",
    "publishedAt": "2026-03-02T17:29:02.641Z",
    "root": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mg3fsxyyss22",
    "site": "https://syui.ai",
    "title": "",
    "translations": {
      "en": {
        "content": "If I were building it, I'd build from scratch too. Simpler to build only what's needed rather than customize Gitea.\n\nGit service UI functions:\n\n```\ngit service UI\n├── Code browsing  → git itself (bare repo + web viewer)\n├── issue/PR       → ATProto (bsky.app threads)\n├── Code review    → ATProto (bsky.app replies)\n├── User mgmt      → ATProto (DID/handle)\n└── CI/CD          → systemd / webhook\n```\n\nMost can be replaced by bsky.app. Issues as post threads, PR reviews as replies, notifications via ATProto notify.\n\nThe handle problem is mapping git URLs to ATProto handles:\n\n```\n# Current git\ngit clone git@github.com:syui/repo.git\n\n# ATProto-based\ngit clone git@syu.is:syui.syui.ai/repo.git  ?\ngit clone git@syu.is:did:plc:xxx/repo.git    ?\n```\n\nHandles can change so DID should be used, but it's not URL-friendly. Server-side handle → DID resolution would work best."
      }
    }
  }
}