keybase / keybase/client

Spoiler alert message

Open
#17,207 0 comments 5 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

Often I have to send sensitive (e.g spoil or password) that must be seen onyl willingly.
It would be nice to send such message in a way that recipient must tap on it to see it, only is they want to

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

The request does not identify a file, test, or entry point. Start by locating the chat message rendering path and determine how a message can remain hidden until the recipient chooses to reveal it; done means the behavior works for sensitive messages without exposing them automatically.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.