And you believe that??? 😆

As a SaaS vendor, I guarantee Google knows how to use feature flags and conditionals to limit access to certain code paths. I know they do, because I also work for a SaaS vendor, and ex-Google employees are the ones who taught us how to do it. There is also no possible way it is as intertwined in the code as they are implying it is. It is awfully convenient for them to claim that, but it's nonsense. The stated goal of preventing students from accessing AI results is quite simple, from client side technical analysis alone I can tell, at least in most ways, how literally tacked on it is. While it wouldn't be an ideal solution, I can personally literally block it with a CSS rule. So could the schools, technically, and it would more or less achieve their goal. But most importantly, so could Google. The fact that they won't tells you everything you need to know about the honesty of their position.

Stop believing and repeating what they're claiming, you're giving near-trillion-dollar companies the benefit of the doubt but they've done nothing to earn that benefit. They're corporate liars, they're deliberately destroying the world and smashing holes in our civilization like a bull in a china shop, and we keep dancing around like we are afraid of being unfair to them, even while they are in the act of being unfair to us and literally standing in front of us telling us something we can see with our own eyes is not true. Just because they have lots and lots of money and lots and lots of platforms to make sure we have no choice but to know all the things they are saying, doesn't mean the things they are saying are at all trustworthy. We need to get over this habitual deference and stop giving equal weighting (or any weight at all) to corporate lies from untrustworthy sources.

Would you like to buy this brand new, lightly used bridge?

that sure was quick of them