4 ms·
While it's a cool tool, what exactly was the (commercial) potential Keybase had? I could never tell.
by herval 6y ago
While it's a cool tool, what exactly was the (commercial) potential Keybase had? I could never tell.
- gallamine 6y agoSecure filesharing and chat, for starters. Secure digital wallets tied to identity. It was a wallet platform I'd actually be interested in.
- chupasaurus 6y agoEncrypted git repos with ties to team chat...
- brigandish 6y agoThat's what I've been using it for lately, it was becoming my main Git platform. I'm sad that this looks like the end of that.
- bloopernova 6y agoAbility to assign roles(groups) to heterogeneous users. So imagine being able to add user@domainA.com, user@domainB.com, and name@nonprofitname.org to cool-dev-group and them being to instantly be able to access the relevant chat rooms, git repos, shared folders, etc. If password/secret management had been added, then access to that too could have been allowed. If SSO/Oauth had been added, then any service could be covered by this sort of role-based-access-control-for-anyone. So no user has been created, they're using their existing identity to access new resources. With some extra coding, triggers and events could have been added to do things like auto-sign public keys.