Devon HudsonandClaude Opus 5.5 40347060d8 Accept a username template for room invites ...

An invite's `username` may be a template with one `{random}`, which the
minted token stores as is and registering fills in. The endpoint checks
a template by filling `{random}` with letters and digits and running the
registration policy on the result, so a template the policy refuses is a
400 when inviting rather than an invite that can't register. A template
with more than one `{random}` is a 400. Every invite may carry the same
template, and the name it fills in to is only known when registering, so
the repeated-username and username-taken checks apply to literal
usernames only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RkxQWj8RAKd7iZ1JQtXdxm

2026-10-14 21:27:42 +00:00

..

index.html

Load Swagger UI earlier

2025-02-11 19:16:59 +01:00

oauth2-redirect.html

Host a Swagger UI both in the static documentation and by the server

2024-08-01 15:17:14 +02:00

spec.json

Accept a username template for room invites

2026-10-14 21:27:42 +00:00