A few of the bits I could find from the hangout (part 1) on this topic ...
12:18:
bytemaster : The answer is no. If you want the equivalent of an unregistered account, register the account to the hash of some random characters. The reason is the way the new protocol is structured. Scalability & performance discussion : transactions are 100 bytes, where bitcoin is 250 bytes, because the transfer operation is referring to account ID's instead of addresses. Which means we're using 3 bytes instead of 24 or 32 bytes to reference accounts. All permissions are based on KeyID's which are a couple bytes rather than 32 bytes. Any key has to be registered before it can be used.
40:15:
fuzzy : Can transactions have public memos/encrypted memo's?
40:33:
bytemaster : Yes, it can have both.
41:05:
bytemaster : encrypted email would be expensive.
41:18:
bytemaster : Multisig/Multisign is more advanced than any other blockchain out there. We have proposed transactions where all multisig particpants only have to click "approve".
42:31:
bytemaster : Security. Your private keys will be more secure than ever, especially with 2FA and Multisig, withdrawal permissions and daily spending limits.
45:19:
bytemaster : It's at least as secure as most of the current banking infrastructure, balancing ease of use, security, scalability.
45:37:
bytemaster : We are implementing features that make it easy to verify that you're sending to the right person.
46:50:
bytemaster : 3FA possible, mostly automated.