-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
we should kill off registration fallback #7676
Comments
I can confirm that it was working, but today it does not work anymore. At least Element Android still relies on it if a registration stage is unknown and can't be handled natively |
per matrix-org/matrix-spec-proposals#2411 (comment): are you sure? |
for the record, the reason registration fallback is broken (and has been since at least #4334 / Synapse 0.34) is that it relies on the old |
I know this is an old topic, but I searched for this as my server is using token registration, which is working in Element Web, but not Element Android. When trying to register a new user with Element Android, it uses the registration fallback (which now returns 404). This breaks token registration completely for me. Has this been considered? Of course, implementing element-hq/element-android#8192 would also make my concerns go away :D |
Yes, these APIs are nonstandard and undocumented. |
https://matrix.org/_matrix/static/client/register is a thing which exists, but as per #6709, is broken, and as per matrix-org/matrix-spec-proposals#2411, is unspecced. I think we should remove it.
The text was updated successfully, but these errors were encountered: