Alexander Neumann

Ah, sorry, I should have been clearer: I'm willing to spend some time merging my changes back into this project, as pull requests. Debouncing is the most important one I...

> When you say it’s completely different, how so? It feels much better. It's a bit hard to describe, at least in retrospect typing on the ErgoDox always felt different...

Without raising the i2c frequency at all, I'm getting around 770Hz scan rate (vs. 360Hz with the default code) :)

PR #44 has only the debouncing code so you can give it a try if you like.

That's possible. Michael described in [his article](https://michael.stapelberg.de/posts/2018-04-17-kinx-latency-measurement/) that in a small experiment he did that one person was able to reliably detect 15ms of added input latency, while other people...

So, anything else I can do to get this merged?

Is there anything else to do?

Hey, thanks for suggesting this. Can you please elaborate what your use case is? Why do you need to know exactly what the error code was? What are the cases...

@wjkohnen Huh, that doesn't sound right, but I'm not sure I understood. Could you elaborate on your use case a bit? I understood you're running restic in a script, then...

Thanks for describing your situation! It seems to me we have different expectations: I didn't think it was necessary to return an error code when the user requested termination via...