Open source the server components of Keybase
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
There's an uproar in keybase chat about the purchase of Keybase by Zoom.
Statements like this [_"Ultimately Keybase's future is in Zoom's hands, and we'll see where that takes us."_](https://keybase.io/blog/keybase-joins-zoom) scare the keybase community and will drive away the more technically minded user-base.
**Please open source the server components to keybase.**
While the Keybase client is open source, and handles all of the encryption + decryption, the server component that streams chats, file transfers, etc between users is not. Keybase will not function if Zoom shuts down the (currently closed source) server component.
This act will help ensure the long term stability of the keybase platform in-case keybase's future is bleak at Zoom.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points for the closed server components. Start by identifying the server-side code and the project's licensing and release process; done would mean the requested Keybase server components are publicly available under an appropriate open-source arrangement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100