the control changes sound like you might have gotten caught in some kind of a-b testing

A determined instigator could easily continue pushing modern yellow journalism with little problem under the system you propose.

They simply need choose which negative stories they print, which opinions they run. How do you frame misrepresentation vs a differing point of view? How do you call out mere emphasis on which true stories are run. Truths are still truths, right?

It's not infrequent today to see political opinions washed through language to provide reasonable deniability by those using it.

Hell, it's not infrequent to see racism, bigotry and hate wrapped up to avoid the key phrases of yesteryear, instead smuggling their foulness through carefully considered phrases, used specifically to shield those repeating them from being called out.

'No no no. Of course it doesn't mean _that_, you're imagining things and making false accusations.'

Azure and GitHub build pipelines are written in yaml and have conditionals, variables, template expansions, etc

>That wouldn't be a bad thing

The government should be the government, and corporations should be corporations. Nothing good will come of having them bleed together.

Like church and state, you keep them separate for the good of both.

creating your uuids client side has a risk of clients toying with the uuids.

creating them server-side risks having a network error cause a client to have requested a resource be created without receiving its id due to a network error before receiving the response, risking double submissions and generally bad recovery options from the UI.

if you need users to provide uuids for consistent network operations, you can have an endpoint responsible for generating signed uuids that expire after a short interval, thereby controlling uuid-time drift (must be used within 1-5 minutes, perhaps), ensuring the client can't forge them to mess with your backend, and still provide a nice and stable client-side-uuid system.

for the uuidv47 thing, you would apply their XOR trick prior to sending the UUID to the user. you presumably just reverse the XOR trick to get the UUIDv7 back from the UUIDv4 you passed them.