Offline mode for kbfs

[rcorre]

It would be really great if my kbfs files are accessible even when I'm offline, and start to sync whenever I'm online. Currently they are completely inaccessible offline.

#943 (comment) claims that offline mode is "on the roadmap", but I couldn't find this roadmap or any issue specifically about an offline mode that I could track.

[songgao]

Thanks for speaking up about your needs! Roadmap as a doc or GH milestone doesn’t exist yet. What we meant in that comment was we plan to implement it at some point. We don’t have an ETA yet, but it shouldn’t be too long. Hang in there!

[erikhuizinga]

Somewhat related:

When not connected to the internet, using cd /keybase/team takes a long time (up to a few seconds). Then, ls results in ls: reading directory '.': Input/output error. This error message is somewhat cryptic and it would be better to warn the user that a connection with Keybase is required to read the directory.

This is on macOS 10.13.4 (17E202), with ls (GNU coreutils) 8.29 and keybase version 2.0.0-20180604163023+f899a761a7.

[lorenzleutgeb]

While waiting for this feature to be implemented in kbfs, does anyone have experience with using a caching file system (such as catfs) on top of kbfs?

[DiagonalArg]

@lorenzleutgeb - I've been trying a different approach. unison works, but when I combine it with incron, I'm having some trouble.

[DiagonalArg]

@lorenzleutgeb - I've tried other approaches, but the only viable one I can see now is running keybase as root, which I'm still hammering on.

(Note that the catfs that you mentioned above is alpha software. Better to use inotify or incon to check for filesystem events, then sync with unison or maybe rsync.)

[damccull]

Keybase team, while considering implementation, it would be awesome to be able to select which files are permanently cached to a specific machine, much like onedrive and google drive allow. This way we don't have to use all our space to sync everything if we don't want to.

[strib]

Thanks! Already in review: keybase/client#15044 !