Jean-Paul Calderone <exar...@twistedmatrix.com> writes: > Looking slightly more broadly, I think it would be great to get Tahoe-LAFS > integrated with some applications that people actually use. I think the > audience for "a command line tool you can use to securely upload and > download individual files to a server you or your friends operate" is > fairly small compared to an audience like "secure storage for your > OpenOffice documents" or "secure storage for photos you take on your > phone". I see these Haskell libraries as a first small step towards > engaging with those larger audiences.
Indeed, the interface is a big deal. I have been quiet partly because I'm doing other things, and partly because my filesystem views are out of sync with mainstream tahoe-lafs and expressing them was seeming non-constructive. But it's been years, and I'll try to limit this to once/year. My view is that the interface to filesystems is via the normal kernel filesystem system calls, and that filesystems can be implemented in kernel (typical for local on disk) or via FUSE or similar. tahoe's interface is of course richer, and thus one would need to have a parallel interface or work that into extended attributes or special ioctls. Coda went down the special ioctl route. This view is basically saying "it's not good to make access only by command line programs; that feels like mtools". Another interesting example is Nextcloud, which is WebDAV but has a client that will sync webdav to local (so you get offline access). I'm not sure offline access makes sense, but the point is that they thought it best to provide a way to interact with data on Nextcloud from programs that have no idea nextcloud exists, just by choosing a directory in the right place. Overall this is a full-on unixhead view, coming from someone raised on K&R C :-) There's another view, which is that tahoe-lafs is primarily suited to backups, and that integrating it into bup or similar is a good path. I think you are suggesting integrating it direclty into libreoffice? I wonder how that's going to work, how libreoffice upstream would view that, or if you mean providing a way for an unmodified program to deal with a directory that is actually stored on tahoe-lafs. _______________________________________________ tahoe-dev mailing list tahoe-dev@lists.tahoe-lafs.org https://lists.tahoe-lafs.org/mailman/listinfo/tahoe-dev
