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

Allow multiple logins #237

Open
imv opened this issue Aug 14, 2014 · 9 comments
Open

Allow multiple logins #237

imv opened this issue Aug 14, 2014 · 9 comments

Comments

@imv
Copy link

imv commented Aug 14, 2014

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.

@naxuroqa
Copy link
Owner

Is there any reason why you want to run 2 instances of venom on the same account?
This would break any support for opening tox:// uris (Which session would it open it?)

@romansimakov
Copy link

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.

@romansimakov
Copy link

I'd vote to have such feature too.

@imv
Copy link
Author

imv commented Aug 14, 2014

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.
I'm talking about separate accounts of course, hence "with different tox data file". You can do that in Toxic btw.
As a provisional behaviour, tox:// urls can be handled from the default identity (.config/tox/data).
Although this feels hacky, so probably multiple logins warrant more discussion if they are to be implemented.

@naxuroqa
Copy link
Owner

Hmm. Well the secondary flag sounds interesting.
I could do that, but the secondary instance would have some minor drawbacks (tox:// uris will get opened in the primary instance)

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.

@ghost
Copy link

ghost commented Aug 14, 2014

Why not prompt for correct session?

@naxuroqa
Copy link
Owner

This would complify things. Not impossible but I don't think the result will justify the effort

@naxuroqa naxuroqa added this to Ready for development in v0.4.0 Apr 12, 2018
@SkyzohKey
Copy link

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 :)

@naxuroqa naxuroqa removed this from Ready for development in v0.4.0 Jun 19, 2018
@physkets
Copy link

Just thought that I'd link to the same discussion that has been happening at qTox for a very long time:
qTox/qTox#1018

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

No branches or pull requests

5 participants