<p dir="ltr">sorry to be so silent on this thread. I have a lot of thoughts that I'd like to add but due to travel I haven't gotten much opportunity to type.</p>
<p dir="ltr">Hans is right about modularity; this is why Barbra's api development efforts are key. however, we are going to have to limit it to functions that we can reuse across different builds of the product. iba-specific stuff that is not relevant to the project's core functionality should (for the most part) reside outside of the api.</p>
<p dir="ltr">I also believe that lee's authentication scheme is important, but we should be certain that the solution is applicable to other builds for other clients.</p>
<p dir="ltr">more to follow once I get to a computer...</p>
<div class="gmail_quote">On Mar 8, 2013 11:26 AM, "barbra" <<a href="mailto:blmack@gmail.com">blmack@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think you are right. <br><br>However, this is a research implementation (and a great, really pretty far along one I feel after reviewing global leaks). So, while it won't be impossible to modularize all of the functionality, it is pretty tightly intertwined right now, and not "kit"-like at all. This whole discussion started with a line of thinking that if we really wanted to begin to support these different levels (and even just different apps submitting content in), and we really wanted to be more of a flexible kit/framework we need to refactor with an API approach. <br>
<br>While we don't need the NSA-level security that Lee and I were discussing just yet (our motives were good :-) ), I do stand by the fact that an API really is something needed in the near-term if we want to be flexible/kit like. And I think it is a smart choice with big gains short-term and long-term, even for the work for GLSP and IBA. Though, clearly this will have to be for InformaCam 1.5/2.0.<br>
<br>-barbra<br><br><div class="gmail_quote">On Fri, Mar 8, 2013 at 11:07 AM, Hans of Guardian <span dir="ltr"><<a href="mailto:hans@guardianproject.info" target="_blank">hans@guardianproject.info</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Maybe I'm sounding like a broken record, but I think that the 'framework' approach would apply very well here, and give us the different consumer/pro levels. I think it will also help get InformaCam to 1.0 faster. In a quick overview, it would be a collection of frameworks something like this:<br>
<br>
phone side<br>
* phone meta data gatherer<br>
* image/video/audio redaction<br>
* image/video/audio data bundler, for putting data into files<br>
* camera fingerprinter<br>
* trickle sync uploader<br>
* OnionKit<br>
* IOCipher/SQLCipher<br>
* content signing/encrypting (APG, GnuPG, etc)<br>
<br>
server side (I don't know this side as well)<br>
* trickle sync receiver<br>
* meta data viewer<br>
* upload verifier<br>
* etc.<br>
<br>
Thinking like this gets to 1.0 faster because it means that we can ignore lots of feature requests and use cases for now, since the needed frameworks can be plugged in later. Also if its presented as a "kit" for building custom apps (e.g. IBA, GLSP, etc) rather than the one app that does everything, its already close to a good 1.0.<br>
<span><font color="#888888"><br>
.hc<br>
</font></span><div><div><br>
On Mar 8, 2013, at 12:03 AM, Nathan of Guardian wrote:<br>
<br>
> Also one other thing in general that I will write more about late, but<br>
> is the idea of "shipping early and often".<br>
><br>
> We have released 11+ versions of Orbot, Orweb and Gibberbot, because I<br>
> am very focused on shipping releases of products when they are good<br>
> enough, and them improving them over time. I have a real distaste for<br>
> feature creep that causes our goal line to keep moving, product<br>
> complexity to increase, and complexity to increase, without ever having<br>
> something in use by real people.<br>
><br>
> At this point, we have been working on InformaCam proper for about a<br>
> year, and we need to get a solid v1 release out there in a bad way. I<br>
> intend to keep an obsessive focus on making that happen. I do intent to<br>
> be aggressive about that goal, and will not apologize for it, because<br>
> the sooner we get there, the better it is for us all.<br>
><br>
> +n<br>
<br>
</div></div></blockquote></div><br>
<br>_______________________________________________<br>
Ssc-dev mailing list<br>
<br>
Post: <a href="mailto:Ssc-dev@lists.mayfirst.org">Ssc-dev@lists.mayfirst.org</a><br>
List info: <a href="https://lists.mayfirst.org/mailman/listinfo/ssc-dev" target="_blank">https://lists.mayfirst.org/mailman/listinfo/ssc-dev</a><br>
<br>
To Unsubscribe<br>
Send email to: <a href="mailto:Ssc-dev-unsubscribe@lists.mayfirst.org">Ssc-dev-unsubscribe@lists.mayfirst.org</a><br>
Or visit: <a href="https://lists.mayfirst.org/mailman/options/ssc-dev/harlo.holmes%40gmail.com" target="_blank">https://lists.mayfirst.org/mailman/options/ssc-dev/harlo.holmes%40gmail.com</a><br>
<br>
You are subscribed as: <a href="mailto:harlo.holmes@gmail.com">harlo.holmes@gmail.com</a><br>
<br></blockquote></div>