Two things I disagree with in this article. 1) I think the author is mixing up privacy and security here. At least to me, security is about whether the program

Two things I disagree with in this article. 1) I think the author is mixing up privacy and security here. At least to me, security is about whether the program has any bugs that allow access to data that the developer didn't intend. Developer's intent is important here, since a program itself does not have any intention, it always behaves exactly as it should. Privacy on the other hand, is whether the user has control over who has access to their data, assuming that the program is secure. So say, if iOS exfiltrated data to Apple, but was intentionally coded that way, then iOS might still be secure, despite not being private. On the other hand, I consider Linux private, because while you could always install malicious packages, it's still your choice to install those packages. 2) The article is specifically discussing security against plugins accessing data / processes outside the application. But this severely cripples the power of plugins. I recognize that this is subjective, but I prefer it when plugins can extend the application in very powerful ways. I think often plugin developers are more creative than the application developer. Chrome, Firefox, VS Code, all have some amazing plugins. That being said, I do like Standard Notes, and while I only tried the product for a little bit I appreciate rhe overall vision.