Looking at the issues is interesting: https://github.com/keybase/client/search?l=Go&p=1&q=xlm&type... and https://github.com/keybase/keybase-issues/issues?utf8=%E2%9C... - apparently running a crypto airdrop is still a way to get user numbers up...
In Keybase iOS Has a Backdoor?keybase
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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:23:53 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 sourcesThis dates back to 2014, but there's an GitHub issue with an answer to this question:
https://github.com/keybase/keybase-issues/issues/788
Slightly more recently in 2015 there was this blog post:
https://keybase.io/blog/2015-07-15/keybase-raises-series-a
The salient point is:
> In two simple steps: (1) we hope to earn a reputation for creating superior, simple crypto clients.
> Then, (2) some people may turn to us for more advanced, hosted solutions. That could be anything from team management (in the enterprise) to hosting of public, signed files.
> On this second idea, we are already working on something big and filesystemy, designed to address pain points for developers first. That product will be free for everyone, unless you need massive storage.
In Experimental Slack-to-Keybase team importerUninstalled because on Windows it registers itself to auto-start on boot no matter what you do. I keep removing it from the autostart places and it keeps registering back.
I get it that they want to get usage telemetry, but it's ridiculous for a security focused app to force itself like that.
https://github.com/keybase/keybase-issues/issues/2380
https://github.com/keybase/client/issues/3904
https://github.com/keybase/client/issues/5990
In Keybase 4.0I have researched their approach in great detail and found design flaws in it like: https://github.com/keybase/keybase-issues/issues/1946
A lot of trust is rooted in their centralized proprietary walled garden API and to make matters worse they actually silently bypass hardware security modules in favor of keys exposed to system memory!
They even encourage users to expose their PGP private keys to their browser and didn't even bother to isolate it to a service worker so browser plugins can't steal it (or just supporting hardware tokens which GPG already did just fine)
Almost everything they do is non standard, not interoperable with anything else, not distributed to keyservers. They are the internet explorer of cryptography.
They did this in the name of UX but it turns out you can have super easy PGP UX AND follow standards as OpenKeychai
Read the rest
n has demonstrated.
Keybase introduced lock-in and their own protocols for problems that did not at all need them. They are 2 steps forward on UX and one huge backwards step for security.
I'll add my usual reminder here that keybase is a proprietary walled garden that made up its own crypto standards and protocols on many levels leading to dangerous design flaws like this one: https://github.com/keybase/keybase-issues/issues/1946
In Cryptographic coin flipping, now in Keybase