@rasterweb
For a #Cryptographic #AI #ImageProtection solution in the browser,
Create an #OpenSource javascript library that can take an encrypted asset and then decrypt it. Then render the image in a #HTML5 <canvas> tag.

I see two possible implementations:

1. #openkey system - meant to add a decryption step; it won't stop anyone who uses the same library to decrypt it. which requires willful intent to steal the image.

2. use a private system, and use auth or payment to release a key

@rasterweb Ultimately, #AI #ImageProtection will likely depend on some registration service that will index the image, register its existence, licenses, and restrictions, and then will depend on the legal system to go after bad actors.

This would take years or decades to come full circle, but getting around copy protection on CDs, DVDs, and Blu-rays has set some case law and example law on the topic, so it's not brand new.

@rasterweb
#metadata and #microformats could provide #AI #ImageProtection by clearly labeling the usage rights of the artwork being scraped or sampled. This won't prevent bad actors, but it will make it easy for people and companies to do the right thing.

Just ingest the microformat and see if it meets your use-case.

#Flickr has similar metadata on many images in its APIs, but the spec could use an update for the #AI age.

@rasterweb
#Cryptographic #AI #ImageProtection can work for a few reasons

1. declares an intent to protect
2. amplifies #copyright law around encrypted content
3. scrappers are usually simple, and this adds complexity at a different layer than the machine learning algorithm
4. #cryptography adds compute time to the process; how much depends on how dense the method is.

But #metadata and #microformats are also useful