"How much efficiency am I sacrificing by making my app cryptographic instead of trust-dependent?" Though VB is talking about something different here, this question he poses is really core to all Privacy apps builders' thinking, incl us @fileverse There is a pleasant flip side to this though. By losing "efficiency" on your app by minimizing its trust assumptions + data collection (eg. having e2ee & zk based anonymity guarentees) you get other UX improvements that really make up for it! Some of my favourites: - faster onboarding. Cryptographic identity for sign ups/logins can be faster than mainstream OAuth flows with trust dialogues and verifications that are a cognitive strain - portability & interop. Everything follows your keys, you dont get the centralized migration pains (like arbitrary Policy changes) - offline basic operations. With less trust coordination and data sharing needed your App can partially work offline. Local cryptographic state updates → sync when connection is available