Open regalialong opened 9 months ago
As far as I know this isn't really possible in Matrix, there has been an MSC about it but the answer ended up suggesting you just change your display name.
This will come off as naive but I can create a room, give it a topic and then convert it to a DM. Why wouldn't it be possible to do something like that programmatically over the bridge? What would be the difference between the bridge-managed DM rooms and the manually created rooms that'd not make it feasible?
This just sounds cursed. I think it may make more sense to have this available as a variable in displayname_template
.
That'd be a solution for pronouns but not for the profile biography.
That'd be a solution for pronouns but not for the profile biography.
You are asking for the addition of a new Matrix event. This is a bridge, why do you expect it to take care of that? Theres a repository for spec change proposals. As a matter of fact, "pronouns" and "biography" are a use of the feature, what you're referring to is extended user profile information. See https://github.com/matrix-org/matrix-spec-proposals/issues/3795.
I'm aware of the extensible profiles proposals, but reading the activity of it (and its sister proposal https://github.com/matrix-org/matrix-spec-proposals/pull/1769), it seems to me this will not happen very soon.
That's why I want the biography (and/or pronouns) attached to the direct message rooms that the bridge already manages (similarly how it sets username and avatar), as a topic.
That's not a "correct" solution but a workaround until extensible profiles are actually implemented. As far as I know, that shouldn't require another event.
Topic is already set for bridged guild channels, can direct message rooms not contain topics, is that my misunderstanding?
This might be too much to ask but Discord User profiles have a biography and pronouns under
user_profile
, just two strings, I would like to have those two exposed as direct message topic (since Matrix doesn't have extensible profiles), similar to channels.I looked into implementing it myself and I don't think discordgo's User exposes this, which means it would require a patch. The handwritten SQL makes it a little difficult for me to jump into the codebase and do it myself.
I can understand if this gets rejected because of the patch required or out of correctness.
Thanks!