-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proper room management #19
Comments
Can we also maybe automatically put the rooms into a predefined space? |
Yep, this is planned :)
…On Sat, Jan 22, 2022 at 10:34 PM Abin Simon ***@***.***> wrote:
Can we also maybe automatically put the rooms into a predefined space?
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBIYQVGC5PCA4OJ4ASFJPTUXOOOVANCNFSM5KTUPRCQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Just a suggestion on how the messages show up in the rooms. I am not sure if you are waiting for the threading MSC to officially land, but maybe having some context on which highlight a message belongs to in the chat would be nice(root comment + replies .. related: #17). As of now, it just looks like random messages in the room. |
Here's what the replies look like on my version of element ( The actual highlights don't display as messages yet, but I anticipate that they will if extensible events (matrix-org/matrix-spec-proposals#1617) will work as described in the spec. |
Oh, I was on |
I think right now, the thread-aware version of Element doesn't allow unknown events to be thread roots. That's why they just show up on their own. They do have a |
Give the ability to create rooms, rename them, all of the good stuff.
The text was updated successfully, but these errors were encountered: