From edf11e9ca2e1c5a9bd94a222e97cea735cf3c78a Mon Sep 17 00:00:00 2001 From: emdee Date: Thu, 22 Sep 2022 04:57:13 +0200 Subject: [PATCH] Update 'MultiDeviceInitialization' --- MultiDeviceInitialization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MultiDeviceInitialization.md b/MultiDeviceInitialization.md index e466ee3..5295471 100644 --- a/MultiDeviceInitialization.md +++ b/MultiDeviceInitialization.md @@ -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.