Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

Groups: Flair for users #118

Open
giomfo opened this issue Oct 6, 2017 · 3 comments
Open

Groups: Flair for users #118

giomfo opened this issue Oct 6, 2017 · 3 comments

Comments

@giomfo
Copy link
Member

giomfo commented Oct 6, 2017

Flair is a series of badges after the user’s (disambiguated) display name.

By default, we apply flair if you are a member of a group to which the current room belongs. E.g. if you’re a member of the Matrix core team, and Matrix HQ is part of the Matrix core team group, then your flair will be automatically visible when entering it by default.

We suggest letting users override which flair is visible per-room though (in MemberInfo for that room, or as a dialog box when joining the room) TBD.

Do we limit the number of flairs? Either arbitrary limit of 3 or whatever TBD

@denyeo
Copy link

denyeo commented Oct 20, 2017

I think flairs will be particularly important for subgroup/labels, to differentiate users within the same group. edit: I've become aware that flairs seem to be being implemented only for Groups (e.g. matrix-dev) at this time, but I'd like to bring up the case of flairs for subgroups (e.g. matrix-dev Core Contributors).

discord roles

For reference, here is how Discord displays roles (equivalent to Matrix subgroups?). Roles have priorities and colours in Discord, and the highest-ranked role of a user determines the colour of their username. This username colouring makes for a handy reference system (e.g. in this case, learners of Japanese can tell at a glance which users are native speakers or advanced learners of the language).

There are UI issues with colouring usernames, so the alternative giomfo mentioned of displaying the top 3/however many flairs is a good idea.

@turt2live
Copy link
Member

Related: element-hq/element-web#5379

@giomfo
Copy link
Member Author

giomfo commented Feb 4, 2018

The flair added to the user’s display name in the room history is finally defined by crossing the 2 following information:

  • The related communities defined in the room settings. The room owners have to set these communities to show flair for them.
  • The publicised communities for the room members. Each user has to define his community flair in the application settings, to display them in rooms configured to show it.

In the mobile application, we display no more than 3 flair.

Riot Android displays the full list of flair when the user clicks on them.
TODO: this improvement should be added in Riot iOS

giomfo added a commit to matrix-org/matrix-ios-sdk that referenced this issue Feb 4, 2018
MXRestClient: Add the method to get the publicised groups for a list of users.
MXSession: Cache the publicised groups of the matrix users in order to limit the server requests.

element-hq/riot-meta#118
giomfo added a commit to matrix-org/matrix-ios-kit that referenced this issue Feb 4, 2018
MXKRoomDataSource: Force a refresh on flair settings change.
MXKRoomBubbleCellData: keep update the flair of the sender.
MXKRoomBubbleTableViewCell: Display the sender flair if any

TODO: display the full flair list when the user clicks on the displayed flair.

element-hq/riot-meta#118
giomfo added a commit to element-hq/element-ios that referenced this issue Feb 4, 2018
Force the matrix session to refresh the cached data related to the publicised groups of the users when the application enters in foreground

element-hq/riot-meta#118
giomfo added a commit to matrix-org/matrix-ios-sdk that referenced this issue Feb 5, 2018
giomfo added a commit to matrix-org/matrix-ios-kit that referenced this issue Feb 6, 2018
by managing the related groups of a room at the RoomDataSource level instead of at the bubble level

element-hq/riot-meta#118
giomfo added a commit to element-hq/element-ios that referenced this issue Feb 6, 2018
Display more details on the user's group (avatar, id)

element-hq/riot-meta#118
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants