[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 gdt):

 Stepping back, I think metadata gets used for three things, and we should
 think about them separately:
  * normal vfs operations like any other filesystem.   This is hard, and I
 think we should look to other filesystems to see what they do about
 uid/gid and username mappings.  zooko's point about unanchored uids is
 totally sensible.  AFS is perhaps a good example, because while it lacks
 the cypherpunk flavor, it has large scale.  But, it's a bit centralized in
 terms of adminsitration.
  * wide-scale sharing.  Here, filesystems blur into publishing systems.
  * backup: here, we want to store metadata to be used later, but it's
 really part of the data of the backup, not metadata about files.


 My complaint about 'tahoe backup' is that I don't see any good reason to
 couple the backup program and the filesystem.  All the reasons about local
 storage of metadata about what's there, etc. should apply to any back-end
 storage.

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