Hugh Nimmo-Smith

I see #22 has been merged. @lewyuburi do you have any plans to do a new npm release?

@erlend-sh Good suggestion, thank you - I've added https://github.com/vector-im/oidc-playground/issues/3 to track this.

Draft implementation in matrix-js-sdk: https://github.com/matrix-org/matrix-js-sdk/pull/2398 Draft implementation in matrix-react-sdk: https://github.com/matrix-org/matrix-react-sdk/pull/8681

~~I've had an initial go at Synapse support in https://github.com/matrix-org/synapse/pull/12924~~. Matrix Authentication Service support within it's compatibility layer is in https://github.com/matrix-org/matrix-authentication-service/pull/221

I wasn't sure if this should be marked as T-Enhancement or T-Task?

With regards to all the sites where errors are not handled. If it is the accepted design pattern is that a consumer of the API should register a global `unhandledrejection...

With regards to design review - This PR adds a new section to the user settings screens: in the case that the homeserver is OIDC enabled and the delegated OIDC...

This was a speculative PR on my part, so do please dismiss if you wish. It is a step towards https://github.com/matrix-org/matrix-js-sdk/pull/2291 which I believe has higher value as it identifies...

Cleaning up this stale PR. I would still advocate for the application of the `@typescript-eslint/no-floating-promises` rule on this project as it forces the explicit handling of promises.

Cleaning up this stale PR. I would still advocate for the application of the `@typescript-eslint/await-thenable` and `@typescript-eslint/no-misused-promises` rules on this project.