Staff dev on 1Password’s developer tools here. We screwed this up in our first few releases of the 1Password CLI, largely out of ignorance. Those releases stored config in $HOME/.op at first. But early feedback pointed us to XDG, so we migrated. Now we check:
1. $XDG_CONFIG_HOME/.op (if var is set)
2. $HOME/.config/op
3. $HOME/.op
I hate to be the dev who says “I don’t know why those other code bases find it so difficult that they put up a fight” but our `findConfigDirectory()` function isn’t exactly complicated, even when you consider all the operating systems that the 1Password CLI supports.
I love JMAP. It's what allowed me and my team (at 1Password) to easily add support for Masked Emails, where we randomly generate your email address in addition to your password.
I've been a happy Fastmail customer for years prior to working on this feature. I've used a wildcard with my Fastmail account, created a new email address for each service I sign up with, and stored that email address in 1Password. All by hand. It's a tiny hassle, but one that I think is worth it.
The Masked Email integration makes that entire process automatic. It's even easier than before. It's enough to convince a few Fastmail-using friends to start doing it.
I can't fully speak for the Fastmail folks, but I know that there are a few upper limits for how many masked email addresses that one account can create. We tried to set them unreasonably high to allow for all manner of legitimate use while still preventing bad actors. They're also monitoring usage and tuning that limit. Plus, you can always email support and ask for a increase for your specific account, if you ever bump up against it.
Definitely! You can decide within Fastmail’s settings[0] which domain you want to use for masked emails. It can be fastmail.com, one of their fun domains like afcrichmond.uk, or one of your own. I've even seen some 1Password coworkers buy a brand new domain purely for their masked emails, so you can generate a “[email protected]” while still using “[email protected]” for your actual personal email.
True! I've been doing [email protected] for a few years now with Fastmail. This makes it one step easier to generate that email address, as well as one-click blocking any alias that starts receiving spam.
Hi, one of the 1Password engineers who worked on this. Glad to hear that you like the idea!
One of the really nice parts of building this out with Fastmail is that you can create Masked Emails for your own domain. So, if you ever decide that Fastmail isn’t right for you, then you still receive all of those emails when you set up a wildcard alias with your new email provider.
Similarly, if you ever decide that 1Password isn’t right for you, that doesn’t stop you from receiving your emails. And the email addresses should still be part of your 1Password export.
1Password is the world’s most-loved password manager.
I’m the tech lead on the Administrator Tools team. We build products, feature sets, and tools for our most powerful users. From building usable and scalable means of managing vaults, groups, and users, to making account recovery simple, and secure, we enable administrators to manage 1Password for their entire company.
You may be a fit for the role if you:
* Are excited to learn new things as you tackle new features and make existing ones better
* Have a critical eye for detail and you understand that perfection is the enemy of good
* Show a healthy balance of being able to work collaboratively while also taking responsibility for the tasks assigned to you
* Show a penchant for clean, idiomatic code that's easy to read and maintain
* Have a strong understanding of web server and RESTful API design
* Are proficient in writing well-optimized MySQL database queries
* Know secure coding practices
* A thorough grasp of how networking works
Bonus points if you have:
* Experience with Golang. It's certainly nice, but not required. Show us that you have a great understanding of any modern programming language, and we'll trust that you'll learn Go just fine.
* Experience with JavaScript, Typescript, and/or React.js. Sometimes you’ll need to dive into the frontend to understand how a feature works.
(Not a “grrr, smartphones” post, just a sad reality post)