Comment by illwrks | Hacker News Reader

Comment by illwrks | Hacker News Reader

I think Adobe I will quickly lean into Content Credentials, across the entire creative suite workflow.

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’.

Any real business that uses Adobe software will be locked into it and it will shut out things like this from competing in a commercial sense.

It enforces the idea that only Adobe can validate the authenticity and origin of an asset, as well as builds a moat.

They could easily roll it out, it introduces more friction from a creative production point of view but they may have no choice now…

That would be pretty much anti-competitive and illegal.

>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?

I work as a designer, I use a lot of their tools at a professional level. My perspective is from a place where Adobe software is embedded in processes, I could change my software but I will receive assets that will be done with the latest tools. Likewise I could supply files from these tools but then the person receding it may not be able to use them. I’m sure there are a lot of people using bits of Adobe software but there are much more using it in a career and it would be impossible to switch and there’s an opportunity for Adobe to turn the screw and lock down the processes in the creative pipeline.

Reply on news.ycombinator.com