Hi all - some edits below. Looks like we need to come to a conclusion on #2.<div><br>Sam<br><br><div class="gmail_quote">On Tue, Jan 29, 2013 at 12:56 PM, Bryan Nunez <span dir="ltr"><<a href="mailto:bryan@witness.org" target="_blank">bryan@witness.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Nice work Nathan and Harlo! I just added my 2 cents to the first question, otherwise I think it's pretty good.<div>
<br></div><div>Thanks,<br>Bryan<br><br><div class="gmail_quote"><div class="im">On Tue, Jan 29, 2013 at 12:43 PM, Sam Gregory <span dir="ltr"><<a href="mailto:sam@witness.org" target="_blank">sam@witness.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Will review once out of my meeting - so give me an hour or so.<span><font color="#888888"><br>S</font></span><div>
<div><br><br><div class="gmail_quote">On Tue, Jan 29, 2013 at 12:38 PM, Harlo Holmes <span dir="ltr"><<a href="mailto:harlo@guardianproject.info" target="_blank">harlo@guardianproject.info</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yeah, replace my #2 with what Nathan says. I hate answering those questions... <div><br></div><div> And yes, for #1, you can send it off via email (or better yet, PGP-encrypted email) to someone and still maintain your data. </div>
</div><div class="gmail_extra"><div><br clear="all"><div><div>++++++++++++++++++++++++++</div><div>Research Fellow, Head of Metadata</div><div><a href="https://guardianproject.info" target="_blank">The Guardian Project</a></div>
<div><br></div><div>pgp: 0xA4469630</div><div>twitter: @harlo</div></div>
<br><br></div><div><div><div class="gmail_quote">On Tue, Jan 29, 2013 at 12:32 PM, Nathan of Guardian <span dir="ltr"><<a href="mailto:nathan@guardianproject.info" target="_blank">nathan@guardianproject.info</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div><br>
A few addition/mods inline - Sam/Bryan, please take a look, to
make sure we aren't straying too far from or missing any major
points.<div><br>
<br>
<br>
On 01/30/2013 12:16 AM, Harlo Holmes wrote:<br>
</div></div><div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Jan 29, 2013 at 10:43 AM,
Nathan of Guardian <span dir="ltr"><<a href="mailto:nathan@guardianproject.info" target="_blank">nathan@guardianproject.info</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<pre style="white-space:pre-wrap;word-wrap:break-word;font-family:sans-serif;margin-top:0px">1. Does the recipient of the photo or video file also need the app or are there other ways to process the data?
</pre>
</blockquote>
<div><br>
</div>
<div>An InformaCam user is supposed to submit their
media to a remote server, which process the photo or
video. The user can always choose to export their photo
once it's been taken, and it can be looked at on the web,
shared over twitter, or posted to a blog. However,
exporting "breaks the seal" so to speak, and the data can
no longer necessarily be trusted.</div>
</div>
</div>
</div>
</blockquote>
<br></div>
Hmm. Is this true though? Couldn't someone decrypt/parse/verify the
metadata in the image, as long as they had the spec for J3M and the
InformaCam embed info? I can send a signed/encrypted OpenPGP email
through an insecure system w/o corrupting the email itself, right?<br>
<br>
I think it is okay to say that from a legal perspective, we want to
keep it in a closed system, but that from a format perspective and from usages outside the legal area, we
want to have an open, non-proprietary format that many tools can
support.</div></blockquote></div></div></div></div></blockquote></div></div></div></blockquote></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_extra"><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div><br></div></div>
</blockquote></div></div></div></div></blockquote></div></div></div></blockquote><div><br></div></div><div>Would it be helpful to mention the hash function here? The trustworthiness of the data isn't the issue but rather maintaining the chain of custody. Sending the hash to a trusted repository in advance of uploading the file helps to do that.</div>
</div></div></blockquote><div><br></div><div>SAM: Can someone tidy up this response; I think we need to emphasize the remote server is run by a human rights group, a news org, an individual etc. But someone you pick whom you trust. Also need to incorporate the questions Nathan raised, Bryans comment re hashing (relevant in any broader application of informacam like functionalities, e.g. on a platform), and Harlo's response re sending via email too.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="gmail_quote"><div><div class="h5">
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_extra"><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<pre style="white-space:pre-wrap;word-wrap:break-word;font-family:sans-serif;margin-top:0px">2. How do you make sure that the files are not manipulated via hacking the app or so?
</pre>
</blockquote>
<div>We are carefully and continuously auditing our
code so as to minimize ways the app can be hacked. We are
an open source project, and encourage members of our
community to help make our code more robust. We are also
aware of "the analog hole" in digital media, which never
fails to poke holes in even the most foil-proof systems of
security.</div>
</div>
</div>
</div>
</blockquote>
<br></div>
I would perhaps say something like this:<br>
<br>
With InformaCam we are working towards standards of evidence that are held by international criminal courts, and making sure that in doing so we raise the bar for a whole range of other users seeking verification, such as news organizations handling citizen-sourced media. Through our partnership
with the International Bar Association, we are trying to understand what it
takes for an app to provide enough checks and metadata to make media much more admissible and probative. We also think that
in some cases, the app and mobile device itself could become part of
the verified evidence or part of the process of confirmation, much like a gun being matched to a bullet or a particular system can be verified as technologically reliable.. <br></div></blockquote></div></div></div></div>
</blockquote></div></div></div></blockquote></div></div></div></div></blockquote><div><br></div><div>SAM: Have made some amends above. Does Nathan's answer fully go to the hacking side? I think he's asking more about the possibilities of spoofing etc? The evidence side is going to be more about improving admissibility not an absolute guarantee.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="gmail_quote"><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<pre style="white-space:pre-wrap;word-wrap:break-word;font-family:sans-serif;margin-top:0px">3. Is there a way to verify user-generated content that was not shot or edited using InformaCam?
</pre>
</blockquote>
<div><br>
</div>
<div>Forensic analysts specializing in digital
media have plenty of methods of verifying photos and
videos; we employ some of those methods when processing
media submitted from the app to the servers. However, one
of InformaCam's key concepts is establishing
an auditable chain-of-custody to lend weight to the
"trustworthyness" of the media. This is something that
cannot be done with forensics alone.</div>
</div>
</div>
</div>
</blockquote>
<br></div>
I would add this:<br>
<br>
This is not to minimize the potential of combining InformaCam with
social or crowd-source verification, as we have seen Andy Carvin at
NPR do, or what the team of editors at Storyful.com do. From a news
journalism perspective, being able to reach out and cross-verify a
photo or video from multiple independent eyewitness sources using good journalistic practice, should complement and build on sorting through data and code. Ultimately, we see our work with InformaCam providing more
data points to both journalistic and legal verification processes, not
replacing them.<div><br></div></div></blockquote></div></div></div></div></blockquote></div></div></div></blockquote></div></div></div></div></blockquote><div>SAM: Minor amends above. Good to reflect the fact that this can complement both forensics approaches and social/crowd-sourced verification, and good journalism. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="gmail_quote"><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div>
<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<pre style="white-space:pre-wrap;word-wrap:break-word;font-family:sans-serif;margin-top:0px">4. Will the app stay limited to Android devices? Will it be available via the official channels (Google Play, AppStore etc.)? When will the pilot version be available?</pre>
</blockquote>
<div>We are piloting the app with partner
organizations instead of releasing to the general public
just yet. <br>
</div>
</div>
</div>
</div>
</blockquote></div>
, however, the source code is completely open-source, and available
for any interested users or groups to join in the development and
testing process. Ultimately, we do feel InformaCam can be relevant
to activities beyond documenting human rights and global crisis, be it documenting an insurance
claim, or gathering rich metadata for historic or personal archiving
reasons.</div></blockquote></div></div></div></div></blockquote></div></div></div></blockquote></div></div></div></div></blockquote><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="gmail_quote"><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_extra"><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>We do think about developing a version for
iOS, but Android is better suited to this project for so
many reasons: world-wide reach, licensing, and most
importantly, hardware. As we've recently seen with the
release of the Nikon Coolpix and Samsung Galaxy cameras,
Android is becoming better integrated with better
pro-sumer hardware; it's exciting to see where this is
leading. Ultimately we'd like to see the types of 'citizen witnessing' functionalities we're developing with InformaCam mainstreamed into everyday tools for filming and sharing.</div></div></div>
</div></blockquote></div></div></blockquote></div></div></div></div></blockquote></div></div></div></blockquote></div></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="gmail_quote"><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_extra"><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div><blockquote type="cite">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> </div></div></div></div></blockquote></div></div></blockquote></div></div></div></div></blockquote></div></div></div></blockquote></div></div></div></div>
</blockquote><div>SAM: Minor adds. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="gmail_quote"><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div><br></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><div><div>-- <br>Sam Gregory<br>Program Director<br>WITNESS<br>80 Hanson Place<br>Brooklyn, NY, 11217, USA<br>Tel: <a href="tel:718%20783%202000%2C%20ext%20309" value="+17187832000" target="_blank">718 783 2000, ext 309</a><br>
Fax: <a href="tel:718%20783%201593" value="+17187831593" target="_blank">718 783 1593</a><br>Email: <a href="mailto:sam@witness.org" target="_blank">sam@witness.org</a><br>
Follow me on Twitter: @samgregory, @witnessorg, #video4change<br>Blog: <a href="http://blog.witness.org/author/sam" target="_blank">blog.witness.org/author/sam</a><br><a href="http://www.witness.org" target="_blank">www.witness.org</a><br>
<br>See It. Film It. Change It.<div><br></div><div><span style="color:rgb(34,34,34);font-size:12.800000190734863px;font-family:Helvetica">WITNESS and The Guardian Project have been named a <a href="http://blog.witness.org/2013/01/how-informacam-improves-verification-of-mobile-media-files/" style="color:rgb(17,85,204)" target="_blank">Knight News Challenge for Mobile winner for InformaCam </a>- a mobile app that improves verification of mobile video and photos. </span></div>
<div><i style="color:rgb(34,34,34);font-size:12.800000190734863px;font-family:Helvetica"><br></i></div><div>New Blog: <a href="http://blog.witness.org/2012/07/visual-anonymity-and-youtubes-new-blurring-tool/" target="_blank">Visual Anonymity and YouTube's New Blurring Tool</a></div>
<div><br></div><div>Have you seen the new <a href="http://www.youtube.com/humanrights" target="_blank">Human Rights Channel</a> on YouTube? <a href="http://blog.witness.org/2012/03/kony-2012-juggling-advocacy-audience-and-agency-when-using-video4change" target="_blank"><br>
</a><br>Read our new report "<a href="http://www.witness.org/cameras-everywhere/report-2011" target="_blank">Cameras Everywher</a>e" for recommendations on what we can all be doing to make the use of video for human rights safer and more effective<br>
<br></div>
</div></div></blockquote></div></div></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br>Bryan Nunez<br>Technology Manager<br>WITNESS<div><a href="tel:%2B1%20%28718%29%20783-2000%20x-348" value="+17187832000" target="_blank">+1 (718) 783-2000 x-348</a></div>
<div>GPG ID: 54E3286C7C631254</div><div>GPG Fingerprint: 6115 6A41 0F5A 9AA0 67B6 79D8 54E3 286C 7C63 1254</div>
<div><br></div><div><span>Check out our <a href="http://www.youtube.com/humanrights" style="color:rgb(17,85,204)" target="_blank">Human Rights Channel</a> on YouTube</span></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Sam Gregory<br>Program Director<br>WITNESS<br>80 Hanson Place<br>Brooklyn, NY, 11217, USA<br>Tel: 718 783 2000, ext 309<br>Fax: 718 783 1593<br>Email: <a href="mailto:sam@witness.org" target="_blank">sam@witness.org</a><br>
Follow me on Twitter: @samgregory, @witnessorg, #video4change<br>Blog: <a href="http://blog.witness.org/author/sam" target="_blank">blog.witness.org/author/sam</a><br><a href="http://www.witness.org" target="_blank">www.witness.org</a><br>
<br>See It. Film It. Change It.<div><br></div><div><span style="color:rgb(34,34,34);font-size:12.800000190734863px;background-color:rgb(255,255,255);font-family:Helvetica">WITNESS and The Guardian Project have been named a <a href="http://blog.witness.org/2013/01/how-informacam-improves-verification-of-mobile-media-files/" style="color:rgb(17,85,204)" target="_blank">Knight News Challenge for Mobile winner for InformaCam </a>- a mobile app that improves verification of mobile video and photos. </span></div>
<div><i style="color:rgb(34,34,34);font-size:12.800000190734863px;background-color:rgb(255,255,255);font-family:Helvetica"><br></i></div><div>New Blog: <a href="http://blog.witness.org/2012/07/visual-anonymity-and-youtubes-new-blurring-tool/" target="_blank">Visual Anonymity and YouTube's New Blurring Tool</a></div>
<div><br></div><div>Have you seen the new <a href="http://www.youtube.com/humanrights" target="_blank">Human Rights Channel</a> on YouTube? <a href="http://blog.witness.org/2012/03/kony-2012-juggling-advocacy-audience-and-agency-when-using-video4change" target="_blank"><br>
</a><br>Read our new report "<a href="http://www.witness.org/cameras-everywhere/report-2011" target="_blank">Cameras Everywher</a>e" for recommendations on what we can all be doing to make the use of video for human rights safer and more effective<br>
<br></div>
</div>