Does it make sense to back up ~/.local/share/keybase?

I make daily incremental backups of my home folder (with [Borg](https://www.borgbackup.org/)) and noticed that the amount of modified data per run has increased significantly after installing Keybase (roughly around 100MB/day, I think, and it doesn't seem to make much of a difference whether I actually do anything with Keybase). As far as I can tell, it's mostly due to stuff in the `~/.local/share/keybase` directory.

Does it even make sense to back up that folder? If it does, would it make sense to exclude parts of it (e.g. `keybase.leveldb`, `kbfs_block_cache`)? Should parts of it maybe be moved over to `~/.cache`?

Version info: `keybase version 2.3.0-20180621160033+75940465b8` on Debian Stretch

(If there is a better place for this sort of question, please let me know.)

Start by reviewing the contents and purpose of ~/.local/share/keybase, especially keybase.leveldb and kbfs_block_cache, using the reported Keybase 2.3.0 Debian Stretch setup as context. Done means providing clear guidance on whether the directory should be backed up, which parts can be excluded, and whether any part belongs under ~/.cache.

Written by the indexing model from the issue text.