A thread can be opened from a message (#80) and continued, but there is no way to see which threads a room has. Element has a Threads panel per room, which is how anybody finds a conversation they were part of yesterday - a thread whose root has scrolled past is currently unreachable.
/_matrix/client/v1/rooms/{roomId}/threads is the endpoint.
Done looks like: a room lists its threads, newest activity first, with unread state per thread.
A thread can be opened from a message (#80) and continued, but there is no way to see which threads a room *has*. Element has a Threads panel per room, which is how anybody finds a conversation they were part of yesterday - a thread whose root has scrolled past is currently unreachable.
`/_matrix/client/v1/rooms/{roomId}/threads` is the endpoint.
**Done looks like:** a room lists its threads, newest activity first, with unread state per thread.
A threads button lists what a room has going on beside the main conversation, newest first, with the reply count and whether you are in it; pressing one opens the thread panel. include=all is sent rather than left to the default the spec defines, because Conduit treats the parameter as required and answers M_BAD_JSON without it — two of the five rooms tested here could not list their threads at all until that was found.
Finished — https://git.salastil.com/Salastil/nobilis/commit/a59b355 and https://git.salastil.com/Salastil/moho/commit/da09eed
A threads button lists what a room has going on beside the main conversation, newest first, with the reply count and whether you are in it; pressing one opens the thread panel. `include=all` is sent rather than left to the default the spec defines, because Conduit treats the parameter as required and answers M_BAD_JSON without it — two of the five rooms tested here could not list their threads at all until that was found.
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.
A thread can be opened from a message (#80) and continued, but there is no way to see which threads a room has. Element has a Threads panel per room, which is how anybody finds a conversation they were part of yesterday - a thread whose root has scrolled past is currently unreachable.
/_matrix/client/v1/rooms/{roomId}/threadsis the endpoint.Done looks like: a room lists its threads, newest activity first, with unread state per thread.
Finished — https://git.salastil.com/Salastil/nobilis/commit/a59b355 and https://git.salastil.com/Salastil/moho/commit/da09eed
A threads button lists what a room has going on beside the main conversation, newest first, with the reply count and whether you are in it; pressing one opens the thread panel.
include=allis sent rather than left to the default the spec defines, because Conduit treats the parameter as required and answers M_BAD_JSON without it — two of the five rooms tested here could not list their threads at all until that was found.