Add Meta Seal watermarking algorithms (PixelSeal, ChunkySeal, VideoSeal, AudioSeal, TextSeal)#48
Open
carlreid wants to merge 6 commits intoc2pa-org:mainfrom
Open
Add Meta Seal watermarking algorithms (PixelSeal, ChunkySeal, VideoSeal, AudioSeal, TextSeal)#48carlreid wants to merge 6 commits intoc2pa-org:mainfrom
carlreid wants to merge 6 commits intoc2pa-org:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Registers some of the open source watermarking algorithms from Meta Seal suite as soft binding algorithms for C2PA:
com.meta.pixelseal.1com.meta.chunkyseal.1com.meta.videoseal.1com.meta.audioseal.1com.meta.textseal.1I noticed the
com.aiwatermarkrelated entries, which appears to be a paid service exposing these same models. If I understand things correctly, then this algorithm list is to be used as a list of potential watermark implementations that would be required to detect all potential cases of content using a C2PA Soft Binding? Which leaves me a little concerned that it could lead to many paid providers re-exposing open source models, such that ultimately the C2PA manifest can't be discovered without paying for access. It seems a little counter intuitive to define an interoperable Soft Binding API spec, yet providers can register here behind paywalls.I have also included an additional fix in
README.mdfromsoftbinding-algorithm-list-schema.jsontosoftbinding-algorithm-list.schema.json.