Skip to content
New issue

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

Check capabilities of remote server in federated conversations #11850

Open
4 tasks
Tracked by #11271
Antreesy opened this issue Mar 18, 2024 · 2 comments · May be fixed by #12208
Open
4 tasks
Tracked by #11271

Check capabilities of remote server in federated conversations #11850

Antreesy opened this issue Mar 18, 2024 · 2 comments · May be fixed by #12208

Comments

@Antreesy
Copy link
Contributor

Antreesy commented Mar 18, 2024

ATM only 29-29 can be federated, but we need to check in future if new features are supported by both servers

  • Storing / reading:
    • federationsStore -> capabilities -> per token
  • Using:
    • useCapabilities wrapper to check room and decide: -> local capabilities or remote
@nickvergessen
Copy link
Member

This is done @Antreesy ?

@Antreesy
Copy link
Contributor Author

Now we're only limiting functionality at federated conversations, based on our local 'federation-v1'. Need to add some things for:

  • getting remote server capabilities and keep them per conversation / per remoteServer
  • adding a wrapper for @nextcloud/capabilities, and use relevant sources for local and federated rooms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🏗️ In progress
Development

Successfully merging a pull request may close this issue.

3 participants