<story><title>Keys.pub – Manage cryptographic keys and user identities</title><url>https://keys.pub/</url></story><parent_chain></parent_chain><comment><author>Sidnicious</author><text>This loses something important about Keybase sigchains: on Keybase, a sigchain represents an identity and &lt;i&gt;not&lt;/i&gt; a single key, which makes it possible to add separate keys for different devices and to seamlessly replace and revoke keys over time. (Non-key-specific sigchains let the Keybase client do interesting things like automatically re-encrypting shared data when someone revokes an old key.)&lt;p&gt;Tying sigchains to keys seems limiting, and I&amp;#x27;m curious if there&amp;#x27;s a reason for it. Otherwise, I like this a bunch.</text></comment>
<story><title>Keys.pub – Manage cryptographic keys and user identities</title><url>https://keys.pub/</url></story><parent_chain></parent_chain><comment><author>Legogris</author><text>I, for one, am happy Keybase user, excited about their new features and can see it already becoming a much better (but not ideal) alternative to Signal for private IM (proper encryption, every device is first-class, usable CLI, no phone-number bullshit, good team chats, etc).&lt;p&gt;But I do see that the same reason I am optimistic is the same reason many users are disappointed and they&amp;#x27;re right - Keybase seems to have pivoted and they are headed in a completely different direction than they were when we joined.&lt;p&gt;Keys.pub looks to fulfill precisely the promise of &amp;quot;what Keybase was supposed to be&amp;quot;. And crucially, I think; looks to be fully open source (server-side included, no sketchy opaque metadata spider-web by a US corporate).&lt;p&gt;I do see these two projects as fully complementary.&lt;p&gt;It would be interesting if this could, optionally, import pubkeys from Keybase as well. I think these could be complementary.</text></comment>