News for hackers. Stuff that matters.
Re:Introducing Keybase Teams by malgorithms on Monday September 18, 2017 @02:57PM (#15278508)
nope! We feel pretty strongly this is the right answer.
Re:Introducing Keybase Teams by malgorithms on Monday September 18, 2017 @03:23PM (#15278719)
Answer to your edit: team names are not private, as their hashes can be found in our merkle tree, which anyone is free to mirror or lookup. So if you name your team `foobar` someone would be able to hash foobar and look it up, and yes, prove it exists. This is a feature, not a bug :-)

But if you picked a team name with very high entropy, then I guess that would be semi-private in that it would be undiscoverable by brute force.

Re:Introducing Keybase Teams by tehno on Monday September 18, 2017 @04:17PM (#15279142)
Same goes for sub-team name? I.e. don't put private project names, future release date related things etc in there?
Re:Introducing Keybase Teams by xnxn on Monday September 18, 2017 @04:38PM (#15279310)
"The very existence of subteams are hidden from all who aren't members of the subteam. Thus, if you wanted to create the team `lets_fire_bob.just_kidding_fire_bruce`, then Bruce would have no way of knowing his number is up."

(from https://keybase.io/docs/teams/design)