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

Private room name alias (for rooms with the same name) #4080

Open
Neui opened this issue Sep 25, 2021 · 2 comments
Open

Private room name alias (for rooms with the same name) #4080

Neui opened this issue Sep 25, 2021 · 2 comments
Labels
T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements

Comments

@Neui
Copy link

Neui commented Sep 25, 2021

Your use case

What would you like to do?

I would like to set for an room an private room name that will be shown instead for me instead of the normal one. This will be private, so no other will see it. This means this is stored either app/client only or in the account.

Why would you like to do it?

I joined multiple IRC rooms, where the title of the room is simply the channel name. However, if you join multiple rooms with the same name but different IRC servers, they all have the same room name and it is not easy to differentiate between them (for context).

How would you like to achieve it?

I thought of an settings entry in the room settings. Maybe a new page "private settings"? Not entirely sure what would be good UX.

Have you considered any alternatives?

Maybe display (in small letters) after the room name the primary server of the room if it detects it shares with an room name (or very similar just in case things like casing or spacing makes them different).

Additional context

No response

@Neui Neui added the T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements label Sep 25, 2021
@KnightWhoSaysNeeeowWumPing

The issue vector-im/element-web#3015 over at element-web seems to address the same. (See also MSC3015)

@Mart-Bogdan
Copy link

Would be nice to implement that spec.

Even in draft form, it has name already defined, that can already be used by implementation.

Clients should use org.matrix.msc3015.[m.state.type].override for room account data key instead of proposed, while this MSC has not been included in a spec release.

I'm new to Matrix. So correct me if I am wrong. But if I understand it correctly -- you can store arbitrary data there? So it can be implemented even in client specific way then.

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

3 participants