C2PA support
#4233
Replies: 1 comment
-
|
This would be very useful for us at Mastodon, as providing trusted information about an image source/processing is critical in those time of misinformation and AI-generated images. In our case, we could really use a way to add the identity information (Mastodon account) when the image is posted, and have an easy way to read the metadata so it could be returned by our API / displayed in the UI. I think this is a project that could be accepted into one of NLNet's open-source funding programs, and the Mastodon project can back the application if thats needed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
C2PA's official home is at https://contentauthenticity.org, the open-source software is at https://github.com/contentauth/c2patool, more depth at https://contentcredentials.org, slightly more human-readable explanatory blogs (from me) at https://www.tbray.org/ongoing/When/202x/2023/10/28/C2PA-Workflows and https://www.tbray.org/ongoing/When/202x/2024/10/29/Lane-Provenance
Tl;dr: PKI-based provable provenance for media files. Extra goodies: Details about what devices and software were involved in creating/manipulating the image.
Disclosure: No relationship with any of the C2PA organizations, just a photographer who cares about provenance and disinformation.
In a world with a lot of C2PA, what libvips should do is straightforward: Write a C2PA manifest into the EXIF saying the image was updated with libvips and some info about what was done. For extra credit, insert some identity information, e.g. a social media account, there are plenty of easy-to-access identity providers people might want to use. If there was already a C2PA manifest there do the right signature-chain things.
Beta Was this translation helpful? Give feedback.
All reactions