Frontend - Message threads

[nickvergessen]

• Overview at https://github.com/nextcloud/spreed/issues/1469
• Rough idea is that when a reply message or a message that has a reply is clicked, we filter the chat stream with that "thread" ID (root parent message).
• All newly written messages should be addresses to that root parent as well (needs a new API parameter, so that you can still reply within a thread for quoting and reactions)
• The UI of course needs to see a button to "go back" to the unfiltered list.

[sascha08-15]

+1 from me - I would love to see threads (similar to slack), not sure about the last point of the ticket tho (go back / unfiltered).

[jooooaah]

+1 whould be helpful in many ways

[Jacques-Olivier-Farcy]

We could use it everyday, must have!

[max-nextcloud]

UX wise I just used zulip for the first time and found the way they use topics instead of threads quite intuitive and maybe a bit simpler as right now I see no way of deep nested threads which for me is a plus.

[szaimen]

UX wise I just used zulip for the first time and found the way they use topics instead of threads quite intuitive and maybe a bit simpler as right now I see no way of deep nested threads which for me is a plus.

This reminds me of what I proposed in https://github.com/nextcloud/spreed/issues/2448 :)

[Antreesy]

Follow-ups:

• [x] Integrations (Files sidebar) support
• [ ] Restructure Shared items -> Details tab
• [x] update thread info from message polling
• [x] Specific message fetching (context + history => thread messages only, do not mix with general chat)
• [x] Parsing of messages to human-readable format
• [x] Focus error when passing to thread tab
• [x] Return state from thread tab
• [ ] Read marker in threaded view is semantically broken
• [x] Patch update threadIn from message polling
• [x] Thread creation action must be embedded with a reply action IMO
• [ ] Return from threaded view in Call mode given that top bar is not usable at that state