Skip to content
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

Please support MSC4171 #3522

Open
xundeenergie opened this issue Sep 23, 2024 · 0 comments
Open

Please support MSC4171 #3522

xundeenergie opened this issue Sep 23, 2024 · 0 comments
Labels
T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements

Comments

@xundeenergie
Copy link

Your use case

What would you like to do?

I'm using mautrix-signal bridge, and private chatrooms are named by the signal-user AND the bridge-bot-user.
I discussed this in the chatroom for mautrix-signal bridge and realizied, that element X does not support MSC4171.

In legacy Element the rooms are named only after the Signal-user. That's what i expect.

Why would you like to do it?

Consistent room namings in bridged rooms.

How would you like to achieve it?

--

Have you considered any alternatives?

Think it is only necessary, that element x has to implement MSC4171

Additional context

Element X V0.6.3

Are you willing to provide a PR?

No

@xundeenergie xundeenergie added the T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements label Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements
Projects
None yet
Development

No branches or pull requests

1 participant