)]}'
{
  "commit": "92e78fce7d4fd16c2eef28f88343dc8a524b7287",
  "tree": "820fdd877f0f7ceef63833b0971f227dee17aeba",
  "parents": [
    "f007969b37d332b0ccc2bbb5d0ac23275837db62"
  ],
  "author": {
    "name": "Marc Kupietz",
    "email": "kupietz@ids-mannheim.de",
    "time": "Sun Jun 14 20:38:50 2026 +0200"
  },
  "committer": {
    "name": "Marc Kupietz",
    "email": "kupietz@ids-mannheim.de",
    "time": "Sun Jun 14 20:38:50 2026 +0200"
  },
  "message": "Reliably embed failure screenshots in Nextcloud Talk\n\nScreenshots often fell back to \"too large to embed\" text instead of the\nactual proof image. A single fixed 800px PNG encode exceeds Nextcloud\nTalk\u0027s 32000-char message limit once base64-expanded (~74KB).\n\nEncode as JPEG (much smaller for UI screenshots) and step the width down\nthrough a list of candidates until the embedded message fits, keeping the\nlargest size that does. Typical search-failure screenshots now embed at\nfull 800px width; even a 336KB screenshot embeds at 520px.\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n\nChange-Id: I32a71646c3e6c57a18e1230080c53abf952b3dd7\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "145a68909188042cb7425b9112740bb7c05a0028",
      "old_mode": 33188,
      "old_path": "lib/utils.js",
      "new_id": "5d1c20e1db375ffb0484444e2e636e7fddf07fd8",
      "new_mode": 33188,
      "new_path": "lib/utils.js"
    }
  ]
}