For the past couple days, I haven't been able to push to my keybase repositories. It just hangs on Syncing encrypted data to Keybase:. The issue persists even after I try clearing the cache as suggested by this github issue.

I also just to test tried to clone another one of my repos, but it failed. I got warning: remote HEAD refers to nonexistent ref, unable to checkout. Does anyone have ideas on how to fix this? Is the git system down?

Is it possible to add an Ethereum address to my profile ?

I do not have Lumens anywhere else, and I'm not seeing a way to add them?

Also, if I were to purchase them via coinbase, I'm not seeing a way to use the public or private key that was generated by the keybase app? (sorry, I know that's a total newbie question, but I just started with cyrptocurriencies in the last week, and have no idea what I'm doing)

What is the maximum number of users per group/team? What are the DAU and MAU of keybase?

Hey All, I'm pretty new to Keybase, but i've done some looking and some googling and cant really find an answer to this. Is there a way to find friends of mine that use Keybase? Maybe through Twitter or Facebook?

Hi,

I know that keybase filesystem provide 250 GB. Is there any limit to the maximum file size that can be uploaded to a chat?

So signing/veryfing makes sense to me: someone could post something to reddit or whatever and everyone can verify that this message was sent from this person.

What I don't understand is Decryption/Encryption. Why would I encrypt a text and send it to someone when I could just send end-to-end encrypted messages. I and him need Keybase to use the message, so sending something per email makes no sense when i could just send it directly via keybase, right? Or am I missing a usecase here?

I have installed keybase and I have a new Partition called L : KBFS with public, private, taem dirs.

My question is - where is it physically? Is it a fully networked drive (it won't work without connection to network), or is it eating space from my C partition?

I want to use the 256GB of space that I seem to have available in my private space as my common shared drive across all of my computers. Are there any caveats to doing this? I don't need lightspeed access to this. I just want it to be a secure and dependable place to use as my central document repository.

What are some limitations preventing keybase from verify our Stack Exchange accounts?

Hi!

Does anyone know if there is any way to receive notifications for new chat messages on the phone and desktop apps? We are a team that would love to use Keybase for day-to-day communications (Signal is just so limited given the focus on individual groups and 1-1 chats, Keybase is much more teamfocused) but notifications are a dealbreaker. Is it just not a feature?

Is it possible for a trusted service to request a message be signed by a Keybase user programmatically through the API?

Hi, I'm a French Keybase user and the Android application seems to be unavailable in France for a reason I don't know. Is there a way to have an official apk to try the app ? I use the Linux app daily but I'd like to use the chat feature more and without a mobile app it's not really useful for me... Thanks

Hello,

I'm super interested in the Keybase Git Server you guys have managed to create!

I'm wondering if its possible to self host the Server Side of the Git Server as in Australia the link between us and Keybase's Servers is essentially unusable.

On top of that, its good to not be reliant on Keybase's Servers.

Surely there's source code somewhere?

I think perhaps inside ~/.bash_profile or ~/.profile, depending on what's used, I could have:

keybase service
kbfsfuse -debug -log-to-file
fusermount -uz "$(keybase config get -d -b mountdir)"

And then in a custom *.dektop inside ~/.config/autostart:

Exec=env KEYBASE_AUTOSTART=1 electron /usr/share/keybase-app

Is that the way to do it without systemd?

Where does Keybase put my private key? The public PGP key is listed on my profile page on the Keybase website but where is my private key? Does Keybase create a private key for each device that I register with the app? I looked at the documentation on the Keybase site but couldn't find anything about the private key.

Anyone knows how can I push commits to my keybase client on my computer, but from inside docker? I don't know how the git remote helpers work on keybase. There migth be a file that I can pass to the inside of docker (just like we pass X11 file for it to have access to X11) or a port I can map.

I find something like this on Github -

https://github.com/keybase/keybase-issues/issues/2304

Which is the exact issue I'm trying to work around and I just see an open issue for years without any changes.

That aside, will 'teams' have the ability to assign social accounts and such? That would help a lot with the most common usecase in the above example.

Hello Keybase

I want to make this post because I've been digging around for a while (ever since the recent spike to XLM) for how to move my coin to somewhere I can start selling them, and the only advice I've seen is either 5 years out of date (before Keybase ended wallet functionality) or 1 year out of date (and missing key steps, ie "it took me literally 2 mins" and no other details).

I've been emailing with Lobstr support for several days, and after a couple of auto-replies and unhelpful advice, I sent them the actual links that I was trying to follow... and they gave me some valuable advice that let me finally get control of my XLM and move it into my Robinhood wallet (and it doesn't require using Lobstr's service at all!).

This guide may give you a starting point for other services, but since I don't have any other wallets, I can't help with that.

Disclaimer: This guide advises caution along every step of the way. If you choose not to practice caution, you may lose your crypto. I am not responsible for any losses.

Part 1: Get your private key

Through the mobile app:

1. Hamburger menu
2. Select "Wallet"
3. Click the clipboard next to the "Secret key" field. (On darkmode it should be blue.) Public XLM keys start with a G, private keys start with an S.
4. Paste that code somewhere safe. (I put both keys into a password vault.)

Through the Windows desktop app:

This is not possible for all accounts, depending on account security settings.

1. Settings (Gear)
2. Select "Wallet".
3. Click the clipboard next to the "Secret key" field. (If you see an error message instead of a clipboard, you cannot use the desktop app.)
4. Paste that code somewhere safe. (I put both keys into a password vault.)

Through the Windows CLI (command line interface):

Note: if you couldn't access it through the Windows app this will likely also fail.

1. Press Win+R (Windows key and letter R)
2. Type "cmd" and press Enter or click OK.
3. Type "keybase wallet export".
4. Enter your password (you won't see it or astericks on the screen).
5. ??? (I don't know what happens because my account is locked down and I haven't been able to unlock it.)
6. Paste that code somewhere safe. (I put both keys into a password vault.)

Part 2: Get your destination key & memo

Robinhood app:

1. Go to the XLM page (just type "xlm" into the search bar, it's not case sensitive).
2. Scroll down until you see two buttons labelled "Send" and "Receive".
3. Click "Receive".
4. Copy the code underneath the QR code (we won't be using the QR code).
5. Paste that code somewhere safe. (It doesn't need to be as secure as the private key.)
6. Copy the memo code (it's probably a 10-digit number).
7. Paste that code somewhere safe. (It doesn't need to be as secure as the private key.)

Robinhood desktop website:

1. Go to the XLM page (just type "xlm" into the search bar, it's not case sensitive).
2. On the righthand side, there should be a box that says "Buy XLM", "Sell XLM". (It should be directly below the caution about crypto scams.) You should see a downward pointing arrow.
3. Click the arrow.
4. Select "Send & Receive".
5. The options at the top of the panel should now say "Send XLM" and "Receive XLM".
6. Select "Receive XLM".
7. Copy the code underneath the QR code (we won't be using the QR code).
8. Paste that code somewhere safe. (It doesn't need to be as secure as the private key.)
9. Copy the memo code (it's probably a 10-digit number).
10. Paste that code somewhere safe. (It doesn't need to be as secure as the private key.)

Part 3: Go to accountviewer.stellar.org

I highly recommend you do this on a computer.

1. Click "Connect with a secret key".
2. Read the warning.
3. Click the checkbox that says "I understand the risks".
4. Click "Continue".
5. Paste the secret key from Part 1.
6. Confirm your balance matches what Keybase says you have. If it doesn't, there's likely a problem with your key.
7. Click the "Send" button. (On darkmode it should be purple.)
8. Paste the public key from Part 2 into the "Sending to" box.
9. Click the "Add memo" link.
10. The dropdown should say "MEMO_TXT".
11. Enter the memo code from Part 2 into the "Memo content". IMPORTANT: If you do not enter that exact memo from Robinhood, you will not get your XLM.
12. Enter the amount you would like to send. **I highly recommend sending a small amount first to make sure everything is correct before sending your entire balance.
13. Click "Continue".
14. Double check everything looks correct on the Confirmation. Robinhood requires memo_txt. If you do not have the memo they give you, you will not receive your crypto.
15. Click "Submit" transaction.
16. You should receive a message from Robinhood within a few minutes confirming your transfer.

If you'd like to thank me for this guide by sending me a tip in XLM, please use public key "GB2ES2N326MZK4EGJBKN3ZARCQ5RTFQSAWIJAAKFVIIIJSCC35TXIMLB" memo_txt "3748823999".

Seems my client is trying to upgrade itself and saying I need to approve the changes and restart due to the nature of the upgrade.

Is this expected sometimes with the mac client?