Skip to content

0.19.15-alpha

Choose a tag to compare

View all tags
@morningstarnasser morningstarnasser released this 13 Sep 22:35
· 22 commits to main since this release
v0.19.15-alpha
688e86d

An attachment that could not be fetched now says why.

Before, the agent saw only "Its content is not available to you" — with no way to tell a file that was too large from one in a format it cannot read. Faced with that, it went looking through the filesystem for the file instead.

A hint that withholds the reason costs more time than no hint at all. Now:

  • Too large → the size, the limit, and a way out.
    It is 24.5 MB — too large to fetch: Telegram lets a bot download at most 20 MB. Ask for a smaller copy, or put the file where it can be read directly.
  • Unreadable format → the formats that are readable.
    .zip is not a format this can read. Readable: pdf, docx, xlsx, pptx, txt, md, csv, json.

Documents get their own ceiling. A photo is not a data carrier and stays capped at 12 MB. A document is one — that is what it is for — so it may use Telegram's real 20 MB limit. Half of that excluded exactly the files the feature exists for: property dossiers, annual accounts, contracts.

The file suffix is derived in one place now. Fetching and explaining have to give the same answer, or the hint describes something other than what the fetch does.

Verify this download

sha256  a1f7f3b9c3c949ae4e61612a95d7ba70d6373c94094b9f10365131226f835a86

The .sig is a raw Ed25519 signature over the archive bytes, base64-encoded. The public key is pinned in install.sh:

Do7lfPckC7pJJtD4BECN/mLPIOqHZVWm/j/MfJOK2hk=

Suite: 2758 tests, 254 adversarial cases.

Assets 5
Loading