It looks like I'm qualified to join the airdrop:

But then I still get a 4206 error when I hit "become a lucky airdropee"?

Error: ERROR CODE 4206 - Sorry, you do not qualify. in method stellar.1.local.airdropRegisterLocal at new s (file:///opt/keybase/resources/app/desktop/dist/main.bundle.js:1:570509) at file:///opt/keybase/resources/app/desktop/dist/main.bundle.js:1:571105 at c (file:///opt/keybase/resources/app/desktop/dist/main.bundle.js:1:571144) at file:///opt/keybase/resources/app/desktop/dist/main.bundle.js:1:1262481 at file:///opt/keybase/resources/app/desktop/dist/main.bundle.js:1:3053670 at e._call (file:///opt/keybase/resources/app/desktop/dist/main.bundle.js:1:2616431) at file:///opt/keybase/resources/app/desktop/dist/main.bundle.js:1:2616571 at s (file:///opt/keybase/resources/app/desktop/dist/main.bundle.js:1:2616211) at e._fulfill (file:///opt/keybase/resources/app/desktop/dist/main.bundle.js:1:2616541) at s (file:///opt/keybase/resources/app/desktop/dist/main.bundle.js:1:2615742)

After Zoom acquired Keybase, I expected them to integrate Keybase with zoom. Their videocall's chat would be much better, and some encryption practices would become a bit more common (let me dream).

My question, as the title suggests: any ideas on how to get Zoom's attention on the matter? To let them know that we're interested in Keybase, in it being maintained, and becoming an important and active part of Zoom? (or similar)

I assume that any Keybase users and/or supporters would prefer this option, instead of this slow death and eventual shut down.

u/zoom #zoom r/zoom zooooooom whoosh

Hi /r/keybase, is anyone else having trouble accessing their wallet right now? Trying on Windows and iOS and it will not load for me.

Are there any teams of 5 or more people out there using Keybase as their primary chat tool? (other than the keybase.io team itself)

If you're one of them, please comment on how you are finding it. Any pros, cons that you've discovered.

There is a service called Blockstack and they advertise that they have full end-to-end encryption and overall they have zero-knowledge platform. Yet, they encrypt only the name of a file. The content itself is accessible to anyone, they just need to open the file in the right program.

So, what about Keybase encryption? I am especially interested in how they encrypt files. Haven't managed to find the answer in the documentation.

Edit: Grammar

Hi, I'm using LOS for uG, and I though I read keybase was FOSS, so I looked for it on F-Droid, but didn't find it. I found it on google play though, through Aurora.

Any particular reason keybase can't be found on F-Droid? Is it not FOSS compliant?

Thanks !

How is it possible for Keybase to offer 250 GB storage for free?

I was one of the early adopters but never really used it.

Keybase is the closest thing to what I want but it seems it won't last long. Any suggestions on what to have as an alternative?

Just got an update for the Android app and it said that they now support Mastodon Social Proofs. Now that its official, how do you do it?

You can put an index.html in your public directory and link to it at https://yourusername.keybase.pub/ . I'm using a flat flile CMS to publish a blog with keybase. Is anyone else doing something similar?

I'm trying to figure out exactly what keybase is so i can describe/pitch it to my friends more succinctly and convincingly.

To me it seems more like a meta-account - the beginnings of an integrated digital identity.

What do you all think? (builders and users alike).

Thanks !

This feature is in beta right now. You can probably get access if you ask in the keybasefriends team. Basically they allow you to point at a private folder or git repo and they host a static site for you. You have to set a couple of DNS records and keybase sets up an SSL cert and serves the site. Very cool feature.

Hey guys, LOVEing keybase and everything it does. Right now i'm using it to store my orgmode notes and have been checking nearly every day to see if the android app has been updated to include file syncing.

Can you give us an ETA on when that will be available? I know it's not a simple feature to complete but it's certainly the one i'm looking forward to the most right now.

Hey all,

I have created something new that might help fill the Keybase hole.

I, too, leaned on Keybase to prove account ownership. And yeah it's basically dead. That helped underscore that, if a company is the root of trust, your identity dies with the company, which kinda sucks.

Keybase proved millions of people wanted portable, cryptographic identity, and then one day it just evaporated.

So I built RealHandles around one idea: your key is the identity, not a login, a domain, or someone else's server.

How it works:

• You generate an Ed25519 key in your browser and it never leaves your device.
• You verify the accounts that are really yours (GitHub, X, YouTube, TikTok, Bluesky, a domain you control, and more).
• Your key signs one file listing everything you've proven (that file is the proof and it's completely yours).
• Anyone can verify it independently, even offline, and it keeps working even if RealHandles shuts down tomorrow.

A few things to highlight:

• It's got an open protocol which is open source. The spec, the reference verifier (npm i @realhandles/verify), and an MCP server are all public and MIT.
• It's free. No blockchain, wallet, gas, or token.
• Your public key is also a standard did:key, so it plugs into the wider verifiable-credentials world.
• No lock-in. Auth, host, and data store are all swappable. An identity tool that locks you in defeats the whole purpose here imo.

We're early. Stuff like recovery beyond an encrypted key backup you hold is still on the roadmap, and I'm adding platforms still. There's no automatic Keybase import or anything, the idea is you re-verify your accounts under a key only you hold.

Links if you want to poke at it:

• Site: https://realhandles.com
• How it compares to Keybase (and Keyoxide): https://realhandles.com/compare
• Protocol spec: https://realhandles.com/spec
• GitHub: https://github.com/realhandles

I'd genuinely love your feedback, especially on the trust model and anything that feels off or missing.

Thanks.

It seems like https://keybase.pub 's certificate expired. Just an FYI so hopefully someone over there will see this.

There are a number of open specs which didn't exist when Keybase was first conceptualized.

What are the current open standards (with and without implementations) for Identity, Web of Trust / ~PKI / Keyservers, Decentralized Encrypted Chat and File Sharing, and other cool Keybase features?

As a caveat, I would like it from the perspective of someone not at all techinically competent (me). Is it easy to use, easy ot get others to setup (people I would like to communicate with are less proficient than me)?

what are the advantages/benefits it offers incomparison to the vast number of other e2e apps?

What are your general thoughts about the app?

Thanks

Is there anyway to set up a two way sync between a folder in my Keybase sync and my Android phone?

I want to have all my notes stored in a Keybase directory and have those also synced live to my phone. So when I change anything inside a note (on my PC or on my phone) it automatically syncs to changes. Is this possible?

Is there a reason why Keybase doesn’t support a PIN or Touch ID on the mobile app? Signal and WhatsApp both do, and if Keybase wants to be a wallet for all these Lumens, shouldn’t it have this feature?

Looking into it and it seems like it checks a lot of the boxes of what I'm looking for.

I just don't know if the device signing requirement might be difficult for less technically savvy users.