Wish the homeserver portability would be worked on more. The ability to change homeserver would really allow people to more easily move on from matrix.org.
Myself included ;).
Optimally it would even allow the switch “after the fact”, so after your original homeserver is down, assuming your client has a local copy of the server-side secret storage. It would need to be based on some cryptographic identity then, I suppose.
It’s nice that this exists, but even for this I’d prefer to use an open source tool.
And it of course helps with migration only if the old HS is still online…
I think most practically this migration function would be built inside some Matrix client (one that would support more than one server to start with), but I suppose a standalone tool would be a decent solution as well.
Wish the homeserver portability would be worked on more. The ability to change homeserver would really allow people to more easily move on from matrix.org.
Myself included ;).
Optimally it would even allow the switch “after the fact”, so after your original homeserver is down, assuming your client has a local copy of the server-side secret storage. It would need to be based on some cryptographic identity then, I suppose.
There’s something that kinda helps with the migration: https://ems.element.io/tools/matrix-migration
It’s nice that this exists, but even for this I’d prefer to use an open source tool.
And it of course helps with migration only if the old HS is still online…
I think most practically this migration function would be built inside some Matrix client (one that would support more than one server to start with), but I suppose a standalone tool would be a decent solution as well.
Yes, this would be a great feature - but it’s a big issue to implement. It’s talked about in this video, worth watching if you’re curious about it.
As far as status go, this issue on the matrix spec is what you want to follow.