- Ya
- 27 Agosti 2026, 17:01 UTC
- Mwandishi
- kamo
- Ahadi ya
- c6923e4
Reporters were describing screen recordings in prose and then posting the file into a chat, because the report form only took stills. It now takes MP4, MOV and WebM beside the four image formats, up to 100 MB each, inside the same ten-file cap. The dropzone no longer implements its own rules. It hands the batch to `ingestFiles` against a new SYSTEM_BUG_ATTACHMENT_POLICY, the same path a chat message and an email go through, which is what gets it per-class size ceilings, a dropped folder recognised as a folder, a duplicate drop ignored, and a copied range of spreadsheet cells left as text instead of silently becoming a bitmap. A refused file no longer discards the rest of the batch with it. Object URLs move to `useDraftThumbnails`, so nothing here has to remember to revoke one. Video renders the way it already does everywhere else in the product: a poster frame drawn with the `#t=0.1` trick and a play badge on the tile, browser controls in the lightbox. Thumbnails are metadata-only fetches, so a drawer full of tiles does not pull whole clips down — which is what the Range support added to MediaService is for, and why this proxy passes Range and 206 through in both directions rather than collapsing them. The upload route stops parsing the body with formData(). That held the whole file in this process's heap, survivable for a 10 MB screenshot and not for a 100 MB recording; it now pipes through node:http like the chat upload does, for the same undici-timeout reason. The button counts files while it works — fetch reports no upload progress, and "Uploading…" sitting there for minutes reads as a hang. Send To AI lists images only. A session reads a picture and cannot watch a video, so offering one would be offering to fail; the dialog says how many are staying behind, and SecurityService refuses one by name if a stale console sends it.