I don't see how this could ever work, in practice. What constitutes a sufficient surveillance capability for a webapp that is constantly evolving? With every ch

I don't see how this could ever work, in practice. What constitutes a sufficient surveillance capability for a webapp that is constantly evolving? With every change to your app, you have to update the surveillance aspect as well. This seems like a real burden that limits innovation. > The requirements apply only if a threshold of a certain number of users is exceeded So, you start the next Instagram with barebones resources. You don't design/build surveillance into your admin console. Your service takes off, and then you have to stop accepting users after some magic number? The government needs to get over the idea that surveilling everyone in all circumstances is the best way to promote a civil society.