Cretezy

I've always maintained the idea that local state should be local, and global state should be global. In other words, I would suggest having the form state inside your widgets....

I had lots of request for something like this. My issue is one of the design choices for MasterPassX is that it is fully stateless. There's no syncing ever required...

1. MasterPassword doesn't provide store site options on the web version. I agree that storing site options is important but hassle-free syncing also is important. 2. 2FA isn't really possible...

I'm not very familiar with the CLI of mpw. Do they have `mpsites`? This new service would be a fully rebrand and would be incombatible with the MasterPassword algorithm but...

We could. Projects using this library will most likely be new and started using Python 3, so dropping 2 wouldn't affect much users. Do you want to make a pull...

Is this done?

Alright well let's try to keep Python 2 instead!

I turned it on and did a test push. I think we should add more Python versions to the travis, as in `pypy3` and the new `3.6`

I'm going to fix the tests today, it's just missing a working RECIPIENT_ID

I agree. I overlooked that. What to make PR?