Hackers Leak Lichess Source Code
lichess.org
lichess.org
The former is fine, as long as the license is the one that the software is publicly licensed under.
Looking at the source code, two things strike me. First, the Scala backend code is incredibly easy to read and inviting. This is a great poster child of how you can a build simple, reliable app in that language.
Second, I'm surprised that the UI code (written in Typescript) is essentially untested. Given the high quality of the code, I was expecting the frontend code to be thoroughly covered by tests, maybe even written in Test Driven Development. But although Jest is included, there seems to be only one test file in `ui/` (and `yarn run test` doesn't seem to work currently). Is the app tested manually after every commit?
But now I wonder how this leak affects my account security. Maybe I should just switch to Go?
1.e4 e5 2.Ke2?
Maybe offer all users a free month as way of apology?
I learned endless maths to understand the cake.
In the end, to my great wrath, I learned that cake is a lie.
I’m sure the NSA (whom relies on Linux) would prevent the leak too.
I even go so far as insisting that my coworkers infer my source from vague documentation & then create their own white-room implementations. They'll get not so much as a println or an import math from me.
Unless you really have a trade secret (such as some obscure and unpatentable process) then Kerckhoff/Shannon's second principle applies as well to business as to cryptography;
2. It should not require secrecy, and it should not be a problem if it falls into enemy hands; [1]
[1] https://en.wikipedia.org/wiki/Kerckhoffs%27s_principle
edit: Oh Ok. Good one! :D
On a lighter note: what better day than today to be a day of jubilation for Scala fans? :)