13 karma · joined May 19, 2023
Why would they willingly start publishing numbers that are worse than 3rd party consensus, out of nowhere?
Background: We had two functions in the codebase with identical names and nearly identical implementations, the latter having a subtle bug. Somehow both were imported into a particular python script, but the correct one had always overshadowed the incorrect one - that is, until an unrelated effort to apply code formatting standards to the codebase “fixed” the shadowing problem by removing the import of the correct function. Not exactly mind bending - but, we had looked at the change a few times over in GitHub while debugging and couldn’t find a problem with it - not until we knew for sure that was the commit causing the problem did we find the bug.
How does it work? You enter a password, which Argon2 converts to a 256 bit key. That key is then used to encrypt and decrypt via AES256. As a bonus, all plaintext is compressed prior to encryption.
This app was purpose built to delight its creators. We love all feedback and contributions nonetheless!
Simplicity aside, practicality is unclear. It seems you can’t escape the need to perform at least one compression operation, per class, per inference. Eg classifying X into one of 10 categories requires a minimum of 10 string compressions. Probably more if you want better accuracy.