keybase / keybase/client

Confused by proof changes of followed person

Open
#8,775 4 comments 6 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 keybase :-)

I just spotted a red notification bar in my chat window:

proofs

All nice and good. But ... this is like a bug report saying 'something is wrong'.
For the future, you might want to provide a link in the message where I can
find out what proofs happen to have changed?

And as immediate questions:

  • should i now re-follow this person to make the message go away?
  • i'm guessing that when i clicked 'follow' the first time, what happened was that my keybase client took all public identities, signed them, and stored the whole thing somewhere. Where? I don't see it on my sigchain...
  • Can I dump such a signed statement? Can I diff it to the current state? (ie actually find out what triggered the warning)

Thank you for any help...

Germano

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 issue identifies the red proof-change notification in the chat window but names no source file or test. Start by reviewing the notification and its comment thread, then trace how proof changes are presented and determine what information a user can inspect; done means the warning explains the change or links to a way to investigate it.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.