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

Distinct avatars per bridged service instance #275

Closed
HarHarLinks opened this issue Apr 6, 2022 · 2 comments
Closed

Distinct avatars per bridged service instance #275

HarHarLinks opened this issue Apr 6, 2022 · 2 comments
Labels
T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements.

Comments

@HarHarLinks
Copy link
Contributor

Is your feature request related to a problem? Please describe.
I think it's great to have the visualization of an avatar to distinguish things, e.g. using the default octocatbot to bridge a GitLab doesn't represent that properly.
Continuing that thought, this is even more interesting when e.g. your GitLab instance has a custom branded logo you can use.
This is especially important when multiple things are bridged in one room, but improves UX even with singular ones.

Describe the solution you'd like

  • Ability to configure avatars either at the config.yml level similar to the default avatar it currently has
  • and/or configure avatar at connection level, when creating a connection

Additional context
Related to #178

@Half-Shot
Copy link
Contributor

I'd like to have it so that each service could have it's own distinct user (go-neb) style for this use case, it's just a bit of a refactor job at the moment.

@Half-Shot Half-Shot added the T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements. label May 12, 2022
@justinbot
Copy link
Contributor

We ended up getting this with service bots (#573), each bot user can have a different avatar.

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