Not at the moment, but this wouldn't be too difficult. Records are shared under the /keybase/private/user1,user2,user3/kbsecret hierarchy, so adding or removing a user would just be a matter of changing the user list (moving the directory) and updating the session to match.
> And I assume every single member of the team has to independently set up the session?
Nope! This is a huge benefit of KBFS - the session is shared with all members immediately.
Edit: Oh, I see what you mean by "set up the session." The session files are shared with all members immediately, but each member needs to tell their own copy of `kbsecret` to load that session.
Now that KBSecret uses its own hierarchy, there are ways to fix that. I just hadn't thought of it before ;)
> Records are shared under the /keybase/private/user1,user2,user3/kbsecret hierarchy, so adding or removing a user would just be a matter of changing the user list (moving the directory) and updating the session to match.
I wanted to mention that we are actually actively working on a feature called, not surprisingly, teams. It'll be useful for both chat and KBFS. A team has builtin mechanism for adding/removing members, and has its own sigchain.
This should provide applications like `kbsecret` with smoother support for team. So for KBFS for example, instead of `/keybase/private/alice,bob`, you'll have `/keybase/team/foo` which has Alice and Bob as members. When Celia joins the team `foo`, you can keep the same path `/keybase/team/foo` rather than having to move stuff (which is actually a copy-then-delete since it'd require re-encryption) to a new folder `/keybase/private/alice,bob,celia`. We'll also have a slightly different rekey process that makes this super fast.
Fantastic! That would be a tremendous boon.
> Thanks for making `kbsecret` and having it based on KBFS!
Thanks for making Keybase and KBFS; they're some of my favorite daily-use applications!