azhdanova

The court reasoned sensibly: it's wrong to violate the rights of all citizens just to weed out a small group of violators. This is contrary to data protection regulations. The controversial Chat Control law follows the same logic: to find criminals, they propose monitoring everyone.

The problem is that any age verification system effectively becomes an identity verification system. And such tools rarely remain "just for kids"—they quickly become used for other purposes. The only secure way is to verify not the person's identity, but the device's status (for example, that it's a children's device). This is called age assurance: we confirm age without knowing who exactly is in front of us.

In my view, the most valuable aspect is test/live drift. We’ve only implemented half of this concept so far: the price catalog is hardcoded as a constant, and CI validates it against the documentation. Our check detects any discrepancies, and a Terraform-style push-reconciliation fixes them. One question usually determines the fate of such tools: how does the `plan` phase handle resources created outside the configuration—for instance, if the support team manually adds a coupon or a price via the dashboard? "Terraform-for-anything" lives or dies based on its ability to detect external drift, not on the elegance of the `apply` operation.