For m.image/m.video/m.audio/m.file messages, content.body is normally just the filename (e.g. "photo.jpg"), and that's all that ends up in the exported txt/html/json — the msgtype is captured in the JSON payload's type field but is never surfaced in the human-readable txt/html output, and no URL/mxc reference or "attachment" marker is included anywhere. A reader of the txt/html export cannot tell a line was an image/file share versus a plain text message named "photo.jpg", and the actual media (especially encrypted media, where the URL is meaningless without the E2EE key bundled in content.file) is never exported or referenced.
How to trigger
Export a room containing image/file messages in txt or html format; the messages show as plain filename text indistinguishable from a real chat message.
Suggested fix
At minimum, prefix media rows with a type marker (e.g. "[Image] photo.jpg") in txt/html output, and note in the UI that attachments themselves are not included in the export.
Filed from the September 2026 client audit (branch lotus @ 4bea4895).
**Severity:** low · **Type:** bug · **Confidence:** medium
**Location:** `src/app/features/room-settings/ExportRoomHistory.tsx:115-126, 194-208`
### Problem
For `m.image`/`m.video`/`m.audio`/`m.file` messages, `content.body` is normally just the filename (e.g. "photo.jpg"), and that's all that ends up in the exported txt/html/json — the `msgtype` is captured in the JSON payload's `type` field but is never surfaced in the human-readable txt/html output, and no URL/mxc reference or "attachment" marker is included anywhere. A reader of the txt/html export cannot tell a line was an image/file share versus a plain text message named "photo.jpg", and the actual media (especially encrypted media, where the URL is meaningless without the E2EE key bundled in `content.file`) is never exported or referenced.
### How to trigger
Export a room containing image/file messages in txt or html format; the messages show as plain filename text indistinguishable from a real chat message.
### Suggested fix
At minimum, prefix media rows with a type marker (e.g. "[Image] photo.jpg") in txt/html output, and note in the UI that attachments themselves are not included in the export.
---
---
_Filed from the September 2026 client audit (branch `lotus` @ 4bea4895)._
jared
added this to the Audit 2026-09 · Medium & Low milestone 2026-09-12 01:51:31 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Severity: low · Type: bug · Confidence: medium
Location:
src/app/features/room-settings/ExportRoomHistory.tsx:115-126, 194-208Problem
For
m.image/m.video/m.audio/m.filemessages,content.bodyis normally just the filename (e.g. "photo.jpg"), and that's all that ends up in the exported txt/html/json — themsgtypeis captured in the JSON payload'stypefield but is never surfaced in the human-readable txt/html output, and no URL/mxc reference or "attachment" marker is included anywhere. A reader of the txt/html export cannot tell a line was an image/file share versus a plain text message named "photo.jpg", and the actual media (especially encrypted media, where the URL is meaningless without the E2EE key bundled incontent.file) is never exported or referenced.How to trigger
Export a room containing image/file messages in txt or html format; the messages show as plain filename text indistinguishable from a real chat message.
Suggested fix
At minimum, prefix media rows with a type marker (e.g. "[Image] photo.jpg") in txt/html output, and note in the UI that attachments themselves are not included in the export.
Filed from the September 2026 client audit (branch
lotus@4bea4895).