The main judgement here seems to be: not everyone was there to get a refund, therefore, just entering the store is not an opt-in consent to biometric scans.
As a counter-example: Australian clubbing venues use facial recognition and id verification to identify banned individuals and detect fake documentation. This is required on condition of entry (therefore, opt-in), and this information is shared across all partner venues.
It's not a hard logic path to follow - If AI becomes a digital necessity for modern society to function, Microsoft's relevance shrinks while OpenAI's relevance grows.
Once OpenAI breaks out of the "App" space and into the "OS" and "Device" space, Microsoft may get absorbed into the ouroboros.
OpenAI's dependence on Microsoft currently is purely financial (investment) and contractual (exclusivity, azure hosting).
This mounts the current working directory into "public". Meaning, all .git, .env etc. will be publicly accessible.
Better form would be to mount a $PWD/src directory instead. The documentation needs to be updated better for newbies. Generally ill-advised. Documentation just needs better updating or warnings. Very dangerous to inexperienced devs.
In comparison the Laravel integration, it instructs the following:
Selling to developers is where i know it will struggle... Developers are cheap ass and would rather build it themselves at 10x the opportunity cost. And the moment it attempts to monetise itself in some form, there'll be a massive "betrayal" exodus a la Redis.