It's difficult to explain, but every time something like this comes up their responses frequently seem "off" and tone deaf.
I'm not sure they understand how much their product can become a part of how people go about their daily life, and how changing that, no matter how small, can have pretty significant effects, with an accompanying emotional response.
A while back they changed the way their vaults worked and you had to upgrade them. I've never been more nervous about an update to anything than I was with that update. The way the software communicated what was going to happen really didn't help, and there was a real feeling that this could all go horribly wrong.
Something I respect from Basecamp is their commitment to keeping their old products around (and keeping them maintained, even if they get no new features). They understand that they become a part of people's lives, and you mess that up at your peril. "Sunsetting" products or features has an impact on your customers that you need to be prepared for.
For reasons that are difficult to articulate I just don't trust AgileBits to not completely bugger up things for me in some way by changing something that they regard as unimportant, but to me is significant.
Even to me, this feels like I'm probably overreacting, but my passwords and online identities are so important that even the smallest hint of untrustworthyness is unnerving. The impact of losing all those details would be massive.
I'll be much more open to alternatives now than I would have been yesterday.
I chose to migrate to storing everything in iCloud Keychain instead. I understand why companies want to move to the subscription model, but I can't justify spending $36/year for an app to store my passwords.
I'm trying Bitwarden now and it seems to be ok. Maybe it's time for a change.
Bitwarden's clients are FOSS. There's a 3rd party FOSS server for it available written in Ruby. So you could even self-host.
[EDIT: there's one written in Rust as well! [1] [2]]
The free tier supports 2 users sharing.
If I ever need to sign into something on a non-Apple OS, I look up the desired iCloud KeyChain-stored password on my iPhone, then manually retype it on the other device.
I feel that gives me extra security.
Actually, manually typing or pasting your password (assuming you aren’t using WebAuthN) opens you up to phishing attacks because you could be fooled by the URL, whereas password managers and hardware tokens will activate only for the associated domain.
With Apple there's only one party involved.
My workflow involves sharing certain accounts with family members and 1Password supports that. For now, that's the killer feature for me.
We use GSuite, but that isn’t really relevant other than for controlling default ACLs to the document; you can just make a private Sheet and then share it by email to whoever you like.
Google Sheets works okay (for this use-case) pretty much everywhere you need it, including on mobile. Doesn’t auto-fill anything, of course, but since the point is sharing the password, not restricting the ACLs of the password in any enterprise sense (i.e. so people that could use a password before can then lose access to it), it’s fine to allow people to just cache the password into iCloud Keychain and/or Chrome Sync. So it’s not as much of a speed bump as you’d think.
I can punt on the cloud problems, but I'll pay for the convenience of a password manager in this case.
I did the same when 1Password moved in this direction after version 6. It was clear then that the stand alone version was going away.
what?
it’s not just storing your passwords. you could use a spreadsheet or plain text file for that.
$36/yr is NOTHING. this is great value for money.
Will keep this in mind when recommending to family and friends, which I do a lot, and will definitely keep an eye out for alternatives moving forward.
The latest extension for Chrome on Windows and Mac barely works for me half the time with the latest update.
When you have sync issues, the workaround in the absence of a Force Sync button (which used to exist) is to create a dummy secure note or to log out and log in again.
Most users won't know this workaround without spending several minutes Googling and digging through search results.
I complained about the lack of a Force Sync button on the clients in the forums, and was told this:
"The reason we don't want too easy an option to force a sync is precisely because folks will choose to use that rather than reaching out to find the root cause"
Needless to say, I wasn't pleased to find out that they wanted to use their paying customers as free testers.
I'd like to switch away, but most of the alternatives I've looked at don't compare very favorably from a UI/UX perspective.
The UI in general also just feels clunky. It's missing that polish the mac app has.
In many ways, I feel that the Windows and Android clients in particular are still second class citizens compared to their Mac/IOS counterparts.
Simple tasks like resetting a password or adding an entry in 1Pass can often be frustrating now.
Previously, with every restart of the phone, you needed to enter master. After, only when the pin is misentered once. They added this ‘new feature’ right when I was installing everything on a new personal laptop. As I recall it, I was entering the master password on my phone, over and over. One of the characters had a shift, which was a pain in the . On iPhone. So I made it lower case. Then, I updated my phone, got the 1password update, and didn’t enter the master for over a month.
Finally, I misentered the pin, and got kicked to the master. Well, you can guess what happened. I was locked out.
You know, a password works because you remember it. My situation revealed the design flaw of bypassing that. If you don’t enter the master for a long time, you lose the habit and increase the risk of losing it.
For me this is the classic example of the corrosive drive to renew a perfectly good product, which ruins the product for some users. But as a designer, I think it’s a fail, but you can’t tell them that.
The pin thing is a big time saver because typing on mobile still sucks, and I'd have to re-type the master everytime I switch between an app and 1Pass. I certainly wouldn't qualify it as a bad feature.
It's a complex system. I had a use-pattern that naturally emerged from the UI (which required the master after reboot), and my habit of turning off my phone every night. So this "feature enhancement" seemed innocuous, but had, I would argue, the unintended consequence that I lost my memory of the master because of a new feature.
I believe this is exactly the sort of thing a smart company, making a security product, should think about before they decide to add a "feature enhancement".
I mistook the great design of the original 1Password product as an indication of a "smart company" who made great decisions, and great products through testing and design.
Now I feel differently. Now I just see another one-hit wonder, who makes improvements by the wiz-bang theory. New! New! New and improved!
The unpopular decisions to drop the standalone version (local vault) is just more evidence to me that AgileBits isn't special. I put them on a pedestal with devotion and evangelism, but they're no different, and maybe worse.
And if you like this rant, you might also like my rant on TransitApp. hahah!
[1]: Before with 1Password I would have to enter the master once every 1-2 weeks. Now with Bitwarden using the same 1-fail bin to master UI, I think I've not defaulted into master for, I dunno, 6-8 months? But I've learned my lesson. I wrote the master on a piece of paper and tucked it away in a book somewhere on my bookshelf. What could go wrong?
I feel like it may be an inexorable and unavoidable consequence of an aging codebase.
That all being said, I absolutely agree the emojis almost always are perceived in a way that’s opposite of the intent, e.g. smug, sarcastic, or some other negative tone.
> one of the developers chiming in about how they must be asking to "make their mobile apps free"
That isn't the actual quote. The developer is pointing out that the apps are "free to use as companions to our desktop apps".
> the other guy talking about how with so many users anything they do will of course be found out
This did come across clumsily, but it was in response to the false dilemma "Was it forgotten, or deliberately not mentioned in the hopes nobody [would notice]?"
Keepass comunity solutions are strong and open source. And free.
What if I have an issue in the future? Will I also be treated poorly?
The OP just wanted to know if the feature was gone, and if so when did it get removed (maybe to find an archived version of the app?), and lastly why it wasn't clearly communicated, but you can just smell the smug in the responses. It's hard for me to read their little "cute" emoji as anything but sarcastic, which is reinforced by one of the developers chiming in about how they must be asking to "make their mobile apps free" and the other guy talking about how with so many users anything they do will of course be found out.