diff options
| author | Daniel Gultsch <daniel@gultsch.de> | 2016-06-04 09:24:27 +0200 |
|---|---|---|
| committer | Daniel Gultsch <daniel@gultsch.de> | 2016-06-04 09:24:27 +0200 |
| commit | 6639d0f23bb983cae7234d6b15f9875464c67093 (patch) | |
| tree | aa40f3d6f223aa4576497779f7e86b85e0f0f675 | |
| parent | becc3eb8676ae3fddc912e0701b7ce174da394b3 (diff) | |
added section on backup to FAQ
| -rw-r--r-- | README.md | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -235,6 +235,11 @@ Making these status and priority optional isn't a solution either because Conversations is trying to get rid of old behaviours and set an example for other clients. +#### How do I backup / move Conversations to a new device? +On the one hand Conversations supports Message Archive Management to keep a server side history of your messages so when migrating to a new device that device can display your entire history. However that does not work if you enable OMEMO due to its forward secrecy. (Read [The State of Mobile XMPP in 2016](https://gultsch.de/xmpp_2016.html) especially the section on encryption.) + +If you migrate to a new device and would still like to keep your history please use a third party backup tool like [oandbackup](https://github.com/jensstein/oandbackup) or ```adb backup``` from your computer. It is important that your deactivate your account before backup and activate it only after a succesful restore. Otherwise OMEMO might not work afterwards. + #### Conversations is missing a certain feature I'm open for new feature suggestions. You can use the [issue tracker][issues] on |