keybase / keybase/keybase-issues
feature request: [|FEDERATION|]: integrate a federated IM protocol to allow inter-operable keybase networks & clients (eg. email, XMPP, or Matrix)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Keybase is great but one drawback is that it is not federated ie. users cannot host their own (interoperable) servers/networks or build their own clients.
This could be solved by integrating a federated IM protocol - or inventing a new one.
In Instant Messaging (IM), federated IM networks are those that allow communications across different IM clients and platforms, similar to the way email allows people to communicate regardless of which email client they choose to use.
Examples of existing protocols that could be integrated include email, XMPP (xmpp.org), or Matrix (matrix.org). Alternatively, Keybase could do something crazy like invent a new one!
Interoperability would reduce barriers to adoption, and help to further develop a vibrant Keybase ecosystem.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; begin by investigating how Keybase clients and networks currently communicate. Compare the mentioned email, XMPP, and Matrix options, with completion defined as an interoperable federated network and client integration.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100