nextcloud / nextcloud/spreed

Combined file messages - follow-ups

Open
#19,371 0 comments 0 reactions 1 assignee View on GitHub

@Antreesy is already working on this.

Since Sep 11, 2026.

bug feature: frontend 🖌️ feature: upload & shares & voice 📤🎙️
Dominant language
JavaScript
Stars
2.2k
Forks
586
Avg merge
18h 27m
Merged PRs (30d)
333

Description

  • Ref #11411
  • Web PRs:
    • #19005
    • #19020
    • #19004
    • #19040
    • #18989

Missing / relevant features:

  • Rendering support
    • single file share #19430
  • Threads support
    • every posted file in a batch creates a thread - 2nd+ files should be replies
    • replies are hidden in main context view
    • replies are not combined in thread context view
    • temporary messages missing indication
  • Reactions support
    • on non-last files ignored, only last message reactions are shown
    • individual reactions can no longer be set on non-last files
  • Deletion support
    • only last file message can be removed
    • should be deleted one by one
    • single file deleted/unshared on Files side
  • Edit support
    • edit caption only works on the last file
    • adding caption on non-last file will break the grouping
    • edit file itself?
  • File actions support
    • 'Go to file/folder', 'Download' always target the first file
    • Individual files can be targeted from Viewer only
  • Read receipts support
    • only last file read receipts are visible
  • Better upload support
    • retry failed uploads - might no longer be combined
    • race condition between userA sharing and userB posting
  • Voice messages support
    • VM excluded from combining entirely
    • VM should not have a caption?
  • Reply/Reply privately/Forward support
    • last file is targeted for replying/forwrding
  • Navigation support
    • focusMessage feature needs workarounds
  • Backward compatibility:
    • An old client without the combining logic will see each message as a separate normal message, with full per-file actions available.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.