better account migration

theotheroracle commented

2023-08-05 17:19:34 +02:00

allow history to be shared retroactively instead of being assigned per-message

theotheroracle commented

2023-08-05 17:20:59 +02:00

Author

also allow keys to be shared across accounts better

theotheroracle commented

2023-08-05 17:39:44 +02:00

Author

you could backup the room to your phone ( with the state dag bits included ) and then upload to a new server

theotheroracle commented

2023-08-05 17:42:18 +02:00

Author

Cat

Ye if your device has enough compute it could easily fake being a server ask your homeserver for a full copy of the room
and then be able to dump that copy into another homeserver

hive ⬡

i was thinking more just, the device asks for a backup and the server provides one if they have proper permissions

Cat

And it wouldnt be a true Fake if this is a defined mechanism
well to insert the copy into another homeserver you would want to have it be a proper join
that way it can all get weaved together into a normal DAG again on the other side of the transfer

Cat > Ye if your device has enough compute it could easily fake being a server ask your homeserver for a full copy of the room and then be able to dump that copy into another homeserver hive ⬡ >i was thinking more just, the device asks for a backup and the server provides one if they have proper permissions Cat >And it wouldnt be a true Fake if this is a defined mechanism well to insert the copy into another homeserver you would want to have it be a proper join that way it can all get weaved together into a normal DAG again on the other side of the transfer

zocker.net commented

2023-08-15 10:48:01 +02:00

another way for migrating between servers could be that you login to both servers with the same client and the client says: “both are the same user, please synchronize all the DAG history my accounts can see so at least my new server has all my history saved”. This could act as an overwrite to the current sync authorization rules and (besides of this announcement APIs) wouldn’t need new APIs for syncing room stuff.

However, as such solution only works with both servers being only and cooperative, IMO having a client backup fallback in the longterm would still be better.

another way for migrating between servers could be that you login to both servers with the same client and the client says: “both are the same user, please synchronize all the DAG history my accounts can see so at least my new server has all my history saved”. This could act as an overwrite to the current sync authorization rules and (besides of this announcement APIs) wouldn’t need new APIs for syncing room stuff. However, as such solution only works with both servers being only and cooperative, IMO having a client backup fallback in the longterm would still be better.

Rows
Columns

better account migration #23