Well, this has a few advantages beyond just a folder hierarchy:
* KBSecret's records are structured, meaning that they have "type" information and can be filtered by use (logins, environment keys, code snippets, &c). I've seen a few attempts (and made one of my own) to add structured records to pass(1), but it ends up being pretty hacky and unreliable.
* One of my goals was to make it easy to share passwords and other secrets with other people, especially once you have a group of people who you know consistently need access to the same secrets. I'm not familiar with an easy way to do that with pass(1), but KBFS makes it at easy as sharing files (i.e., KBSecret records) between /keybase/private/user1,user2,user3/.
Agreed ... I've been tuning my pass "records" and still haven't got them exactly the way I want. Sharing pass records is possible since you can encrypt each password with more than one public key.
* KBSecret's records are structured, meaning that they have "type" information and can be filtered by use (logins, environment keys, code snippets, &c). I've seen a few attempts (and made one of my own) to add structured records to pass(1), but it ends up being pretty hacky and unreliable.
* One of my goals was to make it easy to share passwords and other secrets with other people, especially once you have a group of people who you know consistently need access to the same secrets. I'm not familiar with an easy way to do that with pass(1), but KBFS makes it at easy as sharing files (i.e., KBSecret records) between /keybase/private/user1,user2,user3/.