We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From Matrix discussion this morning: we could say the Invite Receiver OCM Server MAY announce that it supports the invite paste flow:
[...]token=<token>[...]from=<fqdn>[...]
and MAY announce that it support the invite redirect flow:
The Invite Sender OCM Server MAY include a WAYF link in the Invite Message that is similar to a Public Invite Flow page, except that:
The text was updated successfully, but these errors were encountered:
As an alternative to the [...]token=<token>[...]from=<fqdn>[...] format we also discussed the ocm-invite://<token>@<fqdn> format. Which shall we pick?
ocm-invite://<token>@<fqdn>
Sorry, something went wrong.
Just on a call with @MahdiBaghbani now, we will implement the second one (ocm-invite://<token>@<fqdn>) in Nextcloud and then hope others will follow!
No branches or pull requests
From Matrix discussion this morning:
we could say the Invite Receiver OCM Server MAY announce that it supports the invite paste flow:
[...]token=<token>[...]from=<fqdn>[...]
and MAY announce that it support the invite redirect flow:
[...]token=<token>[...]from=<fqdn>[...]
in the URL query parameterThe Invite Sender OCM Server MAY include a WAYF link in the Invite Message that is similar to a Public Invite Flow page, except that:
The text was updated successfully, but these errors were encountered: