This is what savvy developers are for. Make new stuff that you want.
This isnāt a what-if. It has been verified that the government has been using National Security Letters to force companies to compromise their systems and to not tell anyone that theyāve been ordered to do so (to the tune of people within the company not directly involved with the order donāt even know). See all the stories about this in regards to the Internet Archive, which challenged their letter (this rarely happens) and spoke about it:
https://www.aclu.org/national-security/internet-archives-nsl-challenge
Yes, you are correct. The solution is to build systems that function such it is incontrovertible that they have been compromised when they have been made to be compromised.
Build systems that function a certain way when they are unaltered, and when they have been altered they exhibit a different behavior and there is no way around that behavior.
And another way, as Iāve already said, is to facilitate the end-user to fulfill their own privacy in a simple way, like https was supposed to be. The end-user is āin controlā of their own privacy, because of the way the software was designed and interacts with them, but the provider is not-in-control of how those features play outā¦ just acts as a guiding light. Like how the power company gives you the juice, but they donāt dictate how much or how you use it.
This topic was automatically closed after 5 days. New replies are no longer allowed.
