-
Notifications
You must be signed in to change notification settings - Fork 12
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
Bots should not be considered when auto-naming rooms #446
Comments
I've split out the avatar bug; meanwhile this is really a 'Bots really shouldn't be considered when naming rooms' bug |
Therefore we need a convention for actually detecting which users are bots, so clients can hide them appropriately in situations like this. Calculating names serverside could help. |
I think this would require the spec being changed? My first thought was to detect if a bot was the result of integrations and then display it differently on the front-end, but this would be difficult to make persistent. I imagine you could preface all bot usernames with |
Alternatively, it might be useful to be able to configure a room to only consider certain accounts (or ignore certain accounts) when naming the room, which could be useful when chatting with someone with multiple accounts (or even if you yourself have multiple accounts). For example, if I have a DC room with matthew:matrix.org, matthew2:matrix.org, matthew:arasphere and uhoreg_test:matrix.org, I would probably want the room to be just called "Matthew", rather than "Matthew, Evil Matthew, Matthew, and uhoreg test" (or whatever it would name the room in that case). Probably somewhat related to #725. |
Steps to reproduce:
Paul
Paul and giphy
Paul
again but the icon reverts to a "P" instead of Paul's avatarExpected outcome:
Paul
because Giphy is a bot. The room preserves Paul's avatarThe text was updated successfully, but these errors were encountered: