keybase / keybase/client

Using Keybase as a support platform for proprietary software.

Open
#24,811 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
PR merge metrics
PR metrics pending

Description

I'm developing software that needs to authenticate documents and people, I'd like to use the Keybase API and I've already started reading it.

My doubts boil down to the following:

* What is the Keybase lifetime, and if it stops being developed, how will I become dependent on it?
* Is it allowed to use Keybase on proprietary software? what is the cost to use the API? and if it's an opensource software that has sponsors, would there be costs?
* Are there restrictions on use in religious institutions?
* What's the best way to start developing a client that uses the Keybase API?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Keybase API material the author says they have begun reading; no repository file, test, or entry point is identified in the issue. Determine whether the project has documented answers about service lifetime, proprietary use, pricing, religious-institution restrictions, and client development, then consider the work complete only when those questions have authoritative guidance.

Written by the indexing model from the issue text.

Assessment

Domain
api, authentication, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.