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

Support hiding server part of username in message scrollback #71

Closed
primalmotion opened this issue Mar 24, 2023 · 2 comments
Closed

Support hiding server part of username in message scrollback #71

primalmotion opened this issue Mar 24, 2023 · 2 comments
Milestone

Comments

@primalmotion
Copy link

Hey! thanks for the client! looks super promising (though I will wait for notification support to daily drive it :) )

Would it be possible to add an option to only show the username without the server in the message view? (like @user instead of @user:with-super-long-annoying-server-name.io)

@ulyssa ulyssa added this to the v0.0.8 milestone Mar 29, 2023
@ulyssa ulyssa changed the title support for hidding server parts of username in message view Support hiding server part of username in message scrollback Mar 29, 2023
@benjajaja
Copy link
Contributor

benjajaja commented May 10, 2023

I have some users that have usernames like @bot_32934879:bridge.com but with readable display-names like John Smith. It would be nice if we could chose what to display, in addition to hiding the server part, also showing only the display-name. So far I've gotten around this by using the "users" config option to set some aliases, but the aliases don't not get used e.g. for @^P completion.

And maybe in the future, only hiding the server part if it matches the room's server, or your own username's server part.

@ulyssa
Copy link
Owner

ulyssa commented Jul 7, 2023

I've added a new "username_display" setting, which can be set to "username", "localpart", or "displayname". There seems to be some unfortunate interaction between the member lazy loading I added in #62 and showing display names. I'm not sure how I want to resolve that yet, so I've left the default value as "username" for the time being until I can determine how to fix this.

@ulyssa ulyssa closed this as completed Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants