Open imv opened 10 years ago
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?)
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. 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.
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.
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: https://github.com/qTox/qTox/issues/1018
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.