So I've picked through sync.com and for the most part is was pretty easy to follow. 1Password has been the opposite.
I can see there are a few items stored in localStorage (email,deviceUUID,prefix and encrypted account key?) I notice that images come through on scroll in the form of data URIs others as png files so I am thinking all or most of the text data comes through at once. I should mention I get a ton of failures with png. I see some protocol switching, a bunch of overview requests, password lists, misses from Cloudfront etc.
Anyway I can go on but is there a breakdown of how the web app works? I expected keys to be in localStorage however the only piece that seems to be in there is the account key which only effects the next login if changed. So keys are being decrypted and stored somewhere other than Chrome cache or localStorage.
I'd love to know as much as possible however no comments and 20,000+ lines of JS in one file (a lot of which I can barely if at all understand) leads me hear asking for a breakdown. My recommendation is/has been 1Password to clients and for most the web app is not a thing they use but it came up as a few went on vacation and asked questions about the web app I could no answer. I personally am on families but I assume something like this is the same regardless of teams which they are on.
Thanks in advance,
@jpgoldberg seems to like these questions perhaps he can
Also can't say this enough you guys rock! Though I did just do the most recent Windows client with a new client and I had to keep saying this is not how it works on Mac. Hopefully it catches up
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided