keybase / keybase/keybase-issues

Verify Facebook and Twitter without a Public Post.

Open
#3,108 3 comments 6 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

Hi,

Thanks for your work on Keybase. I'm a huge fan, but I'm disappointed that I can't verify with Facebook or Twitter because you guys rely on posts & tweets as the medium for verification. This is like asking people to create a web page on their website to verify ownership of their website instead of just using DNS or Robots.txt.

I would like to propose that instead of using posts or tweets, allow people to add a special link to their Facebook and Twitter bios (or some other metadata field).

I'm determined to never publish a public Facebook post and I have no plans to ever tweet a Keybase verification. Keybase is awesome, but I don't like it more than my privacy.

Sincerely,

Michael

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named in the issue. Start by locating the existing Facebook and Twitter verification flow, then determine how profile bio links or other metadata could be checked; the work is done when ownership can be verified without a public post or tweet.

Written by the indexing model from the issue text.

Assessment

Domain
authentication
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.