)]}'
{
  "log": [
    {
      "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"
    },
    {
      "commit": "2f17a764c88a63737102955aee49f0ca77b36171",
      "tree": "ceae1fcb7605d1d49f7b2e3aa8543aeb1f120724",
      "parents": [
        "65dea514a9f467906c91bbe4a7b0bead731a0390"
      ],
      "author": {
        "name": "Marc Kupietz",
        "email": "kupietz@ids-mannheim.de",
        "time": "Sat Dec 06 11:45:49 2025 +0100"
      },
      "committer": {
        "name": "Marc Kupietz",
        "email": "kupietz@ids-mannheim.de",
        "time": "Sat Dec 06 11:48:05 2025 +0100"
      },
      "message": "Extract NC talk functions from tests to library\n\nChange-Id: I789a893d073a00025ec4bb65311bb893b58b1a06\n"
    }
  ]
}