Someone mentioned the argument that making Obsidian source-available with only a license to protect it will probably result in code theft, and I agree this will probably happen. But let’s turn the tables around. Our privacy is now protected only by a privacy policy. How can we trust that this won’t be used in a nefarious way? As EleanorKonik said above,
lawyers are expensive and legal battles are lengthy, costly processes, particularly internationally
This applies also for legal battles regarding disrespected and circumvented privacy policies.
KillerWhale said:
sync is E2EE
How can I confirm this? That’s right, I can’t. THAT is the basic idea behind making it open source. Or at least source-available.
Don’t patronise us, we have our reasons and they are not out of this world. If it won’t be open-sourced, fine. Do a security audit at least, then. Also, they can make the network & sync component a core plugin and open source only this plugin instead.
Heck, I’d even put a mechanism in place that would reveal as much code as there are paid members, by a factor. Say Obisidian aims at 5.000 regular paid memberships to survive and make a good enough profit. If they have 4.200 paid memberships at a particular moment, only 84% of the code that is current at that time will be revealed at that moment. If it reverts to 3.800 in six months, the revealed source will be reverted to 76% at that moment, etc. If it surpassed 5.000 and more, the whole code will be made available for review. So, by enough people supporting the creators revealing the code will be rendered inconsequential.
There are million of options here to increase trust in Obsidian’s security & privacy model. As I said above, we are keeping our private notes and stuff here, and we want to be sure there’s absolutely NO backdoors, nefarious and malicious code, or even plain old code that can be improved & ironed out.