keybase / keybase/client

Feature request: Allow bots

Open
#8,842 2 comments 25 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

The Terms of Service today forbids the use of bots or other automated tools, but the ability to have bots would be a huge boon for Teams. Is there any way to convince the Keybase team to allow bots?

For example, consider the ability to connect your CRM or intranet to Keybase Teams. Upon some events in the CMR/Intranet the CRM can post to a team channel that something happened, and maybe attach a file in the shared directory at the same time. Think Slack Bots.

I understand the need to prevent abuse (including automated abuse) of the system, so, rather than argue that bots should have free rein, I have a few ideas how I imagine bots can be allowed.

  1. maybe the bot can be signed for by a real user who promises that it will behave. And if that promise is broken, the user who signed will be punished.

  2. Or maybe a bot must be locked to a single Team and will not be allowed to interact with users outside ot that Team?

  3. Make bots a paid feature. If your bot misbehaves, you have to pay again. :)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No implementation file, test, or entry point is identified. Start by reading the linked Terms of Service and clarifying the intended bot scope, authentication, team restrictions, and abuse handling. Done would require an agreed product and technical design for allowing bots in Teams.

Written by the indexing model from the issue text.

Assessment

Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.