Replies: 1 comment
-
Why not implement a view for registration tokens like Element Web did lately? Element Android and iOS both fall back to the ugly webpages at |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Your use case
Homeserver admins can configure their homeserver to require a registration token upon registration, a shared secret token that only allows some users to register. However, since Element isn't "aware" of this feature yet it doesn't prompt for the token on registration. Rather, it accepts the users registration details but then redirects them to the homeserver to enter the token.
This is frustrating for users who attempt to sign up to a host, only to be surprised by an additional requirement. Element is aware of all the registration flows, and could warn about future flows. My suggestion would be to implement a simple warning box when Element is going to redirect you to complete additional flows.
Have you considered any alternatives?
Implement element-hq/element-web#7275, which should hopefully implicitly warn. Given the current progress however, it seems like a intermediary PR to warn might be appropriate.
Additional context
As an example, a homeserver can be configured to have a set of registration flows like:
Beta Was this translation helpful? Give feedback.
All reactions