client VS keys

https://github.com/keybase/client/graphs/code-frequency tells the story well.

There have been 17 releases since Keybase was acquired

https://github.com/keybase/client/issues/19655 https://www.reddit.com/r/Keybase/comments/k9d57l/how\_do\_i\_avoid\_being\_locked\_out\_error\_202/

> development slowed down to a crawl

It's pretty wild that you can see exactly the moment when Zoom bought them on their github activity graph: https://github.com/keybase/client/graphs/code-frequency

GitHub contributions to master branch of keybase/client: https://github.com/keybase/client/graphs/contributors

Reported it here : https://github.com/keybase/client/issues/25398

The moment Zoom took over, contributions to the project effectively collapsed.

Active development stopped the day Keybase was acquired: https://github.com/keybase/client/graphs/contributors 3700+ open issue tickets, most have no responses by a maintainer: https://github.com/keybase/client/issues

The only one I've seen that comes close is https://keys.pub/ but it still misses a lot of what keybase gives (sigchains, etc.)

Previous HN thread: https://news.ycombinator.com/item?id=22995792

Are there any others to consider? It's been quite sad to see Keybase so stifled after being acquired. :-(

Do you think it's worth checking alternatives like https://keys.pub/ or https://keyoxide.org/?

One of the best features from Keybase (personally), is the ability to link identities across multiple different web entities, being able to prove "diggan" on Hacker News is indeed the same as "victorb" on GitHub, for example.

Seemingly, we're getting closer and closer to Keybase shutting down, considering the non-activity since the Zoom acquisition.

Previous threads have mentions of services like https://keys.pub/ and alike, but AFAICT, it doesn't actually provide "cross-service" proofs like Keybase does, and is mainly about managing key signing and related use cases.

What alternatives are online and viable to use today, for the purpose of "proving" that identities across different web properties are the same?

Suppose you only want a replacement for the key management part of keybase, what is there to be recommended? I know of https://keys.pub/ and https://keyoxide.org/ but the former (from someone ex-keybase) has no recent activity and a "not audited" warning, which at least is good to see.

There's also https://keys.pub/ (from someone ex-Keybase, if I remember correctly). I haven't looked at either closely. Can anyone compare and contrast?

I've been a supporter and user of keys.pub for a long time.