1. 8

    (I’m the author of the PR)

    Keybase is a public key database, and one of the things they have added that other large public key databases (such as SKS and PGP) lack is the ability to tie other accounts across the internet to your public key. This reduces the chances of someone MITMing your communication with someone else.

    This being said, I also rarely use keybase itself, but I had some free time and I wanted to see what ruby on rails was like.

    1. 7

      They didn’t need to add the ability to tie other accounts across the internet to your public key. Signing your username would amount to that with a public key lookup. Just put it in your bio. No central server needed.

      1. 2

        That’s what most users have been doing, too.

      2. 2

        So why not something open like the MIT keyserver instead?

        1. 4

          I’m not sure what you’re asking here. (And the MIT keyserver is actually just part of the SKS pool)

        2. 2

          In OpenPGP to tie other accounts across the internet to your public key is not the responsibility of the public key transport / database / directory, but the clients based on information in the public key. While an OpenPGP public key conflates the account on some service with the Name of the person and possibly some other things called identity, it does support it. It is specified in the OpenPGP RFC4880 under the name User ID Packet which is called an identity in the GPG CLI. Usually people use it to tie a GPG key to an email address, but the specification does not restrict it to only email accounts.

        1. 3

          This week I’m adding more language features to slither, specifically I hope to add pattern matching. One of my main goals with this is to implement it without adding any new opcodes to the interpreter, which is key to making sure I’m at a minimal set of instructions to begin adding optimization paths in the future.

          I’m also adding more methods to the my iterator methods proposal for JavaScript, mostly for async iterators as I’ve been putting those off. Hopefully I can have this ready for the next TC39 meeting at the end of May.

          Finally as an “if I have time left over” project, I need to start adding tests to my Node.js WASI implementation. I can take some tests from wasmer and cranelift, but a lot of the tests will need to be written from scratch. As part of this I also need to figure out a good test harness setup for all the individual test files and cases.