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

A way to distinguish guest or AS-ghost room members (SPEC-361) #161

Open
matrixbot opened this issue Feb 29, 2016 · 3 comments
Open

A way to distinguish guest or AS-ghost room members (SPEC-361) #161

matrixbot opened this issue Feb 29, 2016 · 3 comments
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol

Comments

@matrixbot
Copy link
Member

It would be useful if a client can distinguish at a glance of the members list (i.e. the set of m.room.member) events which users are guests, which are ghosts of which ASes, etc...

One way that this could be done easily is by adding another profile-like field, to be supplied along with the displayname and avatar_url fields there.

(Imported from https://matrix.org/jira/browse/SPEC-361)

(Reported by @leonerd)

@matrixbot
Copy link
Member Author

Jira watchers: @leonerd @ara4n

@matrixbot
Copy link
Member Author

Yup. this could be done by extensible profile data, namespaced to the bridge itself, but i'm a bit worried that it's trivially spoofable and unnecessarily 'magic'. It feels slightly nicer to me if the AS was to 'sign' the user into participating in a given usergroup - i believe Erik's plan for user groups is some kind of crypto-based mechanism where the group owner signs the members to prove their membership. Then there's no spoofing, and we can put whatever metadata we like on the group itself?

-- @ara4n

@matrixbot matrixbot changed the title A way to distinguish guest or AS-ghost room members A way to distinguish guest or AS-ghost room members (SPEC-361) Oct 31, 2016
@matrixbot matrixbot added spec-bug Something which is in the spec, but is wrong enhancement A suggestion for a relatively simple improvement to the protocol and removed spec-bug Something which is in the spec, but is wrong labels Nov 7, 2016
@xelra
Copy link

xelra commented Feb 22, 2017

It would be really great if this could be implemented. As it stands, the bridging situation is really awkward, especially when there are 2 bridges involved, because you just can't tell with whom you're talking.

I'm constantly finding myself, browsing the web (GitHub), just to figure out who that is.

@turt2live turt2live added the A-Client-Server Issues affecting the CS API label Feb 7, 2019
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol
Projects
None yet
Development

No branches or pull requests

3 participants