Moritz Poldrack

Leaving said private chat is also not possible: ``` level=info msg="User requested to leave join" room_id="!RooMIdeNTIfIEr:server.com" user_id="@user:server.com" level=error msg="Failed to leave room" error="user \"@user:server.com\" is not a member of room...

Since these are private chat rooms it's not that easy to rejoin…

okay, now for the scariest part…

A number of these can probably be added to the [`.git-blame-ignore-revs`](https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view) file

Note: I do not feel comfortable doing the UI part, so I would request assistance on that part.

In order to enhance the user experience of offen when an OIDC provider is available by implementing Single Sign-On (SSO) with OpenID Connect (OIDC), this way users can seamlessly log...

Thank you for the review. In OIDC something like this is returned: ```json { "iss": "https://id.moritz.sh/application/o/codimd/", "sub": "1af2deecbcff74e06f140b10373d0907f3436f0c9451fe24df5c5e5963ebeb29", "aud": "b7bFpUvCVbUN00eNCFrNI6dyaYpCJcwuWT2gtCzm", "exp": 1704413169, "iat": 1704411369, "auth_time": 1704411369, "acr": "goauthentik.io/providers/oauth2/default", "amr": [...

> should a deployment support users signing in with OIDC and default user accounts, or should a deployment always use a single method I would argue that it's the latter....

I will likely be able to get back to it in May :)

Since this is technically a DoS vulnerability, I just took the liberty of calculating its score.