Features
Attachments, comments and history
What hangs off a card, and what the server writes on its own.
Comments
Markdown, with images pasted straight into the composer. They stay outside the board payload: the card on the board shows only the count, and the body of the conversation arrives when the card is opened.
Pasting a screenshot uploads the image before the comment exists: the composer needs the URL to write it into the Markdown. The attachments are born loose, and the attachmentIds field of creation binds them to the comment.
Attachments
- The file name is generated by the server. The original name is kept as metadata and comes back in
Content-Disposition, but it never becomes a path on disk. - The type is detected from the magic bytes, not from the extension: a
.pngthat is an executable does not pass. - The file is served `inline`, with sandbox and `nosniff`: an attached HTML does not run on the application's domain.
- Uploading can be restricted to images, or turned off entirely, in Settings; and the container can veto that from above.
History
Every column change becomes a record, with the name the column had at that moment. Renaming or deleting the column afterwards does not rewrite the past.
There is no history write route
The record is written by the server, in the same transaction that changes the column, along the three paths that change it: creating the card, moving it, and editing it with another column. Reordering within the same column writes nothing.