Comment by itherseed
2 years ago
You should be always skeptic but when someone write "Pure transparency — trust our code, not our words" in an EXTRA BIG font, you should be extra skeptic.
2 years ago
You should be always skeptic but when someone write "Pure transparency — trust our code, not our words" in an EXTRA BIG font, you should be extra skeptic.
(co-founder of anytype) our main promises are privacy, end-to-end encryption, user controlled keys, self-hosting, p2p sync - all of which should add up to what we can user autonomy from the software provider which we believe to be important. To prove these claims the best way is open the source code. As promises of encryption and ownership stay promises unless you can be sure of it. That was one main motivation and why we think it's worth highlighting.
So I see the networking portions of the code are Free Software - that's great. How are people expected to use it if their use does not fall under "non-commercial use" as defined in the client license? Do you expect people to write their own clients for commercial use, or do you offer commercial licenses?
For non-commercial use, you're prohibited from selling it, but using it within your organization is permitted
1 reply →
The idea if you want to sell clients, you need to get a permission form our association.
6 replies →
Is there a way to make sure I am using the code you published and not a different version?
We do releases in the Github Actions CI. So you can inspect the CI logs and published artefacts(desktop/android). Then you can compare the binaries checksums. I would appreciate ideas on how we can make it more transparent