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

Checkout Tinode #237

Closed
armor009 opened this issue Jun 18, 2021 · 1 comment
Closed

Checkout Tinode #237

armor009 opened this issue Jun 18, 2021 · 1 comment

Comments

@armor009
Copy link

Tox and Tinode are very interesting and valuable projects. I feel they both can benefit from cross collaboration, support and a potential merger. Dev bandwidth can be pooled and both projects sped up. The server can have two modes - distributed open to public and distributed private personal use server mode. If both clients are trying to solve similar problems, why not merge efforts.

Disclaimer: I am not part of Tinode or Tox. Just someone who is looking for a chat server and chat client for his app's requirement. I found tox and tinode as good options. They all solve some parts of the problem. I see tinode stretched thin. Don't know about Tox's dev resource situation. If the two merge and work together, they will solve the problem they have set out to achieve faster

@nurupo nurupo closed this as completed Jun 18, 2021
@nurupo
Copy link
Member

nurupo commented Jun 18, 2021

Thank you for reaching out. Don't think we are interested in collaborating as the projects are rather different, with different goals and design architectures, e.g. federated vs p2p distributed. Tox developers are not interested in a federated solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants