Ancestors

Written by Chris Needham on 2024-10-17 at 09:44

An interesting couple of days talking content authenticity and C2PA with news industry folks

=> More informations about this toot | More toots from chrisneedham@w3c.social

Written by Jeffrey Yasskin on 2024-10-17 at 14:10

@chrisneedham What's your impression of its usability and generality? I heard a rumor that it was being accidentally designed for only large entities to use, which would be a shame.

I imagined that it would have two modes: 1 where the hardware has a secure element that signs pictures (and we collectively distrust hardware that gets hacked), and a second where anyone can create a private key and assert modifications with it (and we aggregate and distrust folks who lie)?

=> More informations about this toot | More toots from jyasskin@hachyderm.io

Written by Jeffrey Yasskin on 2024-10-17 at 14:20

@chrisneedham In (at least) the second mode, we'd need at least one governance body (kinda like a certificate authority, maybe) to help everyone decide whether to trust the signing keys.

[#]KnowledgeCommons...

=> More informations about this toot | More toots from jyasskin@hachyderm.io

Written by Chris Needham on 2024-10-17 at 14:48

@jyasskin There are two main strands to it. One is C2PA itself which is about signed metadata that's bound to content (images, video, audio, anything with a container format), where the signing is done by the hardware or software used to capture and edit. This creates a chain of metadata for how that content got created, what edits were made, etc. It's not about saying what's "true" or not, just verifiably how it came to be

=> More informations about this toot | More toots from chrisneedham@w3c.social

Toot

Written by Chris Needham on 2024-10-17 at 14:49

@jyasskin Now this in itself brings risks that will need to be worked through, but I understand there's a redaction feature that allows sensitive details to be removed.

=> More informations about this toot | More toots from chrisneedham@w3c.social

Descendants

Written by Chris Needham on 2024-10-17 at 14:55

@jyasskin The second part, which a related group called Creator Assertions WG is working on, is around "identity", i.e., the "who" created and published the media. IPTC (news industry standards) are currently looking to set up a CA that can issue certs to news media orgs (and presently distinct from the CA for device/editing software certs).

=> More informations about this toot | More toots from chrisneedham@w3c.social

Written by Chris Needham on 2024-10-17 at 15:01

@jyasskin The BBC use case involves the latter much more than the former. It wants to be able to show "this content genuinely comes from us", regardless of where you see it (on social media, etc), because there's lots of misleading content out there using our branding etc.

=> More informations about this toot | More toots from chrisneedham@w3c.social

Proxy Information
Original URL
gemini://mastogem.picasoft.net/thread/113323315802752285
Status Code
Success (20)
Meta
text/gemini
Capsule Response Time
284.058843 milliseconds
Gemini-to-HTML Time
0.980071 milliseconds

This content has been proxied by September (3851b).