Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Include a room type on all new rooms #569

Closed
BurnyBoi opened this issue Aug 24, 2022 · 1 comment
Closed

Include a room type on all new rooms #569

BurnyBoi opened this issue Aug 24, 2022 · 1 comment

Comments

@BurnyBoi
Copy link

BurnyBoi commented Aug 24, 2022

Is your feature request related to a problem? Please describe.
Now that non-chat clients like MinesTRIX and others are being made, there is a benefit to knowing what each room is made for in order to know which to show on the UI (and where). Currently, rooms made with Element have no type specified like MinesTRIX does for example. This means if a non-chat client wants to know what rooms were made in Element and other clients designed to make chatrooms, it has to just blindly assume all rooms with no type are "chatrooms."

Describe the solution you'd like
Include a type in the content section of m.room.create events to specify that a room is intended to be a "chatroom." (or whatever term makes sense for Element and the like). Once implemented, suggest developers of other Matrix chat clients to include it as well.

Describe alternatives you've considered
Blindly assume all rooms with no type were made in Element and other chat clients.

@SimonBrandner
Copy link

it has to just blindly assume all rooms with no type are "chatrooms."

Not necessarily - we could codify that no room type = chat room (matrix-org/matrix-spec-proposals#3827 already sort of this though only for a specific endpoint)

Anyway, this feels more like a https://github.com/matrix-org/matrix-spec issue...

@element-hq element-hq locked and limited conversation to collaborators Sep 2, 2022
@kittykat kittykat converted this issue into discussion #579 Sep 2, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants