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

Extensible Profiles. (SPEC-93) #3795

Open
matrixbot opened this issue Jan 19, 2015 · 26 comments
Open

Extensible Profiles. (SPEC-93) #3795

matrixbot opened this issue Jan 19, 2015 · 26 comments
Labels
feature Suggestion for a significant extension which needs considerable consideration kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal

Comments

@matrixbot
Copy link
Member

matrixbot commented Jan 19, 2015

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
Copy link
Member Author

Jira watchers: @erikjohnston @ara4n

@matrixbot
Copy link
Member Author

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

-- Stefan Ålund

@matrixbot
Copy link
Member Author

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
Copy link
Member Author

Thanks!

-- Stefan Ålund

@matrixbot matrixbot added the p1 label Oct 28, 2016
@matrixbot matrixbot changed the title Profiles. Profiles. (SPEC-93) Oct 31, 2016
@matrixbot matrixbot added the feature Suggestion for a significant extension which needs considerable consideration label Nov 7, 2016
@ara4n ara4n changed the title Profiles. (SPEC-93) Extensible Profiles. (SPEC-93) Feb 2, 2018
@ara4n
Copy link
Member

ara4n commented Feb 2, 2018

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
Copy link

Hello.

Any news?

@vranki
Copy link

vranki commented Sep 6, 2018

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.

@Half-Shot
Copy link
Contributor

@vranki absolutely agree that the best way forward to show bridged users is to put a flag inside the profile.

For now, bridges are encouraged to put their users inside groups. All matrix.org IRC users are in the group/community according to the network they are part of.

@awesome-manuel
Copy link

Where would those profiles be stored? On identity servers?
Maybe E2EE can be used to present a different level of details to specific users.

@heitorPB
Copy link

It would be nice if some of the fields (e.g. phone number, address, email, etc) would be private.

Telegram handles this in an interesting way: only my contacts can see my phone number, but anyone can send me a message with my @username.

@ara4n
Copy link
Member

ara4n commented Jan 12, 2019

heads up that #1769 may replace this.

@MayeulC
Copy link
Contributor

MayeulC commented Jan 21, 2019

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

This also makes me think that there might be a need for access control on some profile data as well, like only allowing members of some rooms/communities to see parts of it.

Possible use cases:

  • Full name/custom display name, community or room-based.
  • Detailed bio that caters to a specific group, like work or project-specific information. Think like sharing multiple phone numbers or (mail/physical) addresses.

@ajvsol
Copy link

ajvsol commented Jan 28, 2019

Found this issue when discussing Signal's Encrypted Profiles implementation, might be worth checking out.

@Mikaela
Copy link
Contributor

Mikaela commented Feb 10, 2019

Could rel=me be also supported by this? If I link from my Matrix account to my homepage which links to my Matrix account, show a green checkmark or something similar to show that the two are verified to be the same person. This is how Mastodon does it, example.

@Mikaela
Copy link
Contributor

Mikaela commented May 15, 2019

It looks like I have already commented about rel=me without getting any feedback, so I will append on it.

Could clients or homeservers be recommended to implement rel=me checking on top of extensible profiles? If I link to mikaela.info from my profile, then I wish something to check mikaela.info in case it has a rel=me link back to my Matrix account (currently <a href="https://riot.im/app/#/user/@mikaela:privacytools.io" rel="me">@mikaela:privacytools.io on Riot/Matrix</a>) and seeing it tells the client that I am verified as the owner of that domain or Mastodon account or Gitlab account or anything else implementing rel=me.

My usecase is that currently there are several people who are registered on a high amount of homeservers and thus it would be easy to troll by pretending to be them by simply registering on yet another homeserver with the account they usually use and no one would be the wiser as those people could well have registered on that homeserver and thus be that user.

Do you see this as in-scope for this issue or should I open a new one?

@homebeach
Copy link

Profiles could have also something like "liked by: " and Facebook style friends information. With likes list, there could be dating rooms where you could like people's profiles and mutual like would result a match. Clients could implement Tinder-style left and right swipes for such rooms. Friends list would allow you to set different privacy and visibility settings for your profile depending on who is user your friend or not.

@MayeulC
Copy link
Contributor

MayeulC commented Jul 29, 2019

@Mikaela, I would like to note that in light of matrix-org/matrix-spec#246, and matrix-org/matrix-spec#220, it think it would be best to use the URL to pin the public key. Of course, #1769 will likely replace the current issue, and for this to happen we need matrix-org/matrix-spec#245 (MSC #1777). Going forward, if identities were truly distributed, one would only need the public key (we could do it with the public key and one/more "seed" servers for now :))

@Mikaela
Copy link
Contributor

Mikaela commented Jul 30, 2019

What is the public key I should pin in my website, how do I get it?

@auscompgeek
Copy link
Contributor

From discussion in #synchronicity:mozilla.org:

the code sheriffs would have a better life if we'd see a user's [...] time zone

Seems to me that local time zone would be a good fit for a profile field (similarly to Slack).

@ghost

This comment was marked as off-topic.

@predictron-cloud

This comment was marked as off-topic.

@jpcastro4

This comment was marked as off-topic.

@Haui1112
Copy link

Any updates on this?

@ew-at-vier
Copy link

We also would benefit from extensible user profiles.

@DonPrus
Copy link

DonPrus commented Mar 20, 2024

This is blocking me from using Matrix in some local communities.
May be enable just basic key-value with some links? So I can update it with crons or webhooks.

Here are a couple of examples of what I want to use them for. Specify the curator who is responsible for the person in the profile. Indicate the last time you were online in the game, maybe write down some regalia :)

@ara4n
Copy link
Member

ara4n commented Sep 24, 2024

May be enable just basic key-value with some links?

This is progressing over at #4133 which is now in FCP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Suggestion for a significant extension which needs considerable consideration kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
Projects
None yet
Development

No branches or pull requests