Replies: 5 comments · 1 reply
-
|
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.
-
|
More and more cameras support C2PA (I keep a list here https://c2pa.camera), journalistic integrity on fedi could really use this. |
Beta Was this translation helpful? Give feedback.
-
|
I've made an enhancement issue. Thanks for suggesting this! |
Beta Was this translation helpful? Give feedback.
-
|
The enhancement issue: #4420 (not sure why github didn't link it automatically) |
Beta Was this translation helpful? Give feedback.
-
|
Just noticed this discussion, I wrote a related blog article on a use case some months ago: |
Beta Was this translation helpful? Give feedback.
-
|
By a weird coincidence, I just in the last ten minutes published this: https://www.tbray.org/ongoing/When/202x/2025/06/17/More-C2PA It talks (among other things) about issues with open-source and C2PA. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
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