SofleKeyboard VS node-argon2

I made changes to the [Sofle Keyboard](https://github.com/josefadamcik/SofleKeyboard) to be in a layout I prefer. I was wondering if I could get a review/sanity check to make sure it will be fine. I didn't make any real changes beyond adding a key so I don't think there was too much room for error. It produced a clean DRC run for both the schematic and pcb. However this is my first forray into keyboard pcb design, so I wanted to make sure that it will work. I primarily wanted the potential option to go wireless in the future which I've seen you are able to do with the sofle. Thank you!

These are the gerber files https://github.com/josefadamcik/SofleKeyboard/tree/master/Gerbers/v2 but when I download and put them into the printing websites I found myself with a lot of options I dont understand.

When designing it, I was inspired by the Lily58 and Sofle keyboards. I wanted to create a keyboard that is both gaming friendly and easy to learn when moving from a standard keyboard.

Check out the following: Sofle Tweedle Lily58

Please note, it is specifically the Sofle v2, not the Sofle v1 nor the Sofle v2.1 RGB, that has the greater pinky stagger. The Sofle v2 Choc has a pinky stagger between the v1 and v2. See https://josefadamcik.github.io/SofleKeyboard/ for more info.

https://github.com/josefadamcik/SofleKeyboard/tree/master/Gerbers is the gerbers for the sofle PCBs.

Really cool work! Would love to make a version without the number row (48 key is better for me when traveling) and make it wireless. Will it be in a new repository or will it be added to https://github.com/josefadamcik/SofleKeyboard ?

Have a look at the official build guide for a picture of the inserted controllers.

❓ Why is hashing and salting passwords mandatory? A salt is simply a random data used as an additional input to the hashing function to safeguard your password. The random string from the salt makes the hash unpredictable. A password hash involves converting the password into an alphanumeric string using specialized algorithms. Hashing and salting are irreversible and ensure that even if someone gains access to the hashed passwords, they will not be able to decrypt them to recover the original passwords. Hystorically bcrypt is recognized as the best hashing algorithm. However, in terms of robustness against all the new cryptographic attacks targeting hashing algorithms, the current clear winner is argon2. However, since the “youth" (2015) of this algorithm, I chose to use bcrypt

Argon2: this is the newest highly recommended algorithm, and recommended by OWASP. (Edit: originally linked to a low-download library.)

Though I am using bcrypt to hash passwords, recommended approach currently is argon2

As per security.stackexchange.com the recommended number of rounds for Bcrypt is a number such that it takes atleast 250 ms to hash your password. Argon2 on the other hand takes multiple parameters it seems. What is the equivalent configuration you need for Argon2? I am talking about an express webserver here with passportjs if that helps

If you already have Bcrypt & want to start converting to Argon2, check out this guide → https://github.com/ranisalt/node-argon2/wiki/Migrating-from-another-hash-function

You can look at the argon2 npm (https://www.npmjs.com/package/argon2).