Basics of message syncing done

on sync, loop over each persona and pull out the messages for it. relies
on persistent challenges. if challenge/response fails, it generates a
new one and tries again. works really well, so far.

once we have the ability to do more than one persona, this may be
unwieldy and require batch-vaildation of challenges. for now, screw it,
this works great.
Message.send takes a persona for the to now instead of a persona id.
adding notes/messages buttons in header
only show notes/messages buttons when logged in
Merge branch 'master' into message
adding messages skeleton
lots of changes, getting messaging figured out. not there yet
breaking out persona listing into its own controller (for contact search) and also creating the skeleton of persona search
Merge branch 'master' into message
Merge branch 'master' into message
message send finished >=]. now need to work on conversation/message listing (and reply). got my work cut out for me...
disable sync on logout (duh)
new composer, supports a better extension model
implementing composer changes, still buggy messaging...fuck
new composer version (extension bugfixes)
fixing message serialization
updated sharedkey protected model: all data is encrypted via random AES key, and THAT key is pubkey encrypted and saved with the models data. HOWEVER since pubkey is not yet implemented, the AES key for the model is sitting in plaintext in the DB.
messaging updates/styling
removing jenky event bubbling and implementing model-based events for selecting conversations
making progress, but tons of shit broken at this point (mainly replies: verification of owned persona fails). lame.