[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2565: Magic Folder: how do we know whether deletion is intentional?

[Tahoe-LAFS]

#2565: Magic Folder: how do we know whether deletion is intentional?
-------------------------------------+-------------------------------------
     Reporter:  daira                |      Owner:  daira
         Type:  defect               |     Status:  new
     Priority:  normal               |  Milestone:  undecided
    Component:  code-frontend-       |    Version:  1.10.1
  magic-folder                       |   Keywords:  magic-folder usability
   Resolution:                       |  zookos-opinion-needed
Launchpad Bug:                       |
-------------------------------------+-------------------------------------

Comment (by daira):

 Replying to [comment:4 lpirl]:
 > Replying to [comment:3 daira]:
 > > (Currently, that is to upload a deletion marker, which will cause
 other nodes to rename their copy of the file to `$FILENAME.backup` if they
 have it, or do nothing if they do not already have it.)
 >
 > Actual deletion does not happen anyways, does it?

 No. But there may be no other copy of the file in some cases (if it was
 deleted from the client on which it was created, before it was uploaded
 and then downloaded by any other client).

 > Could backup files also be named `$FILENAME.backup_<timestamp>`? But his
 accumulates a lot of old files over time… for users that do not want this,
 it could be optional.

 Yes, that was anticipated but not required for the OTF grant proposal.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2565#comment:6>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage