> in 3 years they want "Log in with Keybase.io" on every website instead of "Log in with Facebook"
Awesome, I brought this up last week:
https://github.com/keybase/keybase-issues/issues/1767
In Keybase's New Key Modelkeybase
keybase-issues
Web Development2014–2026
keybase / keybase-issues
keybase-issues
A single repo for managing publicly recognized issues with the keybase client, installer, and website.
35Distinct people
38Mentions
0Explicit recommenders
899GitHub stars
What to know before exploring
What it is
A single repo for managing publicly recognized issues with the keybase client, installer, and website.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- keybase/client · linked in 3 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year38 dated mentions
Observed mentions: 2014-03-19 16:39:02 UTC to 2026-03-11 21:37:01 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 6 | 2 | 4 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Client-side (app) bugs:
If you've installed Keybase on your desktop, run:
keybase log send
and follow the instructions. If you're on a mobile device, please just post to client issue tracker.
Serious security bugs
We have a bug bounty program on HackerOne, please report there.
Everything else, including website bugs, ideas and suggestions
There's an issues tab on this page.
If you'd like to review our code
We'd like that too.
https://github.com/keybase/client - the client for all platforms
Hall-of-fame Bugfinders
Michael Henriksen
S. Venkatesh
Leigh
Thanks!
Read the full README on GitHubWhat Hacker News says
5 sourcesPermissions errors after installing keybase on macintosh 10.10.3 #1537
2 points · Open discussionHey this is my blog post and that's not all it says. At the time, keybase used a font allowed me to perfectly copy (and make it look like twitter/github was verified) people's profiles.
Totally a lame vulnerability? Yes. Pretty effective? Also yes. If you go back in the github issue[1], it was even good enough to fool Chris, who founded the site, for 10 seconds.
[1] https://github.com/keybase/keybase-issues/issues/397
In Keybase.io Vulnerability (2014)Early, while working on Keybase, I answered it here:
https://github.com/keybase/keybase-issues/issues/788
Technically, not a lot has changed. We're still just putting our own money into it. However, we just added 3 people full-time and 1 person part-time, and so our costs have gone up. I'll admit, we only did this when we got an idea that we thought could turn Keybase into a business.
In a few months we'll be launching a tangential idea - more than just a PGP key directory. This product will let you do some neat things with data backup and signed (possibly encrypted) file hosting and message spooling. It has nothing to do with email, but it requires a real PKI. I'll save the specifics for a big announcement, but the pricing model will reflect our costs with room to make money. More per gig than Dropbox and far less than Tarsnap.
Should t
Read the rest
he "business" fail, we'll be back to where we were when I wrote the above answer.
I moved this to an issue on Github [1]. The key you uploaded to our server has a UID that expired on 2014-11-09. The key you linked to on the MIT key server has updated self-signatures (and subkeys), so doesn't have this problem.
[1] https://github.com/keybase/keybase-issues/issues/1410
In PGP: There’s Life in the Old Dog Yet