Erik Moeller

Kept open for consideration in rewrite efforts and provisionally added to alpha milestone. Tagged with "needs/scoping" to make final decision on scope of validation per above.

Leaving un-milestoned for now but adding "needs user research"; at minimum, would be good to know if this is more of an edge case or fairly common.

I'm now doing the following to investigate: 1) Removed `~/.securedrop_client/data` in `sd-app` 2) Removed `~/.securedrop_client/svs.sqlite` in `sd-app` 3) Did _not_ alter server contents 4) Did _not_ attempt to reset `sd-gpg`...

Well, it must have either had something to do with the server state or with what I did during the sync, because on a fresh sync without interacting with the...

That reasoning makes sense to me; I can re-test the behavior with deletion during large syncs once #975 lands. Note that I didn't notice any user impact other than temporary...

Ran another 350+ sync, CPU for `sd-app` tends to be at ~5% during the message/reply download & decrypt operations, and spikes to ~20% after a sync (presumably when the sync...

Closing, non-critical issue specific to the current codebase/UX, which is undergoing a rewrite (including sync in particular).

Milestoning for now for 1.0.0 (rewrite); i18n is in some ways harder to bolt on later (UX choices have to be revisited etc.), so it'd be good to address as...

Duplicate of #1085; added the GDrive link over there as well.

Notes from today's UX discussion: - While the scope of this issue is "Download progress improvements", Ura is proposing to change the representation of files in the client as part...