>Anything created in an Adobe product has a hash and is synced to their cloud. Opening any asset in an Adobe product without Adobe content credentials is blocked entirely as it’s ‘not verified’.

Doesnt this address the wrong thing?

The risk is people migrating from Adobe to open source clones.

This solution sounds like it would prevent people from migrating to Adobe from open source clones.

So what?

>It enforces the idea that only Adobe can validate the authenticity and origin of an asset

Why would a user who wants to edit a photo need Adobe to do that?