Three Strikes

ninjaroll
ninjaroll
Community Member
in Mac

To be honest, I'm still a fan of 1P, but the recent upgrade to 4 REALLY broke my workflow, and I'm really considering rolling back to 1P3 if even possible. Here is my experience.

Strike one: I have three Macs, two of which are running the latest OS. My work machine is currently on OSX 10.7.x I upgraded both my 10.8 machines to 1P4. Then it was my work machines turn. To my surprise, and I should have read the minimum requirements first, 1P4 does not work with OSX 10.7.

Strike two: My main browser is Chromium. 1P4 does not work with Chromium.

Strike three: I'm a web designer/developer which means I'm responsible with many many many client's servers. I use a GUI sftp application called YummyFTP, and to my surprise, I cannot paste the sftp credentials into it. Doing a bit a research, I found the blog post on Agile regarding this. The post states that applications that use an older pastboard API will not work with 1P4....great.

I spoke with the developer and this was his response:

Well that's pretty poor of 1Passwd ... personally I would complain to the developer : yes, Yummy uses Carbon and yes, there is v2 (a complete rewrite) in the works, but all those apps and of course Yummy FTP are supported by the OS, even the upcoming 10.9, so for the developers to eliminate a few lines of code (no exaggeration!) at this point is premature, and only serves to inconvenience their own users.

1Password is a great application, don't get me wrong, but damn, you guys really know how leave people behind (anyone remember the release of 1P3??)

Comments

  • MikeT
    MikeT
    edited October 2013

    Hi @ninjaroll,

    1. If you send us an email to support+forum@agilebits.com with your proof of purchase at Mac App Store, we'll give you a free license to download 1Password 3.8.x for your older Macs. Apple's working on an update to the Mac App Store that'll let you download the compatible apps for older OS X versions. So, in this case, it'd show you 1Password 3.9.x on Lion and 4.x on Mountain Lion > Mavericks.
    2. That's because Chromium won't code-sign their browser, we need a code signature to improve the security of our browser extensions and our app, so that the browsers have not been modified by anybody other than the company or the group that made it. Firefox doesn't seem to have a problem signing their cutting edge versions. We are getting a lot of feedback from our Chromium users and we're trying to find a way to see if it is possible to whitelist Chromium to work without breaking the security system that we've worked so hard to improve in 1Password 4.
    3. This is not a permanent problem, it's just a known issue right now in 1Password 4 because of the incompatibility issues bought up between our own pasteboard type and the older Carbon pasteboard APIs. The OS X is suppose to convert between them automatically but it is not. We have some ideas to try to fix this and hopefully, we'll get this resolved soon.
This discussion has been closed.