Keybase private profile or address book (Feedback/request)

If the only referencing to other uses (including for address book/transaction functions) is though the "twitter" social model (following), then all connections for each user are available to even a partial match of their username through the user search. This allows(?) for recreation of the entire social graph externally to even Keybase services (which also has this).

The keybase core UVP of the client software does not feel like a wallet project, and more like a project building a wallet to get crypto users to join their new social network.

My suggestion: Focus less on trying to build yet another new social network/chat app, and build a great wallet that prioritizes users privacy and **basic** crypto features: An address book that is not public to anyone who randomly searches and even partially matches my username, and a profile privacy feature.

The issue names no files, tests, or entry points. Start by clarifying whether private profiles and a non-public address book are in scope, then identify the relevant Keybase client components and define privacy behavior and acceptance tests before implementation.

Written by the indexing model from the issue text.