Ticket #142 (closed defect: invalid)
Don’t have a history !
| Reported by: | Overwriter | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: | ||
| Processor Architecture: | Blocked By: | ||
| Blocking: | Operating System: |
Description
Eraser V6 Beta 3
As V6 is a security and privacy tool, I don’t think it is a good idea that Eraser keeps a track of successful scheduled tasks.
Mainly the ones that get added automatically when a user right clicks a file and selects erase.
Blocking
| Id | Summary | Milestone |
|---|---|---|
| #142 | └ Don’t have a history ! |
Blocked by
| Id | Summary | Milestone |
|---|---|---|
| #142 | └ Don’t have a history ! |
Change History
Note: See
TracTickets for help on using
tickets.

You have to. Otherwise error messages will never be shown. Having it there, users are forced to check to ensure that the erasures completes. Be it once in a while or at the end of the day. This fits in the asynchronous workflow I designed (it's supposed to ensure that what you as users want to do isn't affected. Kinda like a do now check later paradigm.)