[Ssc-dev] Authentication, Authorization and Architecture

[Hans of Guardian]

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:

phone side
* phone meta data gatherer
* image/video/audio redaction
* image/video/audio data bundler, for putting data into files
* camera fingerprinter
* trickle sync uploader
* OnionKit
* IOCipher/SQLCipher
* content signing/encrypting (APG, GnuPG, etc)

server side (I don't know this side as well)
* trickle sync receiver
* meta data viewer
* upload verifier
* etc. 

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.

.hc

On Mar 8, 2013, at 12:03 AM, Nathan of Guardian wrote:

> Also one other thing in general that I will write more about late, but
> is the idea of "shipping early and often".
> 
> We have released 11+ versions of Orbot, Orweb and Gibberbot, because I
> am very focused on shipping releases of products when they are good
> enough, and them improving them over time. I have a real distaste for
> feature creep that causes our goal line to keep moving, product
> complexity to increase, and complexity to increase, without ever having
> something in use by real people.
> 
> At this point, we have been working on InformaCam proper for about a
> year, and we need to get a solid v1 release out there in a bad way. I
> intend to keep an obsessive focus on making that happen. I do intent to
> be aggressive about that goal, and will not apologize for it, because
> the sooner we get there, the better it is for us all.
> 
> +n