mkenyon
(Not a “grrr, smartphones” post, just a sad reality post)
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.
(Sorry for the formatting, I’m on my phone.)
Our own Madeline Hanley wrote about that experience, if you'd like to see what it's like to work with JMAP: https://blog.1password.com/making-masked-email-with-jmap/
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.
We go one step further and generate a random email address for each new service you sign up with. It'll look something like "[email protected]".
You can create a new masked email anywhere you have the 1Password browser extension, including our brand new iOS Safari extension.
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.
[ Administrator Tools, Backend Engineer ] https://jobs.lever.co/1password/7166a990-80c2-4cdb-b619-0fab...
Feel free to contact me if you have questions or are curious: michael.abon @ 1password dotcom
Given how they've positioned Pocket and how Firefox's new tab page contains "Recommendations from Pocket", Mozilla seems to want you to enjoy browsing. They want you to enjoy using the Web and to enjoy it using Firefox. It's an interesting play and I'm excited to try it.
> For Fundzinger, we got on the phone with them and explained the situation in detail. They were more than understanding, and offered a deal that worked for us.
Most Flash games have a separate instruction box for what keys to press. Any way to add this?
The statement that the NSA issued, that no one is allowed to use the Seal without written consent, is strictly false.
Section 15.a states explicitly that you may not use the Seal "in a manner reasonably calculated to convey the impression that such use is approved, endorsed, or authorized by the National Security Agency."
This t-shirt does not give you the impression that such use is approved, endorsed, or authorized by the National Security Agency. Fair use, parody, satire, doesn't matter.
I linked the CNET article because the FBI did the same thing a few years back:
"While we appreciate your desire to revise the statute to reflect your expansive vision of it, the fact is that we must work with the actual language of the statute, not the aspirational version of Section 701 that you forwarded to us," Mike Godwin, general counsel for Wikimedia Foundation, the nonprofit company that runs Wikipedia, wrote the FBI in response.
I didn't mean to insult your intelligence regarding Tux. I just know that I would rather people not assume that I know things, especially when responding on the Internet.
Sec. 15. (a) No person may, except with the written permission of the Director of the National Security Agency, knowingly use the words 'National Security Agency', the initials 'NSA', the seal of the National Security Agency, or any colorable imitation of such words, initials, or seal in connection with any merchandise, impersonation, solicitation, or commercial activity in a manner reasonably calculated to convey the impression that such use is approved, endorsed, or authorized by the National Security Agency.
It is that last bit that matters here.
[0]: https://www.gnu.org/software/bash/manual/bashref.html#Event-...
Right now, I'm torn between looking for work immediately and asking for a delayed start, or going on vacation now and looking for work when I get back.
All I know is that Mars Bar (the local bar) will be busy tonight.