Update 'MultiDeviceInitialization'
parent
f9295c44f0
commit
edf11e9ca2
@ -5,6 +5,6 @@ existing profile. We assume all clients use a common tox profile format, though
|
||||
most complement the Tox profile with an ini file or similar.
|
||||
|
||||
If you just copy a profile from one device to the next it will not work as
|
||||
you cannot have 2 profiles with the same keys online at the same time. We could have a simple utility that rekeys a profile and creates a new ToxID, so that we could copy a profile and rekey it. Then the new client running the rekeyed profile could send a DHT announcement updating to the new ToxID.
|
||||
you cannot have 2 profiles with the same keys online at the same time. We could have a simple utility that rekeys a profile and creates a new ToxID, so that we could copy a profile and rekey it. Then the new client running the rekeyed profile could send a DHT announcement updating to the new ToxID. The old keys would be added to the new profile's friends list.
|
||||
|
||||
The profile rekey utility could also do other things at the same time, like empty the TCP_RELAYS section of the profile if desired.
|
||||
|
Loading…
Reference in New Issue
Block a user