Extensible Profiles. (SPEC-93)

[matrixbot]

Documentation: https://docs.google.com/document/d/1jXMElbQR-5ldt_yhWuqzLFBO3-TEJWhRyWF5Y_gGSsc/edit#heading=h.h8vj3b7rllw9
Author: @erikjohnston

We need to decide how to do user profiles, and all the associated "persona" fun, or whatever that was called (e.g., displaying different info to different people).

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

(Reported by @erikjohnston)

[matrixbot]

Jira watchers: @erikjohnston @ara4n

[matrixbot]

This is something we are interested in as well. Any chance you could up the prio?

-- Stefan Ålund

[matrixbot]

Yup, we need it too in the very near future as part of implementing group ACLs at last (and needing somewhere to track what users are in).

-- @ara4n

[matrixbot]

Thanks!

-- Stefan Ålund

[ara4n]

We still need extensible profiles :(

@erikjohnston started work on this a while back at https://docs.google.com/document/d/1jXMElbQR-5ldt_yhWuqzLFBO3-TEJWhRyWF5Y_gGSsc/edit but the implementation has got displaced by other activity.

[expertalex]

Hello.

Any news?

[vranki]

Came here from discussions why bridged users have the bridge name embedded in their nicknames instead of a separate field that could be displayed by client separately if needed. For example (IRC) or (Telegram) after the nick.

User normally doesn't care what service is used by anothers and for example tab-completing a nickname includes the bridge name which is completely wrong.

So please, include the bridge name in the extensible profiles so we could have clean nicknames and display the bridge separately as needed.