Jack O'Connor

The grossest thing I had to do there was suppress a couple "variable doesn't need to be `mut`" warnings, because those variables only need to be `mut` in the x86...

By the way, looking back at this code has reminded me (or maybe made me appreciate for the first time) how intensely complicated the `Jobs`/`hash_many` infrastructure is. It's designed to...

Apologies for the delay in getting to this. I notice that we have `Blake2b`, `VarBlake2b`, and `State` in the same module, with overlapping purposes. Similarly we have `Hash` and `Params`,...

Pie-in-the-sky, this has me wondering about an alternative strategy: What if we separated out the `blake2_simd` backends into a couple standalone crates (e.g. `blake2b_backend` and `blake2s_backend`) that provided a very...

The `community/keybase` package existed before we were shipping a GUI, and it hasn't been updated yet. It might be time to do that. @felixonmars is the maintainer; what do you...

> It's a fairly confusing UX at the moment, I think at least - "CLI only" to me doesn't imply lack of the filesystem @felixonmars, could we update the description...

@RoCaKo some of the comments above are describing issues you'll run into if you try to run KBFS without the GUI, where normally the GUI would prompt you for something...

I think it's safe, though you might run into inexplicable hangs if e.g. someone's Twitter proof gets deleted or whatever. @strib might be able to suggest a status file that...

> Yes it's possible, but it would be easier if BLAKE3-team created a library with a C API - like BLAKE2/libb2. You can find [the official C implementation here](https://github.com/BLAKE3-team/BLAKE3/tree/master/c). (Maybe...

Yeah that's a problem. My worry has been that I don't know how to provide a single build system that's useful to different callers, for example both callers using autotools...