[tahoe-lafs-trac-stream] [tahoe-lafs] #1946: consider removing some st_* fields from metadata

[tahoe-lafs]

#1946: consider removing some st_* fields from metadata
------------------------+-------------------------------
     Reporter:  daira   |      Owner:
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:  soon
    Component:  code    |    Version:  1.9.2
   Resolution:          |   Keywords:  privacy anonymity
Launchpad Bug:          |
------------------------+-------------------------------

Comment (by zooko):

 Replying to [comment:5 gdt]:
 > On the other hand, it has a builtin backup program, even though there
 aren't really any good reasons to blur backup programs and filesystems
 (consider bup with the BUPDIR on tahoe).

 gdt, you might be interested in [//pipermail/tahoe-
 dev/2008-September/000814.html this old thread], where I failed to deter
 Brian from inventing {{{tahoe backup}}}. The thing is, neither bup,
 duplicity, nor any of the other ones that I named would have the same
 behavior that {{{tahoe backup}}} does. I use {{{tahoe backup}}} a lot, and
 I like its behavior, and I suspect we couldn't get the same behavior by
 composing a backup tools and a storage system through a generic POSIX API.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1946#comment:13>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage