Migration plan back to official client?

[wormeyman]

Hey @dennisameling when 5.27 is released I plan to migrate back to the official client. What are you plans for this repository and your fork?

Should I update this repositories readme to have the instructions in the opposite direction?

[dennisameling]

Hi @wormeyman, thanks for reaching out! When 5.27.0 is released, I think I'll do a few final builds of the fork to give people time to migrate to the official client. Ideally would like to show an in-app banner so that folks are aware that there's an official arm64 version now. My focus will then be on Windows arm64, x86 and (hopefully) Linux arm64.

If you indeed could create a PR for the readme that'd be fantastic - thanks for the offer! 🙏🏼

[foliovision]

Hi Dennis. When I migrated to ARM (thank you so much, as running Rosetta just for Signal was a real performance drag), I lost all of my message history. It would be great if when remigrating to the official client we didn't lose our message history a second time.

[dennisameling]

@foliovision thanks for reaching out! @wormeyman kindly provided a PR with migration steps from Signal Unofficial to the official arm64 client.

Side note: this likely won't work for beta versions of Signal. So please wait until the official v5.27.0 with arm64 support is out - then you should be able to migrate your message history.

[dennisameling]

Version 5.33.0 will be the final version of Signal Unofficial to support macOS - users will be asked to move to the official client (and keep their message history in the process) starting from the next release. Have added some more details here: #4 (comment)

Thanks again @wormeyman for providing the info on migrating to the official client while keeping message history! 🙏🏼