This view is over-simplistic. Many—perhaps most—products are designed to serve more than one kind of user.
Obvious example: building an e-commerce platform. The merchant is a kind of user. The customer is a different kind of user on that same platform. Yes, they're humans, but they're not doing the same thing.
Any B2B or B2C type product will have at least two very distinct roles like that. And in those cases, arguing that everyone is just a person as a sort of moral position is destructively vague. It's more difficult to serve someone's needs if you can't start to narrow down what they're trying to accomplish.
While I totally agree with the sentiment that we shouldn't conflate personhood identically with their role in a product, solving useful problems does require that you de-scope and discretize the interactions a bit.
Congrats to the team. Though in the inevitable acquisition, I wish GitHub/Microsoft had been the acquirer: there are a lot of natural fits between that ecosystem and Keybase's model, and a reasonable history of successful acquisition.
Hopefully Zoom avoids gutting Keybase. I found it really useful for bootstrapping credentials when onboarding remote team members and contractors. Way easier to manage than GPG: it was fairly painless even for non-technical people.
Fingers crossed. I wonder what the infrastructure overhead cost is?