aurecchia

I don't think there is an actual name for that. I actually don't think I have ever seen a keyboard with a layout like the one you describe. I'm not really sure if it was really intentional on the Alice layout. The extra B might just be for extra symmetry between the two halves.

Yeah, deleting your local clone and starting over should normally not be necessary, unless you really mess things up badly.

The "local backup branch" is not really needed either because you can still reference `origin/your-branch` even after you messed up a rebase of `your-branch` locally.

Even if you force-pushed and overwrote `origin/your-branch` it's most likely still possible to get back to the original state of things using `git reflog`.

I'm going to give it a try. Thanks for the suggestion!

I think it gives a good, albeit very simplified, explanation of the general idea around the most common OAuth flow.

Like OP was writing, if you are looking at implementing an authorization server, this is not very useful. Even if you are a developer looking to understand how to get authorized to interact with a resource server or authenticate a user, I'd argue that this is not enough. The author clarifies that in the conclusion, but then it's essentially the reader who has to figure out what details are missing and where to get them.

My biggest issue with the MX Ergo is the finish on the "top" part. After a while it starts to degrade and becomes sticky. I have not found a way to clean it properly. :/

For what it's worth, the MX Ergo also works over Bluetooth. I couldn't be bothered with the extra headache that that requires, though.