[Ssc-dev] Fwd: Re: "Server" update

[Wendy Betts]

Hi Nathan,

Sorry, one more question.  I noticed the preferences option has changed on the homepage to "settings" and "send credentials."  What does "send credentials" do?

Thanks.
________________________________________
From: ssc-dev-bounces+wendy.betts=int-bar.org at lists.mayfirst.org [ssc-dev-bounces+wendy.betts=int-bar.org at lists.mayfirst.org] on behalf of Nathan of Guardian [nathan at guardianproject.info]
Sent: 18 November 2013 16:59
To: ssc-dev at lists.mayfirst.org
Subject: [Ssc-dev] Fwd: Re: "Server" update

A new "Share IDs" option was added to the latest app release, and here
is what it does.

-------- Original Message --------
Subject: Re: "Server" update
Date: Mon, 18 Nov 2013 11:58:06 -0500
From: Nathan of Guardian <nathan at guardianproject.info>
To: Wendy Betts <Wendy.Betts at int-bar.org>,  John Shrives
<John.Shrives at int-bar.org>, Mark Ellis <Mark.Ellis at int-bar.org>,  Tim
Licence <Tim.Licence at int-bar.org>, Tim Hughes <Tim.Hughes at int-bar.org>,
 Nigel Richards <Nigel.Richards at int-bar.org>, Mandy Lee
<mandy.lee at int-bar.org>
CC: David Oliver <david at guardianproject.info>,
"bryan at guardianproject.info" <bryan at guardianproject.info>, Harlo Holmes
<harlo at guardianproject.info>,  "ssc-dev at lists.mayfirst.org"
<ssc-dev at lists.mayfirst.org>

On 11/18/2013 11:30 AM, Wendy Betts wrote:
> I have a quick question about the new version of the app.  I saw that a new sharing option has been added - "sharing IDs."  What exactly is submitted when that option is selected?

This is for directly sharing via email, sms or posting to social media
the unique identifiers ("hashes") for any media captured in
InformaCam/eyeWitness. All of this data is already in the J3M data
embedded in the media itself, and is unpacked and imported into the
Analyzer and Dashboard.

The unique identifiers are:

1) Media Hash - this is the unique "md5 hash" computed from the image
pixels or the video pixels+audio - that can be verified by anyone in the
future using the open-source FFMPEG command line tool. This verification
is built into the InformaRepo/Unveillance package automatically, but it
can also be done manually by anyone with ffmpeg.

2) J3M-ID or the "public hash": This is the unique code for a "secure
share" submission to a trusted destination. This is the code that you
can search by in the Dashboard / viewer user interface.

In general, this is a more advanced feature, and not required for the
default workflow. However, it does allow the user to do things like:

1) Post the id's to social media sites (twitter, facebook, etc) to
publicly notarize that the media file existed in this state at the
specific time they posted.

2) Send the id's as an SMS text message, for when they are out of
data/internet coverage, but want to notarize that the files existed in
this state at X time.

3) To notify a contact outside of the InformaCam app itself, that they
have posted this file to Y site, and they can use this identifier to
search for it or reference it later.

Best,
 Nathan


_______________________________________________
Ssc-dev mailing list

Post: Ssc-dev at lists.mayfirst.org
List info: https://lists.mayfirst.org/mailman/listinfo/ssc-dev

To Unsubscribe
        Send email to:  Ssc-dev-unsubscribe at lists.mayfirst.org
        Or visit: https://lists.mayfirst.org/mailman/options/ssc-dev/wendy.betts%40int-bar.org

You are subscribed as: wendy.betts at int-bar.org