- Ya
- 14 Agosti 2026, 00:19 UTC
- Mwandishi
- kamo
- Ahadi ya
- 1bd39da
The composer held every social DM to a flat 10 MB, which is Telegram's photo limit applied to four providers that do not share it. Each now gets its own ceiling, and within a provider each media type gets its own where the API splits them: Telegram 10 MB photo, 50 MB document/video/audio (sendPhoto vs sendDocument) Messenger 25 MB, the same for every kind Instagram 8 MB image, 25 MB video/audio/file Discord 8 MB (the bot upload ceiling) X no attachments at all unknown 8 MB, the tightest of the above These are the limits of the API each adapter posts to, NOT of the consumer app of the same name. The two differ and it matters: Messenger's app raised file sharing to 100 MB while its Send API is documented at 25 MB, and it is the API's number that decides whether the customer receives the file. Sizing to the app's figure would have the composer accept something Meta then refuses, long after the agent has been told it went out. X gets no paperclip rather than one that refuses everything: XAdapter's sendImage and sendMedia both fall through to sendText — media upload was out of v1's scope — so an attached file would go nowhere while the caption arrived alone. Its own ProviderCapabilities says the same. AttachmentPolicy grows `maxBytesByClass` for this, keyed by a new four-value AttachmentClass (image/video/audio/file) that matches how providers split their endpoints and how MediaService routes outbound media. SVG is a file in both.