Matrix Extensible User Profiles — How Do We Get There?

More and more I find myself using the fediverse (based on ActivityPub) alongside Matrix, and the two protocols complement each other nicely in some ways. In other ways their differences seem needless and jarring, only getting in the way. I'd like to be able to offer my contacts the free choice of which protocol to use, depending on what kind of communication they intend (public-ish versus private or group-ish), without everything else being different — especially the user identifier/addressing but also many lesser issues such as the existence of user profiles.

I have long remained hopeful we'd get use profiles eventually. Conceptually it's not a big deal. So where are we now and where are we going?

I had been thinking there would have been enough demand from client makers to make this happen by now. Unfortunately, despite being on the wish list for nine years now, with sporadic contributions from many people interested, it's still stalled.

On the Spec Side

State of the spec. These seem to be the main issues:

Many more specific issues are linked to those.

Technical hurdles: one main blocker:

Can anyone comment from the spec perspective, design or implementation?

Client Design or Support

So, where do we go next? I'm interested to know if there's any working proof of concept in a client? I even created a profile room for myself manually a year ago, following one of the specs, hoping maybe some client would eventually see it.

Can anyone summarise from a client-app perspective?

(Maybe in the room. I'm raising the issue there.)

#matrix #awesomeFOSS #selfHosted

Follow/Feedback/Contact: RSS feed · Fedi follow this blog: @julian​ · use the Cactus Comments box above · matrix me · Fedi follow me · email me · Donate: via Liberapay All posts © Julian Foad and licensed CC-BY-ND except quotes, translations, or where stated otherwise