Feature #12448

Propose to delete data from deactivated persistent features

Added by sajolida 2017-04-14 16:35:00 . Updated 2018-08-18 14:04:46 .

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2017-04-14
Due date:
% Done:

0%

Feature Branch:
Type of work:
User interface design
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

In Bug #12109 we are working on a documentation patch to explain people how to delete the files corresponding to deactivated persistent features. Still, we shouldn’t rely on having people ready the doc so much…

Instead what about asking people whether they want to delete the corresponding data when we detect that some features have been deactivated?

If we agree on this, I could draft a UI.

Subtasks

Related issues

Related to Tails - Bug #12109: Warn the users that removing a persistent feature doesn't erase any data Resolved 2017-01-02
Is duplicate of Tails - Feature #8447: Propose to delete data from a persistence feature when it is deactivated Confirmed 2014-12-16

History

#1 Updated by sajolida 2017-04-14 16:35:17

  • related to Bug #12109: Warn the users that removing a persistent feature doesn't erase any data added

#2 Updated by intrigeri 2017-04-15 07:56:13

  • Assignee changed from intrigeri to sajolida

It surely is feasible, but not entirely straightforward. Do you expect from me a time estimate, or anything else?

Cost put aside, how important do you rank this compared to other work we want to do on the persistence assistant? (Rationale: even estimating costs has a cost, and I’d rather not spend 1h on it if the whole thing ends up being an unassigned low prio ticket for years.)

#3 Updated by sajolida 2017-04-22 10:28:30

  • Status changed from New to Confirmed
  • QA Check deleted (Info Needed)

I have no data to know how important this is. I think that at that point I only wanted you first impression on this being further investigated. Now I have it (thanks!) and I’m fine keeping this ticket assign to me for me research (on the important and on a first UI maybe) without you spending time on evaluating implementation costs yet.

Maybe we’ll get more hints on how to priotize different improvements on this UI if we do the work on additional software.

Unfortunately, such ticket looks like the kind of work that we have the hardest time to fund as it’s neither core work neither fancy enough for grants. Oh well…

#4 Updated by Anonymous 2018-01-18 18:31:58

  • related to Feature #8447: Propose to delete data from a persistence feature when it is deactivated added

#5 Updated by Anonymous 2018-01-18 18:32:38

@sajolida, you already drafted something here: https://labs.riseup.net/code/issues/8447#note-4

#6 Updated by Anonymous 2018-08-17 09:27:50

I would be in favor of such a feature.

#7 Updated by sajolida 2018-08-17 17:32:03

  • related to deleted (Feature #8447: Propose to delete data from a persistence feature when it is deactivated)

#8 Updated by sajolida 2018-08-17 17:32:06

  • is duplicate of Feature #8447: Propose to delete data from a persistence feature when it is deactivated added

#9 Updated by sajolida 2018-08-17 17:32:44

  • Status changed from Confirmed to Duplicate
  • Assignee deleted (sajolida)

Oops… I’m so good at coming up with the same ideas over and over again :)

#10 Updated by Anonymous 2018-08-18 14:04:46

sajolida wrote:
> Oops… I’m so good at coming up with the same ideas over and over again :)

huhuhu :))