I was unspeakably disappointed to read in the blog that AgileBits has added to 1P/iOS an option for insecurely sharing passwords without also offering an option to securely share passwords.
I am unspeakably horrified (and, truth be told, mildly enraged) that you offer an "obfuscate" option. Export > Selected > Encrypted Web Page was dropped from 1P/Mac 3.6 on the ground that it wasn't super-strong and that a false sense of security is worse than no security. You have now built a sharing option that offers your users a false sense of security.
Allow me to offer a suggestion for implementing secure password sharing.
Every 1Password item gets a new field: Sharing password. Initially there is no field into which a user can type a password, only a Generate button that produces a seven-word Diceware-ish passphrase. Once the passphrase has been generated, an edit button appears after the generate button. This procedure will make sharing secure by default but allow a user who wants diminished security to achieve it.
When a user tries to share an item, the choices offered are plaintext and secure. If secure is chosen and a sharing password already exists, it is used. If not, 1Password generates a seven-word Diceware-ish passphrase and offers the same generate and edit buttons. When the secure share is sent, the sharing password is stored into the item.
The transmitted 1PIF never contains the sharing password.
The recipient must type in the sharing password in order to import the item, and the item is saved with the sharing password.
The sharing password need only be generated and communicated the first time that an item is shared, because in subsequent exchanges 1Password already knows how to encrypt and decrypt the item.
I can think of lots of tweaks, such as an option to assign a sharing password to a folder that would be inherited by all items in that folder, but the perfect is the enemy of the good. Just do it.
Whether or not you implement a mechanism for secure sharing along these lines, please either get rid of the obfuscate button or give us back Export > Selected > Encrypted Web Page, because so far as I can see there is no conceivable justification for offering your users the one without the other.