Comment 9 for bug 1358294

Hi all. Thank you for your constructive feedback on the bug. Regarding what mvo said
("But we could remove the cache data.") -- that is closer to the nature of this bug. We recognize there may be user data involved (that is, XDG_DATA_HOME). However, we believe .cache and .config directories could be safely removed. We understand that the decision of whether to keep user data (again, XDG_DATA_HOME) would certainly require design input and update to the application removal interface. Nevertheless, if you consider the user is *removing* the application and not *logging out* (where the latter would make sense to keep all 3 directories [data, config, cache]), removing .cache and .config would be the natural expectation of the user. And I'm saying that from purely user perspective, not a developer one.

To summarize, we think that removing .cache and .config would be a natural thing to do and perhaps we could proceed with the fix, while we defer the matter of keeping/removing XDG_DATA_HOME of the app. In that case, if it's Google Drive, Instagram, or similar app, you documents/pictures are safe even if you remove the app, assuming the app has stored them in the right location. The things you loose are things like cached image thumbnails (which usually can be re-generated), custom layout options, ringtone selection and similar settings, which does not have any serious impact on user's app data, that is being removed. All of these are easy to recreate, assuming we leave the XDG_DATA_HOME, until we have a real UI/fix for it.