The data backup doesn't seem to be recognized in the form as spit out by Threema (.zip) which is confusing

[ell1e]

If I do a threema data backup and want to do an import, it seems like I'm supposed to do things with it (like extracting). I did it wrong at first, and I'm wondering now: why doesn't OpenMittsu just handle this and let me pick the backup as-is, which is that .zip file? Why give me comparatively complicated manual extract & delete instructions instead, that fill about 7 paragraphs in the load backup wizard? Is having OpenMittsu this in /tmp with the appropriate permissions not safe enough? (I would think that on any LUKS encrypted distro that is properly configured, the tempfs should also be encrypted.)

[blizzard4591]

The biggest problem with opening the zip file directly is the encryption used. I started playing with implementing this directly, and its a pain - I need to ship at least two additional dependencies, have them build with openMittsu and interface them.

Since this is a one-person show (for 99% at least), I gave up on that after a couple of days of experimenting (though there could be a stale branch somewhere with some of that) and instead ask users to simply extract the archive. I'd be more than happy to merge in a PR which enables this, but I currently am not willing to put in the time for so little benefit.

But maybe I am wrong?

[ell1e]

IMHO this is the one super visible step every single one of your converting users will need to go through. So that the dialogs are pretty weird gives you a high risk that people will just stop and not use the open client at all. Not that this is necessarily a fault, after all it's an open unpaid offering, just pointing out this can be a consequence.

(I did eventually pass on it when afterwards I got an error that the backup wasn't recognized, concluding the whole process isn't really ironed out much. But I suppose that's a different issue)