keybase / keybase/client

Reddit fails to verify

Open
#26,945 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

## Problem: Reddit fails to verify

You wrote me in an e-mail:
```
Hi, [hvancann](https://keybase.io/hvancann?a=lgGS2SBhOTI2ODg3MGUzYjVmNDMzZjk0MmE0MTAwMTkwNGUxObJodmFuY2FubkBnbWFpbC5jb23OZl2egs4AA%2FSAwMQgjVMMmWBwM2OPap7%2F56Dyy644U%2FtgXoKGwAVotZdPWX4%3D), your attempted reddit identity proof of hvancann never succeeded. We've been checking it repeatedly, and from our perspective, it's either (a) not there, or (b) not posted precisely.

If you think there's a bug, please [post an issue on github](https://github.com/keybase/client/issues?state=open). Include the link to your proof.

And here is your profile, in case you'd like to try again: [https://keybase.io/hvancann](https://keybase.io/hvancann?a=lgGS2SBhOTI2ODg3MGUzYjVmNDMzZjk0MmE0MTAwMTkwNGUxObJodmFuY2FubkBnbWFpbC5jb23OZl2egs4AA%2FSAwMQgjVMMmWBwM2OPap7%2F56Dyy644U%2FtgXoKGwAVotZdPWX4%3D).
You may also prove yourself with the [keybase command line app](https://keybase.io/docs/command_line?a=lgGS2SBhOTI2ODg3MGUzYjVmNDMzZjk0MmE0MTAwMTkwNGUxObJodmFuY2FubkBnbWFpbC5jb23OZl2egs4AA%2FSAwMQgjVMMmWBwM2OPap7%2F56Dyy644U%2FtgXoKGwAVotZdPWX4%3D).

Thanks! -Keybase
```

## Solution

As a team you really have to do something about this. It's a nerdish jungle I had to wade through. It costed me an hour at least already to get to the point in "status". You write 'not posted precisely'.... well then make the process to prove more versatile, I would say.

## Status
The proof is there, but won't validate. I even used the command line tool, but it returned the same message over and over again: proof not found.

Here's the proof
https://www.reddit.com/r/KeybaseProofs/comments/1d5lpye/my_keybase_proof_reddithvancann_keybasehvancann/

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names a Reddit proof URL, the `status` path, and the command-line tool; start by reproducing the verification failure with that proof and tracing the reported result. Done means identifying why the proof is reported missing and implementing a concrete correction, but the issue names no files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication
Issue type
Bug
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.