Skip to content

Client Feature improvements#3197

Open
MTRNord wants to merge 1 commit intomainfrom
MTRNord/client-features
Open

Client Feature improvements#3197
MTRNord wants to merge 1 commit intomainfrom
MTRNord/client-features

Conversation

@MTRNord
Copy link
Contributor

@MTRNord MTRNord commented Feb 3, 2026

Description

  • Adds basic feature validation when building
  • Adds the oidc feature which refers to the new MAS style login
  • Add a list explaining the features to the template
  • Add proper formatting to the user-visible text

Related issues

Resolves #3196, #3186

Role

Website WG :)

Timeline

whenever

Signoff

see Commits :)

…aining the features to the template and add proper formatting

Signed-off-by: MTRNord <MTRNord@users.noreply.github.com>
@MTRNord MTRNord requested a review from a team as a code owner February 3, 2026 11:20
@MTRNord MTRNord added ecosystem Adding and removing ecosystem projects aesthetic Visual inconsistencies or improvements labels Feb 3, 2026
{% elif feature_name == "sso" %}
Legacy SSO
{% elif feature_name == "oidc" %}
OIDC
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TIL its named OAuth2 in spec... Yet everyone talking about it calls oidc...

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"OIDC native" turned out to marketing speech (admittedly it rolls off the tongue a bit easier, e.g. https://areweoidcyet.com/), but concessions have been made in the meantime.

- voip_jitsi: Jitsi-based group calls
- threads: Threading support
- sso: Legacy Single Sign-On (m.login.sso)
- oidc: Native OIDC/OAuth 2.0 authentication (Matrix Authentication Service, added in spec 1.15)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure about namedropping MAS since that's just an implementation. link to spec if clarification necessary?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well it is the one thing most people seem to know it by. I agree with linking to spec though. But I feel like most people will still confuse it with the legacy sso :/ I guess we will find out.

@@ -1,3 +1,45 @@
{# Client macros for the Matrix.org website Features Schema (all boolean values):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
{# Client macros for the Matrix.org website Features Schema (all boolean values):
{# Client macros for the matrix.org website Features Schema (all boolean values):

#2966

@@ -1,3 +1,45 @@
{# Client macros for the Matrix.org website Features Schema (all boolean values):
- e2ee: End-to-end encryption support
- spaces: Matrix Spaces support
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what counts as "support" though?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unclear. This existed before with unclear definition :/

@HarHarLinks
Copy link
Collaborator

I added #3186 to the list of issues resolved by this PR which technically it does. Yet we still need to add the OIDC flag to existing clients that support it. Are you planning this in this PR? Otherwise we need a followup task.

@MTRNord
Copy link
Contributor Author

MTRNord commented Feb 3, 2026

I added #3186 to the list of issues resolved by this PR which technically it does. Yet we still need to add the OIDC flag to existing clients that support it. Are you planning this in this PR? Otherwise we need a followup task.

I would prefer to focus on the technical "framework" here first and add the new features in a new PR so that we dont block on the maintainer feedback loop

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

aesthetic Visual inconsistencies or improvements ecosystem Adding and removing ecosystem projects

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix casing of the clients feature table

2 participants