-
Notifications
You must be signed in to change notification settings - Fork 65
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
Allow multiple logins #237
Comments
Is there any reason why you want to run 2 instances of venom on the same account? |
I guess he talks not about two instances on the SAME account but about two different instances where it's possible to talk under two different accounts. |
I'd vote to have such feature too. |
Some people prefer to have multiple separate handles, e.g. one for work, one for family, etc. In desktop skype it is possible to have several instances running (with --secondary), each for different login. It would be nice to have such feature available in Tox as well. Especially considering that separate identities have to do with privacy, and Tox is a privacy-oriented messenger. |
Hmm. Well the secondary flag sounds interesting. Running more than 2 tox clients on the same machine may also lead to problems with toxs lan discovery, apart from that, it should work. |
Why not prompt for correct session? |
This would complify things. Not impossible but I don't think the result will justify the effort |
Or you can ''just'' have the multiple tox instance running in the same Venom instance like Wire does, then you just bind signal to the correct instance. When opening a tox uri you show a prompt and on response you bind the open uri call to the correct instance :) |
Just thought that I'd link to the same discussion that has been happening at qTox for a very long time: |
Running venom with different tox data file than that of the already running instance
should create a new instance instead of bringing up the window of the already running one.
The text was updated successfully, but these errors were encountered: