keybase / keybase/client

Scenarii where I cannot send exploding messages

Open
#16,093 0 comments 0 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

Hi.
I changed a password at work for a common account. I want to share to my woworker the new password via Keybase chat.
I wanted to send it with a short exploding messages. Unluckly my woworker was on vacation and when he was able to read their keybased messages, the exploding message was already gone.

Do you plan to set the start of countdown of exploding messages the receved time and not the sent one ?

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 files, tests, or entry points are named. Start by locating the Keybase chat handling for exploding-message expiry and review how sender and recipient availability affect the countdown; done means the expiry begins at receipt rather than sending, including when the recipient is offline.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.